# How we use Stacktree: the pages we actually send Source: https://stacktr.ee/how-we-use-stacktree [Skip to content](#main) PFrom Product Hunt? Your first pages are free, no card. Code `PRODUCTHUNT` takes 50% off your first month of Studio.[Start free →](https://app.stacktr.ee/?join=1&from=producthunt) × A Stacktree customer sent you. Your first month is 50% off on any plan, taken off at checkout. [Start free →](https://app.stacktr.ee/?join=1&from=referral) × [stacktr.ee](/) [Examples](/#proof) [How it works](/#how) [Pricing](/pricing) [Security](/security) [Log in](https://app.stacktr.ee) [Publish one](https://app.stacktr.ee/?join=1) By [Steve Smith](/about) · Founder, Stacktree Last updated November 2, 2026 How we use Stacktree # 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. SSteve Smith, founder 176pages published since May Halfupdated after publishing, at the same link 11clients, with their pages filed under them 50updates to one client tracker in its first month - 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 - 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 01 · The tracker ## 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 kept [How the tracker runs →](/client-project-tracker) A client comments "done" on an item of a project tracker from her phone. The agency's agent marks the item done and the counts update, and the client sees "Your comment was addressed". Then she comments that it is not working on mobile, and the agent reopens it.acme.northbank.studio/trackerStacktreenowA comment on “Engagement tracker”On T7 · doneAcme Travel × NorthbankEngagement tracker · Q4Acme Travel × NorthbankUpdated 07:50, from Dana’s comment9 done8 in progress4 blockedOctober5/21 done- T5In progressLogins on every platform - T7In progressCall tracking on both sitesD - T9WaitingAdmin access for Northbank - T11In progressFollow-up emails after quotes 9:41Acme × NorthbankEngagement trackerOctober · Logins and tracking- T5In progressLogins on every platformList item - T7In progressCall tracking on both sitesList item - T9WaitingAdmin access for NorthbankList item - T11In progressFollow-up emails after quotesList item - T12To doReview the sign-up formList item Tap anything to comment on itCancelCommentList itemCall tracking on both sitesWhat should change here?Only the page owner sees thisCancelPostSent to the page’s ownerYour comment was addressedTicked off. Call tracking is live on both sites.See itClose 02 · The Friday report ## 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 →](/weekly-work-report) The week's pull requests from four repositories arrive one at a time. Each one becomes a plain-language line in a report called Work Delivered, under Shipped or Open for review. The figures count up to 4 merged, 5 open for review, 4 repos and 11 review findings. The report is filed under Acme Travel as week 44. Then the next week's report is written the same way.This week on GitHubgh pr list · 4 repos- emails #14mergedfeat: quote follow-ups+0−0in report → - site #212mergedfix(forms): honeypot+0−0in report → - crm #41mergedchore: dedupe pass 1+0−0in report → - app #96openfeat: offline trip docs+0−0in report → - site #215openfeat: 301s for old URLs+0−0in report → - site #208mergedfix: tour dates in UTC+64−22in report → - emails #12mergedfeat: quote template v2+318−140in report → - crm #38mergedfeat: import bookings+512−9in report → - app #94openfeat: trip map+870−31in report → - site #210openfeat: new tour pages+1,120−12in report → + 2 more pull requestsPublished for Acme Travelacme.northbank.studio/week-43Northbank Studio · 19 to 23 October 2026Work DeliveredShipped, open for review, and the analysis behind it.3merged4open for review4repos7review findingsShippedStarted and merged this week.- Tour dates in the visitor’s own time20 Octsite #208They were an hour off for UK visitors. - A clearer quote email21 Octemails #12Price, dates and what is included, in that order. - Bookings land in the CRM by themselves22 Octcrm #38No more copying them in by hand. Open for reviewWritten, verified, waiting on a merge.- A map for each day of the trip23 Octapp #94needs a callA pin for every stop. - Four new tour pages23 Octsite #210for DanaCopy to check before they go live. Filed under Acme Travel · Week 43 03 · The tester kit ## 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 →](/tester-kit) A tester kit at acme.northbank.studio/test-build moves from build 85 to build 87 at the same address. Your agent adds what is new since build 85 at the top and updates the iPhone and Android install cards.acme.northbank.studio/test-buildBuild 85Internal test · 22 Oct 2026Try the new Acme Trips app New since build 85Also new since build 85- Your map arrow points the way you face.It used to stay on north. - Trip documents open with no signal.Vouchers and the plan work offline. New since build 83Also new since build 83- The plan opens on today.On a trip that has started, not on day 1. - Times are local.Your home time sits underneath in gray. New since build 81Also new since build 81- Meeting points on the map.Tap one for the walk from your hotel. - Bigger text in the plan.It follows your phone’s text size. Install it #### Android Android 9 or laterDownload 41 MBVersion 1.0.0 (85)Link works until 29 Oct #### iPhone iOS 16 or laterOpen in TestFlightVersion 1.0.0 (85)Internal groupVersion1.0.0 (85)Commit3b9d0f4Built22 Oct, 11:05Trip codes- 418 552 907 316Lakes and Lodges, 6 daysCopy - 275 640 118 093Canyon Country, 8 daysCopy - 000 000 004 004The Voucher ScanCopy 04 · Wording, approved ## 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 →](/email-copy-approval) Day 3 email · for review Subject: How your trip would work, ref [quote ref] Hello [first name], in case it’s useful while you decide, here’s how a trip with us works. We arrange everything from the airport to the hotel door, with the guide and the transfers your quote describes. Suggested edit · Dana, ops lead We arrange everything from the airport to the hotel door, We look after the whole trip, door to door, Resolved: changed on the page, same link. 05 · Packs and prototypes ## 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. Client space14 pages ### Conference 2026 · panel - 15 OctPresenter packUpdated 4 times - 15 OctPanel brief3 opens - 15 OctBuild-along worksheetPrototype - 15 OctEligibility checkerPrototype - 15 OctIntake checklist generatorPrototype - 15 OctSample dataData 06 · My own agents ## 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 agent Store review statusUpdated 08:00 ListingStatusSince ChatGPT appLive23 Oct Claude pluginListed1 Oct Claude connectorIn review28 Sep What changed today: nothing. The connector is still in review. 07 · Whatever I’m working in ## I 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. Claude Code32Claude30ChatGPT12Cursor3 The part that makes it work ## 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. Versions4Last 50 kept- just nowReplaced by a connected agent · 40 KBRestore - just nowReplaced by a connected agent · 40 KBRestore - 10 hours agoReplaced by a connected agent · 39 KBRestore - 3 days agoReplaced here · 39 KBRestore - 3 days agoReplaced by a connected agent · 38 KBRestore A returning reader seesUpdated since your last visit: 1 changeT11 · Follow-up emails after quotes · Due 31 OctA returning reader seesUpdated since your last visit: 2 changesT7 · Call tracking on both sites · Done ## Send one page your agent keeps current. Start with whatever changes most: the plan, the weekly report, the test build. [Publish one free →](https://app.stacktr.ee/?join=1&from=seo_how_we_use_stacktree) [See the tracker](/client-project-tracker) stacktr.ee [Page video](/page-video) [Ask this page](/ask-this-page) [Client feedback](/client-feedback-loop) [Client spaces](/client-spaces) [Templates](/templates) [Use cases](/use-cases) [Integrations](/agents) [Alternatives](/alternatives) [About](/about) [Blog](/blog) [Changelog](/changelog) [Pricing](/pricing) [Security](/security) [FAQ](/faq) [Made with Stacktree](/made-with) Building with AI agents? See the [developer docs →](/developers) [Send your first link free](https://app.stacktr.ee/?join=1&from=sticky_how_we_use_stacktree) No card · 3 pages free --- Full markdown summary of the Stacktree marketing surface: https://stacktr.ee/llms-full.txt