Send the client update without rebuilding the week from memory.
Every Friday the same tax lands: someone reconstructs what moved, what got decided, and what is still open, then writes it up client by client. The work of remembering is the drag. The judgment about what to say, and whether to send it, stays with you.
Two calls, a Slack thread, three approvals and a scope change are scattered across tools. Nobody holds the whole picture.
The week's activity, decisions and open items are pulled together into a plain draft update per client, sourced and dated.
You cut what the client does not need, sharpen the risk line, and add the context only you know.
The update goes out because you approved it. The reconstruction is gone; the relationship is still yours.
Representative scenario. The moments and timings are illustrative of how a week can go. They are not a client result.
Three plain tools. One useful change.
Status Builder
Turns the week's activity into a first-draft update per client.
It reads the project trail you already keep and assembles progress, decisions and open items into a plain draft, with every line traceable to where it came from.Approval Trail
Keeps a running record of what was agreed and when.
Approvals, scope changes and sign-offs are captured as they happen, so nobody has to remember who said yes to what on which call.Open Items
Surfaces open issues and where each one needs to go.
It flags blockers, waiting-on-client items and slipping dates, and suggests who the next step belongs to. You confirm the call and the wording.The system prepares the work. A person still decides.
Drafts are built only from the project records you already maintain, and every claim points back to where it came from.
The draft is a starting point. You edit the tone, cut what does not serve the client, and add the context only you hold.
Nothing reaches a client until a person reads it and sends it. There is no auto-send and no exception for a busy Friday.
The system can surface a slipping date or an open issue. Whether and how to raise it with the client is always your decision.
Effort and time first. Outcomes later.
Effort and time first, because you can feel those in a week. Whether clients feel better cared for is slower and directional, and it comes later.
After a client call, someone records what was actually said. The decisions, the promises, the thing the client is quietly worried about. If that stops, the Friday update gets assembled from an empty file and reads like it.
See how the Lookout works