When your company changes
A pivot, a raise, a first hire or a new customer. How to tell Pythe, and what each way changes: the dossier, a regenerate, a progress update, the weekly review or graduation.
Updated 2026-10-13
Plans go stale. Pythe has five ways to bring a plan back in line, from small to large.
| Change | Use | What it does | Cost |
|---|---|---|---|
| You finished or learned something | “Tell Pythe what happened” on Home | Ticks matching tasks, marks others in progress, adds any new work the update implies. | A short AI call |
| A week has passed | The weekly review | Compares plan with what you did, asks questions, proposes adds, changes and removals. | About 0.25 credits |
| One new idea | Add more | Drafts one to three milestones for you to confirm. | A short AI call |
| Something big happened | Regenerate your plan | Rewrites only the open milestones with the new context. Completed ones stay. | A plan build |
| The company itself changed | Edit the dossier, then regenerate | Changes what Pythe believes about you, including your stage. | A plan build |
| You finished a stage | Graduate to next stage | Marks the stage graduated and writes the next one. | A plan build |
Dismissing work
If a task does not belong, Dismiss it and say why. The reason is kept so later plans do not bring the same work back.
Examples of what to type when you regenerate
- We just raised a pre-seed round.
- We discovered a new ICP that is converting better.
- We pivoted away from B2C to B2B.
- We hired our first engineer.
- We launched and got early traction.
- New ICP: dental clinics, not vets.
Your own AI apps can make small changes too, such as adding a milestone or updating a status, but only when you ask. See MCP: plan tools.