You will know where your project stands. Every week.
Software projects rarely fail loudly. They fail quietly: a scope nobody wrote down, a month of silence, then a demo that is not what you had in your head and a bill that moved. Everything below exists to make both of those impossible.
The short version
Scope call
Forty-five minutes, free, no obligation. We walk through what your team does today and where it breaks. You leave with a straight opinion whether or not you hire us.
What you get from this step
We walk through what your team does today and where it breaks. You leave with a straight opinion whether or not you hire us.
Written proposal
Scope, price and dates on paper before anything is signed. A document you could hand to any other developer and get a comparable quote. If we think the project is a bad idea, that goes on paper too.
What you get from this step
A document you could hand to any other developer and get a comparable quote. If we think the project is a bad idea, that goes on paper too.
Weekly builds
A link you can open and click, from week one. Feedback goes into the next week's build, so surprises stay small and cheap. If something is going to be late, you hear it that week.
What you get from this step
Feedback goes into the next week's build, so surprises stay small and cheap. If something is going to be late, you hear it that week.
Launch & handover
Code, accounts and documentation, plus a recorded walkthrough. If you replaced us the following week, nothing would stop working. Support is priced separately, so you are never locked in by default.
What you get from this step
If you replaced us the following week, nothing would stop working. Support is priced separately, so you are never locked in by default.
Three things we need from you.
Projects slip for client reasons as often as builder reasons. These are the three that matter, and we would rather say them out loud at the start.
One decision-maker
One person who can say yes. Design by committee is the most reliable way to double a timeline.
An hour a week
To look at the build and tell us what is wrong with it. That hour is worth more than any brief.
The real process
Let us see how the work actually happens, including the messy workarounds. Those are usually the requirements.
Because they will.
Halfway through, you will think of something better. That is normal and usually right. The problem is never the change itself, it is the change that quietly appears on the final invoice.
How we handle it
You ask. We come back within a day with what it costs and what it does to the dates. You say yes or no. Nothing is built and nothing is charged until you have said yes in writing.
What you can hold us to.
A process is only worth something if there is a consequence attached. These are ours.
Our commitment
If a milestone slips because of us, you hear about it the same week and the delay is not billed. You can stop the project at any weekly build, pay only for the weeks delivered, and keep everything built so far: code, accounts and documentation. Nothing we build is tied to us to keep running.
Start with the call.
Forty-five minutes, free, and you leave with a written summary and a straight opinion, whether or not anything comes of it.