stacktr.ee
By · Founder, Stacktree Last updated
Client project tracker

A project tracker your client updates by commenting.

Publish the plan once. Your client ticks things off from their phone with a comment, no login. Your agent reads the comments, updates the page at the same link, and replies to each one.

Publish a tracker free → Open the live example
No login for your client Works from a phone One link for the whole project
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.

Live How Northbank Studio runs Acme Travel’s project. An example, retold from a real engagement.

How it runs

Three moves. None of them is a status meeting.

The page is where the project lives for the client. The comments are how they talk back. Your agent does the bookkeeping in between.

01

Your agent publishes the plan.

Ask Claude, ChatGPT or Claude Code to turn your notes into a tracker and publish it under the client. Every task gets an id, an owner, a status and a date.

02

Your client answers on the page.

They select an item and leave a comment, from any browser or phone, with no account:

doneticks it off doingmoves it to in progress blocked: no loginmarks it blocked and says why due: 12 Novsets a date owner: Danareassigns it anything elsebecomes a note on the item
03

Your agent applies it and replies.

On the schedule you give it, it reads new comments, updates the items and the counts, republishes the same link, and answers each comment with what changed. The client sees “Your comment was addressed” the next time they open the page.

Recorded in the real comment layer

All your client does is tap, type a word and post.

This is the example tracker on a phone, with Stacktree’s real comment layer. Everything after Post happens on your side.

Recorded on the example tracker. The agent’s overnight run is cut to three seconds.

Why a page

Your client won’t log into your project tool. They will open a link.

The usual way

  • ×A board they never log intoInvites expire, passwords get lost, and updates go back to email.
  • ×A weekly status emailOut of date by Tuesday, and nobody can find last week’s.
  • דCan you resend the link?”Every update is a new attachment, so there are five versions in circulation.

With a tracker page

  • ✓One link they bookmark at kickoffStill the right link at handover. Every page you send them can collect at their own address.
  • ✓Answered from a phoneA comment on an item is the whole interface. “done” is enough.
  • ✓Every change keptEach update keeps the version it replaced, so you can always show what changed and when.
Every version kept

Fifty updates in a month, and every one of them is still there.

Each time your agent updates the tracker, the version it replaced is kept: the last 5 on the free plan, the last 50 on paid plans. Restore any of them at the same link, from the page screen or by asking your agent.

Set it up

One prompt, then a schedule.

Paste this into Claude Code, Claude or ChatGPT with Stacktree connected. Fill in the client.

Prompt
Build an engagement tracker for <client> as one page: every task with an id (T1, T2...), an owner, a status (to do, doing, waiting, blocked, done), a due date and a short note, grouped by month, with the counts at the top and the agenda for our next call.

Publish it to Stacktree under the client "<client>" with comments on, and add this to the page: "Select an item's title and leave a comment: done, doing, waiting, blocked: why, due: date, owner: name."

Then, every weekday at 8am: read new comments with list_feedback, apply each one to the tracker, update_site the same page, and resolve_feedback each comment with one line saying what changed.

The schedule is your agent’s: a Claude Code routine, a cron job or a ChatGPT scheduled task. Stacktree keeps the comments until they are resolved, so a run that is late or skipped loses nothing.

S
We run our own client engagements on a tracker like this. My agent updated one fifty times in its first month, and the client always had a single page that was current. It is the page I would least like to go back to doing by email.
Steve Smith, who built Stacktree. How we use Stacktree →
FAQ

What people ask before they send one

Does my client need an account? +
No. They open the link in any browser, phone included, select an item and leave a comment. If the page has a passcode they type it once. There is nothing to sign up for and nothing to install.
Who sees the comments? +
By default only you, the page owner. Turn on shared review and everyone you sent the page to sees each other's comments too. Either way, the reply your agent leaves when it resolves a comment reaches the person who wrote it: "Your comment was addressed", with the note, the next time they open the page. Send each client their own named link and it follows them to any device. If the page asks for their email, the note is emailed to them too.
How does the agent know there is something to do? +
It asks. Your agent reads new comments with the list_feedback tool, on whatever schedule you give it: a Claude Code routine, a cron job, a ChatGPT scheduled task, or just asking it on Monday morning. Stacktree keeps the comments until they are resolved, so nothing is lost between runs.
What if the agent gets an update wrong? +
Every update keeps the version it replaced: the last 5 on the free plan, the last 50 on paid plans. Ask your agent to list_versions and restore_version, or restore from the page screen. The link never changes either way.
Why not just share our project tool? +
Because the client has to adopt it. A page they can open from an email, read on a phone and answer in a comment asks nothing of them. You keep the system of record wherever you like, and the page is how the client sees it and talks back.
Can I keep it private? +
Yes. Links are unguessable by default, you can add a passcode on any plan, and paid plans add your own domain, a company-email gate and one address per client where every page you send them collects.
Weekly work report Tester kit Client feedback loop Approval on wording Client spaces

Send the plan as a page. Let the client tick it off.

Your client never needs an account. Free to start: a free page lasts 7 days, and up to 90 while your client keeps opening it. Paid plans keep it for as long as the work runs.

Publish a tracker free →