Pitch a Services Business Through What Repeats Across Engagements

Two engagements, described in one pitch deck, can look like a company. Or they can look like two impressive things that happened to two different clients in the same year. The difference is rarely the quality of the work. It is whether the presenter has done the comparison.

A services pitch usually fails in a specific way: it shows outcomes and lets the buyer guess at the offer. The buyer sees a before, an after, and a testimonial, and is expected to convert that into "here is what I would commission, what it would cost me in time, and what I would receive." That inference is the buyer's job under this arrangement. It should be the seller's.

The remedy is not a more polished narrative. It is a comparison. Take two engagements, put their needs, deliverables, recurring activities, and responsibilities side by side, and see what stays recognizably the same. Whatever survives that comparison is the offer. Whatever changes is the boundary, and the boundary is information a serious buyer wants, not a weakness to conceal.

The example below is invented. It is not a client's operating history, not a tested pitch, and not a claim about any real consultancy's capacity or results.

Choose two engagements that can actually be compared

Start with cases where you know four things: the starting need, the agreed work, what the client supplied, and what was delivered. If two cases only share a visual style, they cannot teach you anything about the service. If one is your most photographed project and the other is a routine job that paid the rent, the routine job may be the more useful half of the pair.

The pair I want to work with is deliberately unglamorous.

Engagement A — the scattered procedures. A furniture maker with about forty employees has been running on tribal knowledge. Procedures exist in a mix of emails, a shared drive, and the memory of a production manager who is retiring in eight months. The client's stated need: get the essential procedures out of people's heads and into something a new hire can follow. The agreed work: a set of onboarding documents covering the ten most critical production and safety routines. The deliverable is a reviewable documentation set, owned by the client, in the client's existing document system. The consultancy supplies interviewing, structuring, drafting, and a review process. The client supplies access to staff, a single approver, and time on the production floor. The result: ten documents drafted and approved through two review rounds; the production manager's knowledge is partly captured before retirement.

Engagement B — the new service. A regional landscaping company is launching a winter maintenance line. The procedures do not exist yet because the service does not exist yet. Somebody, probably the owner, has to decide how callouts work, what counts as an emergency, who gets dispatched, and what the customer is promised. The client's stated need: onboarding documentation for the new line, ready before the season starts. The agreed work: the same deliverable — a reviewable onboarding documentation set — reached through the same activities, plus a facilitated decision session because the procedures have no source to interview. The client supplies the owner's decisions, plus the same kind of single approver and staff access. The result: a documentation set drafted and approved, with several procedures marked as provisional pending the first month of live work.

Same deliverable. Same core activities. Utterly different engagement.

Find the stable work underneath the different projects

Lay the two side by side and the recurring shape becomes visible.

The recurring need. In both cases the client has knowledge that exists somewhere unhelpful — in people's heads, in scattered files, or not at all — and needs it turned into a document a new person can act on. That is the customer benefit. It is the same need in both engagements, and it is the sentence that belongs at the top of the pitch.

The recurring deliverable. A reviewable documentation set, owned by the client, in the client's own system. Not "a beautiful handbook." Not "transformation." A specific object the client can inspect and keep.

The recurring activities. In both engagements, the consultancy interviews people, organizes what it hears into a structure, drafts procedures, and runs them through review. Four verbs. They survive the comparison.

The recurring responsibilities. The consultancy does the interviewing, structuring, drafting, and revision. The client supplies a single approver and staff access. In both engagements the result is an approved set, which puts the approver on the critical path: the work is not finished until they have read it. That this makes the approver a bottleneck — and that the process should be built around one — is a design assumption worth confirming with the client, not a finding these two cases establish.

The fictional offer includes two review rounds in both engagements. What varies is the work around them: page styling, tooling, the order of procedures, interview time, and any additional rounds needed after the included two. Extra review needs a separate scope decision; a round limit does not guarantee approval. A shared template proves you own a template. It does not, by itself, define the offer.

This is the part I find most persuasive about the method: the offer you end up describing is smaller and plainer than the one most founders want to present. "We interview your people, structure what we learn, draft reviewable procedures, and revise them through two rounds with your approver" is not a grand claim. It is also the thing a buyer can actually commission, budget, and schedule.

Use variation to explain the offer boundary

The first engagement depends on knowledge that already exists. The second depends on decisions that haven't been made. That single difference propagates through the whole project.

Now the boundary becomes sayable. Interview-based documentation, using the four recurring activities, is inside the offer. Facilitating decisions that don't exist yet is a variation the consultancy can price and schedule on top, and it needs to be named in the pitch, because a buyer arriving with an unformed service is buying a different engagement.

And here is the sentence most pitches leave out: if the client can't supply a single approver, the work slows down, and no amount of consulting process fixes that. That is not a complaint about clients. It is a fact about the engagement that belongs in the pre-engagement conversation, because it determines what the consultancy can promise.

