What this site is
Consultant Stack is a working notebook for people who sell expertise on their own. Every article here documents a workflow that has been run end to end: the prompt, the tool, the output, and where it still needed a human to fix it.
There are no tool roundups and no "top 50 AI apps" lists. The unit of content is one repeatable workflow that saves a specific block of time in a specific part of consulting work.
Who it is for
Independent consultants, freelance strategists, fractional operators and solo specialists who already have clients and are now the bottleneck for their own delivery. If you are still looking for your first client, this site will not help you yet.
What gets covered
Research & diagnosis
Turning a vague client brief into a scoped problem statement, a source list and a first-pass hypothesis set.
Proposals & pricing
Drafting scope, assumptions and options from call notes, so a proposal goes out the same day as the conversation.
Delivery artefacts
Producing the deck, the memo and the model from one source of truth instead of rewriting the same argument three times.
Admin & operations
Invoicing, follow-ups, project hygiene and the record-keeping that solo consultants quietly skip.
How it is written
Each workflow is tested before it is published. Where a step failed, the failure is written down next to the fix. Anything that could not be reproduced is labelled as such rather than presented as a recommendation.
Products
Two working kits for solo operators, built from the same material as the notes on this site. Both are one-time purchases — no subscription, no community, no upsell.
Solo Consultant Prompt Vault — $19
Sixty AI prompts for the admin side of client work: pricing without apologising, saying no without losing the client, chasing an invoice that is three weeks late. Four files, instant download.
The Freelance OS — $39
Seven linked Notion databases that answer one question: is this month actually working? Includes the Money Leak view, which shows every project where actual hours beat the estimate.
Published notes
-
The Proposal Doesn't Need Writing. It Needs Deciding.
A proposal is a decision transcribed, not a document written. What to settle before drafting, what to hand to a model, and the failure that costs money.
-
The Client Brief Is a Draft, Not a Specification
A brief describes a problem in the language of a solution. How to convert it into a scoped, falsifiable question before any analysis starts.
-
The Meeting Notes Are Not the Work. The Decision Log Is.
Notes record what was said. A decision log records what was settled, who decided, and what would reverse it.
-
Define Done Before You Start, or Argue About It Later
A deliverable list says what you produce. A definition of done says when you stop and how you prove it.
-
Scope Doesn't Creep. It Gets Invited.
Scope grows through small requests that were each reasonable to accept. Three sentences that set the default before it does.
-
The Four Seconds After You Say Your Price
Why the silence right after you name a number decides the deal, and what to say when the client pushes back.
-
Answering “That’s Too Expensive” Without Discounting on Reflex
Too expensive is rarely a price complaint. Four shapes of the objection, and the response that fits each one — neither discount nor defence.
-
Four Numbers Every Freelance Tracker Should Calculate
Trackers record hours and call it bookkeeping. Four calculations turn the diary into a business: overage, actual rate, days to payment, deadline slides.
-
The Monday Review: Is Your Consulting Business Actually Alive?
Four questions every Monday: did the pipeline move, is any project losing money, who owes you what, did anything ship. Twenty minutes, honest answers.
-
Starting a Consulting Business: The Nine Documents That Do the Work of a Business Plan
A business plan lands no clients. Nine documents do — the service page, rate card, call script, proposal, scope clause and invoice chase.
-
How to Estimate Hours Without Lying to Yourself
Estimates run low for structural reasons. Count the edges, estimate in half-days, keep the buffer, and record what actually happened.
-
The Follow-Up Sequence That Doesn't Sound Like Begging
A quiet proposal is not a rejection. Four follow-ups over three weeks, each one giving something instead of asking — and when to stop.
-
The Money Leak View: Finding the Project That Ate Your Month
A fixed-fee project can pay below your day rate without anyone noticing. Three numbers and one view expose it while it is still small enough to act on.
-
What Actually Belongs in a Weekly Client Status Update
An update is not a summary. Six lines answer the five questions your client is silently asking — and cut the "just checking in" emails for good.
-
The Three Numbers Behind Every Hourly Rate
Most rates are a guess with social proof. Billable hours, the cost of staying open and the value of the outcome set the real number.
-
Delivering Bad News Without Losing the Relationship
Bad news early is an update; the same news late is a breach. Four sentences, one choice, and no apology paragraph.
-
Setting Up Seven Linked Notion Databases Without Watching a Tutorial
Imported in the wrong order, seven linked databases break in predictable ways. Import, fix property types, add relations, then formulas.
-
How to Raise Your Rate Without Losing the Client
A rate increase is a process, not an announcement. Two months notice, four sentences, scope offered instead of a discount.
-
Hourly, Fixed, or Retainer: Choosing by the Shape of the Work
Hourly sells time, fixed fee sells an outcome, retainer sells availability. Four questions about the work tell you which one to use.
-
Turning a Finished Project Into a Case Study With Real Numbers
A case study is retrieval, not writing. Five numbers pulled at project close, one difficulty included, three places to reuse them.
Status: this site is being built in public. Twenty long-form notes are published so far; the rest of the workflow library is still being written and tested. There is no newsletter signup until there is an issue to send.
Start here
Read about this project to see who is behind it, what is already written, and how to get in touch with a workflow you want tested.
Ask a question about the work
Tell me what you are trying to solve. I read every inquiry and reply within a day or two.