You finished the analysis. Now you have to share it.

The exec wants a one-pager. The team wants the working numbers. The board wants the chart, the headline, and a sentence. It's the same data, three different stories — and until this week, telling all three meant duplicating the project, copy-pasting blocks, and praying nobody asks you to update one of them.

That's done.

A project can hold many reports

Open the Report tab. There's a dropdown next to the title now. Create new report. You get a blank board, attached to the same project, the same datasets, the same chat history. Anna already knows everything she knew a second ago.

Build the exec one-pager there. Switch back to the original. Build the deep-dive in a third. Each report has its own title, its own blocks, its own publish status. Switching between them takes a click.

Ask Anna to start one for you: "draft a board summary as a new report." She'll create it, switch into it, and start filling it in — without touching the report you were just looking at.

Reports belong to the project, not the dataset

Before today, opening a different dataset inside a project would swap out the report you were working on. The board belonged to the dataset, not the project, and you'd lose your place every time you flipped sheets.

Now the report follows the project. Switch between sales, returns, and inventory in the same project — your active report stays in view. The numbers refresh against whichever dataset you're holding; the layout doesn't move.

This is the change underneath the obvious one. It's why multiple reports work cleanly: they were never going to make sense as long as a report was a property of a single sheet.

Each report publishes on its own

Every report has its own public URL, its own snapshot, its own publish status. Unpublishing the deep-dive doesn't touch the exec summary. Republishing the board update doesn't bump the rest.

And every link is yours to name.

heyanna.studio/p/q3-revenue-deep-dive
heyanna.studio/p/q3-board-summary
heyanna.studio/p/q3-customer-segments

Anna defaults to a readable slug from the report title. You can edit it inline before you hit publish, or leave it alone if you don't care. The exec opens a link that says what's inside.

A snapshot date sits under every public report — "Snapshot of April 24" — so the recipient knows when the numbers were captured. If you keep working and the data moves on, Anna shows a small republish hint inside the Report tab. Your call whether to push the new version live.

The pattern this unlocks

The pattern is one project, many narratives. The data is the data — one place to prep it, one place to ask questions, one place Anna remembers everything. The narratives split out from there:

A live board for your own working notes.
A trimmed exec summary for leadership.
A deep-dive PDF for the team that wants to verify the math.
A board update that gets republished every month.

Same project. Same datasets. Same conversation. Different reports, each with the audience it was built for.

You stop choosing whose version of the truth wins.

Smaller fixes that come with this

The Report tab header collapsed into one row. Less chrome between you and the canvas.
A first-publish consent step, so the link going public is always deliberate.
Settings now lists every report you've published — hard-delete the ones you're done with.
Deleting a draft unpublishes its link. No more orphan URLs.

Open a project. Build the report your audience actually needs.