Process
How we work: a five-phase development process
Every project runs through five phases in order: scope, architecture, build, harden and handover. Each has a defined deliverable and a fixed price agreed before it starts. During the build you get a demo of working software every week, not a status report.
Why fixed price per phase instead of hourly
Billing hourly moves all estimation risk to the client and rewards the project running long. A single fixed total, on the other hand, forces the estimate to be padded against the unknown. The middle ground is fixing price phase by phase: the scope of the next one is known because the previous one just finished.
What you get in each phase
Every phase ends with something tangible, not with a status meeting.
- Scope: a written brief with what is in, what is out and what success means
- Architecture: technical plan, stack decisions with their trade-offs, and a fixed estimate
- Build: a weekly demo of working software in a real environment
- Harden: a report on tests, performance, security and behaviour under load
- Handover: deployment, documentation and a walkthrough with your team
What we need from your side
Projects stall for the same reason almost every time: nobody with authority to decide. We need one counterpart who can resolve business questions within 48 hours, and access to the systems we have to integrate with. Nothing else.
When something falls outside scope
It happens on nearly every project and is not a problem if handled early. We flag it in writing as soon as we spot it, with the impact on timeline and cost, and you decide whether it goes in now, in a later phase, or not at all. What we do not do is build it quietly and present it in the invoice.