Custom platforms and applications
For when your process does not fit any software on the market, and you have spent three years inside a spreadsheet only one person knows how to use.
- Timeline
- Set by the estimate from the definition sprint
- Price
- Ask for a quote
01
Who it is for
- Companies with a repetitive internal process living in a spreadsheet, on paper, or in someone’s head
- Companies paying a subscription for software that does 20% of what they need
- Companies that want to give their own clients an account, a portal or an app
02
How we start: the definition sprint
We do not quote for something that is not defined. Nobody can, and anyone who does corrects it later through “additional work”.
We start with a definition sprint of 5–8 working days, paid separately. At the end you receive, as a separate deliverable:
- A functional specification — what the application does, screen by screen
- Wireframes for the main flows
- The technical architecture and what integrates with what
- A release plan, in stages
- A firm estimate, within ±15%
The document is yours. You can take it to anyone. Almost nobody does — but the fact that you can is what makes the offer credible.
03
How we continue
The price is derived from the estimate, not from inspiration. We invoice in stages, every two weeks, with something working delivered each time. Never “everything at the end” — that is not fair to you and it is not fair to us.
Questions
Why am I paying for an analysis?
Because it is real work: several days of discussion, architectural decisions and documentation. A free analysis is an analysis done superficially, so it does not hurt when you walk away. We would rather do it properly and have you pay for it.
What does it cost in the end?
It depends on the estimate, and that is exactly why the sprint exists: it turns an idea into a list of features, with a firm figure for the whole project. You learn the cost of the sprint in the first conversation.
What if I change my mind along the way?
It always happens, and that is fine. Scope changes are estimated separately and you approve them before we build them. What we do not do is slip them into the final invoice.
Who owns the code?
You do, entirely, on final payment. No licensing, no dependency on us. If tomorrow you want to work with someone else, they can take it over.
Describe the process you want to digitise. We will set up a definition sprint.
Start a conversation