Attune connects to the tools your team already works in, reads what actually happened this week and writes the client update, with a receipt on every line.
The rhythm. One page every Friday and nothing in between that has not earned it. Progress sits quietly in the panel: no push, no interruption.
Checkout is through QA and ships Thursday. The two blockers you raised on Tuesday are closed and the third needs your sign-off on the copy, which is now the only thing between us and the date. Design is approved and in the build and the updated brand guidelines are live in your workspace.
Every place you look costs a few minutes. None of them feels like the problem. Then the afternoon is gone. Leave it three weeks and you are not writing an update at all, you are reconstructing one from cold.
Nine minutes here. Twelve there. None of them felt like the problem.
Four weeks of scrolling back before you can write a sentence. What goes out is still the short version.
The monthly update is assembly, not authorship. Everything in it is already written.
The client stops wondering whether anything is happening. The record answers it before they have to ask.
A slip you catch in three days is a conversation. The same slip three weeks later is a scope problem.
Every post above is one entry in the engagement. Together they are the record: what shipped, what broke, what you asked for and what they still owe you. Scroll it.
Checkout is through QA and ships Thursday. The two blockers you raised on Tuesday are closed and the third needs your sign-off on the copy, which is now the only thing between us and the date. Design is approved and in the build and the updated brand guidelines are live in your workspace.
Checkout v2 went live at 2:50pm. Your customers get new checkout screens, a shorter address step and saved cards. The copy change you signed off on Monday shipped with it. Rollout notes and the updated brand guidelines are in your workspace.
The provider outage cleared at 8:40 and the checkout deploys are running again. Thursday holds.
The checkout copy deck is ready for your review. Three screens changed. The two questions you left last week are answered on screen two. It is on the staging build, so you are reading it in place rather than in a PDF. Ten minutes should cover it and anything you flag we will turn around Thursday.
checkout-copy-deck · stagingWe are 62% through the retainer with five weeks left. Flag a scope conversation now, before it becomes an invoice conversation.
Priya approved the supplier API paid tier. It is in this sprint and the two issues waiting on it are moving again.
The third supplier API needs a paid tier to go past 500 calls a day. It is $90 a month and it is not covered by the current retainer. Two issues are waiting on the answer and nothing else is affected.
No reply by Thursday and we proceed without it.
The third blocker is on them, not us. Do not frame it as our delay. Push for copy sign-off Monday or Thursday slips.
The checkout rebuild moved into build this morning. The first screens should be testable on Wednesday.
Issues closed, PRs merged, cycles completed, designs approved. The difference between “we’re on it” and “it’s live.”
The blocker raised in a thread on Tuesday and quietly resolved on Wednesday. The decision that never made it into a ticket.
Retainer burn, hours against scope, what is invoiced. The number the client is actually going to ask about.
Your team talks about the client. The client reads about the work. Attune keeps those two things in the same thread without ever letting one leak into the other. Visibility is set per post. Internal notes are invisible to the client account, not merely hidden.
One-click OAuth for Linear and Plane. Or point Attune at any MCP server. Credentials are held at the agency, never per-client.
Tell Attune which projects, repos and channels belong to which client. That scope is the wall. Nothing outside it is ever read.
Attune gathers the week’s signals and writes the update, citing the source behind every claim so you can check the ones that matter.
Nothing reaches a client until you allow it. Auto-publish is an opt-in that ships switched off, so you turn it on once the drafts have earned it. Marking a line internal-only has no such switch: it stays on your side of the wall for good.
“Once we posted little and often, the big updates wrote themselves.”
Writing updates was the job nobody wanted. The longer we left it the worse it got, because a month-end update meant reconstructing a month. Posting more often fixed two things we did not expect. The client could see momentum without having to ask for it. And by the time a major update was due, the information was already in front of us. It also meant we caught drift while it was still a conversation rather than a scope problem.
Connect your stack and see what your last week actually looked like.