How we work
Every build is one quote, paid in six stages. Nothing is due for a stage until the stage before it is delivered.
On this page Six payment stages, one quote · What counts as a minor change, and what is a new feature · After launch: three tiers, each including the one before · Managed hosting · Questions buyers ask
Built on our infrastructure. You see working software before committing to anything else.
The code runs on the accounts you own. The largest payment of the six.
Against the agreed scope, on your infrastructure.
Adjustments to screens and flows that already exist.
Architecture, operations and decisions your team can read.
Working sessions with the people who will own the product.
40%
Moving the product onto infrastructure you own is 40% of the quote, whether that happens at the start of the project or at the end. It is the moment most of the value changes hands, and the price reflects that.
You see working software after paying 10%. If it is not what you expected, you stop there with a scoping document and a proof of concept you can take anywhere.
The usual arrangement is half the fee up front and nothing to look at for two months. Here you fund one stage at a time, and a stage only starts once the one before it is delivered.
A fifth of every quote covers minor changes, and two support tiers include them. So the line matters. Here it is, in plain English.
Minor change · included
New feature · quoted separately
New features are quoted separately at our standard rates, with the same ladder. Most are small; the point is that both sides know before the work starts.
Three tiers — Support, Standard and Priority — priced monthly as a percentage of project value, subject to a monthly minimum. The first three months of Support come with every build.
| Bug fixes: we repair what breaks, without changing behaviourAfter launch: three tiers, each including the one before | Support | Standardeverything in Support | Priorityeverything in Standard |
|---|---|---|---|
| Bug fixes: we repair what breaks, without changing behaviour | ✓ | ✓ | ✓ |
| Minor changes within the original scope | – | ✓ | ✓ |
| We respond and begin work within | – | 7 days | 3 days |
| Monthly fee | 5% of project value minimum $1,000 per month |
15% of project value minimum $3,500 per month |
20% of project value minimum $5,000 per month |
Attaches to any tier, or stands alone. We run the platform end to end and put an uptime commitment behind it.
5% of project value · minimum $1,000 per month
AI and third-party API usage is billed at cost above an included allowance. The hosting agreement states the allowance.
99.5% monthly uptime
| If monthly uptime falls | Credit on that month's fee |
|---|---|
| below 99.5% | 20% |
| below 99% | 50% |
| below 97.5% | 100% |
Monitoring is continuous, with automated alerting and automated recovery for the failure modes we have seen before. Each hosting agreement lists what is covered. We do not promise more than we operate.
Most builds land between four and eight weeks from the day the scope is agreed. You see working software in the first week, not at the end. A prototype is one to two weeks; something with several integrations or two app stores runs longer, and the scoping document says so before you commit.
Anything that needs a new data model, a new integration or a new screen. Those are new features, quoted separately at our standard rates. Changes to screens and flows that already exist are minor changes and are covered.
You do. Code, data and infrastructure end up in accounts you own, and the handover includes the documentation to operate them. You are never locked into hosting with us.
No. Managed hosting is an add-on. Some take it because we then stand behind uptime; others run the stack themselves from day one, and the architecture is built for that.
The first three months of Support come with every build. After that you can stay on a monthly tier, move to your own team with the handover pack, or come back to us per piece of work.
Yes. We deliver as your subcontractor at a fixed price, you keep the client relationship and set your own price, and our name appears on nothing client-facing. Ask us for the subcontracting terms.
We build in English, French, Spanish and Arabic, with right-to-left interfaces as standard rather than as an afterthought. Our work runs in the Gulf, North Africa, Europe and North America, and we deploy in-country where data residency requires it.
Each stage is invoiced when it starts and work on it begins once it is funded. Non-payment pauses a stage rather than breaking the engagement. Currency and payment method are agreed in the scoping document.