Product updates, playbooks and stories from teams building with Atwork.
An AI-drafted client update can remember what you promised last week. What it keeps, for how long, where to see it, and how to forget one client.
An approval belongs where an AI agent decides what to change. Here is where to put one in a workflow, who gets it, and what happens if nobody answers.
An Agent step reads each new client request and labels it in scope, change request or new project, so a change gets priced before anyone does the work.
What an agency project management template has to hold: clients, briefs, deliverables and freelancers, plus a client approval column separate from status.
What can genuinely run unattended in agency client reporting, what still needs a person, and the one status setting that decides whether it works.
Over-servicing is a definition problem, not a time-tracking problem. How to record scope where the work lives, and catch the overflow in week two.
Utilisation rate measures capacity consumed, not revenue earned. Why a utilisation target destroys the signal, and which number to read beside it.
Most multi-client setups duplicate the process once per client. Which parts should be shared, which should vary, and why client isolation is a separate problem.
Scope creep is not caused by pushy clients. It is caused by a change process that costs more to follow than to ignore. How to make raising it the cheap option.
Handover documents cover what is findable and miss what is remembered. Why an overlap beats a document, and what to capture while the work is still running.
The three retainer pricing structures, how each one fails, and why pricing from the hours you sold rather than the hours you delivered underprices by design.
The percentage-of-revenue answer is unusable because it only counts the invoice. A better test: does the tool replace hours, replace a tool, or add an obligation?