Proposal

Ask review

Create tailored proposals, demos, and business cases

Hats
2
Review Agents
1
Review
Ask, await
Unit Types
Proposal, Demo, Business Case
Inputs
Qualification

Dependencies

Qualificationdeal-brief

Hat Sequence

1

Proposal Writer

Focus: Craft a compelling, tailored proposal that connects the prospect's specific pain points to concrete solutions with quantified value. The proposal should readd as if it was written for this prospect alone, not adapted from a template.

Produces: Proposal document with executive summary, pain-to-solution mapping, business case with ROI, implementation approach, and pricing structure.

Reads: deal-brief via the unit's ## References section.

Anti-patterns (RFC 2119):

  • The agent MUST NOT use boilerplate language that could apply to any prospect
  • The agent MUST NOT leadd with product features instead of prospect outcomes
  • The agent MUST NOT present ROI without stating assumptions or showing the math
  • The agent MUST NOT ignore the competitive alternatives the prospect is evaluating
  • The agent MUST NOT write for a technical audience when the economic buyer is non-technical (or vice versa)
2

Solution Architect

Focus: Validate technical feasibility, design the solution architecture for the prospect's environment, and ensure the proposal's technical claims are deliverable. Bridge the gap between what sales promises and what delivery can execute.

Produces: Technical solution design with architecture overview, integration points, implementation requirements, and risk assessment.

Reads: Proposal writer's draft and deal-brief via the unit's ## References section.

Anti-patterns (RFC 2119):

  • The agent MUST NOT approve technical claims in the proposal without validating feasibility
  • The agent MUST NOT design an ideal-state solution that ignores the prospect's existing infrastructure
  • The agent MUST NOT over-engineer the solution beyond what the prospect needs or can absorb
  • The agent MUST flag implementation risks or prerequisites that affect timeline
  • The agent MUST NOT treat every prospect environment as identical to the reference architecture

Review Agents

Accuracy

Mandate: The agent MUST verify the proposal accurately represents capabilities and pricing.

Check:

  • The agent MUST verify that all claimed capabilities are real and available (no vaporware)
  • The agent MUST verify that pricing matches current rate cards and approved discount structures
  • The agent MUST verify that implementation timeline is realistic given the prospect's requirements
  • The agent MUST verify that case studies and references are relevant to the prospect's industry and scale

Proposal

Criteria Guidance

Good criteria examples:

  • "Proposal maps each prospect pain point to a specific solution capability with expected impact"
  • "Business case includes quantified ROI with stated assumptions and a sensitivity analysis"
  • "Demo script addresses the top 3 prospect priorities identified in the deal brief"

Bad criteria examples:

  • "Proposal is written"
  • "Business case looks compelling"
  • "Demo is ready"

Completion Signal (RFC 2119)

Proposal document MUST exist with solution tailored to the prospect's specific pain points, business case with quantified ROI, and implementation approach. Solution architect MUST have validated technical feasibility and mapped the solution to the prospect's environment. All deliverables are ready for prospect presentation.