# Track enterprise implementation timeline

> Follow an enterprise account from kickoff through integration, first data, first value, and blocked steps so solutions teams can unblock launches.

## Agent adaptation contract

- Canonical human page: https://agentry.sh/workflows/implementation-timeline
- Execution mode: on_demand
- Immutable automation template: none
- Applies to: enterprise-sales, b2b-saas, devtools-api
- Required example events: implementation_milestone
- Required Agentry resources: none declared
- Do not use when:
  - Do not use until the example events are mapped to observed project signals, the current onboarding state is verified, and live event/property reads prove the required data is present.
  - Do not recommend this when the product has no stable account or workspace identity.
- Ask before using:
  - Which observed events map to implementation_milestone? Is the current onboarding state verified, and do live event/property reads show non-synthetic traffic for them?
  - Which live properties provide implementation_milestone.account_id, implementation_milestone.milestone, and which stable user or account identifier joins the signals?

This is an adaptable workflow example, not an API recipe. Map event and property names to the project's saved signal map, require status: "verified" from GET /v1/projects/:project_id/onboarding, and confirm the required signals through live event/property metadata and rows. Fetch current OpenAPI or query-blueprint details before making calls. Do not infer unattended authority from this page.

## Why this matters

Enterprise adoption is a sequence, not a single signup. When accounts stall, CS and solutions need to know which milestone is blocked and for how long.

## What you get

- Timeline per account
- Days since last milestone
- Accounts blocked before first value
- Suggested follow-up owner

## Walk through it

**You:**
> Which enterprise implementations are stuck?

**Agent:**
> I'll reconstruct milestone timelines by account.

```text
Endpoint: POST /v1/projects/:project_id/analytics/query
Exact shape: /v1/openapi.json?path=%2Fv1%2Fprojects%2F%7Bproject_id%7D%2Fanalytics%2Fquery&method=post
Custom HogQL goes in the OpenAPI-defined `query` field.
Concept fields:
  query: "SELECT properties.account_id AS account, properties.milestone AS milestone, min(timestamp) AS first_seen, max(timestamp) AS last_seen FROM events WHERE event = 'implementation_milestone' GROUP BY account, milestone ORDER BY account, first_seen"
```

## The output

The agent returns each stuck account, last completed milestone, days stuck, and next action. It should read like an implementation standup note.

## Setting it up

Emit `implementation_milestone` from backend workflows, CRM sync, or manual admin actions.

## Variations

- *"Only show accounts with a signed contract."*
- *"Group blocked accounts by missing milestone."*
- *"Draft the implementation status email."*