Fifth Engineering

About

Built where it runs.

Fifth Engineering is a forward-deployed engineering firm in Lagos. Our engineers join banks, investment firms and development-finance institutions to build the systems their operations run on.

Start a conversation

Five questions about Fifth

  • What is a forward-deployed engineer?

    An engineer who works inside your organisation instead of a vendor’s office. They sit with the people who do the work, find where it breaks, and build the fix in your systems, with your data.

  • Why the name Fifth?

    A team with four engineers does not need a fifth opinion. It needs a fifth engineer: one more person writing code alongside them, who answers for the result.

  • Why do we hand over?

    We build systems your people can run without us. Your team learns as we build and owns the code, the data and the documentation. Whether we stay on afterwards is your choice.

  • Why Lagos?

    The institutions we build for are here, from Broad Street to Victoria Island, and so are their problems: reconciliations across naira and dollar accounts, returns to the CBN and SEC Nigeria, customers who bank by USSD as well as by app. We build for those conditions because we work in them.

  • What will we not do?

    We will not sell you a platform licence or leave you with a report. If software you can buy off the shelf will solve the problem, we will tell you, and help you choose it.

Why we started

Founders’ letter.

To the teams we will join,

Somewhere in your institution, a spreadsheet is holding part of the operation together. Someone rebuilds a regulatory return from it every month. Someone reconciles naira and dollar accounts in it by hand. Everyone knows it is fragile, and it is still there.

You have probably been offered ways to fix it: another platform licence, a report from advisers, and now an AI pilot. Most stop short of the place where the work is done. The licence sits beside the spreadsheet, the report goes on a shelf, and the pilot never reaches production.

The people who understand a problem are rarely the people asked to fix it. We started Fifth Engineering to put them in the same room. Our engineers join your team, sit with the people who do the work, and build the system where it will run: on your data, inside your controls, in production.

If you are choosing someone to build for you, these are the questions we would ask of any firm, including us:

  • Who builds the fix: the person who found the problem, or someone handed a brief?
  • What is measured: what reaches production, or the hours billed?
  • Who owns the result: can your own team run the code, the data and the documentation without the firm?

Ask us the same questions, and compare our answers with anyone else’s.

We are a new firm, and we would rather be judged on our first month inside your team than on anything written here. That is why every engagement starts with four weeks of fixed-scope discovery.

We work from Broad Street, in the Marina, and we are building Fifth for Nigeria first, then the rest of Africa. If something in your operation costs more than it should, write to us. One of us will read it.

Talk soon,Max and Okezie

  • Ayobami J. Opeyemi

    Ayobami J. Opeyemi

    Co-founder and Principal Forward-Deployed Engineer

    Ayobami, known as Max, makes it run. He leads engineering at Fifth and built the backbone of how it works: an engineering system in which every change passes automated security, architecture and design review before it ships. Having built for regulated financial institutions, he puts security, audit trails and reliability into the first version, not the last. His belief is simple: a system is finished only when the client’s own team can run it without him.

    Previously: Founder and Principal Architect, Blackroot Labs

    LinkedIn
  • Okezie Ofoegbu

    Okezie Ofoegbu

    Co-founder and Forward-Deployed Executive

    Okezie opens the doors. He leads Fifth’s work with the institutions it serves, drawing on more than twenty years in African markets, from upstream operations at ExxonMobil to private equity at Emerging Capital Partners, and transactions worth more than US$2.3 billion across Africa.

    Previously: ExxonMobil, Emerging Capital Partners · MBA, Wharton

    LinkedIn

Work with us

Ways to work with us.

  • Discovery

    Four weeks inside your team with a fixed scope. We map how the work runs, measure what it costs you, and agree the problem worth fixing first.

    Weeks 1–4 · Fixed scope

  • Embedded build

    Engineers join your people to build the system, test it on real work, and take it into production.

    Weeks 3–10

  • Product build

    For an organisation with an idea and no technology team: we design, build and launch the product, then run it for you or hand it to the team you build.

    Scoped per product

  • Run and improve

    After handover, we can stay on a monthly retainer to run the system, watch it, and keep improving it.

    Monthly retainer · Optional

Sunset haze over the hills of Tsavo, Kenya, with a lone tree on the plain.

How we work

Your path to a working system.

Every engagement follows the same path, whatever the sector. It starts inside your organisation and is measured by what reaches production.

The timings below are typical. Discovery sets the real plan, and you see it before you commit to more.

  1. 00

    First conversation

    Before we start

    Thirty minutes on how the work runs today, what it costs you, and what fixing it would take.

  2. 01

    Discovery

    Weeks 1–4

    Our engineers join your team with a fixed scope. They sit with the people who do the work, map where it breaks, and agree what to fix first.

  3. 02

    Prototype

    Weeks 3–6

    A working version on your own data, which the people who will use it test on their real work.

  4. 03

    Deploy

    Weeks 6–10

    The system goes into production inside your security and change controls, and we stay close through its first weeks of real use.

  5. 04

    Productise

    Days 60–90

    We harden what works: tests, access controls, documentation, and the reports your auditors and regulators ask for.

  6. 05

    Handover

    Days 90–120

    Your team takes ownership of the code, the data and the documentation. If you want, we stay on to run and improve it.

Our commitments

Built to be owned.By your team.

What each part of your organisation can expect from us, from the first week to handover.

  • A fixed first month

    Discovery has a fixed scope, so you know what the first month covers before you commit to more.

  • Progress you can see

    We report progress by what is running in production and what it has changed for your operation.

  • You own what we build

    The code, the data and the documentation are yours. We keep only the know-how we brought.