Write a package that a buyer can understand without knowing your tools. You will define the business result, client responsibilities, completion standard, exclusions, review rules, timeline, and a defensible pricing structure.
Outcome-led packaging guide
Best for: freelancers who can perform the work but currently describe it with vague labels such as “AI consulting” or “content support.”
Not designed for: hiding uncertain, unlimited, or high-risk work inside a fixed price.
Test the package with one sentence
A buyer should understand the package from this structure:
Example: “For independent consultants, we turn one approved interview into two edited articles and six social posts within ten business days, including one consolidated revision round and excluding website publishing or original market research.”
The ten parts of a complete package
- Buyer: a specific group with a recognizable recurring problem.
- Problem: the costly or frustrating situation the buyer wants improved.
- Outcome: the useful result stated without tool jargon.
- Inputs: source files, access, interviews, approvals, brand guidance, and deadlines the client must provide.
- Deliverables: quantity, format, quality standard, and handoff method.
- Process: discovery, production, review, approval, and final delivery stages.
- Boundaries: exclusions, dependencies, unsupported topics, and third-party limitations.
- Timeline: start conditions, milestones, review windows, and what happens after client delay.
- Price logic: project fee, operating costs, risk allowance, and optional support.
- Next step: application, paid discovery, deposit, or kickoff requirements.
Use tiers only when the workload truly changes
One bounded result, fewer inputs, standard turnaround, and limited review.
More quantity, deeper research, coordination, or additional formats.
Higher urgency, stakeholder involvement, strategy, implementation, or ongoing support.
Three tiers that contain the same work with arbitrary labels and unclear differences.
Build the package in seven steps
1. Choose the smallest valuable outcome
Start with a result that matters but is predictable enough to estimate and inspect.
2. List every dependency
Record the source material, access, approvals, brand rules, technical prerequisites, and third-party tools required.
3. Define “done”
State the final files, quality checks, naming, formatting, acceptance conditions, and delivery location.
4. Write exclusions before pricing
Separate strategy from production, data cleanup from automation, original research from summarization, and maintenance from implementation.
5. Design the review process
Use consolidated feedback, a named approval owner, a review deadline, and a rule for new requests.
6. Estimate the complete effort
Include discovery, communication, setup, production, QA, revision allowance, admin, operating costs, and contingency.
7. Create the upgrade path
Offer the next logical service only after the starter package works—for example, a monthly volume package or monitoring retainer.
Somez AI Lab Example: content package scope
Buyer: independent B2B consultant.
Inputs: one 45-minute recorded interview, brand notes, approved claims, and product links.
Deliverables: two 1,200-word articles, six LinkedIn posts, source notes, and one content calendar.
Review: one consolidated revision round per article.
Exclusions: website publishing, original surveys, legal review, paid-media copy, and ongoing community management.
Schedule: delivery across an agreed four-week calendar after all inputs are received.
Define revision versus new scope
- Revision: correcting tone, clarity, formatting, or alignment within the approved brief.
- New request: changing the audience, strategy, source material, format, quantity, or approved direction.
- Client delay: the delivery date moves when required inputs or approvals arrive late.
- Third-party issue: platform outages, access problems, or vendor changes are handled under a separate rule.
Packaging mistakes that damage margin
- Leading with tools: buyers compare outcomes more easily than software lists.
- Using unlimited language: unlimited requests and revisions make capacity impossible to control.
- Hiding client responsibilities: missing inputs and approvals create unpaid delays.
- Combining discovery and implementation: uncertain work should be investigated before a fixed build quote.
- Offering maintenance accidentally: delivery does not imply permanent support.
Frequently asked questions
Should I offer three pricing tiers?
Three tiers can help when each option changes a meaningful factor such as quantity, speed, support, research depth, or risk. Do not create artificial tiers with cosmetic differences.
What should be excluded from a service package?
Exclude open-ended work, missing-input recovery, custom integrations, regulated advice, third-party delays, ongoing maintenance, and requests outside your proven ability unless separately scoped.
How many revisions should I include?
One or two consolidated rounds are common for bounded work. Define what counts as a revision and what becomes a new request.
When can a package become a retainer?
Use a retainer when the client has a recurring need and you can define capacity, response times, deliverables, approval duties, and change-request rules.
Write one package page, then test comprehension
Give the package to someone unfamiliar with your workflow. Ask them to explain what they receive, what they must provide, what is excluded, and what happens next. Rewrite any part they cannot answer.
Examples are illustrative. A service package should reflect your real ability, client agreements, legal obligations, privacy requirements, and the risks of the work.
Written and reviewed by the Somez AI using our Editorial Policy.