The Claude workflows worth keeping in a solo consulting practice

There's no shortage of takes on what Claude can do for a solo consultant. This article is narrower: the handful of workflows we think are worth making permanent, the ones that tend to sound better than they work, and the setup that holds the rest together.

The test we apply is simple. Some workflows you try once and drop, because they read well in a thread but don't hold up on client work. Others you run so often you stop noticing you're using AI. Only the second kind is worth setting up properly.

This assumes you've already decided AI is part of your practice. If you're earlier than that, start with the three categories of consulting work, which decides which tasks should go to AI at all.

Five workflows worth making permanent

What these have in common: they come up every week, the shape of the work barely changes, and each run gives you a chance to sharpen the prompt.

1. The discovery dossier

Before any discovery call, produce three things: a company brief, a brief on the person you're meeting, and a fit flag. It's three prompts, top to bottom, in one conversation, and it takes a few minutes. Article 3 covers it in full.

It's worth making permanent because discovery calls are frequent, the prompts don't change from call to call, and the prep is exactly the kind that gets skipped when the calendar is full.

2. The meeting debrief

After every meaningful client meeting, paste the transcript and get back the decisions made, the action items, the surprises, and a read on the room. Article 5 has the prompts.

By hand, a debrief takes long enough that it's the first thing dropped in a busy week, and then the context is gone by the time you're back on the engagement. With a prompt, it takes a few minutes, so it actually happens.

3. The deliverable section expander

Outline, then bullets, then an AI prose pass, then your edit. The bullets and the edit are yours; the prose in between is Claude's. Article 2 explains why this order matters.

Every deliverable is made of sections, so the time saved repeats section after section. On a memo with eight sections, that adds up to hours.

4. The proposal chain

Eight prompts that take a deal from discovery debrief to signed proposal: debrief, ICP fit check, scope, pricing, draft, objection handling, follow-up sequence, and a deal debrief. Each step's output feeds the next.

It's substantial enough to be its own product, the Proposal-Closer Prompt Pack. Proposals are the most frequent writing task in a practice, and the chain stops steps from being forgotten. The one most often skipped without it is the deal debrief, which is the step that makes the next proposal better.

5. The case-study harvest

Within two weeks of an engagement wrapping, turn the project debrief into a case study and three posts for your newsletter or LinkedIn. It takes about half an hour when the engagement left good notes behind.

It's worth doing on a schedule because the details that make a case study believable fade fast, and the harvest captures them while they're fresh.

Workflows that sound better than they work

AI as a strategy partner. The pitch is to paste in your business situation and get strategic advice back. What comes back tends to sound right and miss the texture that makes a decision strategic: the political dynamic with the client, the constraint that isn't written down, the thing your gut is telling you. That's Category 1 work. AI is weak at it and sounds confident anyway.

AI-drafted everyday client emails. Most client emails are short, so the time Claude saves drafting one is often lost to editing out the AI flavor. Long emails are a different story, and so are kickoff emails after a deal closes, which have a structure worth templating. For day-to-day correspondence, writing it yourself is usually faster.

Prompting straight for thought-leadership posts. Asking for "ten LinkedIn posts from this engagement" tends to produce readable, generic posts with the usual AI tells: three-part lists, summary paragraphs, hedged claims. The fix isn't a cleverer prompt. It's the section-expander order again: your bullets first, a prose pass, then a hard edit.

Coding help, for most consultants. If your engagements don't involve code, Claude as a coding partner isn't relevant to your practice. Claude Code is a different matter for anyone automating their own operations; we use it to run this store's publishing scripts. That's a workflow for running a business, not for client work.

The setup that makes the rest work

Two things that aren't workflows on their own but make all of the above better.

One Claude Project per client

Give each active client their own Project, with instructions covering their industry, the engagement scope, how they write, and any constraint that isn't in the brief. Keep every conversation about that client inside it. Claude then works from the same context all engagement, and each Project keeps its own memory, separate from your other clients.

This is the most important setup decision of the lot. Without it, every conversation starts from scratch.

Keep your prompts as files

Store the prompts you rely on as files in a prompts/ folder, organized by kind (prompts/proposals/, prompts/meetings/ and so on), ideally with version history. That makes every prompt easy to edit, track and move between machines. Bookmarks and Notion pages work, but files hold up better as the collection grows.

What a day can look like

An illustrative Tuesday, with these workflows in place:

The AI work on a day like this is a series of short runs, each attached to a task that would happen anyway.

Where this fits, and where it doesn't

These workflows suit project-based consulting best, where much of the value is in the deliverables. They fit less well in retainer advisory work, where the conversation is the product. How much of your week is Category 2 versus Category 1 decides how much of this applies to you.

Don't adopt all five at once. Pick one, run it for two weeks, and keep it only if it earns its place.

Going deeper

All five workflows are covered in The Solo Consultant's AI Playbook, whose chapters map closely onto the list above. The Playbook is the full operating model with the prompts.

The proposal chain has its own deeper version in the Proposal-Closer Prompt Pack: eight prompts, a Claude skill, and the Acme Widgets worked example.

And if you want these workflows out of chat entirely, the Claude Workspace Kit is the setup as a folder: standing instructions, context files, four written standards and six ready-to-run briefs. It ships filled in for a fictional practice, including a client folder holding a week of messy notes, so you can see the shape before building your own.

Everything we make for setting Claude up to do client work is on one page: Claude for Solo Consultants.

— Digital Kreative