Claude Workspace Kit for Solo Consultants

Stop pasting your practice into a chat box. Point Claude at a folder that already contains it.

The Claude Workspace Kit is a ready-made workspace folder for consultant client work: standing instructions Claude reads automatically, your context files (ICP, offers, rate floor, voice), written standards for what finished work looks like, six ready-to-run engagement briefs, and a folder-per-client convention with raw material in and finished deliverables out — as files, not chat scroll. Built for Claude Cowork (open the folder — no terminal), works identically in Claude Code, and its context files load into a Claude Project.

The ten-minute proof

The kit ships with the whole thing filled in for a fictional practice — including a client folder holding a week of messy notes. Step 0 of the setup guide: open that folder in Cowork and say “Run brief 04 for the Acme client.” Claude reads the brief, the client's context file, and the notes — and writes a client-ready Friday update into the deliverables folder, under the client's word cap, minus the two things in the notes that shouldn't be in an update. Raw material in, finished file out, against your standards. That's the product. Then you spend 45 minutes making it yours.

What you get

• The workspace — a structured folder with CLAUDE.md standing instructions: files are ground truth, gaps get marked [NEEDED: …] instead of filled with plausible inventions, your rate floor is a hard line, deliverables land as dated files and raw inputs are never overwritten.
• Three context templates — who you serve, what you sell and at what floor, how you sound — with sane defaults and a filled example to calibrate against. (Same skeletons as our Claude Project Kit; filled Kit files paste straight in.)
• Four deliverable standards — what a finished proposal, case study, client update, and internal memo must look like. The standard defines “done,” so output quality stops depending on how you phrased the ask.
• Six engagement briefs — whole deliverables you hand over in one line: discovery transcript → proposal draft · project artifacts → case study · a month of notes → pipeline memo · a week of activity → Friday update · engagement close → offboarding + referral ask · scope-change request → scope memo + reprice options. Each brief: objective, inputs checklist, constraints, what done looks like, and the review pass you run before anything ships.
• Three consultant-type presets — marketing, strategy, and fractional-ops overlays that re-tune vocabulary, emphasis, and output standards for your kind of consulting. Two moves to install; five minutes.
• A complete worked example — the whole workspace filled in for a fictional funnel-diagnostics practice (the same Acme Widgets through-line as our other products), with a brief already run so you can see the input and the output side by side.

Who this is for

Solo consultants and small-agency owners (1–5 people) who bill $100–$250/hr, use Claude for client work most days, and want the work happening in their files with their standards enforced — not re-assembled in a chat window every time.

Who this is not for

• Anyone not yet using Claude on real client work — the templates organize a practice; they don't invent one.
• Developers looking for a software-project scaffold — this workspace is consulting work (proposals, case studies, client updates), not code.
• Anyone whose AI tool is ChatGPT — the kit is honest about being Claude-specific. The standards and briefs would transfer as thinking; the workspace mechanics wouldn't.

Why now

Claude stopped being just a chat window. With Cowork and Claude Code, it works directly in your folders: reads what's there, writes finished files back, and holds a whole deliverable together in one run. That shift is exactly what a consulting practice needs — but only if the folder it lands in is set up for client work. Free guides tell you what such a folder should contain; this kit ships it assembled, with the judgment already encoded.

What it won't do

It won't do the judgment, the relationships, or the advice you actually bill for. The briefs are explicit that delegation is not abdication — every one ends with the review pass you run before anything leaves the workspace. And nothing here fabricates: gaps surface as [NEEDED] markers, not plausible filler.

Format & delivery

• Instant download, one zip — plain-Markdown files in a structured folder. No lock-in: it's your file system.
• Built for Claude Cowork (no terminal, no plugins); works identically in Claude Code; context files upload to a Claude Project. Any current Claude model, any paid plan.
• Free updates for life — new briefs and presets arrive as fresh download links.

Pairs with

• Claude Project Kit ($47) — the chat-side companion. The Project Kit sets Claude up to know your practice in chat; the Workspace Kit sets Claude up to do the work in your files. Same context skeletons on purpose — fill once, run both.
• Proposal-Closer Prompt Pack ($37) — the steered mode: eight chained prompts with your judgment gating every step. The Workspace's brief 01 is the delegated mode of the same job. Messy engagements want the Pack; clean ones want the brief.
• The Solo Operator's SOP Bundle ($97) — ten written procedures for the recurring work. The Workspace's standards and briefs are the delegated versions of several of them; the SOPs are the full operating manual.

FAQ

How is this different from the Claude Project Kit — do I need both?
Different surface, different job. The Project Kit lives in Claude's chat app: instructions and knowledge files that make every conversation start informed. The Workspace Kit lives in your file system: a folder where Claude reads raw material and writes finished deliverables as files. If you work in chat, start with the Project Kit. If you want work landing in folders — or you're Cowork-curious — start here. They share context-file skeletons deliberately, so owning both means filling in once.

Do I need to use a terminal?
No. The kit leads with Claude Cowork — you open a folder in an app. Claude Code (the terminal version) works identically and is covered in one short section, but nothing in the kit requires it.

Do I need a specific Claude model?
No. The workspace works with whatever Claude model you run — it builds on files and instructions, not on any model's features. More capable models produce better long runs; the folder is the same either way.

Can't I build this myself from free setup guides?
Yes — the guides tell you a workspace needs instructions, context, and conventions. The kit ships the finished artifacts: tested instructions with the anti-fabrication and rate-floor rules written, standards that define done for four deliverable types, six briefs with their review passes, and a worked example proving the loop. You're buying the assembled version of a weekend of assembling — plus the parts you wouldn't know to include until something went wrong.

What do I have to fill in?
Three context files (who you serve, what you sell, how you sound — about 25 minutes with the example open) plus one short context file per active client (5 minutes each). A ten-minute test drive on the worked example comes first, so you see it working before you invest the 45.

Refund policy?
We don't do refunds on digital products once downloaded, but if the kit genuinely doesn't work for your situation, reply to your purchase receipt. We'll make it right.