You’ve been doing the same type of work for three years. Each client gets a custom scope, a custom proposal, a custom process that you rebuild from scratch. You’re good at it. You’re also spending 20-30% of your project time on setup, scoping, and onboarding instead of doing the actual work you’re paid to do.
The work itself is repeatable. The delivery system around it isn’t. That’s the gap productization closes.
The 90-day sprint takes your most repeatable service type and builds a system around it: a fixed scope, a documented process, a templated intake, a named deliverable, and a public price. The output is a service you can sell without a custom proposal, deliver without reinventing the process, and describe in one sentence.
Here’s exactly how to do it, week by week, with what to expect at each stage.
Before You Start: Choose the Right Service
Not every service you offer is a productization candidate. Choose the one that meets these criteria:
You’ve done it at least 5 times. You can’t document a process you haven’t run enough to know the pattern. Five completed engagements gives you enough repetition to see what stays consistent and what varies.
The outcome is consistent. Similar clients, similar inputs, similar outputs. If every engagement produces wildly different results, productization will require so much custom variation that you’ve just renamed your custom service.
You can define the deliverable specifically. You can name the output, a document, a report, a build, a plan, and describe it in 2-3 sentences. Not “advice” or “consulting”, a specific thing.
The best first productization candidate is usually your most common type of engagement. What do most clients actually hire you for? Start there.
Weeks 1-2: Define Scope and Deliverable
This is the most important phase. Every problem in the later stages traces back to an underspecified scope.
Day 1-3: The scope session
Pull your notes from your last 5 engagements of this type. For each, list:
- What you actually delivered (not what was originally scoped)
- How many hours it took
- What questions you asked the client before you could start
- What the client valued most about the output
- What took longer than expected
Day 4-7: Write the scope
From your notes, identify the core consistent elements (what you delivered in all 5 cases) and the variables (what changed per client). The core consistent elements become your fixed scope. The variables either become intake form questions or get excluded.
Write the scope in two columns: “Included” and “Not Included.” Fill both columns with specifics. Then write the deliverable description, 3-5 sentences that describe exactly what the client receives.
Day 8-14: The exclusion test
For each item in “Included,” ask: Would I do this for a client who paid me [price]? For each item in “Not Included,” ask: Would a buyer reasonably expect this to be included? If yes, either include it, add it to a future upsell offering, or explicitly name the exclusion in your service description.
Weeks 3-4: Document the Process
Your process is in your head. That’s fine for custom work. For productized work, it needs to be in a document so you can execute it consistently and eventually delegate pieces of it.
The Loom method:
The fastest way to document a process is to record yourself doing it. Take a real client project and record a screen capture (Loom works well) of each major step, narrating as you go. Don’t edit. Don’t make it polished. Just capture the steps.
After recording, write a bullet-point version of what you did in sequence. That’s your process draft. You’ll refine it after 3-4 more runs.
What the process document needs:
For each step:
- What you do (action)
- What inputs you need from the client (if any)
- What tool you use
- What the output is (a document, a section of the final deliverable, a decision)
- How long it takes
After weeks 3-4, you should have a process document that someone else could follow with reasonable guidance. This is also your quality checklist, run through it before delivering to every client.
Weeks 5-6: Build the Intake and Delivery Templates
The intake form and the delivery template are the systems that make productized delivery fast and consistent.
The intake form (aim for 15-20 questions):
Review your process document. For every step that requires client information, write an intake question that collects it upfront. Then add questions for context (company size, stage, goals), scope confirmation (confirms they understand what’s included), and logistics (payment, timeline preferences).
Test the form by completing it yourself as if you were a client. Then have one of your existing clients complete it. Where they’re confused or provide incomplete answers, revise the question.
The delivery template:
Your final deliverable should have a consistent structure every time. Create a template document with the sections, headers, and placeholder content pre-filled. Instructions at the top explain how to customize each section.
A good delivery template cuts your production time by 30-40% by eliminating the blank-page problem on each section and ensuring you never miss a component.
The Loom recording step is where most productization sprints stall. Freelancers resist documenting because it feels like overhead. It is overhead, in the short term. In the long term, it’s the difference between a scalable product and a service that depends entirely on your availability and memory.
Weeks 7-8: Price It and Test With 3 Warm Prospects
Calculate your price using the formula: (hours per engagement × target hourly rate) × 1.2 buffer. Then check market pricing for comparable services.
If the hours-based math produces $2,400 and market comparables are at $2,500-$3,500, price at $2,800 for your test phase.
The warm prospect test:
Identify 3 people in your network who fit your target buyer profile and who have (or recently had) the problem your service solves. These don’t need to be your best clients, they need to be real potential buyers.
Email them:
“I’m launching a new fixed-price service: [service name]. It’s a [timeline]-day engagement that delivers [specific deliverable]. Fixed price: $[X]. I’m testing it with 3 clients before the full launch, would it be useful for where you are right now?”
Short. Specific. An easy yes or no.
What the test reveals:
- Do they understand what they’re buying without a lengthy explanation? (If not, the deliverable description needs work)
- Do they have questions about the scope before saying yes? (If yes, add those answers to the public description)
- Do they push back on price, or do they accept it? (Tells you whether you’re in the right range)
Three test engagements give you the first case studies, the first real timing data (does it actually take 14 days?), and the first refinements to your intake form and delivery process.
Weeks 9-10: Refine Based on Feedback
After the first 3 engagements, debrief each one:
- Did you deliver within the stated timeline?
- Were there scope questions or edge cases you didn’t anticipate? (Add them to your exclusions list or intake form)
- Was the deliverable what the client expected? (If not, rewrite the service description)
- How many hours did the delivery actually take vs. the estimate?
- What would you do differently next time?
Make these changes before the public launch. The service you launch publicly should be the version you’ve already tested and refined, not the first draft.
Adjust the price if the timing data shows you’re significantly over or under the original estimate.
Weeks 11-12: Public Launch and Marketing
Add the service to your website on a dedicated page. Use the one-page structure from the anatomy article: service name, one-sentence outcome, included scope, timeline, price, who it’s for, who it’s not for, how to book.
Launch sequence:
Day 1: Post on LinkedIn announcing the service. Be specific about what problem it solves, who it’s for, and how it works. Include a client quote from one of your test engagements if you have permission.
Day 3: Email your existing list (even if it’s small) with the same message.
Day 7: Post a behind-the-scenes piece: “Here’s how I built this service and why it works the way it does.” This builds trust and differentiates you from competitors who just have a service page.
Ongoing: Include the service in your email signature, mention it when relevant in client conversations, and reference it in outreach where appropriate.
What to Expect in Year 1
A productized service doesn’t immediately generate more revenue than custom work. In year 1, you’re building the system and the reputation around it. Expected progression:
- Months 1-3: 1-2 productized clients alongside custom work
- Months 4-6: 3-4 productized clients, building a referral base
- Months 7-12: Productized revenue starts matching or exceeding custom revenue per hour
The hourly efficiency gain is the main early win. If productized delivery takes 12 hours instead of 16 (because you have a template, a process, and no setup overhead), you’ve immediately increased your effective rate by 25% at the same price.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
