Did the release fix it, or was it the campaign?

Sign-ups went up on Thursday. Was it the new onboarding, the newsletter, or the launch on Product Hunt? The release log is in one tool, the campaigns in another, the price change in a chat thread. So the answer is a guess.

Changes puts them on one timeline, next to the numbers they could explain.

A change is one thing that your company changed, or one thing that changed around it. It has a time, a kind, a title and who wrote it. The time can be a moment, a day, a week or a range.

Releases that you already send to Sequential show on the timeline by themselves. You do not record them again.

Tallyfox is the invoicing app in our demo. Its timeline holds three releases, a new price for Pro, a Product Hunt launch, a flag for a new invoice editor, a new onboarding checklist, a tracking change and a slow day at its payments provider. A newsletter that an agent proposed waits for a person to confirm it.

Release 2.14.1 named two cases. One is invoice-mailer: SMTP timeout, an error from the server. Before the release, it came on 6 of 8 days. Since the release, Sequential has not seen it. The release page shows each case and how it is doing, and what else changed around the release.

You see the facts side by side. You decide what they mean.

1. 01

   The cases it named.

   Each case that the release claims to fix, with its stage, for example Measuring, Fixed, Improved, No change or Worse.

2. 02

   What else changed around it.

   The campaigns, price changes and incidents near the release, so a better number is not given to the wrong change.

3. 03

   Sessions and a funnel, before and after.

   Open the sessions on either side of the release, and compare a funnel before and after it.

A change can also name the cases it addresses, such as a flag or a copy change. You link them on the change.

• People. Owners, admins and members record a change on the Changes page: a title, a kind and a time. The time is now by default.
• CI and coding agents. A project token with changes:write records changes through MCP or the API, one at a time or up to 100 from one source. A re-run changes nothing twice.
• Chat agents propose. An agent in claude.ai or ChatGPT can only propose changes. They wait on the Changes page until a person confirms them.
• History too. An agent can record changes from the past, for example last quarter’s campaigns from your marketing tool.

Changes knows only what your team and your agents record. So Sequential never reads an empty week as a quiet week. When an agent asks about a period with no changes, the answer says: "No changes are recorded for this period. That says nothing about whether anything changed." A list of changes near a time says: "Nearness is not cause."

Sequential shows the facts side by side. It never says that a change caused a number to move.

• Who sees what. A planned price change and some company changes are for owners and admins only. Everyone else sees the change after it happened, or never.
• Viewers read. Viewers see the changes that everyone can see. They do not record changes.
• Text is checked. Titles and summaries are one line. Sequential refuses links, emails, secrets and text that reads like an instruction to an AI.
• Optional. Cases, releases and charts work the same without Changes. Record as much or as little as you like.