9-Grid Playbook › Row 1 — Who & Why › Cell 01 — ICP & Pain
Cell 01 · Depth Page
Foundation page. Every downstream cell (motion, pitch, pricing, objection, partner) inherits the two named personas and the five-point qualification frame defined here.
The single highest-leverage section in the playbook. Get the persona + pain wrong and every downstream cell pollutes.
The buyer journey starts with whose pain we treat, not what we sell. This section sits upstream of the entire acquisition motion — it determines whether marketing is pointing at the right humans, whether the demo storyline lands, and whether the discount-floor logic survives CFO scrutiny.
Missing this page costs measurable Rp:
eJourney is sold to two named humans, not a segment. CFO is gate (mentioned, not depth-carded). IT Director is veto (handled in Cell 06 Objections).
CFO Budget-Gate (mentioned, not carded): not in active discovery — appears at Negotiation stage (Cell 06). Decision criteria: Rp-defensible ROI math, multi-year TCO clarity, contract terms manageable. Treated as gate persona — we prepare for them but don't pitch to them.
IT Director Veto (mentioned, not carded): handled at Trust/Compliance moment of pitch (covered in Cell 05 Pricing safeguard items + Cell 06 Objections). Concerns: data residency, integration surface, security posture, PDP. Not depth-carded here because rep talks to them only at proposal stage.
Within the same buyer profile (CHRO sponsor + L&D Head champion), two distinct sell paths emerge based on whether the customer already has an LMS or needs one. The pitch sequence, objection profile, and integration scoping differ between the two — but the buyer profile and pain map stay identical.
| Path | Customer state | Wedge | Integration surface |
|---|---|---|---|
| Path A · with-LMS | Customer already runs Moodle / Talenta / Workday / SuccessFactors / custom LMS · L&D team trained · investment locked in | "Don't switch LMS — make it smarter with 3 pillars layered on top via SCORM / LTI / API" | IT-led scoping required · varies by customer LMS API depth · standard SCORM/LTI works for most · deeper integration via REST API |
| Path B · without-LMS | SMB or LMS-fatigued corporate · ready to consolidate vendor sprawl · or first-time L&D digitalization | "One platform — modernize foundation + add AI loop in one move. CanPlus LMS bundled at no extra line item." | Native (no LMS-to-pillar plumbing) · onboarding faster · vendor lock-in concern addressed via Yayasan Petra ownership + 4 paten HKI + data portability clause |
How to identify path during discovery: ask "what's your current LMS situation?" early in the call. If they name a vendor (Moodle, Talenta, etc.) and seem committed → Path A. If they describe vendor fatigue or no LMS yet → Path B. Don't assume; ask. Misidentifying the path = pitching LMS displacement to a customer who's married to their Workday investment, OR pitching API integration to a customer who wants one-platform simplicity.
Four sub-blocks. A five-point qualification frame — Situation, Pain, Impact, Critical Event, Decision Criteria — keeps every discovery call aimed at outcome, not features. Pain heatmap shows intensity. Anti-ICP names the no-go. Buyer voice = their words, not ours.
| CHRO Sponsor | L&D Head Champion | |
|---|---|---|
| SSituation | New CHRO ≤18 bulan · post-attrition wave · board demanding "AI roadmap" · 2-4 vendor stack saat ini | 3-5 vendor L&D paralel · team capacity rata-rata 80% utilized · QBR cycle Q+1 setelah budget lock |
| PPain | Kontribusi L&D tidak terlihat di P&L; AI narrative kosong; succession pipeline thin | Vendor sprawl + admin overhead; ROI story lemah ke CFO; team burnout signals |
| IImpact | Personal: career risk jika board ask Q4 jeblok. Org: Rp 200M–2B/tahun training spend tanpa defense. | Personal: burnout + risk kehilangan 1-2 team. Org: training cycle slow 2-3 bulan; vendor switching cost 6-12 bulan. |
| CCritical Event | Q4 budget lock · annual board meeting · post-merger HR integration · OJK / regulator review (banking) | New L&D budget cycle · vendor contract renewal window · ISO/audit finding · QBR ke CFO |
| DDecision Criteria | Strategic narrative · CFO-defensible ROI · 100% Yayasan ownership / audit posture · ID vendor track record · partnership feel | Onboarding rigor · team adoption · vendor consolidation · QBR cadence · self-edit modul tanpa vendor dependency |
Source note: these are representative archetype voices distilled from real discovery calls + Yayasan Petra context + CRM notes. To reach ship-gate criteria the sales team will log the next 5 discovery call verbatim moments tagged by persona — target 8+ verbatim quotes pulled from 3+ real call transcripts.
Pragmatic moves a rep makes. Discovery questions mapped to the qualification frame + listen-for table + disqualify script.
Saya capek" · "repot" · "nggak terlihat ROI-nya"Sudah 3 vendor" · "switching cost" · "vendor sprawl"Board nanya AI strategy" · "CFO push back"Attrition naik" · "tim burn out" · "capacity habis"Kontrak vendor expire" · "budget cycle"Kepingin coba AI" · "eksperimen budget"Tim antusias dengan tech baru" (tanpa pain anchored)Boleh proof-of-concept gratis?" (vendor-shopping signal)Bandingkan dengan Vendor X, Y, Z" (race-to-bottom)Innovation lab" framing tanpa P&L commitmentLihat C.3 di atas — polite-no script. Use kapan: ≥3 red flags listed + 0 acute pain treated. Send via email/WhatsApp dalam 24 jam setelah call. Tagging di CRM: "DQ — vitamin buyer" atau "DQ — below scale" untuk re-engagement reminder dalam 12-18 bulan.
Observable, named criteria. Failure mode if shipped early is concrete.
The discipline carries to any product team that sells through a sales motion. The content rewrites per product.
Feeds Cell 03 Discovery & Pitch (inherits question bank + listen-for) · Cell 04 Product & Packaging (translates acute pains to pillar value) · Cell 06 Objections (inherits verbatim language + per-persona objection profile) · Cell 08 Sales Ops (inherits buyer fit-score signals for lead routing) · Cell 09 Handover (inherits adoption-risk signals from persona profile).