Skip to content
DESIGN7 min read

Productising consulting services: packages that sell themselves

Bespoke work is expensive to sell and exhausting to deliver. Here is how to find the named, scoped, repeatable offer hiding inside the work you already do — and what to deliberately keep custom.

The Impact Collab design title card: "Productising consulting services: packages that sell themselves".

What it means to productise consulting services

To productise consulting services is to turn bespoke work into a named, scoped, repeatable offer with a fixed price and a defined outcome. Same problem, same process, same deliverables, most of the time. The client is buying a known thing, not an hourly promise.

That is the whole idea. It sounds mechanical. It is actually the single biggest lever most purpose-led consultants have on both income and hours, because it attacks the two places where independent practices leak money: the sales conversation and the scoping.

A bespoke practice sells from scratch every time. You take the call, you listen, you go away, you write a proposal that is really a small strategy document, you send it, you wait. Three hours of unpaid work per opportunity, and a conversion rate you have probably never measured. A productised practice sells a thing that already exists. The conversation is shorter, the proposal is a page, and the buyer can say yes without a committee.

Why bespoke feels safer and costs more

Most consultants resist packaging for the same reason. "Every client is different."

Every client is different. Their context is different, their politics are different, their data is a mess in a unique way. But your method is not different. You almost certainly run the same diagnostic, ask the same eight questions, build the same three artefacts and land in the same kind of recommendation. You just rebuild the container each time.

The cost of that shows up in four places:

  • Unpaid pre-sales. Custom proposals are unbilled consulting.
  • Scope drift. With no defined edges, the work expands to fill the relationship.
  • Pricing by hours. Bespoke work gets priced on effort, so your income is capped by your calendar. This is the exact mechanism that makes people believe earning well and doing meaningful work are in conflict. They are not. Hourly pricing is.
  • No compounding. You never get faster, because you never do the same thing twice in the same way.

Packaging does not remove judgement from your work. It removes rebuilding from your work.

Find the package inside what you already do

Do not invent an offer. Excavate one. The package you can sell next month is already sitting in your last two years of invoices.

1. List your last ten engagements. Client, problem they came with, what you actually delivered, what they paid, how long it took.

2. Cluster by the problem, not the client. Ignore industry and size. Group by the question the client was really asking. You will usually find two or three clusters and a tail of one-offs.

3. Pick the cluster you want more of. Best margin, most energising, clearest result. Not the biggest cluster — the one you would happily do forty times.

4. Write down the steps you took, every time, in that cluster. Be honest and specific. "Stakeholder interviews" is not a step. "Six 45-minute interviews against a fixed question set, synthesised into a themes map" is a step.

5. Name the outcome the client got. Not the deliverable. The thing that changed. A board that finally agreed on priorities. A pricing model they can run without you. A measurement framework that survives a staff change.

What you now have is a process and a result. That is a product. Everything after this is packaging.

Give it a name and edges

A package needs four things a buyer can hold:

  • A name. Plain and descriptive beats clever. "Impact Measurement Foundations" tells someone what they are buying. "The Ripple Method" does not.
  • A duration. Six weeks. Ninety days. One day plus two follow-ups. Time-boxing is what makes the price defensible and the scope finite.
  • A defined set of inclusions. Number of sessions, number of interviews, what documents they receive, who is involved.
  • A single headline outcome, stated in the client's language.

Then write the exclusions. This is the part people skip and regret. If implementation is not included, say so. If the package covers one business unit, say one. Exclusions are not defensive — they are how you keep the price honest and the delivery calm.

Price the outcome, not the hours

Once the scope is fixed, the price stops being a function of your time and starts being a function of the result. This is not a trick to charge more for less. It is an accurate reflection of what the client is buying: your accumulated judgement, applied fast.

