We build the tool your team is missing.
Custom business software is only useful if your team opens it every morning without thinking about it. That is the only test we are interested in.
What we build
Websites and web applications
Public site, customer portal, back office, internal tool. We look after performance and search visibility too, because a slow site loses customers before they have read a word.
Business software
The tool that replaces the shared spreadsheet, the chasing emails and the double data entry. It follows your rules, not those of a vendor selling the same product to everyone.
Automation and artificial intelligence
Scripts, integrations between the tools you already have, sometimes a language model. We will also tell you when AI adds nothing to your problem, which happens often.
Inherited systems
A tool built by a supplier who stopped answering, software nobody dares touch: we take the code on, steady it, then build on it.
How a project starts
- 01
A first conversation
An hour on the phone or at your offices, to understand what you do and where you are stuck. Free, and with no strings attached.
- 02
A written proposal
Scope, timeline, firm price. Plus the list of what we have deliberately left out of the first version: projects fail when nobody dares cut the scope.
- 03
Audit
The real state of the code, the infrastructure and the data. What is about to break, what is expensive to maintain, what can stay as it is. You get a report you can actually read, an estimate for putting things right, and a costed comparison between keeping and rebuilding.
- 04
Regular releases
You test something usable very early, then every two weeks. Whatever nobody uses gets dropped along the way.
What you take away
At the end of a project, everything sits with you. It is not a paid extra.
The source code
In your repository, in your name, with the full history.
The documentation
Installation, day-to-day operation, and the technical decisions with the reasoning behind them.
Control of the accounts
We can administer the technical accounts while we are working together. Whenever you ask, we sign over full control, with admin rights and the means to recover them.
A proper handover
If you bring the work in-house, we train whoever picks it up.
Tell us what brings you here.
A specific project, an idea that is still vague, or something you already run and want an outside opinion on. The first conversation commits you to nothing, and you will be talking to one of the two founders.
We reply within 24 working hours