Skip to content

Digital systems don't fail on launch day.They fail when everyone needs them at once.

Ohm Core builds, connects and runs the digital systems institutions depend on. Full delivery, architecture through handover, not advice from the sidelines.

For any organisation whose systems cannot afford a bad day.

Stephen Otieno Ouma. Every engagement is led personally by Steve Otieno, our founder. Meet Steve

Institutions lose money, trust and time in the same four ways.

Every one of them is predictable. Every one can be fixed before it becomes a headline.

Demand on a public service across one month, illustrativeDemand stays low through launch day, then climbs toward a deadline and breaks far above the capacity the system was planned for. Running costs rise steadily underneath.ABCDCapacity planned for an average dayRunning cost
Demand on a public service, one monthIllustrative

What we sell is simple: systems that keep working when everything peaks at once, delivered by engineers who have already done it at international scale.

A decade of delivery stands behind every engagement.

people served, no downtime
4.8M+people served, no downtimeM-TIBA national health platform, Kenya. 5,000+ clinics and hospitals, 20 insurers.
more usage in year one
180%more usage in year oneEquity Bank to PayPal payment service, Kenya. Bank customers moving money to and from PayPal.
faster system updates
87%faster system updatesReleases that took an hour of downtime now take 8 minutes, with no service interruption.
lower trade processing costs
30%lower trade processing costsKenya to UK digital trade corridor. Customs paperwork costs down 40%.

Results from systems our founder led or helped build in senior and lead roles. They are his track record, not Ohm Core client engagements.

We build the system, connect it, keep it running, and hand it over.

Eight services, in the order institutions usually need them. You describe the outcome. We deliver the working system.

Enterprise systems, built and delivered at scale

Registration and enrolment, claims and case handling, records and reporting, fleet and asset management. Built for national volume, and delivered across multiple countries and regulators.

  • Integration and interoperability

    Making your systems talk to each other, to banks and payment providers, and to other agencies. New systems connected to older ones, securely and automatically, with no re-typing.

  • Regulated environments

    Data standards, data residency and cross-border rules, treated as design inputs from day one rather than paperwork at the end. Learned working with regulators on two continents and on a trade corridor between two governments.

  • Cloud and platform engineering

    Foundations that make change cheap and safe. Kubernetes, GitOps and infrastructure as code, on AWS, on premises, or both.

  • Keeping services running

    Monitoring that spots trouble before the public does, disaster recovery that has actually been rehearsed, and ongoing support.

  • Systems assessment and reliability review

    An independent health check of what you already own: how it behaves on its worst day, what fails next, and what that would cost. Usually where a relationship starts.

  • Cost reduction

    Cutting what your technology costs to run, without adding new ways for it to fail.

  • Training and handover

    Your team learns to run what was built. No permanent dependency on any supplier, including Ohm Core.

The same discipline, delivered in health, payments, banking and trade.

Steve led or helped build each of these in senior and lead roles at the organisations that ran them. They are named so you can check them. References available on request.

M-TIBA, at CarePay

Healthcare, Kenya

Health cover for 4.8 million people

A national platform connecting members, 5,000+ clinics and hospitals and 20 insurers, usable from the simplest mobile phone. Steve's work covered the tools that register members and check claims.

  • 5,000+ members registered in under 10 minutes
  • Claims checks cut from days to minutes

Equity Bank and PayPal

Payments, Kenya

Bank customers connected to PayPal

Led the delivery that let Equity Bank customers in Kenya move money to and from their PayPal accounts.

  • Bank and PayPal connected in one service
  • Usage up 180% in year one

Software Group

Banking, Africa and South America

Banking beyond the branch

Managed rollouts that let banks serve customers through local agents: cash in and out, bill payments and small-business onboarding, on two continents.

  • About 30% more agent transactions completed

Kenya to UK digital trade corridor (TLIP), 2023 to present

Government and trade, Kenya and UK

Trade paperwork moved online between two governments

Technical lead on a platform that moves export documents for tea, flowers and coffee between exporters, freight companies and government agencies in both countries, including KRA, KenTrade and KEPHIS.

lower cost to process a shipment
30%lower cost to process a shipment
lower customs paperwork cost
40%lower customs paperwork cost
of UK border-check requirements covered in the pilot
80%of UK border-check requirements covered in the pilot
faster border control decisions
17%faster border control decisions
planned service interruptions in production
0planned service interruptions in production

