Public Sector
Programs that get built — not just signed
We arrive with the technical architecture and the project finance structure already mapped. That is what unlocks decisions inside the public sector.
The B2G reality
Why public technology programs stall
Most public-sector technology decisions die in the gap between intent and budget. The architecture is approved, the supplier is selected — and then the program waits for the next fiscal cycle that never quite frees the resources required.
We close that gap by structuring project finance alongside the technical proposal, from day one. Our Dubai (FZE) entity lets us bring international financing structures to African public programs without forcing them into the constraints of a single annual budget line.
And because we are accountable for both the financing structure and the technical delivery, we can't survive a half-built program — our incentive is the same as the customer's.
Delivery model — B2G
Six steps, with financing built in
The same delivery model used for enterprise programs, plus a sixth step that is unique to the public sector: project finance structuring.
Discovery
Strategic and technical context — including the financing constraint, not just the technical one.
Design
Reference architecture and program roadmap, defensible inside cabinet, ministry and treasury.
Sourcing
Brand selection backed by exclusivity agreements and aggregated buying power.
Integration
Deployment, testing and cutover run by the same engineering team that designed the architecture.
Operation
Run, evolve and govern — with measurable SLAs and a clear handover path.
Project finance wrap
Financing structured alongside the technical proposal from day one. This step is what unlocks the others.
B2G only
Where this lands
Areas of application
Critical platform modernization
Tax, customs, social security and registry platforms that have to keep running while they are being modernised.
Smart cities
Urban sensing, mobility and citizen services delivered as integrated programs — not as disconnected pilots.
Digital health
Clinical interoperability, patient identity and operational platforms across networks of public hospitals.
Identity & e-Government
Civil identity programs and the digital services that depend on them, designed at country scale from the start.
How we engage
From the first conversation to a structured proposal
Entry points vary — a technical office, a ministry, a state-owned enterprise. The pattern is the same: an initial scoping conversation under NDA, a joint discovery to align the architecture with the financing constraint, and a structured proposal that ties the technical scope to a credible financial path.
Time from first conversation to a structured proposal depends on the program's complexity and the maturity of the financing requirement. We move quickly when the brief is clear, and we say so when it isn't.
All conversations are confidential. We don't publish names of public programs we work on.