Signs it is time to move
None of these is a disaster on its own. Together they cost hours every week and eventually turn into a real risk.
- The file exists in several copies and nobody is sure which one is authoritative
- One person knows how it works, and their departure would be a problem
- The same data gets retyped in two or three different places
- There is no way to see who changed what, or when
- Access cannot be restricted: everyone sees everything
What we build instead
A web application you reach from a browser, built around the way you already work rather than the other way round. We start from your real screens and your awkward edge cases, not from a standard product you would have to work around.
- Your data in one place, with access by role and by team
- The processes you repeat every week, with follow-up steps triggered automatically
- A complete change history, useful both for compliance obligations and for tracking down a mistake
- Migration of your existing data, without losing years of history
- The exports and integrations you need: accounting, HR, invoicing
A concrete example
A group with several subsidiaries ran a central part of its daily operation inside a desktop database that only one person truly understood. We replaced it with a web application their team now uses every day: people and resources tracked in one place, weekly processes properly tooled, roles and full traceability to satisfy their compliance obligations, and years of history migrated without losing a single record.
The client name is covered by a confidentiality agreement. We are happy to walk through the project on a call, with the code in front of us.
Scope and budget
Scoping comes before the quote: we list the screens, the roles and the integrations, and then you get a fixed amount. Development runs in iterations, with a weekly demo on a test address.
At handover the code and the accounts are in your name. You can bring maintenance in-house or keep us on a monthly retainer for changes.
Questions fréquentes
Can you get the data out of our current file?
Yes, and it is almost always the first step. We take the contents of your workbooks or your existing database, history included, cleaning up the duplicates and inconsistencies these files accumulate along the way.
Why not just buy off-the-shelf software?
When a standard product covers your need, we will say so, because it is cheaper. Custom is worth it when the way you work is your advantage, or when no product handles your particular cases without permanent workarounds.
How do you avoid disrupting the team during the switch?
We usually ship the most painful part first and run it alongside the old file, so the benefit arrives before the project ends and nobody is forced to switch everything at once. The old system stays available until the new one has earned the team’s trust.
What if we want to change supplier later?
You leave with everything: code repository, hosting, database and documentation, all in your name. We deliberately use widespread, well-documented technology so another developer can pick the work up.
Let's build something.
Five quick questions. We come back to you with a scoping proposal.
What do you need built?
Pick the closest match. We will sort out the detail together.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.