Product updates, playbooks and stories from teams building with Atwork.
Separate planned hours, certainty and real capacity before you hire. Why teams feel busy with capacity spare, and four ways to resolve an overbooked week.
Web builds slip because the critical path runs through the client's week. Why a page needs two states, when to ask for content, and how to date a launch.
What a client portal should show, how to give clients access without workspace membership, and how to keep it current without a weekly update ritual.
How to replace the weekly status call: what belongs in a written client update, how often to send it, and why the page and the message must share one source.
Why agency revision rounds multiply, what an approval must contain to hold, how to separate feedback from decisions, and how many rounds belong in the contract.
The nine-step agency client onboarding checklist: what to send when, how to run the asset chase as one list, and why the approver must be named at kickoff.
What belongs in an agency's monthly client report, what to cut, how to report a month that went badly, and who actually reads the first page.
Connect a Telegram bot to Atwork: workflows send status updates and approval buttons to client groups, and replies create items and update statuses automatically.
Vista is an Atwork view where you describe a page and Dana builds it on your live sheets: dashboards, forms, and client pages you can publish as apps.
Connect LinkedIn to Atwork and publish from a workflow: a status change on a sheet row becomes a post on your profile, with images, links and visibility control.
On Airtable Team a commenting client costs a full $20 seat. On Business they are free. Why the more expensive plan is cheaper for agencies.
Wrike sells seats in groups of five and caps Team at 15 users. A $10 seat costs $16.67 at three people, and the 16th hire takes the bill from $150 to $500.