Technology & Operations Operator

Your business runs on you.Let's fix that.

I build the operating systems that let a company run without its founder in every decision. Ten years building software. Developer operations at Meta. The business systems in between.

Start a project What I build

Carol Kariuki, technology and operations operator, Nairobi

What I take on

The four things that are usually actually wrong

01
Operations that don't scale
The process worked at ten people and is quietly breaking at forty. Nobody decided to change it. It just stopped holding.
02
Execution that stalls
Work dies in the gaps between teams. Everyone is busy, nothing is landing, and nobody owns the handoff.
03
Technology you can't use
You bought the tools. Nothing is connected, the numbers disagree with each other, and nobody trusts the dashboard.
04
You are the bottleneck
Everything routes through you, because almost nothing is written down. Taking a week off would cost more than it's worth.

See how each of these gets fixed

How we work together

Three things you can actually buy

Every one of them ends in something that exists and runs. Fixed scope, built, handed over. Not a seat filled or a retainer.

Mission Control

Installed · fixed scope

You are the only person who knows what is actually happening.

An executive operating system, built around how you work and handed over running. One screen every morning that answers what now: priorities, open loops, who you are waiting on, what lands this week. Underneath it sits the operating rhythm that keeps the screen honest.

What you get

A daily command centre: start of day and end of day, one screen
Open-loop tracking so commitments stop living in your head
A weekly operating rhythm, and the reports that come out of it
Your data in your own instance, structured so it stays yours
Handover, so it runs without me

Built independently and running in production for an executive today.

Process automation

Fixed scope · built and handed over

One repeatable job is eating your team's week.

Take a process your team runs by hand every week and turn it into a system that does the work and stops at a human review step. Not a workflow diagram. Not a recommendation. A working thing, in production, documented, that your team owns afterwards.

What you get

The process mapped end to end before anything is built
A working system, in production, with a human review gate
Documentation your team can operate and change
A handover, so it does not depend on me

Most recently a proposal engine. An RFP goes in and a reviewable draft package comes out: requirements matrix, fit score, drafted sections against the client's own methodology, statement of work, and an explicit list of what a person still has to supply.

Build sessions

A few hours a week

You want the thing built, with your team in the room.

Working sessions where we build it together instead of me disappearing and returning with software. This suits you when the system has to survive inside your team, or when someone there needs to extend it after I am gone.

What you get

Scoped, recurring sessions instead of an open retainer
Your team builds alongside me and keeps the knowledge
The same handover discipline as a full build

01
Tell me where it's stuck
A few lines about what you are building and what keeps breaking. No form, no discovery-call ritual.
02
We scope it properly
One conversation to find out whether there is a real system here, what it would take, and whether I am the right person. If I am not, I will say so.
03
Fixed scope, then built
You get a defined piece of work with an end date, not an open-ended arrangement. Then it gets built and handed over.

Read the full detail on each

Selected work