Building a productised services business

The single decision that defines a productised service is what you say no to. The temptation is to take any work that comes in; the discipline is to keep the offer narrow enough to deliver consistently.

The wedge filters:

• Repeatable. You've done this same kind of work for 5+ clients with broadly the same scope. You can describe what they got in one sentence.
• Bounded. A clear "done" — the deliverable is something you can put on a checklist, not "we improved their marketing."
• High-value per hour. Your time delivering it should be worth at least $200/hour of equivalent agency rate; ideally $400+.
• Low custom-research per project. If every project starts with two weeks of discovery, you don't have a productised service yet — you have consulting that ends in delivery.

Good wedges that have built solo-to-team-of-3 businesses recently:

• Webflow / Framer site builds (14-day delivery, $4-12k).
• SOC 2 readiness sprints (8-week, $25-50k).
• ICP research + cold outbound list build (2-week, $3-8k).
• Brand identity in a sprint (5-day, $8-15k).
• Migration projects (Mailchimp → Loops, Salesforce → HubSpot, Stripe billing rebuild) at fixed price.

Bad wedges that turn back into agencies:

• "Marketing for B2B SaaS" — too broad, ends up custom every time.
• "Fractional CTO" — value is in judgement, not deliverables; doesn't productise.
• Anything where the customer's situation determines >40% of the work.

The exercise: write the offer in one sentence with a number in it. If you can't, the wedge isn't tight enough yet.

Three pricing structures that consistently work for productised services, with the trade-offs:

1. Fixed-price-per-engagement. One number, one deliverable, one timeline. Best for: project work where the scope is genuinely repeatable. The lever: raise the price every 5-10 sold engagements until conversion rate drops noticeably; you're nearly always under-pricing in year 1.

2. Productised retainer. Same standard offer, billed monthly, indefinite duration. Best for: ongoing-need services like SEO content production, paid-media management, ops support. Lower CAC per dollar of LTV than per-project; harder to sell initially because the buyer can't see "what they get this month" as clearly. Pair with a "first month at single-engagement pricing" to lower the trial barrier.

3. Sprint-and-handoff. Defined 2-12 week engagement that ends in a deliverable plus a handoff to the customer's team. Best for: setup-once work (audits, migrations, builds) that the customer then operates themselves. High value per engagement; depends on a strong lead-flow because each sale is a one-off.

Pricing instincts that pay off:

• Always price tiered (Standard / Premium / VIP), even when the deliverable is the same. The premium tier exists to anchor — most sales are Standard but the existence of Premium raises the perceived value of Standard. Aim for 5-10% Premium uptake.
• 50% deposit on signature, balance on delivery. This is non-negotiable; it screens out customers who'd haggle on every milestone.
• Raise prices as soon as you have a 60%+ close rate. A 60% close rate at $5k means you're cheap; the same close rate at $8k means you've priced correctly.
• Discount per-engagement, never per-hour. Never reveal an hourly rate. The moment a customer is computing your effective hourly, you've lost the productised frame.

Productised services break in predictable ways as you grow. The transitions:

Solo (1 person, $5-30k/month): You're the whole business. Sales, delivery, support all in one head. Constraint: your hours. Lever: cut delivery time per engagement through repeatable assets — checklists, templates, internal SOPs, code/design starter kits. The first hire is usually a delivery assistant for the mechanical parts of the work, not a fellow specialist.

2-3 people, $30-100k/month: You're delivering plus selling; one or two delivery people handle the standard work. Constraint: quality consistency. Lever: a detailed delivery playbook (Notion or Loom-heavy) and a 1-hour weekly QA review for the first 10 engagements per new team member. Watch out for the founder becoming a bottleneck on every project review — define which decisions actually need you.

4-5 people, $100-300k/month: You're mostly selling and running the business; a delivery lead manages output. Constraint: lead flow. The constraint shifts from delivery to demand. Lever: invest in content, SEO, partnerships, and referral incentives. The founder transitions from operator to revenue function.

Beyond 5 people the math usually starts pulling you back toward agency economics (high headcount, custom work creeping in). At that point you either commit to becoming an agency, or productise harder and add software/automation to push utilisation past 80%.

Every productised services founder eventually asks: should I turn this into a SaaS? The honest answer is "sometimes, and later than you think."

Signals that flipping makes sense:

• The repeatable 60-80% of the work is being done the same way in software you already wrote internally.
• Customers actively ask "can I just buy the tool you use?"
• The customer's willingness to pay for a self-serve version is high relative to the time the service takes you.
• You have at least 30-50 paying customers giving you sample data on what they actually use.

Signals that flipping is a trap:

• Customers buy the service for the judgement, not the deliverable. (SaaS doesn't sell judgement.)
• The service exists because the customer doesn't want to learn the workflow. (They won't learn it just because there's a SaaS now.)
• Your gross margin on the service is already 70%+; SaaS won't dramatically improve unit economics.

The best transition pattern: build the SaaS as an internal tool to make your team faster, then offer it as a side-product to existing clients at a steep discount, then graduate it to a standalone product once it has 10+ self-serve users. The companies that try to flip cold (shut down services, launch SaaS) usually run out of cash before the SaaS has product-market-fit. Run both in parallel for 12-18 months.