01
Roles
Each person sees the work that belongs to them. Permissions follow the job, so a screen is not a shared login and a private folder.
02 · SERVICE · GERMANY
Custom web applications
Software shaped around the way your team already works.
THE WORK
How this service is actually done
Off-the-shelf tools ask a team to change its process. We start from the other side: who does what today, where a spreadsheet has become the real system, and which exceptions a template keeps dropping. The first version is limited to that, not to a catalogue of features.
Roles decide what each person is allowed to see and change. Screens keep the next step visible on a phone and on a desk. The data lives in one place, with a history, instead of in files that only one person trusts.
A custom web application is justified when the cost of the workaround is higher than the cost of a focused build. It is not justified when a page, a form, and an email would do the job. We say so before the work starts.
INSIDE THIS SERVICE
What this covers
02
Screens
The next step is visible, on a phone and on a desk. A screen earns its place by removing a workaround, not by resembling a dashboard.
03
Data
Records stay in one place, with a history, instead of a spreadsheet that only one person can edit. The campaign and the team read the same source.
THE BOUNDARY
Where it fits
A FIT
This fits teams whose offer or operations have outgrown a template: too many roles, too many exceptions, or a spreadsheet everyone is afraid to edit. The campaign can already be running. The application is what the campaign needs behind it.
A LIMIT
We do not rebuild a whole company in version one, and we do not replace tools that already work. The scope stays on the steps, the roles, and the records the brief names.
THE FIRST VERSION
From the first call
Three marks for this service. The page, or the product, goes into real use before the scope grows.
-
01
Map
Who does the work today, and where time or trust is lost.
-
02
Shape
The smallest set of screens and records that removes that loss.
-
03
Live
The first real use, then the corrections the first weeks reveal.
ON THIS SERVICE
Questions teams ask
When is a custom web application the right service?
When a template or a spreadsheet can no longer hold the roles, the exceptions, or the records. If a page and a form are enough, we say that instead.
Do we have to throw out our current tools?
No. Most builds keep the tools that already work and replace the gap: the copy-paste, the missing screen, or the report nobody trusts.
What does the first version include?
The steps the brief named, the roles that touch them, and the data those steps need. Later work waits until that version is in real use.
The rest of the work
One brief can use more than one service. These are the others, in the same order.
Digital marketing
Search, content, paid, and the follow-up that turns attention into a conversation.
AI automation
Chat, follow-ups, reports, and sorting handled in the background.
Interface design
Clear screens, designed for a phone first and a desk second.
APIs and integrations
Connect the tools you already pay for, instead of replacing them.