Skip to Content
Orphic
/

Product Proposal

What it does

It writes decision documents for brands, not research reports. The reader is the person voting in the greenlight meeting, and the document has to hold up there: every claim must answer “where did this number come from?”

Two kinds of proposal

  • New product — from market opportunity, audience, and pricing through to the launch plan; answers “should we build this?”
  • Line extension — extending an existing line across sizes, price tiers, and audiences; answers “where do we extend, and into what?”

When what you actually want is a product concept brief (design a new product, write the concept), it takes that route instead of forcing the proposal template.

Typical flow

  1. New or continued — an existing proposal can be continued, revised, or restored from a previous version instead of starting over.
  2. Gather — it consumes existing market research and competitor material (read from the asset library), then fills in what a proposal specifically needs: audience segmentation, pricing method, channel unit economics, compliance boundaries. Numbers follow the same sourcing rules as the research reports.
  3. Write-up — following the proposal template: opportunity, audience, pricing, channel, launch timeline, exit signals. Key claims carry their sources.
  4. Audit — a deterministic pass over section completeness, unsourced numbers and claim boundaries; problems degrade to warnings.

What it delivers

  • A proposal document ready for the greenlight review (Word / PDF or slides);
  • Sources and premises behind each claim;
  • Explicit exit signals: what would mean this should stop.

Limits

  • It does not do category research (use Market Insight) or competitor benchmark reports (use Competitor Intel) — it consumes their output rather than repeating it.
  • You make the go/no-go call: it gives a sourced judgement, its premises and its exit signals.