Skip to content

Technology & Operations Operator

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

I build the operating systems that let a company run without a founder in every decision. What depends on people today becomes a system that runs reliably: documented, automated, and owned by you. Technology operations at Meta, developer ecosystems, and the business systems in between.

Start a projectWhat I build
Carol Kariuki, technology and operations operator, Nairobi
200+

High-priority escalations a month

95%

Resolution rate

2M+

Records analysed

3,000+

Developers in the community

What I take on

The four things that are usually actually wrong

Each of these has the same root: the business depends on people holding it together, not systems. That’s the thing worth fixing.

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

Your whole operation, visible and running, so it no longer lives only in your head.

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

The repetitive work runs itself, freeing you and your team from what a system should be doing.

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

The tool or system you're missing, built, so a workaround stops being your process.

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
  1. 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.

  2. 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.

  3. 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

Three problems, worked through

See all work

Background

Why the operations advice is technical

The systems I design are built, not just advised. That’s the difference between operations that sound good and operations that actually run.

  1. Carol Kariuki with Eugene Mutai during the VituMob years
    2010–2020

    Built software

    Mobile apps, browser extensions, production e-commerce systems.

  2. Carol Kariuki leading a Developer Circles session in Nairobi
    2018–2020

    Led a developer ecosystem

    Facebook Developer Circles Nairobi, to 3,000+ developers.

  3. Carol Kariuki at Meta headquarters, 1 Hacker Way, Menlo Park
    2020–2022

    Operated at Meta

    Developer support, escalations, cross-functional delivery.

  4. Carol Kariuki
    2022–now

    Builds operating systems

    Executive operations and automation for founders and investors.

Read the full background

Writing

Working notes

Read all writing

Tell me where it’s stuck.

A couple of lines about what’s currently held together by people instead of systems is enough to start. If I can help, I’ll tell you how. If I can’t, I’ll tell you that too.

Start a projectLinkedIn