AI shouldn't require a second career.

Point Claude at a folder that already holds your practice — the context, the standards, the briefs. Raw notes in, finished client files out. Built for solo consultants and small agencies.

The shortest path

Start free. End with Claude doing the work.

Begin with the free brief. If it earns its place in your week, the Workspace Kit is the same idea applied to everything else you do.

Already running the practice and stuck on one thing? These fix a named bottleneck instead.

The bottleneck

Friday, 2 p.m. The proposal is due by 5.

You wrapped a discovery call on Tuesday. The prospect is warm. The proposal is supposed to land before they leave for the weekend, because the followups go cold over Saturday.

It's now Friday. You open Claude. You type "write a proposal for a B2B SaaS doing onboarding consulting." You get something generic. You rewrite most of it. You second-guess the price. You stare at the scope for twenty minutes. The clock keeps moving.

Three hours later, you send the proposal. It's fine. Not great. Sent.

That's the workflow most consulting AI tools quietly assume you're stuck with — open AI, write a vague prompt, edit the output, ship a thing that's 70% as good as what you'd write with a clear head and unlimited time. We built a pack for the version where that takes 25 minutes instead of three hours, and the proposal is sharper because each step in the chain feeds the next.

See the eight-prompt workflow →

Why most AI products fail you

A pack of 100 prompts is a pack of 100 vague ones.

You've bought one of the megapacks before. Forty-seven dollars, 120 prompts, "10x your output." You opened the zip, scanned three prompts, closed the tab. Two months later you found it in a Notion page titled "to organize."

That's the structural problem with volume-optimized AI products: the prompts that actually produce useful consulting output need three things that don't scale linearly with prompt count.

  • Context. A useful prompt knows what kind of work you do, who your buyer is, and what your hourly rate looks like. Generic prompts know none of this.
  • Cross-prompt continuity. Real consulting work is a chain — discovery debrief feeds the ICP check, which feeds scope, which feeds the proposal. A folder of 100 standalone prompts has no chain.
  • Worked examples. Without an example of what good output looks like for a specific situation, the prompt is a guess. With one, it's a recipe.

Tightening one prompt to all three of those takes a worked walkthrough, an example, and a pitfall section. By the time you've done that for ten prompts, you don't have 100 prompts anymore. You have eight or ten well-built ones that actually run.

Read the journal →

Built by operators, for operators.

Most AI products are pitched at everyone. Ours aren't. We build for the hour of your week when a discovery call becomes a proposal, a client becomes onboarded, a finished engagement becomes a case study. Everything here is battle-tested on real deals, not authored from a template.

What outcome-specific looks like

One prompt, one job, one shape of output.

"Outcome-specific" is the kind of phrase that sounds like marketing until you see one. Here's the actual opening of the Discovery Debrief prompt — the first of eight in the Proposal-Closer Pack. You paste raw call notes. You get back a structured debrief in five minutes.

Excerpt — Discovery Debrief promptYou are my deal strategist. I'm a solo consultant. I just finished a discovery call with a prospect. I'm going to paste raw notes below. Your job is to produce a structured debrief I can act on in 5 minutes. Return exactly these sections, in this order: 1. Who & what they do (2 sentences max). 2. The real problem — not what they said they wanted; what they actually need. 3. Budget signal — direct, indirect, or none. Quote the specific phrase. 4. Decision process — who decides, who influences, what's the timeline. 5. Red flags — scope creep, payment, expectation mismatch. Be direct. 6. Recommended next step — send proposal, paid discovery, disqualify, or ask 2 clarifying questions. Voice: direct, no hedging. Assume I'm reading this between meetings.

That output then feeds the next prompt (ICP fit check), which feeds the next (scope), which feeds pricing, which feeds the actual proposal draft. Eight prompts. One workflow. Run end-to-end the same way every time.

Open the Pack →
  • Outcome-specific

    Everything solves one named job. Close a proposal. Onboard a client. Debrief a deal. No 'general productivity' grab-bags.

  • A system, not a bag

    Eight prompts chained together beat a hundred standalone ones. Each step's output feeds the next. The ladder is the product.

  • Claude-first, not warmed-over

    Built for the tool serious operators actually reach for. The prompt-based products carry ChatGPT-compatible notes; the two Kits are Claude-only by design, and we say so.

The receipts

Specific work, specific time saved.

25 min
vs. 90+ min · proposal end to end

Article 11 walks the eight prompts of the Proposal-Closer Pack through a real engagement (Acme Widgets, $4M ARR SaaS, $12,700 deal). Discovery debrief, ICP check, scope, pricing, proposal draft, objection handling, follow-up sequence, deal debrief. Each step's output feeds the next.

See the Pack →
10 SOPs
for the work that breaks at 2-3 clients

The first time something falls through the cracks, it's a slip. The fifth time, it's a system problem. Kickoff emails sent late, invoice nudges forgotten, scope-creep conversations postponed, case studies never harvested. Ten written procedures that catch each one.

See the SOP Bundle →

Current catalog

Which one is for you

Pick the thing eating your week.

