Productized service designer
Skill SkillMedev/freelancer-consultant-os/skills/productized-service-designer
For solo freelancers: position, productize, price, and run client work like a business.
npx -y skills add SkillMedev/freelancer-consultant-os --skill productized-service-designerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Converts custom freelance work into fixed-scope, fixed-price productized offers using the scope-box procedure, a 3-tier structure with the middle tier as the target, and deliverable definition rules. Use when a freelancer says "how do I productize my services", "I want to stop trading hours for dollars", "package my offer", "every project is a custom quote", "design my service tiers", or "clients keep asking what exactly they get". Do NOT use for choosing a pricing model for a software product - use saas-pricing instead; for the overall pricing rationale of a business, use pricing-strategy.
SKILL.md
8.5 KB, as published. Nobody here has run it
Productized Service Designer
Custom quotes make every sale a negotiation and every project a new invention. Productizing - a named offer with fixed scope, fixed price, and defined deliverables - lets the freelancer sell the same thing repeatedly, get faster at delivering it, and price on outcome instead of hours. The costly mistake this skill prevents is the fake productization that names a package but leaves scope elastic, which combines fixed-price risk with custom-work chaos.
This is the second skill in the Freelancer / Consultant OS setup sequence: it takes the positioning statement from freelance-positioning as input and hands its offers to retainer-pricing-calculator for pricing validation. Worked example: Maya, a freelance brand designer at $6,000/month on hourly work at $75/hr, moving to productized retainers for DTC food and beverage brands.
Operating procedure
Step 1: Collect the inputs
- The positioning statement and niche from freelance-positioning (if it does not exist, do that first - a productized offer for "anyone" sells to no one).
- The 5-8 most repeated deliverables across past projects, with actual hours each took. Label estimates as guesses.
- Current income and rate (Maya: $6,000/month, $75/hr, roughly 80 billed hours).
- The client outcome the niche pays for (Maya: a launch-ready, consistent brand system).
Step 2: Run the scope-box procedure
Draw a literal box. Inside the box goes only work that meets ALL four tests:
- Repeated: delivered at least 3 times before, or trivially derivable from work that was.
- Bounded: the freelancer can state maximum hours with 80 percent confidence.
- Outcome-linked: the client can see how it serves the promised outcome.
- Self-contained: does not depend on unpredictable third parties (a deliverable blocked on the client's dev team is a scheduling landmine).
Everything else goes outside the box - either dropped, sold as a separately-quoted add-on, or handled through the change-order process in statement-of-work-writer. Maya's box: brand audits, packaging design, social templates, web graphics, monthly creative direction. Outside her box: naming, copywriting, motion design, print brokering.
Step 3: Apply the deliverable definition rules
Every deliverable inside the box gets written to this standard - vague deliverables are where fixed-price margins die:
- Named artifact: "packaging design for one SKU", never "packaging support".
- Quantity: exact counts ("up to 8 social templates per month"), never "as needed".
- Format: file types and destinations ("print-ready PDF plus editable source files").
- Revision rounds: 2 rounds standard, defined as one consolidated set of comments per round. This is the pack-wide standard; statement-of-work-writer and scope-creep-defense enforce the same number.
- Turnaround: business days from receipt of complete inputs, with the "complete inputs" condition explicit.
Bad: "Ongoing design support for your brand." Good: "Up to 8 social templates per month (source files + exports sized for Instagram and TikTok), 2 revision rounds each, delivered within 3 business days of receiving copy and product photos."
Step 4: Build the 3-tier offer structure
Three tiers, not two (no anchor) and not four (analysis paralysis). Design the middle tier FIRST as the offer you actually want to sell - this is the price-anchoring rule: middle tier = target. The bottom tier exists to make the middle look complete; the top tier exists to make the middle look reasonably priced. Expect roughly 60 percent of buyers to take the middle when the tiers are built this way.
Rules:
- Each tier up should add clearly nameable value, not just "more hours".
- Effective hourly rate should be highest on the smallest tier - small commitments carry more overhead per hour, so never discount downward.
- The top tier should be 1.6-2x the middle price and genuinely deliverable, because some buyers will take it.
- Cap total sold capacity within the utilization limits from retainer-pricing-calculator (Maya: 88 billable hours/month, red line at 80 percent).
Maya's tiers (monthly retainers; middle-tier price validated by retainer-pricing-calculator at $4,900):
TIER 1 - BRAND SUPPORT $2,800/month (up to 18 hrs, ~$156/hr effective)
Up to 8 social templates + up to 4 web graphics per month
2 revision rounds per deliverable, 3-business-day turnaround
Async only (Loom + email)
TIER 2 - BRAND SYSTEM RETAINER $4,900/month (up to 36 hrs, ~$136/hr effective) <- TARGET
Everything in Tier 1, plus:
Packaging design for 1 SKU per quarter
Monthly 60-min creative direction call
Quarterly brand consistency audit
2-business-day turnaround
TIER 3 - BRAND PARTNER $8,500/month (up to 60 hrs, ~$142/hr effective)
Everything in Tier 2, plus:
Packaging for 1 SKU per month, launch campaign support
Biweekly strategy calls, 1-business-day turnaround on priority items
Note the arc: at $75/hr Maya billed 80 hours for $6,000; two Tier 2 clients bill 72 hours for $9,800 - more income, fewer hours, because the price is anchored to the brand-system outcome, not the clock.
Step 5: Pressure-test each tier
- The stranger test: could a new subcontractor deliver the tier from the written scope alone? If not, the definitions are too loose.
- The worst-client test: if the most demanding past client bought this tier and consumed every stated maximum, is the effective rate still above the floor from retainer-pricing-calculator ($107.95/hr for Maya)? If not, tighten quantities or raise the price.
- The outside-the-box test: for the 3 most likely off-scope requests, confirm each is explicitly outside and has a route (add-on price or change order via statement-of-work-writer).
Concrete thresholds
- 3 tiers; middle tier = the target offer; top tier at 1.6-2x middle.
- 2 revision rounds standard on every deliverable (pack-wide; cited identically in statement-of-work-writer and scope-creep-defense).
- Effective rate at every tier's stated maximum stays above the capacity floor from retainer-pricing-calculator.
- A deliverable that took wildly variable hours across past projects (max more than 2x min) does not go in the box until scoped tighter.
- Revisit tier contents no more than quarterly; weekly tinkering means the offer never accumulates sales evidence.
Deliverable
A one-page offer sheet: the scope box (inside / outside lists), three tiers with names, prices, fully-defined deliverables per the five rules, and the pressure-test results. This sheet feeds retainer-pricing-calculator for validation and statement-of-work-writer for contracting.
Do NOT
- Do not build the middle tier by discounting the top one; design the target first and construct the anchors around it.
- Do not write "unlimited" anything. Unlimited revisions or requests is an uncapped liability sold at a capped price.
- Do not leave any deliverable without a quantity and revision count - every undefined term will be interpreted in the client's favor at the worst moment.
- Do not price tiers off hours alone; hours set the floor (via retainer-pricing-calculator), the outcome sets the price.
- Do not put a deliverable in the box because one client asked for it once. Three repetitions or it stays out.
Quality bar
Done when: every deliverable satisfies all five definition rules; the middle tier is the target and its price clears the calculator floor; effective rates decrease from bottom tier to middle; the three most likely off-scope requests have named routes; and the sheet passes the stranger test.
Escalation and neighbors
Price the tiers against real capacity with retainer-pricing-calculator (next in the setup sequence). Contract them with statement-of-work-writer. When a live client pushes past a tier's boundaries, run scope-creep-defense. For writing the proposal document that presents these tiers to a specific client, use sales-proposal-writer.