A field guide · October 2026

The Micro-Consulting Playbook

Small AI engagements that clients say yes to
by Mat Siems
Part I

The Micro-Offer

What a small engagement is and why clients say yes.

Chapter 1 · Part I

Small Enough to Say Yes To

This is a book about small work. Not small in ambition, small in shape: an engagement with a fixed scope, a short calendar and one deliverable a client can point at when it is finished. A paid audit of how a team uses AI. A fix for one painful workflow. A kit of tested prompts. A two-week agent pilot. A half-day training session. A documentation sprint that turns tribal knowledge into something a model and a new hire can both read. Each one is easy to buy, quick to deliver with Claude, and designed to lead to the next.

Why small? Because the hardest part of consulting has never been the work. It is the yes. A large engagement asks a buyer to commit budget they have not got, to a person they have not tested, for an outcome they cannot yet picture. A small one asks them to risk a little money on a specific result by a specific date. The first conversation goes to committee. The second goes to a card payment, or at worst to a manager who can sign without a meeting.

There is a second reason, and it is the one that makes this the right moment. Agentic tools have collapsed the effort behind a large class of useful work. What once took a consultant three weeks of reading, drafting and building now takes a few focused days with Claude doing the reading, drafting and much of the building. If you sell that work by the hour, the tooling makes you poorer. If you sell it as a fixed outcome, the tooling makes you a business. The micro-engagement is simply the commercial shape that fits the new economics.

A small yes is still a yes. It is also the only kind a stranger can give you.

The book is built on a hundred moves, grouped into ten parts. The early parts cover the offer itself and the craft you will use to deliver it: how to brief a model, how to feed it context, how to work in a repository with Claude Code, how to encode repeatable work as skills. The middle covers shipping, delivery and the shape of a price, without ever naming a number, because your numbers depend on your market and nobody else's. The last parts cover proof, pipeline and where this is all heading. Every chapter is either a move you can make this week or a micro-engagement you can run, and most chapters end with a nudge to try it.

One warning before we begin. Small engagements are not a lesser form of consulting. They are harder to do well, because there is nowhere to hide. A twelve-month programme can absorb a bad fortnight. A two-week sprint cannot. You will need to scope tightly, deliver visibly and measure honestly. In exchange you get faster feedback, happier clients and a pipeline that refills itself. The trick, it turns out, is not to sell more. It is to sell less, sooner, and then do it again.

Why the small yes is easier to give Large engagement Small engagement THE MONEY Budget not yet held A little, at risk THE OUTCOME Hard to picture A specific result THE DATE Open-ended A specific date WHO SIGNS A committee Card or one manager EFFORT WITH CLAUDE Three weeks A few focused days SIX SHAPES OF SMALL WORK Audit Fix sprint Prompt kit Agent pilot Training Doc sprint A small yes is still a yes, and the only kind a stranger can give.
Fig 1 · Small Enough to Say Yes To. Large versus small engagements: what each asks of a buyer, and six shapes of small work.
Chapter 2 · Part I

Sell Outcomes, Not Hours

Hourly billing has one quiet flaw that becomes a loud one the moment you start working with Claude: it punishes you for getting faster. Every hour the tooling saves you is an hour you cannot invoice. Become twice as quick and, on a day rate, you have halved your income for the same result. Nobody designs a business that way on purpose. Plenty of consultants drift into it by default.

The alternative is to price the outcome. The client is not buying your attendance; they are buying an audited workflow, a working pilot, a trained team, a set of prompts that produce compliant copy on the first attempt. Describe that thing precisely, put one price against it, and agree a date. How long it takes you is now your business, not theirs. When Claude does in an afternoon what used to take a week, the efficiency is yours to keep, and it funds the next improvement in your method.

