We run our own client work on Stacktree. Here’s what we actually send.
I built Stacktree, and I use it every day: for my own consulting clients and to run the company. These are real numbers from my account. The pages are real too, retold with the clients’ details changed.
- Engagement tracker · Acme Travel
- Work delivered · 26 to 30 Oct
- Build 87 · Acme Trips, internal test
- Follow-up emails: wording for review
- Panel brief · From workflow gap to working prototype
- Presenter pack · Conference 2026
- Store review status (auto)
- Growth loop run report · 3 Sep
- Discovery report · a training provider
- Investor update · August
- New-hire pack · booking team
- What changed in October
- A note for a prospect
- Moving road trip · family
One tracker, kept current by my agent.
My main engagement runs on one tracker page: tasks, owners, dates and the next call’s agenda. My agent updates it as the work moves, fifty times in its first month, so the client always has one page that is current. The page tells them how to tick things off themselves: select an item and comment “done”, and the agent applies it and replies.
50 versions in a month, every one keptHow the tracker runs →
The week’s pull requests, written for someone who doesn’t read them.
For a client whose apps I work on, my agent read a week’s pull requests across four repos and wrote them up for someone who doesn’t read code: what shipped, what was waiting for review and why it mattered, and the analysis behind it. One page instead of a status email full of PR links. Run it every Friday and the weeks collect under the client.
How the weekly report runs →Our testers have one link, whatever build they’re on.
When we rebuilt an app, the testers got one page: what’s new since the last build, install steps for iPhone and Android, and the test codes to try. After each build the agent rewrote the top of it, six builds so far, and it has been opened on 33 devices. The link testers saved on day one still works.
How the tester kit runs →A client reviewed a week of follow-up emails without a meeting.
I drafted the emails as one page and sent the link. The client selected words and suggested new ones, or commented where they had a question. Twenty-three comments and six versions later, every change is on the page with a note beside it, and the same link is where the sign-off happens.
Approval on wording →Fourteen pages for one conference panel, in a day.
For a client’s conference panel I needed a presenter pack, a panel brief, a worksheet, sample data, a resources page and four working prototypes the audience could click. Claude Code built and published all fourteen into the client’s space in one day, and the presenter pack has been updated four times since.
The agents that run the company publish their work as pages.
Our growth loop runs on a schedule and published its run reports as pages I could read on my phone. Another agent checks our app store listings and writes what it finds to one status page, with what changed at the top. I read one link instead of a log.
Written by a scheduled agentI publish from the assistant that made the thing.
Of the pages that record which assistant sent them, Claude Code and Claude sent about the same number, and ChatGPT and Cursor the rest. They all land in the same account, and the client work is filed under the same clients. The odd one is personal, like a road trip plan for the family.
Nothing I send is ever the final version, and that’s fine.
Every update keeps the version it replaced: the last 5 on the free plan, the last 50 on paid plans. So my agent can update a client’s page as often as the work moves, and I can always show what changed and when, or put it back.
Send one page your agent keeps current.
Start with whatever changes most: the plan, the weekly report, the test build.