Each row names a problem and where to start on it. Every one has a free way to test the idea before paying for anything.

It all works, but nothing is repeatable. Good output one day, mush the next, and no reliable way to tell what changed. Every engagement starts from scratch, and the same setup gets retyped into every new chat. Test it free with the Friday Update Brief — one brief, ten minutes.
Workspace Kit · $97
Proposals are eating your week. Three hours each, slightly different every time, sent late on Friday. Test it free with the Discovery Debrief — it's the first prompt in the chain.
Pack · $37
You want Claude to know your practice, but you work in chat. No folders, no files — you just want every conversation to start already knowing your clients, your offers, and how you write.
Project Kit · $47
Operations slip at two or three active clients. Kickoffs, weekly updates, invoices, retros — the work between the work.
SOP Bundle · $127
You want the operating model first. The whole approach to AI-native consulting end to end, before drilling into one workflow. Pair it with the Pack and save, or take everything at once.
Playbook · $47
You'd rather just have all of it. The Playbook, the Pack and the SOP Bundle together — or the Playbook and Pack on their own as the Starter Bundle.
Mega · $177

Still not sure? Start here — it walks the same question in a bit more detail, and it's free to read.

1 of 3

The honest version

Who this isn't for.

The catalog is built for one persona: solo consultants and small-agency owners (1-5 people) who already use Claude or ChatGPT and have done at least ten engagements. If that's not you, here's the honest call:

  • First-time consultants. The workflows assume you have scar tissue from past engagements to map them onto. Without that, the prompts and SOPs read like theory. Bookmark for later.
  • Anyone running zero active engagements right now. Procedures without engagements are filing cabinets without files. The kit pays back when you actually run it on real client work this week.
  • Anyone expecting AI to replace the parts of consulting that need judgment. It can't. The whole catalog argues against trying. If your pitch is "AI will write my deliverables for me," this isn't that pitch.
  • Anyone who reads books and doesn't apply them. The $37 Pack pays back the first time you run it. The $177 Mega Bundle pays back inside a month. Neither pays back if it sits in your downloads folder.

If you read those four and still want in, you're the right buyer. The rest of the page is for you.

Pre-empted objections

The questions you're already asking.

I already have Claude working. Why do I need any of this?

Because working and working the same way twice are two different problems. Good output one day, mush the next, and no reliable way to tell what changed between them. The setup gets retyped into every new chat, and last month's hard-won fix is gone with the conversation it lived in. A prompt is something you retype; a brief is something you version. Six months in, your briefs carry every correction you've ever made to them — a chat window cannot accumulate that. Standards do the same job for quality: they turn "I'll know it when I see it" into a test the work either passes or it doesn't. That's the whole difference between having Claude working and having it work the same way twice.

Is this a consultant OS?

That's the phrase a lot of people search for, so: close, but it's a different shape. The products on that shelf are usually built inside a workspace app and they organise records about your work — clients, projects, invoices, statuses. These sit in a folder on your machine and produce the work itself: you point Claude at the folder, hand it raw notes, and get a finished proposal, case study or client update back as a file. If you already run something for tracking, this doesn't replace it. It fills in the part where the writing actually gets done.

Is this just a repackaged ChatGPT prompt list I could write myself?

No, and that's the most honest answer. You could write versions of these prompts yourself. The catalog's bet is that you won't, because writing them well takes the worked example, the pitfall list, the cross-prompt continuity — the parts that turn a prompt into a workflow. Every product is a system that runs end to end on real client work, not a folder of standalone screenshots. The Pack ships with an Acme Widgets walkthrough that proves the chain. The SOPs ship with a paired Claude prompt for the AI-tractable steps in each one.

Do I need Claude, or does ChatGPT work?

It depends which product. The Proposal-Closer Pack, the Playbook and the SOP Bundle all carry ChatGPT-compatible notes, and the prompts run there with no edits — Claude is sharper on structured business reasoning, so it's the recommended default, but it isn't required. The two Kits are Claude-only by design: the Project Kit configures a Claude Project, and the Workspace Kit is a folder Claude works in directly. Neither has a ChatGPT equivalent and we'd rather say so than imply one.

What's the difference between all of these?

Two groups. The Kits set Claude up: 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. The rest solve a named bottleneck — the Pack is the deepest workflow on one job (proposals, eight chained prompts), the Playbook is the operating model across the whole practice (eight chapters, 19 prompts), and the SOP Bundle is the operational layer of ten written procedures for the work between the work. The Starter Bundle pairs the Playbook and the Pack; the Mega Bundle adds the SOP Bundle to those two, three products in one zip at $34 off.

Will I get updates when you ship new versions?

Yes — free for life. When any product ships a new version, you get an email with a fresh download link. Bundles re-zip when any constituent product updates. No re-purchase, no upsell.

What's the refund policy?

No refunds on digital products once downloaded. If something genuinely doesn't work for your situation, reply to your purchase receipt and we'll make it right — exchange, partial credit toward a different product, or a hand-write fix. We've never had to send a "no" to that email.

AI shouldn't require a second career.

Start with the free brief. Ten minutes tells you whether the rest is for you.