This also changes the conversation with the buyer, mostly for the better. A day rate invites haggling over inputs: why does this need five days, could it be four, who is on the team. A fixed outcome invites a discussion about value: what is this worth to you, what happens if it works, what does done look like. The second conversation is more useful to both parties and much less exhausting. It also forces you to define done, which, as later chapters will argue, is the single most valuable habit in this kind of work.

It is worth saying plainly what you are refusing. Staff augmentation, renting yourself out by the day to sit inside someone else's team, is a perfectly respectable job. It is just not micro-consulting. It makes you a contractor with extra steps, paid for presence rather than results, and it scales exactly as far as your calendar. The micro-consultant's deliverable is a system, a document, a capability or a decision. Your attendance is incidental.

Bill for the hole, not the drill. Especially now the drill is doing most of the work.

There are honest risks. A fixed outcome means you carry the overrun if you scoped badly, and some work genuinely cannot be bounded in advance. The answer is not to retreat to hourly rates. It is to scope smaller. If you cannot describe the outcome with confidence, sell a paid discovery that produces the description, then price the outcome once you can see it. Uncertainty is a reason to shrink the first engagement, never a reason to unfix it.

Try this on your current offer. Rewrite every line item that mentions days or hours as a noun the client will own at the end. Five days of AI consulting becomes a ranked list of the six workflows worth automating, with a working prototype of the first. It reads better, it sells better, and it quietly commits you to something you can actually be proud of. Your hours were never the product. They were just the only thing you knew how to count.

Getting faster: who keeps the gain? INCOME PER JOB Fixed outcome Day rate halved 1x 2x SPEED WITH CLAUDE REWRITE EACH LINE ITEM Five days of AI consulting an input you count Six workflows, ranked + a prototype of the first Hours invite input haggling Outcomes invite value talk Bill for the hole, not the drill. The drill is doing most of the work now.
Fig 2 · Sell Outcomes, Not Hours. Day rates fall as you speed up; fixed outcomes keep the gain. Rewrite inputs as nouns.
Chapter 3 · Part I

The Diagnostic Call

The first call with a prospective client is not a pitch. It is a diagnosis. Most consultants waste it by explaining what they do, which the buyer could have read on the website, instead of finding out what is wrong, which the buyer may not fully know themselves. The expensive problem rarely arrives in the first sentence. It arrives around question twelve, after you have stopped talking.

Go in with a list. Twenty questions is a good number, though you will not ask them all. Start with the work, not the technology: walk me through the last time this went wrong, who touched it, how long did it take, what did it cost, what did you do instead. Then move to the edges: what have you already tried, who would need to approve a change, what happens if nothing changes this quarter. Only at the end ask about tools, and even then ask what they use rather than what they want. People describe their aspirations in terms of software. They describe their problems in terms of Tuesdays.

Claude is useful on both sides of the call. Before it, paste in what you know about the business, their public material and the sector, and ask for a tailored question list ranked by how likely each is to surface a costly problem. After it, paste in your notes or a transcript, with permission, and ask for a structured summary: the presenting problem, the underlying problem, who owns it, what it costs, and which micro-engagement would address it. That summary becomes the first page of your proposal and, more usefully, the thing you send back the same afternoon so the buyer can correct it.

The correction matters. A buyer who edits your summary of their problem has started co-writing the proposal. They now own part of the diagnosis, and people rarely reject diagnoses they helped write. Keep the summary short, a single page, in their language rather than yours. If you find yourself writing leverage or synergy, ask Claude to rewrite it in the vocabulary the buyer used on the call.

Pitching on a first call is like prescribing before the patient sits down.

There is an art to ending the call, too. Do not close by offering a proposal. Close by naming the problem back to them, in one sentence, and asking whether you have it right. If they say yes, tell them what a small first step would look like and when you can send it. If they say no, you have just learned something far more valuable than a sale, and the call is not over.

Try it this week. Write your twenty questions, ordered from work to edges to tools, and keep them in a note you can open on any call. Then run your next conversation without describing your services until the last five minutes. You will talk less, learn more and quote on the right problem. The buyer will remember you as the person who listened, which in this market is a surprisingly rare distinction.

