PlaybooksABM, shown by example
Scenario datasheet No. 04
Simulation
fiktives Szenario, reale Methodik
Project Smart Factory
- Industry
- IIoT / Predictive Maintenance
- ABM type
- 1:Few
- Program duration
- 6 to 9 months
- Deal size
- €450,000 + €80,000/year / plant
Fictional company
Starting position
A provider of industrial automation and IIoT software: sensor hardware plus AI-driven predictive-maintenance software that prevents unplanned downtime on the factory floor.
Numbers up front
Deal economics
Roughly €450,000 up front (hardware plus implementation) plus an €80,000/year SaaS fee per plant. Expansion to additional plants is the real lever (land and expand). Sales cycle of 6 to 12 months.
Deal size
€450,000 + €80,000/year / plant
Headline metric · Core KPI
Year 1 revenue potential: €1.5 to €2+M
Size, criteria, triggers
Target Account List (TAL)
The TAL brings together exactly the accounts that fit the ideal customer profile: size, criteria, trigger events.
40 accounts (1:Few): top-tier automotive suppliers (Tier 1) and large machinery manufacturers in the DACH region with at least 5 production sites. Multi-site is a selection criterion, because the expand path carries the deal economics.
Four roles, four vetoes
The buying committee
Four roles, four concerns, four plays: each persona gets the answer their veto hinges on.
Plant Manager
IT projects that slow down operations are the enemy.
VetoHead of Maintenance
Fears the AI will devalue his job or overwhelm his team.
VetoCIO / IT Security
Sees red the moment machines talk to the cloud.
VetoCFO
Wants to know when the €450,000 pays for itself.
VetoRole
Plant Manager
Cares about one thing only: OEE (Overall Equipment Effectiveness) and keeping production running.
Concern / objection
IT projects that slow down operations are the enemy.
Play
An OEE opportunity analysis based on the equipment types on his floor, plus documented proof that installation happens during live operation (zero downtime).
Role
Head of Maintenance
Wants hard proof, not buzzwords.
Concern / objection
Fears the AI will devalue his job or overwhelm his team.
Play
The "Shock Box": a physical mailer containing a real worn-out bearing component and a QR code to an exclusive video analysis of his specific equipment type. How would the system have caught this failure 6 weeks earlier? Framing: a tool for his team, not a replacement.
Role
CIO / IT Security
Concern / objection
Sees red the moment machines talk to the cloud.
Play
A security architecture dossier with a reference architecture (edge-first, on-prem option), IEC 62443 compliance, and a pentest summary, addressed to him before he is pulled into the deal.
Role
CFO
Concern / objection
Wants to know when the €450,000 pays for itself.
Play
A tailored ROI calculator using the downtime costs of his sector, with both conservative and aggressive scenarios. A conservative model convinces CFOs more.
Phased plan
The program
Month 1 to 2
Foundation
- TAL and stakeholder mapping
- Personalized landing pages per sector cluster
Month 3 to 4
Air Cover & Shock Box
- Air cover on LinkedIn
- Shock Box wave to heads of maintenance
Month 5 to 6
Deep Dive & Pilot Plant
- Deep-dive sessions (live demo on real machine data)
- Followed by a pilot-plant offer as an entry product with defined success criteria
Honest ranges
Benchmarks & KPIs
Honest ranges as planning figures, not guarantees.
| KPI | Target | Rationale |
|---|---|---|
| Account engagement (≥2 personas active) | 18 to 22 of 40 | The Shock Box drives above-average response |
| Discovery calls / demos | 12 to 16 | ~30 to 40% of the TAL |
| Opportunities (active sales stage) | 10 to 14 of 40 | Ambitious, but reachable given multi-site pain |
| Pilot-plant wins | 3 to 4 | Win rate of 25 to 30% on opportunities |
| Year 1 revenue potential | €1.5 to €2+M | 3 to 4 pilots × (€450K + €80K) |
| Expand potential (3 years) | €5 to €10M | Rollout to additional plants of the accounts won |
Methodology generalized
Why this works
- The deal never dies on value, it dies on one of the four vetoes.
- The program neutralizes each veto individually and in parallel, not one after another.
- The Shock Box makes an abstract software promise physically tangible.
Apply this scenario to your company