Vs [competitor category — e.g. BI platforms, named class]
[Two sentences, under ~180 characters: the job their category does, and the category Alfred occupies that they don't.]
[Fair, one line — under 32 chars.]
[Who they actually serve.]
[Direct / Secondary / Indirect.]
When you're in this deal
[The situation and the verbatim signals to listen for — “we already have X”. Note any disqualifier. The trap: the comparison that concedes the frame — name it so the seller doesn't take the bait.]
Alfred
[Decision claim — brief + why]
[Provenance — sources shown]
[Execution — acts with approval]
[Memory — compounding outcomes]
[Competitor category]
[Structural gap 1 — stated fairly]
[Gap 2 — reactive vs proactive]
[Gap 3 — no execution loop]
[Gap 4 — no outcome memory]
[Their genuine strengths, conceded plainly — it buys credibility for the claim that matters. Note when they're simply the right choice, and why Alfred connects to or sits above them rather than replacing them.]
| You'll hear | Respond |
|---|---|
| “[Objection 1 — usually ‘we already have X’.]” | [Reframe to the decision-layer job; keep-it-don't-replace-it where true.] |
| “[Objection 2 — their newest credible feature.]” | [Acknowledge it honestly, then name the structural dependency or gap.] |
| “[Objection 3 — budget or overlap worry.]” | [Quantified answer from the canon, with its citation carried below.] |
Sources: [market stat + named source, e.g. “63% of marketing leaders miss opportunities from slow decisions — PwC CMO Survey 2025”]. Alfred figures are confirmed module outcomes from internal canon (product-marketing repo, modules/marketing.md) — reconfirm before external use. Competitor claims are category-level; demo numbers are the fictional Northwind Labs scenario. Internal use only.