Skip to content
Kalinko Labs
Back to Blog
· 3 min read

Building Digital Infrastructure in West Africa

Lessons from designing identity, payment, and education systems for Guinea — where connectivity is low and stakes are high.

govtech infrastructure west-africa

The Starting Point

Most conversations about digital infrastructure in West Africa start with what’s missing. Unreliable power. Low internet penetration. Limited data center capacity. These are real constraints, but they’re not the whole story.

What’s often overlooked is the pace of change. Guinea went from near-zero mobile money adoption to millions of transactions per month in under a decade. The infrastructure didn’t wait for perfect conditions — it adapted to the ones that existed.

A busy tech workspace representing the energy behind West Africa's digital transformation
Fig 1. The gap between infrastructure ambition and ground reality is where the interesting engineering happens.

Three Systems, One Foundation

Over the past year, I’ve been researching three interconnected projects for Guinea’s digital public services:

  1. A unified digital identity platform — one verified identity across all government services
  2. A payment gateway — interoperable mobile money and bank transfers for government transactions
  3. A headless LMS — education infrastructure that works offline-first

Each solves a distinct problem, but they share a common dependency: trust infrastructure.

Data flow diagram showing how identity, payment, and education systems connect through shared APIs
The three systems share authentication, consent management, and audit logging — building once instead of three times.

Designing for Constraints

The standard playbook for building government digital services assumes reliable connectivity, centralized data centers, and citizens with smartphones. None of those assumptions hold uniformly in Guinea.

Internet penetration outside Conakry hovers around 25%. Power outages are daily occurrences. Many citizens interact with digital services through USSD menus on feature phones, not apps on smartphones.

This changes everything about how you design systems.

A feature phone displaying a USSD menu — the primary digital interface for millions
Solar panels on a rural building — alternative power infrastructure
A team collaborating at a whiteboard — designing systems that work offline-first
Left to right: USSD as primary interface, solar-powered infrastructure, and the design sessions that bridge the gap.

Offline-First Is Not Optional

Every system I’m designing treats connectivity as a luxury, not a given. The identity platform caches encrypted verification data on agent devices. The payment gateway queues transactions for batch settlement. The LMS stores course materials locally and syncs when connectivity returns.

This isn’t a workaround — it’s the architecture. Systems that degrade gracefully in low-connectivity environments aren’t just more resilient; they’re more equitable.

What I’ve Learned So Far

A short talk on the design principles behind offline-first government services.

Three lessons that keep resurfacing:

Start with the hardest user, not the easiest. If your system works for a farmer in Kankan with a feature phone and intermittent power, it will work for everyone. The reverse is not true.

Interoperability is a political problem, not a technical one. APIs are easy. Getting three ministries to agree on a shared data schema is the actual challenge.

Build for the next decade, not the next quarter. Guinea’s digital landscape will look radically different in ten years. The systems we build now need to be flexible enough to evolve without being rebuilt.

Code on a laptop screen — the technical layer that connects everything
A team meeting around a table — the human layer that makes it work
Digital infrastructure is equal parts code and coordination.

What’s Next

I’m moving from research to architecture documentation. The next phase is producing detailed technical specs for each system and identifying potential pilot partners — government agencies, mobile money operators, and education NGOs willing to test early implementations.

If you’re working on similar challenges in West Africa, or if you’ve built government digital services in constrained environments elsewhere, I’d like to compare notes: laminekalinko2@gmail.com.