A few principles that hold up:

  • Price the package, quote the package. No hourly breakdown in the proposal. The moment you show hours, you invite negotiation on hours.
  • Offer two or three tiers, not five. A tight version, a standard version, and one that includes ongoing support. Most people take the middle.
  • Track delivery hours privately. You need to know your effective rate per package so you can adjust. The client never sees it.
  • Raise the price when the package gets faster. Efficiency you earn belongs to you, not automatically to the buyer.

Do the arithmetic before you launch. If a package prices at $12,000 and takes you 60 hours, you know your number. If the second delivery takes 40 hours because you built the templates, you know what happened and you can decide what to do with it. Vague pricing hides this from you entirely.

What to keep bespoke

Productising everything is a different failure. Some work should stay custom, and being deliberate about which is part of the discipline.

Keep it bespoke when:

  • The problem is genuinely novel and you are being paid to think, not to run a method. Long-horizon strategy work often sits here.
  • The relationship is the product. Ongoing advisory, board work, executive coaching at senior level. The value is your continued attention, and a scoped package misrepresents it.
  • You are still learning the shape of the problem. Do not package something you have delivered twice. You will lock in a bad process.
  • The client is a research and development opportunity — a piece of work that will teach you something you can productise later. Price it properly, but keep it flexible.

A healthy independent practice usually runs a small number of packages that carry the majority of revenue and the majority of the pipeline, plus a deliberate slice of bespoke work that keeps the thinking sharp. The ratio is yours to choose. The mistake is drifting into all-bespoke by default and calling it client service.

Make the package sell itself

"Sells itself" is not a promise that you stop selling. It means the offer does the explaining so you do not have to.

That requires three things to be true.

The buyer can repeat it to someone else. Test this. Describe the package to a peer, wait a week, ask them to explain it back. If they cannot, the name or the scope is doing too little work. Referrals only travel if the offer is describable.

It exists somewhere a buyer can read it. A page on your site with the name, the outcome, who it is for, what is included, the duration and — ideally — the price or a price range. Publishing the price filters out the wrong conversations before they reach your calendar. That alone is worth hours a month.

The first step is small and obvious. A scoping call, a paid diagnostic, a short assessment. Something with a clear next action rather than "get in touch to discuss your needs".

One warning. Packaging is a positioning decision, not a formatting exercise. If your positioning is broad — "strategy for purpose-driven organisations" — the package will read as generic no matter how neatly you scope it. Narrow the problem first. Broad positioning with sharp packaging still converts badly.

Launch it before it is finished

The version of the package in your head will not survive contact with a buyer, so stop refining it in private. Write the one-pager. Take it to the next three conversations that fit the cluster. Notice which parts they ask about, which inclusions they ignore, which words they use back to you. Rewrite. Deliver it twice. Rewrite again.

Packages get good through iteration, not through design. Three cycles in, you will have something you can sell in a twenty-minute call and deliver without dread.

This is Product Design — the first pillar of the Impact Architect Framework™ that shapes how we work at The IC. It is deliberately first, because pricing, packaging and positioning are what create the room for everything else. Visibility is harder without a clear offer. Systems have nothing to systematise. And the three-day week that some of our members work toward is arithmetic before it is a lifestyle: it only happens when what you sell is no longer measured in hours.

None of this is easy to do alone. Most consultants can see the pattern in someone else's business and not their own — which is exactly why we run Foundation Pods and small-group Expert Pods, and why the community is capped at 150 members rather than open to everyone. The IC is not where you summit. It is the base camp that makes the climb survivable.

If you are ready to stop rebuilding the same proposal from scratch, join the Community Waitlist and put your packaging in front of people who have done it.

Written by

The IC EA

The Impact Collab

Ready when you are

Membership is invite-based and capped at 150. Join the Community Waitlist and we will be in touch after the next review.

Join the waitlist

Stay in the loop

Occasional notes on impact, pricing, boundaries and building a business of one — plus event updates. Sent via our Luma calendar; unsubscribe any time.

Abbey writes these. One list, one unsubscribe link, and nothing else done with your address.