Run Your Business

How business systems work, and where they break

This is the overview: what a business system is, why they get tangled, and how to change one without stopping work. Each article above takes one piece of it.

You already have systems. Some of them are you.

Every business does the same six jobs, whatever it sells. It keeps track of people. It has somewhere people find it: a website, a booking page, a link in a bio. It posts. It gets paid. It turns an interested stranger into a name. And it stays in touch with the people who already know it. The six essential business systems breaks those down one at a time.

You're doing all six right now. The only question is what each one runs on. Some run on a tool you pay for. Some run on a spreadsheet, a reminder you set yourself, or the fact that you'll remember. That last one counts. It's a system too, and it's the first one to slip when the client work is busy.

The trouble lives between the tools, not inside them

Look at any one tool on its own and it probably works. The email tool sends email. The calendar takes bookings. The breakage is in the hand-off. Someone books, and now the email tool needs to know, the invoice needs their name, and the course needs to let them in. Each of those moves either happens by itself or waits for you.

That's why adding a tool so often makes things worse. Say your email tool can't do the automation you want, so you add a second one. Now the list lives in two places, and some people get two copies. So you add a connector to keep the two in step. It drops things now and then, so you start a spreadsheet to check which list is right. One problem has become four things to look after. Why adding tools usually makes it worse follows that spiral all the way down.

The rule of thumb is to count the hand-offs, not the tools. Fewer places for someone's details to live means fewer places for them to go missing.

What a tool costs isn't on its pricing page

The subscription is the part you can see. You'd probably say you pay for a few things, until you go down the card statement line by line. How to audit your business systems walks through that count, including the per-sale fees and the tool you signed up for once and forgot.

The rest doesn't show up on any statement. There's the time spent moving details from one tool to another, and the afternoon that goes when a connection stops without telling you. And there are prices that climb as you grow: more contacts moves you up a tier, and adding an assistant costs another seat. What your "affordable" tools actually cost adds all of it up, and one expensive run through business tools is the same lesson learned the long way. In a FableForge account, adding your VA or your whole team doesn't change the bill, and there's no cap on contacts.

Your clients pay a version of it too. They meet your systems before they meet your work: the booking page, the invoice, the welcome email, the place they log in. Your systems are your client's first impression walks that path from their side.

Build it for your worst day, not your best one

A system designed on a good day assumes you'll keep having good days. Business systems that work when you're tired starts from the other end. Design for the day you're unwell, short on sleep, or pulled five ways at once, and the good days look after themselves. In practice that means fewer decisions, more that runs without being remembered, and a bar low enough to clear on a bad week.

The same thinking settles smaller choices. A newsletter sign-up needs a name and an email, and putting a five-slide survey in front of it gives people five chances to leave. A survey earns its extra steps when the answers change where somebody goes next. Forms vs. surveys has the full list of when to use which.

The CRM sits in the middle, because every system is about a person

Every one of the six jobs is about somebody: a person booking, paying, signing up, or asking. So the record of that person is where everything else hangs. How a CRM becomes your relationship hub is about exactly that shift, from a list of names to the place each relationship lives.

Two things do most of the organizing inside it. A pipeline is for something with steps, where several people are at different steps at once: a discovery call, then a proposal, then a yes. A tag is for something true about a person that doesn't move, like where they came from or which workshop they came to. When you can't decide, the CRM pipeline library has the test to use. If you didn't track this in a pipeline, what would actually break? If the answer is nothing, it's a tag. See what the CRM does →

Outgrowing a system means it worked

What ran fine with a handful of clients starts to creak with a lot more of them. What works at $5K won't work at $50K names the signs. You're doing the same manual task far more often than you used to. The first part of each morning goes on working out who needs what. Clients start asking where to find things. None of that means you set it up wrong. The business got bigger than the thing you built for it.

Sometimes the answer is to add to what you have, with an automation here and a template there. Sometimes the setup can't carry the new size, and it's time for a bigger change.

Changing systems without stopping work

The worry with a bigger change is breaking something halfway through. How to change your business systems without breaking everything lays out a way around it. Pick one area, the one that frustrates you most. Try the new setup with real work, not demo data. Send new people into it first while everything existing stays where it is. Move the old pieces over one at a time, and check each one. Cancel the old tool last.

Before any of that, it helps to know what you've got. The audit article has a checklist that maps every tool you use against those six jobs. The Tech Stack Audit is ten questions about the tools you pay for and how well they work together. It takes two to five minutes, and the result comes by email.

Where to start in these articles

Not sure what you've got? Start with the audit. Something specific keeps breaking? Read why adding tools makes it worse. Growing, and it's all starting to creak? Read the one about $5K and $50K. And if the CRM is the piece you keep circling back to, the pipeline library is the practical one.

Questions about running your business systems