Four steps that end in handover, not dependency.

  1. Step 1

    Assess

    We look at how your systems cope on their worst day: busiest periods, key dependencies, weak points. Then we rank what is most likely to fail next.

  2. Step 2

    Design

    Plans built on evidence from how your systems are really used, and sized for the busiest day of the year, not the average one.

  3. Step 3

    Build

    Every change is rehearsed and tested before it touches the live service, so improvements arrive without interruptions or surprises.

  4. Step 4

    Hand over

    Your team gets the manuals, the training, and the controls. You own the system and can run it with confidence. No black box, no lock-in.

How we think

  • Plan for things going wrong.

    Systems are designed to survive bad days, not just perform on good ones.

  • No single point of failure.

    No one person, machine or supplier whose absence stops the service.

  • Let machines do the routine work.

    Repetitive manual work is where errors and delays are born.

  • Measure everything.

    If you cannot see how a service is performing, you cannot trust it or improve it.

Every contract is led by an engineer who has been on call when it mattered.

Stephen Otieno Ouma, founder of Ohm Core

Stephen Otieno Ouma

Founder and Principal Consultant

Steve Otieno on LinkedIn(opens in a new tab)

A decade of delivery, by sector

Steve has spent ten years building and running the systems behind banks, insurers, health cover and government trade, in roles from hands-on engineer to engineering director.

His roles include engineering director at Ogilvy Africa (WPP), and senior roles at CarePay, the company behind M-TIBA, and at Software Group, an international banking technology firm.

  1. 2015 to 2019

    Business systems foundations

    Inventory systems for aviation, insurance comparison tools, and an international money-transfer service made four times faster.

  2. 2019 to 2023

    Multi-country delivery leadership

    Banking rollouts across Africa and South America, the Equity Bank to PayPal service in Kenya, and Kenya's largest digital health platform.

  3. 2023 to present

    International trade infrastructure

    Technical lead on the Kenya to UK digital trade corridor, working with government agencies in both countries.

  4. Today

    Ohm Core Ltd

    A consultancy where every contract is led personally by senior expertise, and scaled with a trusted network of specialists.

Why not a large integrator?

A fair question. Here is the honest answer.

Ohm Core is one principal and a network of specialists. For programmes that need more hands, we work as a consortium partner or as specialist support to a larger contractor.

  • Senior-led delivery

    The person who scoped the work is the person doing it. It is never handed down to juniors.

  • A director on every contract

    A director with ten years of delivery leads every engagement personally, from first meeting to handover.

  • Capacity that scales

    A vetted network of specialists joins as the work requires, so the team matches the scope.

  • Faster to start

    No bench to fill and no layers of approval. Work starts when the contract does.

  • Direct accountability

    One person answers for the outcome, and you have his number.

See what the written assessment looks like.

An anonymised, illustrative page. Every assessment is written for your systems, in plain language your leadership can act on.

Request my assessment
Written assessmentPage 3 of 9
Sample

Section 2

What is most likely to fail next

Ranked by likelihood and cost. Each risk links to the fix in section 4.

  1. 1Payment confirmations time out at the month-end peakPayments queue, customers retry, and duplicate charges reach the call centre.Likelihood: HighFix in: Weeks 1 and 2
  2. 2One database carries every serviceA single failure stops registration, claims and reporting at the same time.Likelihood: HighFix in: Month 1
  3. 3Alerts reach staff after the public noticesHours spent finding the cause while complaints build.Likelihood: MediumFix in: Month 1
  4. 4Disaster recovery has never been rehearsedNobody can say how long a full recovery would take.Likelihood: MediumFix in: Month 2
Illustrative example. Real assessments name your systems, your peak days and your numbers.

Find out where your systems are at risk.

We open every engagement with a free written assessment, in plain language: what could fail, what it would cost you, and what to fix first. A plan you can act on whether or not you hire us.

It starts with a short call. We reply within three business days to arrange it, and the written assessment follows within a week of agreeing your requirements.

What you receive

  • A short call to understand your systems and what you need
  • What is most likely to fail next, ranked
  • What each failure would cost you in money, service and time
  • What to fix first, and in what order
  • A plain-language summary you can share with leadership

Prefer to talk first? hello@ohm-core.com or +254 704 760 842

A summary is enough. Nothing confidential is needed until we speak.