01 / Header and document control
Battlecard: Northstar Analytics vs. SignalFrame (fictional).
Buying context: B2B software team replacing spreadsheet reporting.
Owner: account lead (illustrative role).
Last verified / next review: [add dates after source checks].
Status: illustrative draft; not approved for a live deal.
02 / Competitive situation
Competitor signal: the fictional buyer has shortlisted both vendors.
Reason: consistent reporting without slowing analysts.
Known in this scenario: department teams use spreadsheets.
Unknown: approval owner, budget, and rollout constraints.
Do not use for other segments without fresh research.
03 / Buyer decision frame
Desired outcome: shared metric definitions and useful self-service.
Stakes: less time reconciling conflicting reports.
Criteria: metric governance and analyst autonomy.
People: analyst champion, administrator, economic buyer.
Risk: unclear ownership of metric-definition changes.
04 / Competitor snapshot
Illustrative positioning: SignalFrame emphasizes rapid, team-managed dashboards.
Apparent fit / strength: teams prioritizing dashboard setup speed.
Tradeoff to validate: cross-team approval and governance.
Material changes: [check current product and policy sources].
All vendor details are fictional; no real evidence is supplied.
05 / Recommended position
Position: if governed definitions matter, demonstrate Northstar’s illustrative approval workflow.
Lead with: consistency plus self-service exploration.
Do not lead with: unsupported implementation-speed claims.
Acknowledge: team-managed dashboards may fit other priorities.
Treat every product statement here as fictional.
06 / Discovery and objection response
Buyer: “SignalFrame looks quicker to get started.”
Acknowledge: speed matters. Clarify: first dashboard or governed rollout?
Respond: compare both against the same workflow; no speed claim yet.
Prove: analyst proposes a change, administrator approves, second team uses it.
Ask: who decides when speed and consistency conflict?
07 / Proof plan and next move
Claim to prove: a metric change can be reviewed and reused across teams.
Format: the same guided task with both vendors.
Success: buyer observes approval and consistent reuse.
Owner / date: account lead and buyer administrator; [agree date].
Next step: book the comparison and record observed results.
08 / Claims to use, qualify, or avoid
Approved claim: none; this is a fictional draft.
Qualification: verify edition, permissions, and actual workflow.
Source / checked: [official documentation URL + date]; [authorized test notes + date].
Do not claim: “Northstar is always faster to implement.”
Use instead: “Let’s test the workflow your team needs.”