Two proposals leave your agency in the same week. One promises a technical audit, four blog posts a month and "ongoing optimisation"; the other promises a content strategy, some outreach and "monthly SEO". Both clients are plumbers with similar sites, and a few months in they'll be getting different work from different people at different prices. A productised service ends that: a named package with fixed deliverables, a fixed process and a fixed cadence, so selling, delivering and staffing stop depending on who wrote the proposal.
Why "we do SEO" costs you on every deal
When the service is undefined, three things happen. Every sale becomes a negotiation about scope, because the prospect has nothing to compare your offer against. Every engagement becomes a bespoke plan that lives in one account manager's head. Every new hire has to learn each client separately, because no two look alike. None of this shows up on an invoice. It shows up as proposals that take days, handovers that drop things, and clients who can't say what they're paying for, which is the first step towards leaving.
A product fixes this because it's a unit. It has a name, a buyer it's for, a list of what's in it, a list of what isn't, a rhythm it runs on, and a view the client gets at the end of each month. Once that unit exists you can price it, staff it, measure it and improve it. You can't do any of those things to a service you reinvent each time.
Build packages from the work you already do
Don't design packages from what you'd like to sell. Design them from what you already deliver to the clients who stay.
- List every deliverable you shipped to your last few clients: audits, fix lists, briefs, articles, page rewrites, reports, calls.
- Mark each one as recurring (it happens every month) or one-off (it happens once, usually at the start).
- Group the recurring items by the kind of client they serve. A content-led client and a technical-led client need different mixes.
- Name each group, and write down what it excludes as carefully as what it includes.
Most agencies end up with three shapes. A foundation package, sold once: an audit, a keyword map, a prioritised fix list and a plan. A monthly retainer in two or three tiers, where tiers differ by volume (how many pages written or rewritten, how many keywords tracked, how many fixes specified) and never by quality. And add-ons for a specific need: local search, an online store, AI visibility, a site migration.
Take a fictional two-person agency that serves trade businesses. Its foundation package is an audit, a keyword map and a fix list, delivered in the first two weeks. Its retainer has two tiers that differ only in how many pages get written or rewritten each month. Its single add-on covers the Business Profile and local pages for clients who serve a defined area. That's three things to sell, each with a checklist, and a new account manager can run any of them in their first week.
Fix the deliverables, let the strategy flex
Here's the mechanism that makes packaging honest. You control effort and output: the audit gets delivered, the fixes get specified, the articles get published, the report arrives on the agreed day. You don't control Google. So a package promises the things you control, and the strategy inside it (which keywords, which pages, which fixes first) flexes per client.
Keep every deliverable countable and finishable. "Ongoing optimisation" can't be counted, so it can't be delivered or invoiced. "One on-page pass across the money pages each quarter" can. A deliverable the client can tick off is one they'll remember paying for.
Exclusions matter as much as inclusions. Implementing code changes on the client's site, design work, paid ads, buying links and handling a surprise migration are all things clients assume are "SEO" until the scope says otherwise. Make them add-ons or quotes, not silent extras. Google's own "Do you need an SEO?" guidance warns against anyone who guarantees a ranking; a package that promises outputs rather than positions keeps you on the right side of that line and keeps your promises keepable.
Make the package the process
A package is only a product if the work behind it is the same every time. So each package gets a written run-sheet: what happens at onboarding, what happens every month, who owns each step, and what the client sees when the month ends.
For a retainer the monthly rhythm has four stages. Baseline: the audit and keyword confirmation, with a recorded starting point. Plan: accepted findings become tasks with an owner and a month. Produce: content ships and on-page fixes go live. Prove: the re-audit runs, you record what moved, and the client sees it. Same order, every client, every month, so that the eighth client is the same work as the third.
Staffing follows from the run-sheet. A strategist owns the plan, a writer owns production, an account manager owns the proof. A new hire gets the run-sheet instead of a tour of someone's memory, and a client who moves between account managers doesn't notice.
What to take away
- A productised service is a named package with fixed deliverables, a fixed process and a fixed cadence, and it's the unit you price, staff and improve.
- Build packages from the work you already deliver to clients who stay, and write the exclusions as carefully as the inclusions.
- Promise the outputs you control (audits, fixes, content, reports), and let strategy flex inside the package rather than promising positions.
- Every package needs a written run-sheet, so delivery doesn't depend on who's holding the account.
Next
With the packages named, the next job is putting a number on each one and writing scope that holds: Scoping and pricing SEO.