onecell

Sign in

Help/Recipes/Studio or agency developer

Client update page

Written for them, not for the team.

For
A studio or agency developer, or anyone who reports to a client or stakeholder
When
Weekly, at a milestone, or at the end of an engagement
Takes
A few minutes of agent time
You get
A draft update in the client's cell, in their language, ready to share as a read-only link once you have read it

The prompt

Not connected yet? Set up your AIRun in ClaudeRun in ChatGPT
Write a client update for <client> covering <period>, from what is in
onecell and the repo. Save it to <client's cell> as a draft.

1. Gather: the latest repo snapshot and any handoffs for this client's
   work (search), decisions made in the period (list_decisions for the
   cell), and git log if the repo is here.

2. Write for the client, not the team: what they can now do or see, in
   plain words. Leave out internal work unless it changes something for
   them. Never claim anything that isn't live for them.

3. Sections: new this period, fixed, coming next (no dates unless we have
   agreed them), and anything we need from them, as a callout.

4. Reply with the link. Don't share it or create a link until I have
   read it; then share_document gives me a read-only link to send.

What your agent does

  1. Gathers what happened

    Snapshots, handoffs and decisions from the client's cell, and the git history when the repo is at hand.

  2. Translates for the client

    What they can now do or see, without internal detail, and nothing that isn't live for them.

  3. Writes a draft in their cell

    New, fixed, coming next, and what you need from them.

  4. Waits for you before sharing

    Nothing leaves onecell until you have read it. Then one command makes a read-only link.

What you get back

Open the full example →

An update for Northwind Studio, a made-up client of a made-up invoicing app. Internal work, like the reminders rebuild, appears only as what the client will notice.

Sample client update: Northwind's invoicing portal, week 3

This week

Your clients can now pay part of an invoice and come back for the rest. You'll see each payment on the invoice, and the reminder only asks for what is still owed.

Invoices you send to clients in Germany and France now arrive in their language, with the right tax wording.

Try it

  1. Open any unpaid invoice

    Choose Allow part payments under Payment options.

  2. Send it to yourself first

    Pay a small amount with a test card to see what your client sees.

Next

Reminders are being rebuilt so none is ever sent twice. You won't notice a change, apart from fewer apologetic emails from us. Expected by the end of the month.

What we need from you

  • Tell us which of your 14 team members should get payment notifications
  • Send your logo in SVG, for sharper invoice PDFs
.md for agents

Variations

A handover pack at the end of a project

Ask for a handover instead: what was built, how to run it, where everything lives, every decision made (from list_decisions), open items, and who to ask. Point to where credentials are kept, never the credentials themselves. It pairs with the project primer and the latest snapshot.

A stakeholder update inside your company

Replace the client with a team or leader, and add: “Lead with what they need to decide or unblock.”

One cluster per client

Keep each client in its own cluster, with a cell you share with them. Their updates, decisions and handover then live where they can read them, and nothing from other clients is in view.

Tips

  • Read it as the client would before sharing. “We refactored the auth layer” means nothing to them; “sign-in is faster” might.
  • Only claim what is live for them. “In early access” is fine when it is true.
  • Ending with one ask gets more replies than ending with none.