---
name: "signature-to-launch-and-account-ops"
description: "Use after signature to run onboarding, implementation, and the standing account-ops artifacts that keep the account healthy."
triggers: ["launch plan", "onboarding tracker", "implementation milestones", "account ops", "go-live", "white-space", "site activation"]
version: "1"
---
# Signature to launch and account ops
Use this after signature to run onboarding, implementation, and standing
account ops. Start from the signed scope and start date, the owners on both
sides, the implementation or onboarding milestones, the current standard
operating procedure (SOP), rate file, and contact list if any exist, and the
metrics the account is judged on.
## Turn signature into a launch plan within days
Kickoff date, owners per side, milestone dates, and the go-live or first-value
date. Every milestone has one owner, one date, and entry and exit criteria:
what must be true to start it and what proves it done. A milestone moves only
when its exit test passes.
## Orchestrate onboarding across teams
Ops, implementation, customer success, and customs or compliance where they
apply. You run
the tracker; each team owns its steps. The buyer sees one plan, not five
queues.
## Stand up the account-ops artifacts
The SOP, the rate file, the contact list, and the contract upkeep log — kept
current. A stale artifact is flagged with its last-verified date, never
silently trusted.
## Track implementations line by line
Site or workstream, readiness state, open items with owners, and the
activation date. The stuck site gets the attention, not the average.
## Hold account-health guardrails in every review
Metric performance, revenue quality, and pay and contract-terms adherence. A
breach gets a dated correction with a named owner.
## Feed expansion back, then build white-space
First-year grow plays run from the renewal-expansion skill once the launch is
stable. Launch health first, upsell second. Once stable, build the enterprise
white-space table: product, use-case, business-unit, geographic, and user
expansion, each with dollars, probability, and timeline. Hold a quarterly
exec-sponsor plan beside it: QBR dates, executive visits, and the decisions
each session must produce. Multi-thread every key account across 3 to 5
strong relationships, because a champion leaving is the top expansion risk; a
single-threaded account is flagged at risk.
## What you hand back
The launch plan with dated milestones, the onboarding tracker across teams,
the current SOP plus rate file plus contacts, the site activation read, the
white-space table with exec-sponsor plan, and a health review with dated
corrections.
## Fallbacks
No buyer owners named means you draft the responsibility grid with your side
filled and the
buyer side blank for them to confirm. No existing artifacts means you start
the SOP and rate file from the signed scope and mark every line that needs
buyer confirmation.
## Approval gate
Nothing goes to the buyer and no launch date or SLA is promised without your
explicit yes.