You know what should happen after a client says yes. You could probably draw it on a napkin.
You've already done the hard part
The part that's missing is the stretch of uninterrupted weeks it would take to build it, test it, and write down how it works. So it stays on the list, and you keep doing the manual version (probably with a tutorial open in another tab).
People tell me some version of this all the time: I could figure it out myself, and then I remember I don't want to. Honestly, I think that's the right call. Building it is a second job, and you already have one.
The tools got added one at a time
A proposal tool when the PDFs got old, a form builder for intake, an email platform for your list, a folder structure that made sense in 2022. Each one was a good decision on the day you made it. Nobody ever sat down and designed how they'd pass information to each other, so right now that job is yours. You copy the client's details from the form into the contract, then the invoice, then the folder name.
It's a setup problem, and building the setup is a different trade
What you're looking at is what happens when a setup grows without a plan, and it happens to almost everyone I work with. Running a client business and wiring seven apps together are two separate skills, and you only signed up for one of them.
I'm Molli, an Online Business Manager & Systems Strategist, and I happen to love the other one (put me in front of a fun automation and I lose track of time).
One thing I always do first is get the manual version working before I automate anything. If a process is fuzzy when you do it by hand, automating it makes the fuzzy thing happen faster.
What I build
Every build is scoped to your business, so yours will be some combination of these.
Client flows
Inquiry, proposal, signed contract, onboarding. Connected, so a new client moves through without you pushing every step along by hand.
Automations between your tools
The tools you already pay for, passing information to each other, so a detail gets typed once and shows up everywhere it's needed.
A home for the work
A workspace, dashboards, templates and SOPs set up around how you already work, so anyone helping you can find what they need without asking you first.
Custom tools
When the thing you need doesn't exist off the shelf, I build it.
Every build comes with video walkthroughs and written documentation. Those are part of the build, every time.
What The Build doesn't cover
Working out what you need from scratch. That's the Consulting Call, and its fee applies toward The Build.
Running your systems week to week after handover. That's The Partnership, my ongoing OBM work, which is by application.
How The Build works
The audit
I go through every tool, every workflow and every task you're doing by hand, exactly as it is today. Please don't tidy up first, because I need to see where things break. Nothing gets changed at this stage.
The build
I start with a mockup, so you can look at what I'm proposing and tell me you hate it before I've spent five hours building it. Then I build in your tools. Most client flows follow a pattern I've built before, so my time goes into the parts that are specific to you. I change what's causing the friction and leave what's working alone.
The handover
You get video walkthroughs of everything, documentation you can look things up in later, and enough training that you're comfortable running it yourself.
The part of the build you'll never see
Most of what I'm thinking about during a build never shows up in the finished thing, and that's on purpose.
The more people have to think about a step, the less that step happens.
Where it's going to break
I spent almost ten years in customer service, so I know nobody remembers which email address they signed up with. Where I can, the form already knows who's filling it out, and the wrong-email error never gets a chance to happen.
What nobody's going to read
I assume the important email gets skimmed at best (I skim them too). So the thing your client needs to know shows up in more than one place.
What you'll keep doing on a rough week
I build for the week you're running at about 10%. If a step only works when you're at full power, I take it out or make the system do it. I think about this on every build, because I work with a lot of neurodivergent founders.
I work in the tools you already have
I start with what you're already paying for, because most of the time the tool can do the job once it's set up around how you work. That might be HoneyBook or Dubsado. It might be Zapier, Tally, Kit and your existing Google Drive. It might be Notion, if Notion suits how your brain works.
If a tool truly can't do what you need, I'll tell you, and I'll tell you what I'd move to and why.
What you own when we're done
I build it to be maintainable. You shouldn't have to come back to it a few months from now because it's gotten overwhelming again.
The infrastructure. Everything lives in your accounts, so you're never relying on me to keep it running.
Video walkthroughs of every piece I built.
Written documentation you can hand to a VA, a team member, or future you.
Enough training to change things yourself when your business changes.
Nervous about giving someone access? That's fair.
I don't change anything until I've seen how it runs today, and I change one thing at a time so we can both see what each change did. Nothing I build is a black box that only I can touch.
A client, on her new proposal flow
“I am obsessed with the proposal that goes straight into them being able to sign a contract right away and how BEAUTIFUL it looks. I thought I was only missing a few features here and there, I had NO idea lol. That's how busy I have been.”
Jordain S., Social Media Strategist & Photographer
An ongoing client, on the Notion dashboards I built for her
“From helping me run a major summit to building out beautifully organized Notion dashboards, she consistently delivers work that's thoughtful, efficient, and done with a level of excellence that makes my whole business run smoother.”
Rachel Starr, Community By Design Co.
Finding the distance between “a few features” and what your tools can already do is what the audit is for.
See how other builds came together →
The Build starts at $1,200
I price by the result, so you get one price for the whole build and we agree on it before I start. The final number depends on how complex your setup is and what we're building.
Your quote spells out the scope, the price and the timeline. Some builds take a few weeks and some take longer, and you'll know which one yours is before you say yes.
If you've already done a Consulting Call, that fee applies toward The Build.
Tell me what you want built
Send me the short version. I'll read it, we'll have a scoping conversation, and then I'll send you a proposal with the scope, the price and the timeline. No rush on getting back to me once you have it.
Questions first? Email me at molli@virtuallymolli.com.
If you can't name what you need built yet, the Consulting Call ($397) is where we map it, and that fee applies toward The Build.
Questions people ask
How long does The Build take?
It depends on how much we're building. Some builds are a few weeks and some take longer. We settle the timeline during scoping and it's written into your proposal, so you're never guessing.
Do I need a Consulting Call first?
No, as long as you can tell me what you want built. If we start scoping and the picture turns out to be fuzzy, I'll say so, and the Consulting Call is where we map it. That fee applies toward The Build, so the work carries over.
Do I need to clean things up before we start?
Please don't. If you tidy up first, I lose the clues about where things break, and I need those. Show it to me exactly as it is.
What if I don't know which tools I should be using?
That part is my job. Tell me what you want to happen and I'll work out which tools can do it, starting with the ones you already have. If you can't say yet what you want to happen, that's a Consulting Call question.
I have a really specific way of doing things. Will you build around it?
Yes. There's usually a pattern I follow, and then I build around the intricacies of how you do it. The more opinions you bring about what you do and don't like, the better the build gets.
Couldn't I get AI to build this?
You can get a long way, and I use AI every day. I also don't fully trust it. The people who trust it completely tend to come to me at step 350 of its instructions, where the step doesn't exist, or it exists on a plan they aren't paying for. AI will get information from A to B. Thinking about what you'll keep doing in a busy week is still my job.
What happens after handover if I need help?
You'll have the walkthroughs and the documentation, and the point of the handover is that you can run it yourself. If you'd like me to stay on and run things with you, that's The Partnership, my ongoing OBM work. It's by application, and it's a separate conversation from The Build.