4Rooks Strategy
05_lighthouse_customers/account_files/_account_template

[Company name] — account file

Vertical: [building automation / industrial / smart home / agritech / automotive] Region: [country, city] Size: [revenue band, headcount, embedded engineers] Stage: [0-7 from pipeline_tracker.md] Owner: [Florian / Markus / both]

Why this account is a fit

  • ICP fit: [brief]
  • Trigger event: [what's happening that makes now the moment]
  • ROSA hook: [the one-line case for them]

Buying committee

Role Name Title Status Notes
Economic buyer (CFO/CEO)
Technical champion
Procurement gatekeeper

Contact log

Date Channel Person Summary Next step

Discovery notes (the diagnostic conversation)

  • How many product variants?
  • How many hardware platforms?
  • Embedded engineering team size?
  • % of time on platform vs product?
  • Stack (Zephyr / Linux / Yocto / RTOS / OTA / fleet)?
  • Trigger event and date?
  • Prior standardisation attempts?
  • Buying mechanics (sponsor, budget, procurement)?

What they would buy

  • Free first call ✅ done / not done
  • Architecture & migration assessment (€__k)
  • Pilot (€__k, scope: __________)

Risks / objections

Decision criteria (in their words)

Notes


Last modified 2026-05-05. Suggest a change to this page →