Tools that take work off people
Customer portals, operations dashboards and internal systems. We usually start with one process that currently lives in a spreadsheet and eats a dozen hours a week.
Symptoms worth a conversation
If you recognise even two of these, the saving is usually measurable in headcount.
- 01
A critical process lives in a spreadsheet
One file that one person understands, opened by five at once, with change history encoded in file names. It works right up until that person takes leave.
- 02
Data gets retyped between systems
Someone moves records from email into the ERP, from the ERP into a spreadsheet, from the spreadsheet into a deck. Every retype is a cost and a place for errors.
- 03
Customers ask for status by email
Instead of checking a portal they call and write, and support spends half a day answering questions a system could answer on its own.
What we build
Scope depends on the process, but these parts recur in every project.
Customer portals
Order status, documents, invoices, service tickets and history in one place. Fewer calls to support, more self-service.
Operations dashboards
Views tailored to a specific role rather than one screen for everyone. Routine actions take a few clicks and do not need a two-day training session.
Integrations and automation
Connections to ERP, CRM, warehouse, mail and partner systems. Queues, retries and error handling so an outage on the other side does not take the process down.
Roles, permissions and audit
Who sees what and who changed what. A full event log — needed for audits, disputes and working out what actually happened.
Reports and exports
The summaries someone assembles by hand once a month, generated automatically and emailed or exposed over an API.
Development in sprints
After the first release we keep working in two-week cycles against a clear backlog. You can raise or lower the pace as needs change.
How we get to production
- 01
Week 1 — process map
We sit down with the people who run the process today. We map how it actually works, not how the procedure describes it. This is usually where the biggest savings are found.
- 02
Weeks 2–3 — prototype
A clickable prototype of the key screens goes through testing with future users. Changes at this stage are ten times cheaper than after delivery.
- 03
Weeks 3–10 — build
Two-week sprints, a demo at the end of each, staging access throughout. We finish one process end to end before adding a second.
- 04
After launch — development
Further processes, integrations and improvements raised by users. The backlog is shared and visible to both sides.
What it costs
from €13,000
A first release covering one process usually lands between €13,000 and €27,000. Ongoing development is billed per sprint from €2,700.
- Workshop and process map
- Clickable prototype with user testing
- Build including roles, permissions and audit trail
- Integrations with the systems you already run
- Technical documentation and team training
Common questions
Yes, and that is usually how we start. One process delivered end to end produces a measurable saving and a solid basis for deciding on the next. Large systems built all at once tend to end in an overrun budget.
We either migrate it or integrate in real time, depending on whether the old system is going away or staying. Both paths are costed separately during the process mapping stage.
In the EU by default — Vercel with a database in Frankfurt, or AWS in eu-central-1. If you require hosting on your own infrastructure, we deliver the application as a container with deployment instructions.
Yes, provided the code is available and can be run locally. We start with a review and a technical debt report estimating what is worth fixing and what should be rewritten.
It starts with an audit
Tell us in two sentences what you want to achieve. We reply within one business day.