Healthtech · API Platform · 0→1 · Pierflow

The connectivity layer for healthcare in Africa — building the API platform hospitals, payers, and patients can plug into.

Pierflow is an API-first, AI-native platform that connects hospitals, payers, suppliers, and patients into a single interoperable network across Nigeria and West Africa. I joined as API Product Manager — owning the API surface, the technical roadmap, and the partnership development that turns a platform into an ecosystem. In six months, I authored the Paper-to-Digital (P2D) Engine architecture capable of processing 6,000 FHIR-ready records per day, designed the HMS Integration API for partners like LinkHMS, defined the embedded insurance distribution model, and opened active conversations with 10+ institutional and technology partners at World Health Expo Lagos 2026.

Role

API Product Manager

Company

Pierflow · 2026–Present

Focus Areas

API Product · FHIR R4 Interoperability · AI/ML Pipelines · Ecosystem Partnerships

Outcome

6,000 records/day · 10+ active partnerships · Africa CDC accelerator applied

Step 01 — Context & Mandate

An API-first platform needs a product manager who can think in endpoints, schemas, and ecosystems.

Pierflow is positioned as the connectivity layer for healthcare in Africa — an interoperable network where hospitals, payers, suppliers, and patients can exchange data through a single, standardised API surface. Built in Lagos, designed for West Africa, modelled on the developer-platform DNA of companies like Stripe and Twilio.

The mandate when I joined was clear: every part of the product is an API. Every workflow has a developer-readable contract. Every partnership is a technical integration, not a slide deck. My job was to own that surface — the documentation, the schemas, the versioning, the developer experience — and translate it into commercial traction with the institutions that move African healthcare.

African healthcare is fragmented by design. Every hospital runs its own HMS. Every HMO uses its own claims schema. Every supplier has its own catalogue. Pierflow's thesis is that the network effect comes from standardising the connectivity, not the systems.

Core stack: FHIR R4, REST APIs, OAuth 2.0, multimodal LLMs (Claude and GPT-4o), OCR fallback chains, OpenCV-based image enhancement, NDPR-compliant data handling. The platform speaks the international standards (FHIR, ICD-10, LOINC, ATC) but is tuned to the realities of how data actually moves in Nigerian hospitals — paper, scans, WhatsApp, fragmented spreadsheets, and inconsistent identifiers.