HG Insights|Phoenix

Onboarding Milestone Tracker (30/60/90)

Walk into the 60-day check-in knowing exactly which milestone slipped.

Onboarding Milestone Tracker (30/60/90)
Sample preview

Sample output for this workflow will appear here once it is captured.

Run the workflow in Claude, ChatGPT, or Phoenix Playground using the buttons below to see real output.

Overview

For newly-closed customers, surface which 30/60/90-day adoption milestones have been hit vs missed. Reads adoption intensity over the first 180 days from your supplied `onboarding_start_date` (CRM), checks functional area engagement, and verifies named sponsors are still present. Output is a milestone checklist with green/yellow/red on each — your CSM walks into the 60-day check-in knowing exactly which milestone slipped.

Use cases

  • Catch onboarding stalls before they become churn risks

    A customer that misses the day-30 adoption milestone is 3x more likely to churn at renewal. This workflow surfaces which milestone slipped, when, and what the strongest evidence is — so your CSM intervenes on day 35, not day 365.

  • Sponsor-still-here check

    The exec who bought your product six weeks ago may have already moved to a new role. If `contact_search` no longer returns them, the workflow flags it as a yellow on the sponsor-stability milestone — and your CSM knows to multi-thread before the 60-day check-in.

View workflow prompt
# Onboarding Milestone Tracker (30/60/90)

## Parameters

- `{{domain}}` *(required)* — Customer company domain. Example: `acme.com`
- `{{your_product}}` *(required)* — Your product the customer onboarded. Example: `HG Insights`
- `{{onboarding_start_date}}` *(required)* — CRM-supplied onboarding start date (YYYY-MM-DD). Required because company_contracts cannot derive it (outsourcing-only data).. Example: `2026-02-01`
- `{{prior_contacts}}` *(optional)* — Comma-separated named sponsors from the deal cycle. Example: `Jane Doe, John Smith`

## Purpose
Surface which 30/60/90-day onboarding milestones have been hit vs missed for {{domain}} on {{your_product}}, anchored on the CRM-supplied {{onboarding_start_date}}. Output is a milestone checklist with green/yellow/red on each.

## Process
1. **Compute milestone dates** — from {{onboarding_start_date}}: day-30, day-60, day-90 dates.
2. **Adoption shape** — `company_install_time_series` for {{domain}} filtered to {{your_product}}, `timeRange: last_6_months`. Look at `data_points[]` from {{onboarding_start_date}} onward. Did `current_intensity` cross the threshold (typically 30) by day-30, day-60, day-90?
3. **Functional engagement** — `company_fai` filtered to {{your_product}}. Capture current `departmentUsageShare` in the target function (Engineering / Sales / IT / etc.). The tool is point-in-time — no growth field. A product onboarded to Engineering should show meaningful current Engineering `departmentUsageShare` by day-60; if the target function shows a low current share, that's a missed engagement signal regardless of whether it's "down" (no temporal baseline available).
4. **Sponsor coverage** — if {{prior_contacts}} is supplied, iterate each name and call `contact_enrich` with parsed firstName + lastName + `companyDomain` = {{domain}} (named-presence check; `contact_search` only filters by title / seniority / location, not by name). Are the deal-cycle sponsors still in seat? If not, that's a yellow on the "sponsor stability" milestone.
5. **Company-context check** — `company_firmographic` for {{domain}} static context (industry, scale). For strategic events (M&A, RIF, new CIO) in the onboarding window, route through `web_search` (and `sec_filing_section` if public). Firmographic is static-only, not an event stream.

## Output Format
- `# 📋 {{domain}} — Onboarding Health (Day-N of 90)`
- `## Milestones` — checklist:
  - `Day-30: <Hit|Missed>` — `current_intensity` at day-30 + evidence
  - `Day-60: <Hit|Missed>` — `current_intensity` + first FAI signal + evidence
  - `Day-90: <Hit|Missed>` — adoption shape + sponsor still present + evidence
- `## Recommended next step` — one action tied to the first missed milestone (or "Continue cadence — all milestones hit")

## Quality Checklist
- {{onboarding_start_date}} is the anchor — never compute a start date from another signal
- Each milestone cites its data
- Sponsor stability is "unscored" if {{prior_contacts}} empty (no absence inference)
- Strategic-event context is non-judgmental — flagged separately from the milestone verdict
- Cap tool calls at ~8