Fractional Operations Partner for founders ready for calm scale
From operational chaos to calm — by design.
I help visionary founders move from being the system to leading a calm operating system your team can run, so your business works beautifully even when you’re offline.
If your business looks polished on the outside, but behind the scenes it depends on your brain, your presence, and your constant decisions — you’re in the right place.
Not ready? Get the Starter Kit instead.
For founders with teams, who are still the answer to every question.
How to start
- Book an Ops Health Check (45 min)
- Leave with the 2–3 patterns creating pressure + clarity on what to fix first
- If it’s a fit, we build it together inside Founder Freedom Ops
If you’re the hub of everything… this is for you.
- Delegation “doesn’t stick” — people still come back to you.
- Your mornings start with pings, approvals, and “quick questions.”
- You can’t fully unplug because you’re scared it’ll break.
- Your Drive is a maze and your processes live in Slack + scattered Looms.
- You’re constantly context-switching — and it’s killing your ability to create, sell, and lead.
- Someone asks “where’s the doc?” and you lose 15 minutes searching like it’s a scavenger hunt.
- You’re quietly thinking, “I should be more organized by now.”
You’re not failing. Your business just outgrew founder-held operations.
Imagine leading a business you can actually trust.
The backend matches the front-end excellence. Work has a clear home. Ownership is defined. Your team runs delivery without daily input — and you get your brain back.
- You step away for 1–2 weeks and nothing cracks.
- Your team knows what to do (and where to find things).
- Fewer approvals. Fewer emergencies. Consistent delivery.
- One calm source of truth replaces scattered tools.
- You lead with clarity — not urgency.
Your operating system, designed like a product
The Founder Freedom Ops System™
A structured three-month transformation that turns a founder-dependent business into a documented, delegatable operating system.
This isn’t “more tools” or endless SOPs. It’s calm operational design: clear ownership, clean decision flow, and systems your team will actually use — so the business stops relying on your memory, your availability, and your nervous system.
The C.A.L.M. Ops Framework™
Capture → Architect → Launch → Maintain — so calm becomes the default.
Capture
We capture what’s living in your head and scattered across the business — tools, workflows, decisions, responsibilities, and friction. Relief starts here. (Most founders feel lighter in week one.)
Architect
We design the operating system around how your business actually runs: decision pathways, ownership, rhythms, and the simplest structure that will hold, without creating a “corporate” business you hate.
Launch
We build the core systems: your central ops hub, file architecture, essential SOPs, and team rhythms, with adoption baked in, so your team uses it without you policing it.
Maintain
We embed sustainability: review rhythms, red-flag indicators, and clear stewardship so your systems don’t decay, they compound.
What we do together in 90 days
Month 1: Clarity from Chaos
We capture and audit how the business is operating today. You get a clear picture of what’s happening, and what’s relying on you. Nothing important lives only in your head anymore.
Month 2: Structure & Systems
We turn clarity into operating design. Roles, workflows, decision flow, a calm central hub, and only the systems that unlock bandwidth now, no overbuilding.
Month 3: Sustainability & Freedom
We stabilize what we built, reinforce ownership, set maintenance rhythms, and run the Founder Freedom Test, so the business proves it can run without you.
What changes after we work together
- You can go offline without bracing for what will break.
- Your team stops waiting for you to approve/clarify everything.
- Delegation actually sticks — no more “quick questions” bouncing back.
- “Where is that doc?” disappears because work has a clear home.
- Delivery runs cleanly without you being the glue.
- You feel proud of the backend — not embarrassed by it.
What we build to make that true
- An Ops Blueprint (how work flows + what’s relying on you)
- A calm source of truth (so answers don’t live in Slack or your head)
- “Where things live” rules (so Drive stops being a maze)
- A minimal SOP library (only what creates relief + consistency)
- Team rhythms (so execution doesn’t depend on reminders)
- Handoffs + ownership clarity (so decisions stop routing back to you)
- A maintenance system (so it doesn’t decay the moment you get busy)
A real example: “Where is that doc?” solved
A global tech nonprofit with a team across 4 countries scaled fast. Files were scattered across Drive, Notion, and Slack. New hires were lost. Everyone recreated work.
What we did:
- Interviewed the team to observe how they actually searched
- Designed simple rules: Drive = storage, Notion = directory/wiki, Slack = comms
- Rebuilt the Drive structure and access logic
- Prioritized usability over “perfect tools”
Questions dropped, onboarding became easier, and the team could find what they needed without asking.
“This is great……really starting to steer our organization to embed a better, finer, more reliable oil machine, and it’s much appreciated.” — CEO
Calm systems. Human-centered design. Built to be used.
- Ops as a product: designed around real behavior, not ideal behavior
- Not tool-first: blueprint first, tools second
- Restraint-first build: only what creates relief + scalable clarity now
- Adoption embedded: ownership + rhythms + walkthroughs so it actually sticks
- Soft power delivery: supported, not judged — calm, but CEO-level direct
What I know about operations, I learned by carrying everything myself.
I’ve lived what happens when growth outpaces structure, the constant pings, the decisions that only you can make, the fear that stepping away means things break.
Now I design operating systems the way a product designer designs experiences: around how people actually work, not how they should work. Systems that feel clear, hold under pressure, and don’t require you to be the glue.
Because you don’t need more pressure, you need a system that holds.
Calm isn’t passive. It’s power.
Work with me: Founder Freedom Ops System™ (90 days)
calls + async support + implementation + hub build + SOPs + adoption systems.
I take on 3 clients at a time to keep delivery high-touch.
Common questions
“I don’t have time for an ops overhaul.”
We start with Capture to remove mental load fast — relief first, then we build only what unlocks bandwidth.
“We tried hiring help. It didn’t work.”
That’s usually a foundation issue: ownership, decision flow, and source of truth. We fix the root so your next hire finally sticks.
“I’m scared this becomes endless SOPs.”
We document only what repeats and what your team needs to run delivery without you. Minimal + usable.
“Maybe we just need ClickUp/Notion set up better.”
Tools come after operating design. You’ll get the blueprint first, then the simplest stack to support real flow.
Start here: The Calm Operations Starter Kit™
A soft, elegant starter kit that helps you step out of operational chaos and into clarity — with a self-audit, the Founder Freedom pathway, and your first calm team rhythm.
- Chaos Audit scorecard
- Founder Freedom Pathway overview
- C.A.L.M. quick wins
- Weekly Team Rhythm template
- Choose-your-first-calm-system prompt
The Founder Freedom Test
If you stepped away for 7 days… would the business run cleanly without you?
Your business can run beautifully without you.
Let’s design the operating system that makes calm your default — and gives you real freedom again.