Diagnose first, describe yourself last Claude You Buyer BEFORE Their material + sector Ranked question list THE CALL 1. Work: the last time it broke 2. Edges: tried, approvals 3. Tools: what you use The expensive problem around question twelve AFTER Notes or transcript One-page summary problem · owner · cost · offer Summary, same afternoon Corrections: co-writing it Close by naming the problem back, then ask: have I got it right?
Fig 3 · The Diagnostic Call. The diagnostic call as a sequence: Claude prepares, you ask, the buyer corrects.
Chapter 4 · Part I

The Paid Audit

The fixed-scope AI audit is the best front door a micro-consultant can build. It is low risk for the buyer, fully paid for you, short enough to finish before anyone loses interest, and it ends with a roadmap that you are uniquely positioned to deliver. It is a sale that manufactures the next sale, provided you run it properly.

The shape is simple. Over a week or two you interview a handful of people, observe how work actually flows, review the tools and data in play, and produce a ranked list of opportunities. Each opportunity gets a short description, an honest estimate of value, an estimate of effort, a note on risk, and a recommended micro-engagement to address it. The top two or three are scoped tightly enough to be bought straight off the page. The rest are parked, visibly, so the client sees you are not simply selling everything you found.

Claude makes the audit faster without making it shallower. Interview transcripts go in, with consent, and come out as themes, quotes and repeated complaints. Process descriptions turn into simple flow diagrams you can check with the people who described them. A spreadsheet of tasks can be scored against a rubric you write together with the client. The synthesis that used to take days of rereading notes becomes an hour of reviewing and correcting what the model drafted. Your time goes where it should: on judgement about which opportunities are real.

Be strict about what the audit is not. It is not free, because free audits are treated as samples and their recommendations as opinions. It is not a strategy deck, because nobody in a small business acts on strategy decks. And it is not open-ended. Fix the number of interviews, the number of opportunities you will rank, and the date of the readout. When the client asks you to look at one more department, smile and add it to the list of things the next engagement could cover.

An audit that does not end in a decision is just an expensive way to feel modern.

The readout is where the audit earns its keep. Present the ranked list live, explain the top three, and show a rough prototype of the first if you can, even a single artifact built the night before. Then ask which one they want to start with. Not whether. Which. The audit has done its job if the buyer leaves the meeting choosing between your next engagements rather than wondering whether to have one.

To build your own, write the deliverable first. Draft a sample audit report for an imaginary client in your sector: the ranked table, the three scoped recommendations, the parked list. Then work backwards to the interviews and reviews you would need to fill it honestly. You now have a product, a template, and a fairly good idea of what you are selling. Most consultants describe their audit. Very few have one they could show.

The audit narrows everything to one choice Interviews, flows, tools Every opportunity found Scored: value, effort, risk Top three, scoped Readout: which one? not whether Parked, visibly not hidden CLAUDE DRAFTS Transcripts to themes Processes to flows Tasks to rubric scores FIXED UP FRONT Number of interviews Opportunities ranked paid · bounded · dated An audit that does not end in a decision is an expensive way to feel modern.
Fig 4 · The Paid Audit. The paid audit funnel: from every idea to a scored top three and a readout choice.
Chapter 5 · Part I

The Two-Week Sprint

If the audit is the front door, the sprint is the first room. Two weeks, one problem, one working result. It is long enough to ship something real and short enough that nobody needs board approval, a procurement process or a steering committee. Most importantly, it is short enough that momentum survives. Long engagements do not usually fail from bad work. They fail from fading attention.

Two weeks has a natural rhythm. Day one is access and kick-off: credentials, a named decision-maker, a written definition of done. The first week is building, in small increments, with a demo at the end of it. The second week is refining, testing against real cases and preparing the handover: the runbook, the prompts, a short recorded walkthrough, a session with the person who will own it. On the last day you demo the finished thing, show the measured change, and propose what comes next.

