Fractional ops support for founder-led companies under ~10 people. I remove the friction so your team can execute without you in the middle of everything.
What I do
Processes. People clarity. Tools. Handoffs. No 40-page decks — just the work that makes the friction go away.
People clarity
Role definitions, onboarding systems, communication norms — built so your team knows what they own and can act without asking.
Process & systems
CRM cleanup, tool consolidation, workflow documentation — replacing the fragile duct-tape infrastructure with something that holds.
Handoffs & visibility
Meeting cadences, KPI dashboards, follow-through systems — so things actually move without you as the relay point.
The cost of unbuilt systems
You're not getting back what you're putting in.
Is this for you?
You're the answer to every question in your company, and you're exhausted by it.
Things fall through the cracks when you're not watching.
You have good people, but unclear ownership — and it costs you.
You've grown past the point where winging it works, but you're not ready to hire a full-time ops person.
You know what needs to change. You just don't have the bandwidth to do it yourself.
Worth knowing: If your primary constraint is messaging, positioning, or product-market fit — that's a different problem. I can fix the operational infrastructure around a sales pipeline, but I'm not a marketing strategist.
The compounding cost
What costs an hour today costs a day next year.
How it works
I work inside your business, not at arm's length. The systems I build belong to you when I'm done.
One conversation
We talk. You tell me what's broken. I tell you honestly if I can help.
90-day scope
I map the gaps and propose a focused engagement — specific problems, clear outputs, defined timeframe.
Embedded, not advisory
I work inside your business, not at arm's length. The systems I build belong to you when I'm done.
The manual tax
A Tuesday afternoon, everywhere
“Hey — should we move forward with that vendor, or wait for you to review the contract? Also, the new team member isn’t sure who to send the weekly update to. And client X replied — not sure if you wanted to handle that one.”
Three decisions. All of them yours. None of them had to be.
About
Rachael Dietrich
Fractional Operations · Founder of UNI.FY
I work with founders who have vibrant visions and who love what they do — and want to keep loving it. The ones building something real who just need someone who genuinely loves the ops side to run alongside them.
UNI.FY exists because the founders I admire most figured out how to protect their energy. Not by doing less — by building better infrastructure around everything that doesn’t need to run through them.
People first, systems second
Remove the constraint without adding complexity
Build it so it runs without me
On working with Claude
I use Claude as a second brain — trained on my clients, priorities, and way of thinking. Part of what I bring to every engagement is helping founders build that same infrastructure: not just access to AI, but a workflow that actually holds.
The assessment
Two minutes. No calendar link required.
The assessment
Four questions. Two minutes. An honest read on whether this makes sense for where you are right now.
If you were unreachable for two weeks, your business would…
Be honest. This is just between you and the page.
Where does work most often break down?
Pick the one that costs you the most right now.
What's your biggest constraint right now?
This one matters most for figuring out whether I can actually help.
If revenue is the constraint, what do you believe is actually blocking it?
This helps me understand whether there's an ops angle I can work with.
Context
Most founders at your stage are choosing between these. Here's how they compare — honestly.
If you're a 20-person company with a real budget and a specific function to fill — hire a fractional CMO or CFO. That's the right answer. I work best with founders who are a step before that: enough traction to need real infrastructure, lean enough that one person who can see the whole picture makes more sense than five specialists.
How to work together
Both engagements start with a conversation. I don't scope anything until I understand what's actually going on.
Ongoing
For founders who want someone embedded
$750–$1,500/month
90-day minimum
I lead 1–2 specific initiatives we've scoped together — things with a clear before and after. And alongside that, you have direct access to me for the ops questions that don't fit neatly into a project.
What "access" actually means
A hire you're unsure about. A process that just broke. A vendor decision sitting in your inbox. You message me, I respond with an ops lens. This is often where I add the most value — because I already know your business.
Project
For founders with one specific problem
$750–$2,000 flat
Scoped to the work · 4–8 weeks typical
One initiative, start to finish. We define the scope, I build it, and hand it off documented and ready for your team to own.
Many project clients move to ongoing after the first sprint.
Get in touch
I read every submission before I reply — usually within a day, always with a specific reaction to what you shared. No generic funnel.
Common starting points
Most engagements start with one of these. Click any to see what it actually involves.
I set up Claude as a working part of your ops — not just an account you have. Instructions built around your voice and decisions, plus training for you and your team on when and how to use it.
Build the systems that let a new executive assistant get up to speed without needing you to teach them everything. Role clarity, tool access, decision trees, and communication norms.
Assess how your CRM is actually being used versus how it should be. Clean up the pipeline, standardize stages, and build the hygiene habits that make your data trustworthy.
Define the 5–8 numbers that actually tell you how your business is performing. Build the cadence and ownership so you're reviewing them regularly — not chasing them down.
Map how information flows through your business and where it breaks down. Build the channels, norms, and escalation paths that reduce noise and stop you being a communication bottleneck.
Design a lean meeting structure that produces clear decisions and real follow-through. Agendas, note formats, action item ownership, and async alternatives that actually get used.
Organize your shared drives so your team can find things without asking. Build the folder structure, naming conventions, and permission logic that scales as you grow.