Sales Offer Packaging

Use this skill to turn technical capability into clear offers that clients can understand, compare, and buy.

Core Principle

Confused clients do not buy. Clear offers sell faster.

Sell outcomes before technology. Translate features into business value, then state exactly what is included, excluded, optional, and expected next.

Package Structure

Every sales package should include:

• Package name
• Best for
• Problem it solves
• What is included
• What is not included
• Optional add-ons
• Estimated price range or starting price
• Estimated timeline
• Client responsibilities
• Expected result
• Next step

Read references/package-menu.md for package examples, comparison table format, add-ons, and pricing guardrails.

Workflow

1. Identify the business problem:
   • missed inquiries, poor follow-up, manual encoding, scattered leads, unclear operations, lack of reports, support burden, or custom workflow need.
2. Match the problem to the right package level:
   • audit, starter automation, lead management, customer support automation, booking system, operations system, admin dashboard, custom app, monthly support, or full digital operations.
3. Translate technical work into outcomes:
   • "Google Sheets automation" becomes "organize inquiries and follow-ups without manually copying messages."
   • "Admin dashboard" becomes "central screen to monitor bookings, staff activity, payments, and reports."
4. Define inclusions and exclusions.
5. Add options:
   • add-ons, upgrade paths, monthly support, and custom features.
6. Provide price/timeline guidance:
   • use ranges or starting prices when exact scope is not known.
   • mark assumptions clearly.
7. Write a simple client-facing explanation.

Review Rules

Before handoff:

• Avoid technical language before business value.
• Do not promise guaranteed revenue, growth, or savings.
• Do not invent exact prices when scope is unknown.
• Include exclusions to prevent scope creep.
• Make the package easy to compare with other packages.
• Offer a low-risk entry package when the client is unsure.
• Avoid pushing custom app development when a smaller automation package fits.

Output Contract

When using this skill, provide:

1. Recommended package name and tier.
2. Client-facing package description.
3. Inclusions, exclusions, and optional add-ons.
4. Price/timeline range with assumptions.
5. Expected business result.
6. Next step or call to action.