With Claude as your delivery partner, two weeks holds a surprising amount. A workflow automation that reads incoming documents, extracts what matters and drafts a response for a human to approve. A small internal tool built as a single-file prototype and then hardened. A skill library for a team's recurring writing tasks. An agent pilot running against a sample of last month's real work. None of these are trivial, but all of them fit, provided the scope is one problem and not three.

That proviso is the whole discipline. The sprint lives or dies on the definition of done you write on day one. Make it specific, checkable and in the client's words: the team can process a week of supplier invoices with the assistant, and nine out of ten drafts need no more than light edits. Avoid adjectives like robust or seamless, which describe how you feel rather than what you can test. If you cannot write a definition of done in two sentences, the sprint is too big. Split it.

Two weeks is not a deadline. It is a container, and containers are what keep things from spreading.

There will be pressure to stretch. A client sees early progress and asks whether you could also handle a related process. The answer is yes, in the next sprint. Write it down, put it on the list for the closing demo, and keep going. A sprint that finishes on time with a smaller scope builds more trust than one that finishes late with everything in it.

Try sketching three sprints you could sell tomorrow. For each, write the problem in one line, the definition of done in two, and the handover pack in three. If any of them needs more than that, it is a programme pretending to be a sprint. Shrink it until it fits on a card. Small, finished and demonstrated beats large, nearly done and explained, every single time.

Two weeks, one problem, one working result Week 1: build in increments Week 2: refine, test real cases DAY 1 DAY 5 DAY 10 Kick-off access · owner · done First demo progress, shown Final demo measured change + next Handover pack runbook · prompts · walkthrough · owner A related process? yes: next sprint Done: two sentences, checkable, in the client’s own words. e.g. nine of ten drafts need only light edits
Fig 5 · The Two-Week Sprint. A two-week sprint timeline from kick-off to final demo, with the handover pack.
Chapter 6 · Part I

Name the Thing

An unnamed service is a favour. A named one is a product with a price. This sounds like marketing whimsy, and partly it is, but it rests on a practical truth about how buyers think. People file things by name. A bit of help with our AI stuff goes in the mental drawer marked miscellaneous, which is also where budget goes to die. The Inbox Triage Sprint goes in a drawer of its own, beside other things that cost money and produce results.

A name does three jobs at once. It tells the buyer what they are getting before you explain it. It lets them repeat it to someone else, which is how referrals travel. And it constrains you, because once the engagement has a name it has a shape, and shapes resist the kind of slow sprawl that turns a fixed-scope job into an open-ended one. The Prompt Kit for Customer Support cannot quietly become a CRM migration. The name would object.

Good names are plain. They say what the thing does, for whom, and sometimes how long it takes. The AI Readiness Audit. The Two-Week Agent Pilot. The Policy Documentation Sprint. The Team Claude Workshop. Clever names that need explaining defeat the purpose. If you have to describe the name before you can describe the service, you have built a second problem. Leave the wordplay for your blog posts.

Claude is quite good at this, if you brief it properly. Give it the problem the engagement solves, the buyer it is for, the deliverable, the duration and three names you already dislike, and ask for twenty plain options ranked by clarity. Then say the best five out loud to someone who does not work in your field. The one they can repeat back to you an hour later is the winner. Memorability is a test, not a vibe.

If they cannot say it to their boss, they cannot buy it from you.

Once a thing is named, give it a page. One page, with the problem, the deliverable, the timeline, what the client provides, what you provide, and what typically happens next. Do not put a price on the page if your market prefers a conversation, but do make clear that a price exists and is fixed. That page becomes the link you send after a diagnostic call, the attachment to a proposal and the thing a buyer forwards to the person who signs. It does more selling than you do.

