Internal apps: the right screen for the work you actually do
The screen your team needs, built in days
Your team stops working in a spreadsheet sent round by email
Automation handles the repetitive steps. There is always one step where a person must decide — and that step needs a screen.
What you get
Exceptions have somewhere to land
Whatever does not pass automatically appears in a work queue, not an email lost among others.
Each person sees only their part
Rights by role, instead of one file everybody can open and anybody can break.
The data stays valid
Fields validate on entry. No more three date formats in the same column.
It works on a phone
People in the warehouse or on site do not have a laptop open. The screen is built for where they are.
How it works
1. What the person decides
We start from the decision that stays human and build strictly what it takes to make it quickly.
2. The screen
A plain interface over real data, not a configuration panel that needs training.
- Next.js
3. The connection
The screen reads and writes the data layer, so what it shows is what the rest of the system knows.
- PostgreSQL
4. The trail
Every action is recorded with who and when. An approval with no trail is not an approval.
- PostgreSQL
Where it works well
- Work queues for an automation's exceptions
- Validated entry forms for small teams
- Approval screens with a history of decisions
- Replacing a shared spreadsheet that has become critical
Where it does not
- We do not build products for your customers — internal tools only
- Where existing software already does the job, a new screen is wasted cost
- Applications with hundreds of screens are a software project, not an internal tool
What we use
- Next.js
- PostgreSQL
Frequently asked questions
- Why not just use Airtable or Notion?
- For plenty of cases you genuinely should — and we will say so. They run out at fine-grained rights, strict validation and volume.
- Who owns the app?
- You do, with all the code. No monthly licence for your own internal tool and no components you cannot inspect.
- How long does it take?
- A simple screen, a few days. A tool with several roles and approvals, two to three weeks.
- Can we change things ourselves afterwards?
- Wording, fields and simple rules, yes — the enablement service covers that. Structural changes stay with us or your own developer.
- Does it need training?
- If it does, we built it wrong. The aim is that somebody manages without explanation, the first time they use it.