Custom Applications
Software Shaped Around Your Work.
Most businesses run on a tool that nearly fits. The workarounds start small — a spreadsheet beside it, a shared inbox, a rule everyone knows but nobody wrote down — and a year later the workarounds are the actual system. Nobody chose that, it just accumulated. We build the thing that fits instead: your workflow, your data, your database.
Examples
What This Looks Like.
A CRM that holds the whole customer picture
Contacts, conversations, quotes, jobs and invoices in one place, shaped around how you actually sell. Instead of four tools and a spreadsheet that only one person really understands.
The internal tool
The one screen your team lives in all day. Usually it replaces something currently held together by a spreadsheet, a shared drive and a group chat.
The client portal
Your customers stop emailing to ask where things stand, because they can open it and see.
A system that replaces a stack
Our Coaching Platform replaced a pile of apps for a personal trainer: clients, plans, habits, weekly reflections, messaging. One login, five to seven hours a week back.
AI features inside something that exists
Extraction, drafting, and search across your own documents, built into the tool people already open rather than bolted on beside it.
The layer between two systems
Two pieces of software that should talk to each other and don't. We write what goes in between and keep it running.
A dashboard worth opening
One number, correct, on a Monday morning. Not twelve tiles of whatever happened to be easy to compute.
In Every Build
Every application ships with this.
Your database, your repository, your accounts. Exportable the day you ask.
Every data store in the EU, with server functions in Frankfurt.
Row-level security from the first table.
Roles and permissions enforced on the server, not hidden behind a menu.
A working version in front of you every week, not a demo at the end.
Documentation and a handover session, so the system outlives the project.
How We Work
Fixed Scope. Fixed Price.
The same shape every time. Nothing gets built before the scope is written down and the price is agreed, because that is the only way a fixed price is safe for both of us.
- 01
Discovery
1 week · freeWhat the product is, in one sentence. Who logs in, and what each of them may see. Those two answers decide the architecture, so they come before anything else.
- 02
Scope and price
Before we buildOne named product, not a category. Fixed price agreed in writing, no hourly billing behind it.
- 03
Prototype
Week 1Something you can click, running on real data, before the rest is committed. It is the cheapest moment to change your mind.
- 04
Build
4 weeks typicalA working version every week. You see it move rather than hearing that it is going well.
- 05
Live, and ours to keep running
OngoingHosting, patching, monitoring and backups. New scope is quoted like the first build was.
Questions
The Ones People Ask.
The same handful comes up in every first conversation. Here they are answered before you have to ask them.
What if we don't know exactly what we want yet?
Almost nobody does, and a fully specified brief is not what we ask for. What we need is the problem, the people who have it, and the one workflow that hurts most. Discovery turns that into a scope, and the prototype turns the scope into something you can react to.
What does it cost?
Most systems land between EUR 1,500 and 3,000. Fixed price, agreed before we write anything, with no hourly billing behind it. What moves the number: how many types of user exist, how much has to talk to systems you already run, and whether the data is sensitive enough to change the obligations. Discovery answers all three, and discovery is free.
How long does it take?
Something clickable in the first week, and most systems live about four weeks after that. Both dates are agreed before the build starts rather than estimated as we go.
Why not just buy something off the shelf?
Often you should, and we will say so. Standard software is cheaper, faster and someone else maintains it. Custom is the right call when the workflow is the thing that makes you money, when per-seat licensing has started to outweigh a build, or when what you need genuinely does not exist. If a well-structured Airtable and one automation would serve you better, that is the honest answer and it costs us the project.
Can it talk to the systems we already have?
Usually yes. Anything with an API, a database connection or a webhook can be connected, which covers most accounting, CRM and ERP software. Where a system has no way in, we find that out during discovery rather than halfway through the build.
Who keeps it running afterwards?
We do. Hosting, security patching, dependency updates, backups and monitoring are part of the partnership, along with small fixes. Building something new is quoted as a new fixed scope.