> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thread.app/llms.txt
> Use this file to discover all available pages before exploring further.
# Success plans
> Phased plans with owners, milestones and dates — customizable per account, mirrored to the customer portal.
A success plan is what turns "we sold them something" into "we're delivering something." Thread builds plans as phases of work, each with tasks, owners, dates and dependencies. Apply a default plan from a template and then customize for the specific account — without ever forking the template.
## What it looks like
The plan reads top-down as phases. Each phase has tasks, an owner per task (you, the customer, or "joint"), and a target date range. The current phase is highlighted; complete tasks line through; the customer sees the same plan in their portal.
Tasks can be plain checklist items, scheduled actions (an email, a doc, a meeting), or links into other parts of Thread (a workflow run, a form, an upload).
## How it's wired up
| Node | Role |
| ------------------------------ | --------------------------------------------------------------------------------------------- |
| **Apply success plan** | Instantiates a template onto the account. Variables fill in account-specific dates and names. |
| **Milestone start / complete** | Triggers when a phase begins or ends — fire Slack updates, queue follow-ups. |
| **Task action nodes** | Email, doc, meeting, form, upload — each becomes a checkable task on the plan. |
Templates live under **[Templates](https://stitch.thread.app/home/templates)** in your workspace. The "Apply success plan" node in any workflow points at one. Templates are immutable snapshots — applying a template copies its current state onto the account, so future edits to the template don't disturb existing accounts.
## Customize per account
Plans are customizable after they're applied. Without forking the underlying template, a CSM (or a workflow) can:
* Add, remove or reorder tasks for this account
* Reassign owners
* Shift dates to match the customer's timeline
* Drop in account-specific actions that aren't in the template
The customer sees these changes in their portal in real time.
## When to use it
* Every onboarding gets a plan. The question is just *which* template to apply.
* Have one template per segment (Enterprise / Mid-market / SMB) and one per motion (new logo / expansion / renewal). Branch in the workflow before applying so each account gets the right starting point.
## Next steps
The plan in motion — kickoff, milestones, first value.
What the customer sees of the plan.
Wiring up Apply success plan in a workflow.