The operations platform, inside your bid.

What you get for the annex

A bid pack, built against your scope and delivered in your own template, so your proposal team can place it without rewriting it.

• A technical description of the platform and of the modules in scope, at annex length and in annex tone.
• A compliance position: where the data sits, how it is encrypted, backed up and exported, which languages the interface runs in, and what the field application needs in order to work without a network.
• A cost structure you can put straight into the financial model, and a firm envelope once the scope is fixed.
• The references you may cite, with the published pages that document them.
• A deployment schedule you can commit to in the bid, process by process, with the first one live in weeks.
• The contractual shape: a subcontract under your prime contract, or a licence direct to the awarding authority.

From a defined scope, in three working days. If your deadline is shorter than that, say so when you write: it usually still works.

What it costs in your model

Pricing has two components: an initial deployment and a recurring operating fee. There is no public price list: each engagement is quoted on its scope.

We publish no tranche and no rate card, because a district and a national concession are not the same order of magnitude and any range honest enough to cover both would tell you nothing. What we do commit to is the shape above, the drivers below, and a firm figure inside your deadline.

What the price does not depend on.

Not the number of users. Field teams are never charged per agent, so putting the application in every hand does not increase the bill.

In a PPP that matters more than anywhere else. These contracts are won on coverage, and coverage means hundreds of field agents. Equipping all of them changes the operation. It does not change the fee, so it does not change your financial model either.

What does move it

• The number of processes you digitise, and how far each one reaches.
• The integrations with the systems already in place.
• The number of sites and of maintained assets.
• Where the data is hosted, and by whom.

Hosting, data and the compliance matrix

On-premise or in-country. Encrypted, backed up and exportable at any time. No proprietary format. No lock-in. A simpler architecture also means fewer exposed components.

The interface runs in English, French, Portuguese, Spanish and Russian. The field application keeps working without a network and syncs when it finds one, which is what makes it usable outside the capital. The server side is deliberately small, which shortens the security questionnaire rather than lengthening it.

What happens when the programme funding stops

Every funder asks this, and so does the authority. It reads far better answered in the bid than discovered in year six.

Designed to stay affordable when the project funding ends, so the utility can keep running it on its own budget.

Your data is exported in an open format, and the training videos stay usable with no time limit: at the end of the contract, whatever the reason, the utility keeps the video files.

We will also write the boundary, in your words: what the utility keeps whatever happens, and what continues only while the operating fee is paid. Stating that line is worth more in an evaluation than claiming there is no line.

Who signs what

Two shapes work. A subcontract under your prime contract, where we deliver inside your programme and the client relationship stays yours. Or a licence direct to the awarding authority or the utility, with us named in your bid as the provider.

We have no preference between the two. We run under your programme, and the scope you bring us is yours.

What we need from you

• The scope you want covered: which processes, how many sites, and the asset count if you have it.
• The systems already in place that we have to sit alongside — billing, GIS, maintenance, stock, ERP.
• The annex template, the submission date, and the compliance matrix if the tender carries one.
• The languages the interface has to run in, and the ones the training content has to be in.
• Whether we may be named in your bid — and whether you may be named here.

References you may cite

Seven deployments are documented publicly. Water and sanitation first; two of them sit outside the sector and show the same platform under different constraints. Each page names the operator, what was deployed and over what period, so your proposal team can quote it without asking us first.

Tell us the tender

The scope, the deadline and the template. That is enough for us to start the pack.