Enterprise Architecture.

Bring us in when integration costs exceed feature costs, when no single person can draw your current state on a whiteboard, when M&A or core-system replacement is on the table, or when regulators (BoG, CBN, NCA) require evidence of architectural governance. If you have under 100 engineers and a clean monolith, you probably need senior staff engineers, not an EA function.

We use TOGAF ADM as the engagement scaffold and ArchiMate for modelling because procurement and audit teams recognize them. For banking and insurance clients we layer BIAN service domains over TOGAF capability models so technology investments map cleanly to business capabilities. We use the frameworks as tools, not as religion - artifacts that no one reads after the engagement are a waste of your money.

We use lightweight Architecture Decision Records (ADRs) checked into Git, paired with C4 diagrams at context, container and component levels. Every significant decision captures the alternatives considered, the tradeoff and the reversal cost. This is far more useful 18 months later than a 200-page Word document, and it keeps the architecture discoverable as teams change.

Yes. We score vendor exposure on data portability, API openness, exit cost, contractual notice periods and concentration risk. For African banks and telcos, we pay particular attention to core-system contracts (Temenos, Flexcube, Oracle FSS, Huawei BSS) where exit timelines run to years. The deliverable is a quantified lock-in heatmap and a sequenced de-risking roadmap, not a binary judgment.

We tie every initiative to a measurable business capability and a board-level OKR. Wardley Mapping helps surface which capabilities are commodity (outsource), which are evolving (buy and customize) and which are genesis (build). The output is a sequenced, funded portfolio that the CFO can defend and the CTO can deliver, not an architectural ideal disconnected from budget cycles.

A foundational engagement runs 8 to 14 weeks and delivers current-state and target-state architectures, a capability heatmap, an integration reference architecture, a sequenced roadmap and a governance operating model. Ongoing retainers add quarterly roadmap reviews and decision-forum chairing. We don't do 12-month strategy projects - if it takes that long to write down, no one will execute it.

If your real problem is delivery velocity, you need DevOps and engineering leadership, not an architect. If it's a single failing system, you need a focused modernization team. EA pays back when complexity, integration and portfolio choices are the binding constraints - not when one team is just slow.