Operations for One: Running a Lean Practice With AI
A solo practice has no back office. So you become it, at night, for free. AI is the first thing that actually changes that math.
Run a one-person practice and AI won't manage the business for you. What it will do, reliably, is absorb 20 to 30 percent of your administrative load if you point it at the right work: routine email, meeting notes, light drafting, documentation. For a solo professional, especially one in their late forties or fifties, that's not a productivity tweak. It buys back billable hours and stops your practice from being capped by your own stamina.
The appeal of going solo is freedom. Choose your clients, set your schedule, do work that's actually yours. The hidden tax is operations. Invoicing, scheduling, follow-ups, tracking engagements, updating materials, the small jobs that don't take long alone and together cost you a day every week.
If you came to this after twenty-plus years inside organizations that had whole departments for this, the adjustment stings. You used to give work to the back office. Now you are the back office. Your judgment is still your moat. The administrative drag around it is what eats the hours you'd rather spend on clients, or on not working.
What is the real operations problem for solo practices?
Most solo professionals are strong at the core work. You went independent because you're a capable advisor, consultant, coach, or specialist. What you didn't design for is the overhead of running an actual business, and it accumulates quietly until it becomes the limiting factor.
A therapist with twenty clients loses hours a week to scheduling, documentation, insurance paperwork, and billing, none of which is therapy. A management consultant running four engagements burns evenings on status reports and client updates. The standard advice is "hire an assistant," which is right at a certain scale. Below that scale, the answer is a lighter infrastructure you can stand up yourself in an afternoon.
What does a solo practice actually need to run?
Strip it down. A one-person practice needs five operational functions to run without friction. AI has a role in all five, but the real gains cluster in the first three.
| Function | What it covers | Best owner at solo scale | AI impact |
|---|---|---|---|
| Client communication | Email replies, scheduling, status, wrap-up summaries | You + light tools | High, drafting and follow-ups |
| Documentation | Meeting notes, decisions, deliverable records | You | High, structure and cleanup |
| Content & visibility | Proposals, posts, list email, case studies | You | High, first drafts and reuse |
| Financial admin | Invoicing, expense tracking, reporting | Accounting software | Low to moderate |
| Internal reference | Your notes, templates, SOPs | You, occasionally AI | Moderate, depends on capture |
Notice what AI doesn't do: it won't replace real finance software, and your internal reference is only as good as what you bother to write down. Start where work already passes through your keyboard and you feel the most repetition.
How do I stop email from eating my day?
Email is where solo professionals lose more time than they'll admit. Not the serious conversations, those earn your attention, but the routine ones: scheduling, the post-meeting follow-up, the question you've answered twenty times. The pattern I see with the independent consultants who handle this well is that they don't try to automate the whole inbox. They build one drafting lane and route the routine mail through it.
The setup is simple:
- Keep a short snippet on your desktop: "Draft a concise, professional reply to this client email. I'm a solo consultant working with them on [project]. My voice: direct, plain, no fluff. Here's the email and context."
- When a routine message lands, paste the thread, add one line of context if it needs it ("we're two weeks behind because their VP changed scope"), and run it through Claude.
- Read the draft, fix a line or two, send.
Five-minute emails become ninety-second edits. Across thirty a week, that's four to five hours a month back. The bigger win is cognitive: the nagging "I still need to write that person back" leaves your mental queue far faster, which is what keeps interrupting deep work in the first place.
How do I handle meeting notes without losing an evening?
Meeting notes are the most reliably skipped task in solo practice. You mean to write it up, the day gets away from you, and three weeks later you're squinting to remember what you promised and what the client said about budget. Claude can't sit in the room for you, but it makes the distance from raw notes to a usable document much shorter.
A routine that works: right after a call, set a three-minute timer and dump what happened into your notes app. No polish, just bullets, "agreed to move launch to July," "CFO worried about change fatigue." Paste that into Claude and ask for a structured summary: topics discussed, decisions made, next steps, owners. The output is clean enough to send the client if you want, and it becomes the reference document for the engagement.
An executive coach does this after every session. By the end of an engagement she has a complete chronological record, what the client walked in with, what shifted, what they decided. It makes her sharper in the work, and it protects her if a client ever disputes what was agreed.
Templates and SOPs: the infrastructure you never built
Most solo professionals have no written procedures. They have habits and muscle memory, which works fine until you want to scale, or until you notice you're rebuilding the same document from scratch every single time.
A one-time investment in templating pays out continuously. Spend two hours this month asking Claude to help you document how you handle five recurring tasks: onboarding a client, structuring a status report, writing a close-out summary, standing up a new engagement folder, sending a renewal nudge. You describe how you do it. Claude turns it into a clear, reusable template. Next time, you're executing, not reinventing. A financial planner who built a five-template library found new-client onboarding dropped from a full-day slog to about two hours. The substance didn't change. He just stopped rebuilding the scaffolding.
The one habit that changes everything: Write It Down First
If you take one rule from this, take this one. Call it Write It Down First. The professionals who get the most from AI have built the habit of externalizing their thinking in real time. You can't hand execution to Claude if the raw material lives only in your head. Notes after every meeting, a quick context capture before an email, five lines in a running doc on where an engagement stands, those inputs are what AI turns into output.
I resisted this for a while, honestly. It felt like busywork on top of busywork, and I assumed a good enough model would just infer the context. I was wrong. The constraint is almost never the model's capability. It's the quality and completeness of what you feed it. The day I started keeping a two-line running note per active client, the output quality jumped more than any prompt tweak ever delivered.
I already have an assistant. Is this still for me?
Yes, because they do different jobs. A human assistant handles scheduling, coordination, and anything that needs a person on the other end. AI handles drafting, documentation, and synthesis. Most established practices want both. If you're earlier, AI is the cheaper first hire, and it helps you figure out what a human assistant would actually need to own later.
What tools do I actually need?
Less than the automation crowd will tell you. A solid AI chat tool like Claude, a note or document system you'll genuinely use, and basic invoicing software if you don't already have it. No complex integrations, no automation platforms, no six-app stack. The simpler the system, the more likely you'll still be using it in six months, which is the only metric that matters. On confidentiality, this is not the place to be casual: use an enterprise tier with stronger data protection for client work, or strip identifying details before pasting, and check your profession's ethics rules first.
The honest first month
Don't try to build all of this in a weekend. One new template or system per week. By week four you'll have the operational spine of the practice standing, and maintenance after that is light, mostly using what you built and adding a template when a new recurring situation shows up. The freedom you wanted from going solo was never supposed to cost you a day a week in admin. This is how you take that day back without hiring anyone, starting with the next meeting you bother to write down.