The Packaging and Productisation Mini-Guide

When a buyer asks what you charge and your answer is "it depends," you have just handed them a reason to delay. Buyers who cannot see a price cannot evaluate whether the thing is for them. They park the decision and move on to something easier to think about. Custom quotes also signal uncertainty on your end. Even if you are entirely confident in your work, a bespoke proposal process looks like you are figuring out the answer as you go. Buyers read that as risk. A named package with a fixed scope reads as "this person has done this before and knows exactly what is involved." The good news is that productising does not mean you stop doing great, tailored work. It means you stop selling the process of figuring out what to charge and start selling the outcome itself.

Before you can package anything, you need an honest list of what you have delivered in the last 12 months. Pull your invoices, your client emails, your project folders. Write down every type of work you completed. Do not filter for what felt strategic or impressive. List everything, including the bits you consider routine. Now look for the work that repeated. If you helped three clients set up their email automation, that is a candidate for a package. If you wrote lead magnet copy for four different businesses, same thing. Repetition is the signal that you have figured something out and can deliver it reliably. Finally, note where you spent the most time explaining the scope to clients before they bought. Those are the areas where packaging will do the most work for you. If clients keep asking the same questions, your offer is unclear, not your clients.

Most service providers describe what they do in terms of activities: "I will audit your site, write three emails, and set up your workflow." Buyers do not buy activities. They buy what happens after the activities are done. For each package you are building, write down the single most important thing the client will have or be able to do when the work is finished. "A five-email welcome sequence your subscribers receive automatically" is an outcome. "Email copywriting services" is a category. One of those is easy to say yes to. Outcome-first framing also makes it easier to scope the work cleanly. If you know the finish line, you can work backwards to the exact inputs you need from the client and the exact deliverables you are providing. That clarity is what makes a fixed price defensible.

Two packages is workable. Three is the sweet spot. More than four and buyers start comparing features rather than choosing. You want the decision to be "which version of this do I need" rather than "which of these twelve things is right for me." A simple three-tier structure that works across most service businesses: an entry-level package that solves one specific problem fast, a core package that is your main offer and the one you want most clients to buy, and a premium version that adds speed, access, or scope for buyers who want more. Name them clearly. "Starter," "Growth," and "Done For You" tells a buyer where they sit faster than any feature list. The middle package is where most of your revenue will come from, so build that one first. Get the scope exactly right for a typical client. Then build down and up from there.

Every package needs two columns in your head: what is included and what is explicitly not included. You do not need to publish a long exclusions list, but you do need to know where the boundary is so you can describe the package clearly and enforce it when clients ask for extras. Good scope statements are short and concrete. "Three months of LinkedIn content: 12 posts written, formatted, and scheduled" tells the buyer exactly what they are getting. "Ongoing social media support" tells them nothing and guarantees scope creep. If you find yourself writing bullet points that start with "this could include," stop. The package includes specific things. If the client needs something outside those things, that is a new conversation. Boundaries are not unfriendly. They are what make a fixed price possible.

If your pricing starts with how many hours something will take you, it will always be too low. Hourly-based pricing caps your income at your capacity and frames you as a resource rather than an expert. Buyers who know the hourly rate start trying to minimise hours. Buyers who see a package price ask whether the outcome is worth it. Instead, look at the value of the outcome to the buyer. A welcome email sequence that converts even 2% better over a year is worth thousands in revenue to a business with a real list. A productised audit that saves a founder six hours of wasted ad spend per month is worth several times what you might charge for an afternoon's work. Your price should also reflect what comparable outcomes cost buyers elsewhere. If a buyer could hire someone to do this inside their business, what would that cost them annually? Your package price should look like a bargain against that comparison, not against your hourly rate.

You do not need a new website section, a pricing page overhaul, or a PDF proposal template before you start selling your packages. You need to say the package name and the price out loud to five people and see what happens. Start with your next enquiry. When someone asks what you charge, describe the package instead of asking questions to build a custom quote. Watch where they hesitate. Listen to what they ask about. That is your scope gap or your framing gap, and it is much easier to fix at this stage than after you have built out an entire sales page. Most service businesses need two or three real sales conversations before the package language clicks. That is normal. Do not treat early hesitation as evidence that packaging does not work. Treat it as information about what to sharpen.

A productised service only works if the scope holds. The most common failure point is not the sale, it is what happens two weeks in when the client asks for something outside the package and you say yes anyway. Before the project kicks off, send a short document (one page is enough) that lists what you are delivering, what you need from them, and when. This is not a legal document. It is a shared reference that both of you can point to when questions come up. Clients who know the scope upfront ask fewer out-of-scope questions. When something outside scope comes up, name it plainly. "That is not inside the package, but we can talk about adding it" is a complete sentence. Saying yes silently trains clients to keep asking and trains you to keep giving ground. Holding scope is not difficult once you have named it clearly at the start.