01
“Every quote is a day rate and a guess.”
One fixed price for a written scope, with milestones and a start date. Running costs are listed separately. It is a number you can put in the budget, and it moves only if you change the scope.
Agreed before anyone writes code. A written list of what will be built, what will not, and one fixed price, with milestones and a start date. If we estimate badly, the overrun is ours, not yours.
Why a fixed price
Payment is 40% to start, 30% at the midpoint and 30% on delivery. Two revision rounds are included. If we estimate badly, the overrun is ours.
These terms are published on our pricing page, not revealed in a contract at the end. The code sits in your own code account from day one.
Written scope. One price. Your code.
1
Fixed price, agreed before any code
40/30/30
Payment at start, midpoint and delivery
2
Revision rounds included in every build
2018
Building and running production software since
What we hear
What you get
Features written as things a user or admin can do, plus the screens and steps. It also lists the systems it connects to, such as Stripe, PayPal or iyzico, your WooCommerce store or an accounting tool.
What this price leaves out on purpose. This part explains why two quotes differ, and most quotes skip it.
Copy, images, product data, account access, test cards and store developer accounts, each with who provides it and when.
One number split 40 / 30 / 30, a delivery date and two revision rounds. A new screen or rule is a scope change, priced first. Running costs for outside services are listed separately.
Who it is for
If the first version can be written down, we take the risk of a wrong estimate. If it cannot yet, a fixed price only moves the argument to the end.
A good fit
You know what needs building, or the audit or roadmap has decided it, and want a price you can commit to.
You need a fixed number for a budget, an investor or a board, and a written definition of done.
You want to compare our quote fairly against others, line by line.
Not a fit yet
A fixed price on a vague scope only moves the argument to the end.
Build one working part first, or start with Discovery
Developers by the hour, or a two-year programme with a steering committee.
A Run plan with monthly hours, or a larger firm
How a quote is made
Step 01
A Discovery call, a System review report or a roadmap step, or a scoping conversation if none exist.
Step 02
You correct anything we misunderstood here, where corrections cost nothing.
Step 03
One fixed price against the written scope, with milestones, running costs and a start date.
Step 04
Work starts on the first payment. The code lives in your own accounts from day one. Ownership of the work (the IP) passes to you as each payment is made.
FAQ
Tell us what needs building. We agree what is in, what is out and the price before work starts.
Step 1 of 2
Two quick steps: what is going on, then where to send our reply. An engineer reads it and tells you honestly if we are not the right fit.
Which of these is closest?
Two steps. We ask for an email on the next one.
An engineer reads it and usually answers the same working day. In the meantime, feel free to explore.
Cookies
Before you go — have a system that's stuck, or needs AI?
We build what's missing, add AI where it really helps, and keep it all running.