Variation is not the enemy of repeatability. Concealed variation is. A buyer who understands that an unformed service requires a decision session before drafting begins is not being warned away. They are being given a map.

Draw the offer statement, then draw its edge

Out of that comparison comes a plain sentence a new customer can act on:

We interview your team, structure what exists, draft onboarding procedures, and revise them through two rounds with your single approver. You receive a documentation set in your own system, owned by you.

And the boundary list, which is just as important and usually missing:

Projects where the procedures already exist and can be described by staff. One client-side approver and reasonable staff access. Two review rounds are included; additional rounds are separately scoped. If procedures don't exist yet because decisions haven't been made, a separately scoped decision session precedes drafting, and affected procedures remain provisional. If your team cannot supply an approver or protected staff time, we re-plan the delivery dates with you.

That is a repeatable service. It is not identical engagements. It is not a promise that every project feels the same. It is a clear statement of what repeats, what varies, and what the client must bring.

The problem is judgment, not labor

A recurring temptation is to describe a clean four-step method and let the clean description imply that the work is easy.

In this example, the work is not the same in both engagements even though the steps match. Constructing procedures from decisions takes longer than transcribing existing ones. Confidence is different. The first case produces a set that reflects a real practice; the second produces a set that will be tested by the first winter and probably revised. Both are honorable outcomes. They are not the same product, and a buyer who priced them identically on the basis of the method description would be misled.

The judgment also shifts. In the first engagement, the judgment is mostly about what to leave out — forty employees have more procedures than the ten that matter, and the consultancy's value is partly in selecting. In the second, the judgment is about anticipating the operating reality the client hasn't lived through yet. Both are human, hard, and not automated.

So the pitch should say so. A method that names its own limits is more credible than one that promises uniformity. The founder who says "this will take longer and be less certain, because the service is new" is not weakening the offer. They are proving they understand it.

Discuss capacity last, and only with evidence

Nothing in the two engagements above tells you whether the consultancy can run four of them at once, or two, or how quickly they can turn one around.

The recurring method is a candidate explanation for consistency. It is not evidence of capacity. The two cases say: this is what a single engagement looks like, this is what varies, this is what the client must supply. They say nothing about staffing, throughput, margins, or how many clients can be served without the quality collapsing.

If the pitch needs to make capacity claims, those need operational evidence: the actual number of engagements run in a period, how many people worked on each, how much of the process was overlapping, what the calendar actually supported. Two invented cases, and two real ones for that matter, cannot produce that evidence. They can only define the work whose capacity would be measured.

The offer statement is one sentence. The capacity claim is a different sentence, and it needs its own records.

What a new customer should be able to say back to you

After reading the pitch, a buyer who has never commissioned this service should be able to say, in their own words: This is what I'd get, this is what I have to bring, this is where my project might need an extra step, and this is where my situation might slow it down.

That is a testable thing. It is more useful than a testimonial and it can be checked before the pitch ever leaves the building. Read the offer statement aloud to someone who has not been part of the comparison. If they can name the deliverable and their own obligation, the comparison did its work. If they can't, the pitch is probably still showing outcomes and asking them to infer.

The human work stays visible all the way through. A services business that presents a method without the judgment it requires has not made itself more repeatable; it has made itself less honest, and the first engagement that turns out to be a decision problem rather than a transcription problem will embarrass the pitch, not the buyer.

The two engagements above are constructed examples, not records of real clients, real results, or verified capacity.

Frequently asked questions

What makes two engagements worth comparing in a services pitch?

They should share known starting needs, agreed work, client-supplied resources, and delivered results. If they only share a visual style, they cannot teach you anything about the service; a routine job may be more useful than a most-photographed project.

What becomes the offer after comparing engagements?

Whatever stays recognizably the same across needs, deliverables, recurring activities, and responsibilities is the offer. What changes is the boundary, and the boundary belongs in the pitch because it tells a serious buyer what varies.

What are the recurring activities in the article’s example?

Interviewing people, organizing what is heard into a structure, drafting procedures, and running them through review. The recurring deliverable is a reviewable documentation set owned by the client in the client’s own system.

What does the comparison say about capacity?

It says nothing about staffing, throughput, margins, or how many clients can be served without quality collapsing. Capacity claims need operational evidence such as actual engagements run in a period, people per engagement, overlap, and what the calendar supported.

How should a project with no existing procedures be treated?

If procedures do not exist because decisions have not been made, a separately scoped decision session precedes drafting, and affected procedures remain provisional. The pitch should name that variation rather than conceal it.

Further reading

• Pitch Paid Discovery Before Quoting the Full Delivery — Consult this before quoting the work that depends on decisions the client has not made: it treats that unknown as a bounded investigation that can end in stopping.
• Who Will Do the Work? Make the Company’s Team Slide More Than a Biography Page — Read if the pitch must show who delivers the work; it maps functions to people and honest capacities, so staffing claims stay separate from the method comparison.