How we work
Most software projects go wrong for reasons that have nothing to do with code. The usual causes are unclear scope, slow decisions, nobody clearly responsible, and surprises at the end.
Our process is designed to remove all four.
The process
- 1
Free 30-minute call
You describe the problem and we ask a lot of questions. You leave with a rough scope, cost and timeline, even if you never hire us. The call is with the senior architect who would lead the work, not a salesperson.
- 2
Discovery, 3 to 10 days
We sit with the people who do the work and document how it happens today, what goes wrong and what "done" looks like. You receive a written scope, a data model, a screen list and a clear list of what version one will leave out. For large or complex programmes, discovery runs as its own short engagement.
- 3
Proposal within 48 hours of discovery
Scope, price, timeline, payment schedule, assumptions and exclusions, usually in two or three pages.
- 4
The two-week pilot
We build the most important part of the product and hand it over working, so the decision to proceed is based on real software. You keep everything built during the pilot.
- 5
Build in two-week cycles
Every second Friday you get a working link, a short written update and the plan for the next two weeks. There is a shared board you can open at any time, and a 30-minute call each week, or more often if you prefer.
- 6
Testing and launch
Automated tests on the important flows, manual testing, a security review and load testing where it matters. Then we deploy to your cloud, migrate your data and train your team.
- 7
After launch
Bug fixes are free for the first 30 days. After that you choose a full handover with documentation or a monthly support plan.
Engagement models
Fixed price
Best when the scope is clear. You know the price before we start, and we carry the risk if our estimate is wrong. Any changes are quoted separately and need your approval first.
Time and materials
Best when the scope will change as you go, which is true of most product work. You pay for the hours worked, up to a monthly cap you set, with a weekly log of where the time went.
Dedicated team
Best when you need capacity for several months rather than a defined project. A monthly rate per person, with one month's notice.
Support retainer
For live systems that need a team accountable for keeping them running.
Payment terms
- Fixed price: payments are tied to milestones you have accepted.
- Monthly models: invoiced at the start of each month on 7-day terms.
- We invoice in USD, GBP, EUR or INR.
- Every invoice includes a written record of what was delivered.
What we ask from you
Projects fail on the client side as often as on the vendor side. These four things make the biggest difference.
- One decision maker who can approve things without a committee.
- Two hours a week for a call and for reviewing what we have built.
- Feedback within three days. A demo left unreviewed for two weeks slows everything down.
- Access to the people who actually do the work, as well as their managers.
With those in place, we can move quickly.
Related
Services
Software services, end to end
Custom Software Development
Software built around how your business actually works
Dedicated Teams
Add senior developers to your team by the month
Not sure yet what you need?
Book a 30-minute call with a senior architect and tell us about the problem. We will explain what it would take to build, roughly what it would cost and whether custom software is the right answer at all.