Engagements
Fixed scope, fixed price, quoted before anything starts. Start with a day if that is all you need.
Start here
small, fast, no committeeOne day, one thing, scoped and quoted in writing before it starts.
A report that eats four days a month. A form that has to work offline. Two systems that will not talk. Something broken nobody has had time to look at.
Tell me what's stuck$1,000 a day. One purchase order, one contract, one invoice — draw the days down over six months, a line of email at a time.
For organisations whose finance process costs more than the work does.
Projects
fixed scope, fixed priceA full programme MIS, an offline field system, or a reporting engine replacing a manual process across several countries.
Eight to twenty weeks, delivered in stages you sign off.
A programme that wants the whole picture — and one working pipeline — before committing to a build.
Four to six weeks. Systems assessment, one live data pipeline, one donor-facing dashboard, written recommendations.
One report pack, one migration, one integration, or one offline form set for a single programme.
Priced on the outcome, not the days. One to three weeks.
Ongoing
annual, invoiced monthlyInvoiced monthly against one annual purchase order.
Hosting, monitoring, support, iteration.
The savings-group ledger, licensed for a programme.
What every engagement includes
How buying works
Scoped to sit under your approval threshold. Tell us yours and we will quote to it.
You own what we build.
Source, data, documentation, and hosting you can take elsewhere. No licence to keep paying and no vendor who has to be involved to change something.
Questions procurement asks
What if we need to stop?
Projects stop at the end of any signed-off stage, and you keep what has been delivered to that point. Retainers run to the end of the term you bought.
Who owns the code?
You do, on delivery, in your own repository. Where a donor requires open source, we license it that way.
Where does our data sit?
In a region named in writing before contract, with sub-processors listed and notice before any change. [SUPPLY: region + sub-processor list]
What happens if you are unavailable?
Source and documentation sit in your repository from the first delivery, hosting is in your own accounts where you want it, and export is unconditional — so another developer can pick the work up without us. [SUPPLY: escrow or named backup engineer, if offered]
Do you have insurance?
[SUPPLY: professional indemnity cover and limit, or state plainly that none is held]
Can you invoice in EUR or GBP?
[SUPPLY: confirm which currencies the company can invoice and receive]
All prices in USD. Invoiced against a purchase order. We do not bill hourly.
Tell me what's stuck. I will send back a price and a scope in writing.
Tell me what's stuck