i'm the person who sees the five-step process hiding inside your "i'll just do it manually for now" habit.
i've helped 350+ service-based business owners build the systems they keep meaning to set up — so their businesses stop living in their heads.
as a mom of 3 under 5 working 15–20 working hours a week...I know what it means to need a backend that runs without you — because mine has to.
i'm not teaching this from theory. i built these systems because i had no other option. school pickup doesn't move. sick days don't reschedule. if my business didn't run without me, it didn't run.
so i built it to run without me. and then i helped 350 other people do the same thing.
2018
i jumped into the online space and clients came fast. on the outside, it looked like success. on the inside, i was drowning. i hired in a panic, tried to hold everything together with duct tape and good intentions, and learned the hard way that growth without systems is just chaos with a better instagram.
2019
out of desperation, i started building actual systems — for hiring, for delivery, for everything that kept breaking. for the first time, my team could breathe. and i realized backend operations weren't just boring admin work. they were the difference between a business that worked and one that owned you.
2020
i became a mom in the middle of a pandemic while running operations for multiple 6- and 7-figure businesses. that season confirmed what i already suspected: if your backend isn't solid, everything collapses the second life gets hard. systems didn't just help — they saved me.
2022
after years of being the engine behind other people's businesses, i started teaching what i'd built. streamlined the complicated stuff, simplified the process, and created the early version of what would become the back office method.
2026
the back office co. now exists to do one thing: help service-based business owners build the backend their businesses should have had from the start — so they can stop working nights and weekends and actually show up for their lives.
(and why that matters for you)
How I Went From Drowning In My Own Business To Building Backends That Run Themselves
what i
actually believe:
systems aren't about being organized. they're about removing the decisions you shouldn't have to make every single day.
your backend should be boring. the most effective client onboarding is the one you set up once and never think about again. the best follow-up sequence is the one that goes out while you're at school pickup.
you're not behind because you're bad at this. you're behind because nobody helped you build the infrastructure. that's the only thing we're here to fix.
and "just hire a VA" is not the answer if the VA has no documented process to follow. the system comes first. the help comes second.
350+
Clients supported
7
years Building backends full-time
2-3
Iced coffees consumed daily
What's the difference between the Society, the Intensive, and the Done-With-You Build?
Questions You're Probably Wondering
(but didn't want to ask yet)
The Back Office Society is ongoing monthly support. You get a new system every month, live office hours, direct access to me, and a community. It's for people who want consistent help and accountability over time.
The Intensive is a one-time 60-minute session where we figure out the single most important system you need right now and I give you a blueprint to build it yourself. It's for people who need clarity and direction but want to implement on their own.
The Done-With-You Build is custom work where I actually build your backend systems for you over several weeks. It's for people who are done trying to DIY it and just want someone to handle it.
Not sure which one fits? Just reach out and we'll figure it out together.
How long does it take to see results?
If we're setting up client onboarding or email automation, you'll feel the difference within a few weeks—things start running without you having to think about them.
If we're overhauling your entire backend, it takes longer to build everything out, but you'll start seeing breathing room as we go, not months later.
The goal is always quick wins that build momentum, not waiting forever to see if it worked.
How do I know it's time to hire you?
When you're spending more time managing your business than actually working in it. When client onboarding only happens if you do it manually. When you can't take a day off without everything grinding to a halt. Or when you realize you've been "meaning to systemize" for six months and still haven't done it. That's when.
Should I just hire a VA instead?
A VA will inherit whatever systems you have (or don't have). If your backend is already a mess, they'll just be managing the mess for you—and you'll still be the one answering their questions, fixing what breaks, and holding it all together.
I build the systems first. Then, if you want to hire a VA later, they'll have clear processes to follow, documented workflows, and automations already running. They become support, not the solution.
Think of it this way: I'm the architect. A VA is the assistant. You need the blueprint before you need the help.
Can I just figure this out myself?
You could. But if you've been planning to "figure it out" for the last six months and you're still here, that's probably your answer.
