How we work
No hourly billing that quietly doubles, no scope change you did not approve, and nothing that stays locked to us.
Five steps: a free conversation about the problem, a fixed written quote for a fixed scope, a staged build where you see working software every week or two, a handover where you receive the source code and every account in your business name, and an optional support agreement you can end whenever you like.
The five steps
- We talk it through
- A conversation about the problem, not a sales pitch. If we are not the right people for the job we will say so and point you somewhere better. Free, and there is no obligation after it.
- You get a written quote
- A fixed price for a fixed scope, in plain English, with a delivery date. No hourly billing that quietly doubles. If the scope changes later, you approve the change and its cost before any work starts.
- We build it in stages
- You see working software every week or two, not a status report. That means you can course-correct early, while it is still cheap to change your mind.
- You take ownership
- At handover you receive the source code, the accounts, the domains and the documentation, all in your business name. Nothing stays locked to us. You could hire anyone else tomorrow and they could pick it up.
- We look after it
- An ongoing support agreement, or on-call as you need it. Your choice, and you can change or end it whenever you like.
Why fixed scope rather than hourly
Hourly billing puts our incentive and yours on opposite sides. A fixed price for a fixed scope puts them on the same side: if we work out a faster way to do it, that is our gain, and your number does not move.
Scope changes are expected. We price the change, you approve it in writing, then we build it. Nothing reaches your invoice that you have not agreed to first.
What handover actually includes
- The source code, in a repository under your account
- Every hosting, domain and third-party account registered to your business
- Environment and deployment documentation
- Whatever a new developer needs to run it locally on day one
- A walkthrough with your team, recorded if you want it
We keep no rights over it and no ability to switch it off. You could hire anyone else tomorrow and they could pick it up.
What we ask of you
- One person who can make decisions
- Access to the people who do the work the software is about
- Feedback on each stage while it is still cheap to change
Last reviewed · Site changelog