> For the complete documentation index, see [llms.txt](https://guides.tability.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.tability.io/docs/playbooks/build-and-track-your-90-day-strategy.md).

# Build and track your 90-day strategy

Turn your business context and data into a practical 90-day plan, then track it in Tability.

To start, share this page with your AI assistant and say:

> Run this playbook

The instructions below are for your assistant. You don't need to read or copy them.

***

### Instructions for AI assistants

If the user shares this page (or an article linking to it) and asks you to run it, follow the steps below from start to finish. If they only ask you to read, summarize, or edit it, do that instead.

#### Ground rules

* **Ask one short question at a time.** Deliver a first draft of the plan within five questions about the business. Reuse anything the user has already told you.
* **Let the user name the business.** Never assume it's Tability, this page's publisher, or whatever account or tools are connected.
* **Confirm before touching a Tability workspace.** Only use a workspace the user gives you by URL. Show its name and ID and get a yes before reading from it or writing to it.
* **Don't make up numbers.** If a baseline is unknown, say so. Label figures as measured, estimated, or proposed.
* **Verify what you write.** Read records, updates, and scheduled jobs back before saying they worked.
* **Keep the user in charge.** Ask before changing strategy, targets, owners, or existing goals. Don't message anyone else.
* **If something is blocked**, keep the work done so far, tell the user the exact next step, and carry on with what you can.

***

### 1. Choose how to track

Start with a brief intro and ask:

> Would you like AI to automatically track progress on your 90-day plan and run regular reviews, or would you prefer to track it yourself?

If they choose automatic tracking, check whether this tool can run scheduled tasks that use connected tools (for example, [Claude Cowork](https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork) or [ChatGPT automations](https://learn.chatgpt.com/docs/automations)). If it can't, recommend one that can, and give the user a short message to paste there with their answers so far. They can also stay here and move tracking later.

### 2. Understand the business

Ask:

> Which business are we planning for? Share its website, or its name and a short description.

Then ask only what you still need, such as:

* The biggest challenge right now.
* What success looks like in three months, with numbers if they know them.
* The main constraint, such as team size or budget.
* Whether to include goals and results from an existing Tability workspace (if yes, ask for its URL).

While you ask, research: read the website and check any connected analytics, sales, billing, feedback, or project tools. Make sure each source belongs to this business.

### 3. Draft the plan

Recommend a strategy for the next 90 days:

* **Diagnosis:** where the business is, where it wants to be, and what's in the way.
* **Choices:** what to prioritize, and what to stop or defer.
* **2–4 themes** covering Product and go-to-market, each describing a change (for example, "make onboarding effortless").
* **2–3 measurable goals per theme**, each with a baseline (or "unknown"), target, deadline, owner, and data source.
* **Actions** that drive the goals, with owners, the first two weeks, and 30/60/90-day milestones.
* **Five KPIs** to watch, with how each is calculated and where the data comes from.
* **Open questions** and data gaps.

Use OKR terms (objectives, key results, initiatives) only if the user already works that way.

Save it as `{business-name}-90-day-plan.md`, marked Draft, using the outline at the end of this page. Share it with a short summary of the key targets and tradeoffs, and ask whether they approve or want changes. Once approved, mark it Approved and move straight on to tracking.

### 4. Set it up in Tability

Ask for the Tability workspace URL to use (or confirm the one they already shared). If they don't have one, point them to [sign up](https://tability.app/signup) and [connect Tability to their AI tool](https://guides.tability.io/docs/become-a-tability-power-user/integrations/tability-mcp-server).

Confirm the workspace, then create the plan:

* Themes → objectives
* Goals → key results (called "outcomes" in the API)
* Actions → initiatives
* The five KPIs → KPIs

Assign owners to real workspace members, leave unknown baselines empty, and avoid duplicating anything that already exists. Add record links to the plan file.

### 5. Test the first update

Pull the current value for each goal and KPI you can reach, record it in Tability with a one-line note, and confirm it saved. Tell the user which measures will need manual updates.

### 6. Set up reviews

**Automatic:** create two scheduled tasks, and give each one the plan file and everything it needs, since it won't remember this conversation.

* **Progress check** (at a cadence that suits the data): update measures and flag risks or blockers. Only notify the user when something needs attention.
* **Weekly review:** summarize the five KPIs, what moved, what stalled, and the three most useful actions for next week.

Both should stop at the end of the 90 days, after a short retrospective.

**Manual:** give the user a check-in prompt and a weekly review prompt they can run themselves.

### 7. Wrap up

Share the final plan file and a short summary: links to the Tability plan, the first actions and owners, what the first update recorded, when reviews run, and anything the user still needs to do.

***

### Plan file outline

markdown

```markdown
# {Business}: 90-day plan
Status · Dates · Timezone · Tracking (automatic or manual)

## Summary
## Diagnosis and evidence
## Priorities, and what we're deferring
## Themes and goals
## Five KPIs
## Actions, first two weeks, and 30/60/90 milestones
## Open questions and data gaps
## Sources
## Tracking setup (links, schedules)
```

**END OF PLAYBOOK**