Value positioning research

Runs only for sales/discovery, partnership, and board/investor meetings. Cross-references what you learned about the attendee's company with your own sales context to find concrete positioning angles — never generic pitch advice.

Your sales context

Keep a small sales-context note in your workspace (or pull the equivalent from your CRM/enablement docs) with:

• Key differentiators — what actually makes your product different
• Integration partners — tools your product connects with
• Case studies — named or anonymized customers, their industry/size, and the outcome metric
• Common objections — with your standard responses
• Tracked competitors — who you displace

If none of this exists yet, the play still works — pain-to-solution mapping and tech-stack discovery run on web research alone; the section is thinner but useful. Tell the user once, at the end: adding sales context makes the next briefing's positioning sharper.

Searches (run simultaneously, 3–5 depending on available context)

1. "[Their company]" tech stack OR tools OR platform OR uses → what they run; match hits against your integration partners.
2. "[Their company]" paired with your company name or domain → existing relationship, mentions, shared investors, competitive overlap. Skip if already run during company research.
3. "[Their company]" challenges OR pain points OR struggling OR migrating → pain signals to map against your value props.
4. (If you track competitors) "[Their company]" [Competitor A] OR [Competitor B] → competitor usage; critical for displacement positioning.
5. (If you have case studies in their industry) [Your company] [their industry] case study OR customer story → published proof to reference.

From the results, extract four things: tools they use (integration hooks), pain signals (value mapping), competitor usage (displacement angle), and industry matches to your case studies (social proof).

Output subsections

Value Mapping. Match their specific needs to your capabilities. Every line is grounded in a researched finding, formatted: "They [specific finding, with source] → your product [specific capability]". A mapping with no finding behind it doesn't ship.

Integration Hooks. Only integrations confirmed on BOTH sides — their stack (from research) and your integration list. No overlap found → say so honestly rather than stretching.

Recommended Positioning. 2–3 sentences framing the pitch for this specific company and person: their stage, recent news, the attendee's role and priorities, any displacement opportunity. The "elevator pitch calibrated to this meeting" paragraph.

Reference Customers. Case studies matching their industry, size, or use case, with the outcome metric. No genuine match → omit the subsection; a forced weak match reads worse than nothing.

Grounding rules

• Never write "highlight your product's strengths"-grade advice. If a claim isn't traceable to a specific finding about their company plus a specific capability of yours, cut it.
• Displacement angles require an actual signal that they use the competitor — a guess is not an angle.
• The attendee's seniority shapes the framing: an economic buyer hears outcomes and reference customers; a hands-on evaluator hears integration hooks and workflow specifics.