Buyer Package Framing

Workflow

1. Parse the buyer need:
   • site type
   • robot workflow
   • evaluation goal
   • timeline
2. Check whether Blueprint already has a matching package or hosted path.
3. If yes, frame the recommendation around that real asset.
4. If partial match only, state the gap explicitly.
5. If no match, frame the answer as a scoped capture/package path, not a fake SKU.
6. Add pricing logic only after the package shape is clear.
7. Call out approvals needed for discounts, terms, or custom commitments.

Required Output

Always return these sections:

• Recommended package
• Who it is for
• Included now
• Not included
• Proof / evaluation path
• Pricing rationale
• Risks or blockers
• Human-gated decisions

Writing Rules

• Keep commercial language concrete.
• Name the exact artifact or hosted path when possible.
• Use caveats where evidence is incomplete.
• Prefer “currently available” and “requires confirmation” over soft bluffing.

Escalation Rules

Escalate instead of smoothing over when:

• rights or privacy status is unclear
• the hosted path is not actually ready
• the package does not exist in sellable form
• support burden would materially change pricing
• the buyer is asking for terms, discounts, or guarantees

Do Not

• invent tiers or bundles the delivery system cannot support
• imply purchase automatically includes rights the buyer does not have
• sell readiness review as the main product by default
• hide uncertainty inside vague commercial language
• approve live pricing, discounts, or terms