Look at your last three engagements this week. Give each one a name, as if you had sold it as a product. Then notice which you would be happy to sell again exactly as described, and which you would want to change. The ones you would sell again are your catalogue. The rest were favours, which is fine, but you should stop pretending they were strategy.

A name turns a favour into a product UNNAMED “Help with AI stuff” a favour Miscellaneous where budget dies NAMED Inbox Triage Sprint a product, a price Its own drawer paid, with results A NAME DOES 3 JOBS Tells what it is Travels by referral Constrains scope One page per named offer price exists, and is fixed Problem in their words Deliverable the noun they own Timeline fixed dates Client provides access, people You provide the work, the kit What comes next the next rung
Fig 6 · Name the Thing. An unnamed favour versus a named product, three jobs of a name, and the one-page sheet.
Chapter 7 · Part I

One Vertical, Deep

Generalists compete with everyone. Specialists compete with almost no one. This is old advice, older than any of the tools in this book, but it matters more for micro-consulting than for most kinds of work, because small engagements live or die on how quickly you can scope them. A consultant who already knows a sector arrives with the scoping half done.

Consider the difference on a diagnostic call. A generalist asks a dental practice how appointments are booked and spends twenty minutes learning the vocabulary. A specialist already knows the booking software they probably use, the regulations that govern patient records, the three tasks that eat the receptionist's afternoon and the reasons previous automation attempts tend to fail. The specialist's first question is the generalist's fifteenth. That head start becomes a sharper proposal, a faster sprint and a client who feels understood rather than interviewed.

Specialising also sharpens your craft with Claude. Every engagement in the same sector teaches you something reusable: a prompt that handles the jargon, a skill that knows the compliance rules, a seed dataset that looks like real records, a checklist of the questions that matter. After five engagements you have a library tuned to one kind of client, and the sixth engagement starts from that library instead of from a blank page. Your margins improve, your quality improves, and your proposals start to read like they were written by someone who has done this before. Because they were.

Choosing a vertical is less mystical than people make it. Look for a sector where you already understand the work, where businesses are small enough to buy without committees, and where documents, messages and repetitive decisions make up a large share of the day. That last test matters, because it is where language models earn their keep. Legal practices, estate agents, accountancy firms, charities, clinics, trades businesses and small publishers all fit. Pick one you can tolerate talking about for years.

The riches are in the niches, as the saying goes. So, more reliably, is the repeat work.

The fear is that specialising shrinks the market. In practice it does the opposite, because a specialist becomes the obvious call, and obvious calls get referrals from inside the sector, where people talk to one another constantly. You can always take the occasional interesting job outside your lane. You simply stop needing to.

Try this as an exercise rather than a commitment. Pick one sector and spend an hour with Claude building a briefing on it: the typical business, its software, its regulations, its recurring pain, its vocabulary. Then write three named micro-engagements for that sector alone. If they come easily, you may have found your lane. If they feel forced, try another. The point is not to find the perfect niche. It is to stop being a little bit useful to everyone.

Where the obvious specialist lives Know the work no vocab lessons Small buyers no committees Document-heavy days messages, decisions Your lane SECTORS THAT FIT Legal practices Estate agents Accountancy Charities Clinics Trades Small publishers The specialist’s first question is the generalist’s fifteenth.
Fig 7 · One Vertical, Deep. Your lane sits where knowing the work, small buyers and document-heavy days overlap.
Chapter 8 · Part I

Productise the Repeatable

The third time you build the same thing, it stops being a project and becomes a product. The first time, you were learning. The second time, you were remembering. The third time, if you are still starting from a blank page, you are simply refusing to notice a pattern. Micro-consulting rewards the people who notice.

Productising does not mean building software. It means turning a repeated engagement into a repeatable one: a fixed description, a standard set of inputs, a template deliverable, a library of prompts and skills that do most of the heavy lifting, and a checklist that tells you what to do on each day of the sprint. The client buys the same named outcome. You deliver it with a fraction of the original effort, at the same price, and with better quality because every previous engagement has sanded down a rough edge.

