Partnership
Pick the commercial shape that suits the account. The delivery process underneath is the same either way.
A written scope, a fixed number and a fixed date. Best when your client has already signed a proposal and you simply need it built and handed over.
A reserved block of senior hours every month across all your accounts — builds, fixes, changes, whatever is on top. Unused hours roll once.
One named engineer inside your team, in your standups and your tooling, booked hourly or monthly. Scales up the week a pitch lands.
You sell our platform bases under your own brand and your own pricing. We stay invisible and carry delivery and support behind you.
Pricing is quoted per engagement after a scoping call — we would rather read your brief than publish a number that fits nobody.
How it runs
Same rhythm on a two-week microsite and a nine-month platform. You always know what lands next Friday.
You send the brief. We come back with a written scope, assumptions, a named lead developer and a delivery date — with no discovery invoice attached.
Data model, API surface and screen flows agreed before a line of production code. You get artefacts you can show your client as your own.
Weekly builds on a staging URL under your domain, daily written handover in your timezone, and a standing call if you want one.
Repos, credentials, documentation and a walkthrough. Then a support window, or a retainer if you want us on call.
The white label rules
Most partners test us on a fixed-price build first. That is exactly how we would do it too.