How we work
How we price a software project, and why the number does not move
We agree the work and a fixed price in writing before we start, and that number does not move unless you ask for something that was not in it. If you do, we price that change separately and you decide — rather than discovering it at the end as a larger invoice.
Why fixed scope, not hourly
Hourly billing puts the risk of a slow month entirely on the client, and it rewards the wrong things. If a problem takes us longer than expected because we misjudged it, that is our cost to carry, not yours.
The trade is that scope has to be defined properly up front, which is why we prototype first. A fixed price on a vague scope helps nobody.
What you get for the money
- A written plan: what we will build, and explicitly what we will not
- A working build every week, which you can open and use
- The repository, servers and accounts in your name from day one
- Documentation and a handover at the end, with support agreed in writing
What happens when you want a change
You will want changes — every project has them, and seeing working software weekly is what surfaces them. We price the change, you approve it or you do not, and the original number stands either way.
If something costs more than it is worth, or a ready-made tool would do the job, we will tell you. Losing that piece of work is cheaper for us than building something you regret paying for.