Claude is the reason this is now realistic for a solo practitioner. In the old world, productising a consulting service meant hiring juniors and writing procedure manuals they would ignore. Now the procedure manual can be a skill that loads itself when relevant, the templates can be generated from structured inputs, and the repetitive analysis can be run by an agent following instructions you wrote once and refined over many runs. The juniors, in other words, are the tooling, and the tooling actually reads the manual.

The trick is to productise from evidence rather than from hope. Do not invent a product and then go looking for clients who want it. Look back at what clients have already paid for, find the engagement you have delivered most often, and write down what you did, step by step, while it is fresh. That write-up is the first draft of the product. Each subsequent delivery refines it. Within a handful of runs you have something you could, in principle, hand to a capable colleague.

A process you can describe is a process you can improve. A process you can only perform is just a habit with an invoice.

Watch for one trap. Productised services can become rigid, and rigid services start fitting clients badly. Keep a small, explicit space for tailoring in every engagement, perhaps a day of bespoke work inside a fixed frame, and be honest when a client's problem does not fit the product. Recommending something else, or nothing at all, builds more trust than forcing a square engagement into a round business.

This week, find your most repeated engagement and write its playbook: inputs, steps, prompts, outputs, checks, handover. Store the prompts and templates where you will find them in ten seconds next time. Then sell it again. The fourth delivery will be faster than the third, and the fifth faster still. That curve is the whole business case for small work, quietly bending in your favour.

The third build is a product EFFORT PER DELIVERY price stays fixed RUN 1 learning RUN 2 recalling RUN 3 pattern! RUN 4 faster RUN 5 faster margin grows The playbook from evidence 1 Inputs 2 Steps, day by day 3 Prompts and skills 4 Outputs and templates 5 Checks 6 Handover Keep a day of bespoke work inside the fixed frame.
Fig 8 · Productise the Repeatable. Effort per delivery falls with each run while the price holds; the playbook captures it.
Chapter 9 · Part I

Pilot to Retainer

A pilot that ends cleanly with nothing left to maintain is a pilot you designed wrong. That is not cynicism about clients. It is a recognition that useful AI systems need looking after: prompts drift as the business changes, models improve and open new options, new edge cases appear, and someone has to notice when quality slips. If the pilot proves value, the natural next step is ongoing care. Design for that from the start.

The design work happens before you write a line of code. When you scope a pilot, ask what will need to happen after it succeeds. Who will monitor the outputs? Who will update the prompts when the product range changes? Who will review the evaluation set each month and add new cases? Who will try the improved model when it arrives? In most small businesses the honest answer is nobody, and that answer is the retainer, offered openly, not sprung as a surprise at the end.

Be explicit about this in the proposal. Describe the pilot, its definition of done and its measured outcome. Then describe, in a short paragraph, what keeping it healthy would involve and what a monthly arrangement would cover. You are not selling the retainer yet. You are making sure that when the pilot succeeds, nobody is surprised that success needs maintaining. Buyers appreciate being told the whole shape of the commitment early.

The retainer itself should be small and specific, like everything else in this book. A monthly review of a sample of outputs against the evaluation set. Prompt and skill updates as needed. A short written report showing what the system did, what changed and what you recommend. A fixed number of small improvements per month. A response window for problems. Avoid the vague retainer that promises ongoing support, because vague retainers get cancelled at the first budget review, when nobody can remember what they were for.

Pilots prove something works once. Retainers prove it keeps working, which is the part the buyer actually needed.

Not every pilot should become a retainer. Some systems are simple enough that a good runbook and a trained champion are all the client needs, and recommending that is honest and occasionally excellent for referrals. But you should decide that deliberately, at the end, based on what the system needs, not drift into it because you never thought about what came after.

