1 · Define the activation "aha moment"

The single highest-leverage thing for a self-service SaaS is naming the moment a new user first gets real value, then measuring time-to-it. For Vemcount that's likely first sensor connected → first live data seen, or first report created. Once it's named:

• Every onboarding/re-engagement Series uses it as the goal/exit rule — stop nudging once a user reaches it.

• Track activation rate (% of signups who reach it) and time-to-activation as your core onboarding metrics.

• Push the milestone to Intercom as an attribute (e.g. activated = true, first_data_at) so messaging can branch on it.

2 · An in-app onboarding checklist (not just a tour)

Tours are one-time overlays; a persistent checklist stays until the user finishes. For self-service activation this usually beats a tour because it's always visible and shows progress. Suggested items:

• Connect your first sensor ☐

• See live data on a dashboard ☐

• Build your first report ☐

• Set one alert ☐

Build it in Intercom (Checklists), tick items via the same platform attributes that drive the aha-moment tracking, and hide it once complete.

3 · Contextual in-app help (deflect tickets)

Beyond onboarding, surface help where users get stuck — a targeted message or article suggestion based on where they are in the platform. Examples:

• Sitting on an empty dashboard a while → "Want help adding your first widget?"

• On the reports screen with no report built → suggest the custom-report guide.

• A sensor showing offline → surface the troubleshooting article inline.

These are Intercom outbound messages/tooltips gated on the page or a platform attribute. They're the self-service safety net that prevents support tickets.

4 · Fin as the front line

Fin is already live on the content. The self-service play is to let Fin resolve the long tail of "how do I…" questions before a human is needed, and to mine Fin's conversations for which articles are missing or weak — then fill those gaps. Treat unanswered Fin questions as your content backlog.

5 · Expansion loops (licences = ARR through the product)

Self-service should also drive growth. When a user hits a usage signal, suggest the next module in-app:

• Lots of footfall data but no sales data → suggest conversion tracking.

• Single entrance counter running well → suggest zone/dwell analytics.

• Office occupancy in use → suggest IAQ; facility energy in use → suggest the full ESG set.

Each nudge links the relevant guide and grows licence count — ARR expansion driven by the product itself, not sales outreach. Reuse the per-segment value points from the onboarding Series copy.