How we work

Survey, build, operate, and own the outcome.

Four commitments shape every engagement: we diagnose before we prescribe, we build compliant by design, we hold to international engineering standards, and we own the result.

Diagnose before we prescribe

We understand the problem better than anyone in the room, then build the smallest thing that proves value, no big-bang projects, no decks that gather dust.

Compliant by design

After the data-protection fines that reshaped this market, “compliant” can’t be an afterthought. We build with NDPA, DPIAs, encryption, and in-country hosting from the first line, and document it for your risk, legal, and data-protection teams. For government records the residency rule is stricter still: the data stays in Nigeria, and classification fails closed.

International standards

Code review, automated testing, CI/CD, security, and documentation are how software survives production. You get engineering you could hand to any global firm, at a cost that makes sense here.

We own the outcome

We price and plan around your result, fraud reduced, onboarding shortened, hours freed, not the hours we work. If it isn’t working, it isn’t done.

The method

Maple Foundry: every engagement runs through it.

A method, not a product. Stage 0 applies to government records work and is the stage most vendors skip.

00

Records survey

Inventory the estate: what exists, in what medium, in whose custody, at what quality and volume. Extraction tested on a real sample. Government engagements start here, and we will not quote a build without it, because extraction is where these projects die.

01

Discovery

Understand the problem; define the outcome and the success metric.

02

Scope (SOW)

Deliverables, exclusions, milestones, acceptance criteria, agreed up front.

03

Data foundation

Access, quality, pipelines, in-country hosting, DPIA.

04

Build

Iterative, demoable increments; security and monitoring from day one.

05

QA & evaluation

Testing, model evaluation, failure-mode analysis, UAT.

06

Handover & launch

Documentation, training, go-live, audit trail. For a ministry the acceptance artifact is the certificate of completion, and the handover includes the exit package: an export in open formats, the source, and a runbook.

07

Operate

Monitoring, retraining, support, continuous improvement.

Contact

Let's talk about what you are building.

Twenty minutes. We will tell you what we would do, and say so plainly if we are not the right firm for it.

Arrange a meeting →