Try it on your next proposal. Add a section called after the pilot with three sentences: what the system will need, who could provide it, and what a small monthly arrangement would include. Notice how it changes the conversation. The buyer starts thinking about the pilot as the beginning of something, rather than as an experiment they might quietly abandon. Which, for most AI pilots in most businesses, is exactly what happens otherwise.

Design the after before the pilot starts Pilot prove it works Proved? no Stop and learn yes WHO WILL… monitor the outputs? update the prompts? review the eval set? try the next model? Needs care? no Runbook + champion good for referrals yes Small, specific retainer · monthly sample review · prompt + skill updates · short written report · fixed improvements · response window Pilots prove it works once. Retainers prove it keeps working. say so in the proposal, not at the end
Fig 9 · Pilot to Retainer. After a successful pilot: who keeps it healthy, and when a retainer is the honest answer.
Chapter 10 · Part I

The Offer Ladder

Put the previous chapters together and you get a ladder. At the bottom, something free and small: a teardown, a tool, a useful article, a short diagnostic call. Above it, the paid audit, which finds the problem. Above that, the build sprint, which fixes it. At the top, the monthly retainer, which keeps it fixed and improves it. Every client enters low and climbs, and you never have to invent a proposal from scratch again.

The ladder solves a problem most consultants do not notice they have: every sale is a custom negotiation. Without a ladder, each prospect gets a bespoke proposal, each proposal takes a day to write, and each one is a fresh guess at what the buyer might accept. With a ladder, the question is simply which rung they should start on. A buyer who already knows their problem can skip the audit. A cautious one can start with a teardown. The structure is fixed; the entry point flexes.

Each rung should make the next one feel inevitable. The teardown ends by showing what a proper audit would find. The audit ends with a ranked list whose top item is a scoped sprint. The sprint ends with a working system and a clear description of what keeping it healthy involves. Nothing about this is manipulative, provided each rung is genuinely valuable on its own. A client who stops at the audit should still feel they got their money's worth. Most will not stop, because they have seen what the next step looks like.

Your catalogue of micro-engagements slots into the ladder neatly. Training sessions and prompt kits often sit beside the audit as small, low-risk first purchases. Workflow fixes, documentation sprints and agent pilots are build sprints. Monitoring, evaluation reviews and continuous improvement are retainer work. Map each named offer to a rung and you can see, at a glance, where your gaps are. Many consultants discover they have five ways to start and no way to continue.

A ladder is just a sequence of small yeses arranged so that each makes the next one easier.

Draw yours this week. Four rungs, named offers on each, and a single sentence explaining how each rung leads to the next. Then look at your last ten clients and mark where each one entered and where they stopped. The places where clients stop climbing are where your offers are weakest, or where the bridge from one rung to the next has not been built. Fix the bridge before you add more rungs.

This is the shape the rest of the book fills in. The craft parts teach you to deliver each rung quickly with Claude. The delivery and pricing parts teach you to run each rung cleanly. The proof parts teach you to turn each finished rung into the reason for the next one. The ladder is not the strategy. It is the frame that lets small work add up to something large.

Every client enters low and climbs Retainer keeps it fixed Monitoring Eval reviews Improvement shows what keeping it healthy involves Build sprint fixes it Workflow fix Doc sprint Agent pilot its top item is a scoped sprint Paid audit finds the problem AI audit Training Prompt kit ends by showing what an audit would find Free teardown shows the gap Teardown Free tool Article Diag. call Fix the bridge before you add more rungs.
Fig 10 · The Offer Ladder. The offer ladder: four rungs, named offers on each, and the bridge between them.
Free preview · Part I

Keep reading

You have read the first 10 of 100 chapters of The Micro-Consulting Playbook. The full book has every chapter and plate, as PDF and EPUB in English, French, Polish and Spanish.

The full book is coming soon to the shop.

Already bought it? Read the full edition online

The Micro-Consulting Playbook · First Edition, October 2026
100 chapters · 10 parts · one hundred diagrams
by Mat Siems · MS Books, No. 9 · 2026