Most solo consultants have too many tools, not too few
You probably don't need more software. You need fewer, better-chosen tools and a handful of routines you actually run. That is all systems for a business of one really are: the smallest stack that keeps money tracked, work delivered, pipeline warm and admin off the floor.
The instinct when things get messy is to buy something. A new CRM. A new project tool. A new automation that promises to tie the other twelve together. Six weeks later a client's details live in three places and none of them are current.
Simplicity is not a compromise here. When you are the whole operation, every tool you add is a tool you have to maintain, remember, pay for and eventually migrate off. Complexity has a running cost and you pay it in attention.
The four systems for a business of one that actually matter
Everything a solo practice needs to hold sits in four categories:
- Money — what came in, what went out, what's owed, what's set aside.
- Delivery — the work itself, and the record of it.
- Pipeline — conversations, proposals, follow-ups.
- Admin — the calendar, the inbox, the contracts, the renewals.
If a tool isn't doing one of those four jobs, it's a hobby. Be honest about which of your subscriptions are hobbies.
Six tests before a tool earns a place
Before you add anything, run it through this:
- One job, done clearly. Tools that do six things do none of them well enough to trust.
- You can run it on a bad week. If it only works when you're rested and organised, it doesn't work.
- Your data comes out. Export to CSV or PDF, without a support ticket. You will change tools eventually.
- Setup under two hours. Anything that needs a weekend of configuration is a project, not a tool.
- Cost is proportionate. A $90-a-month tool for a practice billing modestly is a decision, not a default.
- It replaces something. New tool in, old tool out. Otherwise you're accumulating, not systemising.
Apply that test properly and most of what you're being sold falls away.
Money: know your position in under five minutes
The test of a money system is simple. Can you answer, right now, how much is owed to you, how much you owe, and how much you can safely pay yourself? If that takes more than five minutes, the system is broken.
What you need:
- A separate business transaction account. Non-negotiable. Mixing personal and business money is the single most common reason solo operators can't see their numbers.
- Cloud accounting or invoicing software that connects to that account. Invoices out, receipts captured, bank feed reconciled. One tool, not three.
- A tax and super set-aside. A second account, funded on a rule you decide with your accountant, every time money lands.
- A rolling twelve-month cash view. A spreadsheet is fine. Contracted income by month, known costs by month, the gap visible. This is the single most useful document in the business and almost nobody keeps one.
- A bookkeeper or accountant. Not a tool, a person. Get advice about structure, GST and tax from someone registered to give it — this article isn't that.
One routine holds it up: a monthly close. Ninety minutes, same day each month. Reconcile, chase what's overdue, update the twelve-month view, pay yourself. That's the whole thing.
Delivery: one home per client, one definition of done
Delivery systems fail in a specific way. The work gets done well and the record of it scatters — half in email, half in a shared drive, half in your head. Then a client asks what you agreed in March and you spend forty minutes finding out.
What you need:
- One folder or workspace per client, structured the same way every time. Contract, scope, working files, outputs, notes.
- A proposal-to-scope template. The document that wins the work should become the document that defines the work. Rewriting it from scratch is wasted effort and it invites scope drift.
- A definition of done for each engagement. Written, agreed, visible. What you'll deliver, by when, and what marks it complete.
- A meeting note habit. Same format each time: decisions, actions, owner, date. Sent to the client within a day. This is your scope defence and your relationship builder at once.
- A way to record outcomes, not just outputs. If you work with purpose-led clients, you'll be asked what changed. Capture it as you go, in the client folder, while it's fresh. Retrofitting impact evidence a year later is miserable work. Our view on why honest measurement matters sits alongside the community's commitment to the Sustainable Development Goals.
Templates are the leverage point here — build them once, reuse them forever. Every hour spent making a reusable scope document buys back ten.
Pipeline: a list, a stage, a next action, a date
Most solo consultants don't need a CRM. They need a list they look at every week.
A pipeline system needs four fields and nothing more:
- Who
- What stage they're at (conversation, proposal out, verbal yes, signed)
- What the next action is
- When that action is due
That's it. Spreadsheet, simple database, kanban board — pick whatever you'll open. The tool is irrelevant. The weekly review is everything.
Block forty-five minutes at the same time each week. Move each entry forward, set the next action, follow up on anything past its date. Add one line for visibility work — the post, the conversation, the referral ask you'll make this week.
The reason pipeline collapses in a business of one is not laziness. It's that delivery expands to fill all available time, and when you're busy, prospecting feels optional. It isn't. The forty-five minutes is what stops the feast-and-famine cycle.
Admin: reduce the surface area
Admin is where solo operators lose hours without noticing. The goal isn't to do it faster. It's to have less of it.
- Calendar as the source of truth. If it isn't in the calendar, it isn't happening. Include delivery blocks, not just meetings.
- A scheduling link. Ends the six-email back-and-forth. Set your available hours deliberately — this is a boundary tool as much as a booking tool.
- One "waiting on" list. Everything you've asked someone else for, with a date. Check it weekly.
- A renewals note. Insurance, professional memberships, domain, subscriptions, contract end dates. One page, one annual review, no surprises.
- A password manager and a backup that runs itself. Both boring. Both the difference between an inconvenience and a catastrophe.
Inbox rules do more than any productivity app. Filter newsletters out of the main view. Deal with client email in two defined windows a day. Nothing else earns real-time attention.
The routines are the system — the tools are just where it lives
Four cadences hold the whole stack together:
- Weekly, 45 minutes. Pipeline review, waiting-on list, next week's calendar.
- Monthly, 90 minutes. Financial close, invoicing, cash view update.
- Quarterly, half a day. Rate the five pillars of the Impact Architect Framework™ — Product Design, Visibility, Impact, Systems, Wellbeing — one to ten. The pillar with the lowest score is your next quarter's focus. Members do this at onboarding and repeat it; you can run the same discipline on your own.
- Annually, a full day. Contracts, pricing, tools audit, what you'll stop doing.
If you only adopt one, take the weekly. It is the cheapest hour in the business.
Why this matters more than it sounds
The Company of One philosophy isn't about staying small for its own sake. It's about building something that produces a good income without producing a second job. Some of our members work toward a three-day week — and the ones who get there don't do it on discipline. They do it because their systems remove the decisions.
That's the real argument for a minimum viable stack. Every tool you don't have to maintain is attention you keep for the work that pays and the work that matters. The point of infrastructure is that you stop thinking about it.
The IC isn't where you summit. It's the base camp — the place you sort your kit, fix what's broken and set out properly. Systems are the kit.
Start with the one that's costing you most
Don't rebuild all four categories this month. Pick the one that's leaking. If you can't say what you're owed, start with money. If you're rewriting scopes from scratch, start with delivery. If your income swings hard between quarters, start with pipeline.
Give it ninety minutes. Set up the smallest version that works. Run it for four weeks before you change anything.
We build this kind of infrastructure together inside The IC — Foundation Pods each month across the five pillars, and Expert Pods for small-group work on the specific thing that's stuck. Membership is capped at 150 so the rooms stay small enough to be useful. Join the Community Waitlist and we'll be in touch when a place opens.