Building the Battlecard Automation Brief
Objective: Given a confirmed competitor price cut, build a structured battlecard section following the lesson's template, then sequence a four-week rollout plan for automating future battlecards.
You're the competitive intelligence lead at Awfis Space Solutions, the flexible workspace operator. A rival coworking chain just cut per-seat monthly pricing 15% in your two biggest cities, and sales has a renewal call in four hours.
Turn the confirmed price cut into a battlecard section sales can use today, then plan how this becomes automatic instead of a fire drill next time.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free tier tables and timelines cover both artifacts without needing a project management tool
Paid upgrades (optional, faster/deeper)
Structured output mode keeps every battlecard section in the same four-part format sales already knows, no freeform text to interpret
No access? Draft the four fields manually in Notion using the same template
The process
2 steps
Step 01 of 02
The lesson's battlecard section says the template needs four parts: what changed, why it matters, how to position against it, and three objection-handling lines, delivered fast enough to matter before the call, not a 40-page report published quarterly.
Given 'Rival coworking chain cut per-seat pricing 15% in Mumbai and Bengaluru, effective this week', write the four-part battlecard section a rep can read in 90 seconds before their call.
Procedure
- State what changed in one sentence with the specific number
- State why it matters to this specific renewal call
- Write a one-line positioning statement that doesn't just match the discount
- Write three short objection-handling lines a rep can say without sounding scripted
BATTLECARD, Rival Coworking Chain — Mumbai/Bengaluru Price Cut WHAT CHANGED: Cut per-seat monthly pricing 15% in Mumbai and Bengaluru, effective this week. WHY IT MATTERS: Client's renewal call is today, they will likely bring this number up. POSITIONING: Don't match the discount, point to Awfis's occupancy-guarantee SLA and faster fit-out timeline as the reason price isn't the full comparison. OBJECTION LINES: 1. 'Their price is lower because their occupancy guarantee is weaker, ask what happens if they can't seat your team on day one.' 2. 'We can walk through a 12-month total cost comparison, not just the headline seat price.' 3. 'Happy to match on a pilot floor if the SLA terms stay intact, want me to draft that today?'
Healthy
Every field is filled with a specific, usable line, no field just repeats 'competitor lowered price'.
Unhealthy
The positioning line just says 'we are better value' with no concrete differentiator.
What this means
A battlecard section is only as useful as its most specific line, vague positioning gets ignored on a live call.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Positioning line has no concrete differentiator | Pull one real SLA or feature difference from the product team before sending this to sales | 30 min |
Step 02 of 02
The lesson's rollout order starts with a pricing/features alert pipeline in week one, then CRM win/loss extraction in week two, then an AI share-of-voice baseline in week three, then automated battlecard generation in week four, fastest ROI first.
You just handled this battlecard manually under time pressure. Using the lesson's four-week order, what gets built first so this doesn't happen manually again?
Procedure
- Week 1: stand up an n8n + Perplexity alert pipeline for the top three rival coworking chains' pricing pages
- Week 2: run a CRM win/loss extraction on the last 12 months of closed-lost notes to check how often price is the actual reason
- Week 3: baseline AI share of voice for 'coworking space [city]' category queries
- Week 4: connect the battlecard template built in step 1 to auto-generate whenever the week-1 pipeline detects a pricing change
AWFIS CI ROLLOUT, 4-week plan Week 1: Pricing/features alert pipeline live for top 3 competitors Week 2: Win/loss extraction complete, price-cited-as-reason % established Week 3: AI SOV baseline for 'coworking space Mumbai' and 'coworking space Bengaluru' Week 4: Battlecard template wired to Week 1 pipeline, auto-generates on every pricing alert
Healthy
Week 1 is the alert pipeline, not the battlecard automation, matching the lesson's fastest-ROI-first order.
Unhealthy
The plan starts with building the full battlecard automation before any alert pipeline exists to feed it.
What this means
Automating the last step first means automating nothing, there's no reliable signal yet to trigger it.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Plan jumps straight to battlecard automation in week one | Reorder so the alert pipeline that feeds the automation ships first | 5 min |
Final deliverable
A four-part battlecard section ready for the renewal call, plus a four-week CI automation rollout plan.
See a reference example
Jyoti CNC Automation, battlecard section (excerpt) WHAT CHANGED: Rival machine tool distributor added a 5-year extended warranty at no extra cost. WHY IT MATTERS: Prospect's RFP explicitly weights warranty terms. POSITIONING: Reframe around total lifetime service response time, not warranty length alone. OBJECTION LINE: 'A longer warranty on paper means little if their average service response time is 3x ours, want the comparison sheet?'
Success criteria
You're done when you can:
- Battlecard section fills all four parts with specific, usable lines, no generic filler
- Rollout plan sequences the alert pipeline before the battlecard automation, matching the lesson's fastest-ROI-first order