Buying Journey Enablement Example: Industrial
Offering: NFA-500 retrofit controller (Northfield Automation) Motions: direct to large plants; 8 partners (distributors and one integrator) Evidence: win/loss on 8 lost deals; interviews with 3 partners
Why this example exists: the group is larger, the specification is often written by an outside integrator, and partners do most of the selling. The gap sits at requirements building, where the spec is written around a competitor.
## Journey map
| Buying job | Roles active | Needs to move forward | Stall (checked / hypothesis) | Asset |
|---|---|---|---|---|
| Problem identification | Maintenance engineer, plant manager | See the cost of the aging controller | Hypothesis | Status-quo checklist (build) |
| Solution exploration | Maintenance engineer, integrator | Learn that a shift-long retrofit exists | 3 of 8: never considered retrofit | Application note, partner explainer |
| Requirements | **Integrator**, technical evaluator | Spec text and standards summary | **5 of 8 lost: spec named a competitor** | **Spec text + standards summary (missing)** |
| Supplier selection | Procurement, plant manager | Comparable offer, TCO | 2 of 8: unlike-for-like comparison | TCO sheet, battle card |
| Validation | Maintenance engineer | Reference at a similar plant | 3 of 8: no reference in their industry | Reference case (one, permission pending) |
| Consensus | Plant manager, finance | Payback and shutdown risk | Hypothesis | Business-case template (build) |
## Direct vs partner
Distributors: short sales guide, demo unit access, bracket-kit stocking plan, margin sheet.
Integrators: spec text, I/O mapping guide, program import tool, early access to firmware. Direct
team: full narrative, site survey process, battle cards.
## Training and certification
Sales level (half a day: narrative, top objections). Technical level (two days: configure,
install with the bracket kit, commission; **tested on a demo rig**). Service level for partners who
commission. Certified partners are listed, get lead sharing, and a demo unit. Recertify at each
major firmware release.
## Feedback loop
Partner managers log objections and hotline questions; monthly review for six months with Sales,
Service, and product; assets updated; a short "what changed" note to partners.
## Missing assets (ranked)
1. Spec text and standards summary for integrators (5 of 8 lost deals)
2. Business-case template for the plant manager and finance
3. Second and third reference cases (permission needed)
## Stall hypotheses to check
1. Is "no reference in their industry" a real blocker or an excuse? Call two lost accounts.What to learn from this
- The biggest gap is a role the team doesn't sell to. The integrator wrote the spec; no asset served them.
- Partners get a different toolkit, not a shorter one. Distributors need stocking and margin; integrators need spec text.
- Certification is tested on a demo rig. Attendance alone doesn't commission a controller.