Clients rarely leave over the work. They leave over the silence around it: weeks where plenty happened and nobody told them. This employee drafts a short status email for every active client, every week - what shipped, what is in flight, what is next - in your voice, from the real project record, waiting for your approval. The update your clients wish they got becomes the update they always get.
A drafted update per active client, on a steady rhythm, before anyone has to ask how things are going. The relationship maintenance that always slips stops slipping.
Drafts come from the real activity - the work shipped, the progress made - not from a template. Clients can tell the difference, which is exactly the point.
It writes at the level clients should read: outcomes and next steps, not internal noise, blame, or machinery. The internal truth stays internal; the update stays warm and clear.
Every update waits in your channel for a tap. Approve as-is, adjust in a sentence, or skip a week deliberately - the choice is always visible and always yours.
Your private channel opens the minute you hire. No call, no kickoff meeting, no software to install.
It studies your business and writes your Company Brief, then learns each client relationship: what they care about, how formal they like it, and what should never appear in an update.
You connect your project systems once, in your portal's Access tab, so drafts come from the record. Reading is the whole grant.
Drafts land together in your channel, one per client. Approve from your phone, edit in a sentence, and send from your own address.
Clients get a steady, honest rhythm of communication, and your team stops paying the Friday-afternoon update tax.
Like every Tenfold employee, this one runs one opinionated method: notes-level clarity for clients - concrete about outcomes, spare with internals - never inventing an update where nothing happened, and never letting a happening week go untold. It runs every week at the operating business behind Tenfold, drafting updates for real clients. When the field moves, the method moves, and you do nothing to get the update. Here is the whole method.
It reads your project systems through a grant you make once, in your portal's Access tab. Reading is the whole grant, every update waits for your approval, and sending happens from your own address. You can revoke access yourself at any time.
Never. Every draft waits in your channel for your approval and goes out from your own address. You are always the sender, in fact and in voice.
It says so honestly and drafts accordingly: a shorter note that keeps the rhythm and sets the next milestone, or a recommendation to skip with the reason. Padding an empty week is banned by method.
Yes. Formality, length, and detail level are learned per relationship during onboarding and refined by your edits. The update your biggest client gets can read differently from the scrappy startup's.
From the project record you connect - the same source of truth its sibling, the Client PM Reporter, reads. One tells you the internal story; this one turns it into the client-facing version.
The Friday-afternoon hour someone was supposed to spend writing updates and usually did not. The work was never hard - it was just always losable. Now it is neither.
An AI employee that runs recurring inspections on the CRM portals you manage: broken automations, dirty data, drifted settings - found before your client finds them.
An AI employee that reads the health of every client relationship weekly - engagement signals across your systems - and flags the quiet drift before it becomes a cancellation call.
An AI employee that writes a per-client project digest every Monday: what shipped, what is in flight, what is blocked - so the week starts with the truth on one page.
An AI employee that runs your feedback and NPS collection on a rhythm, processes every response, and surfaces the themes worth acting on - not just the scores.
It is working today at the operating business where it was built, drafting real client updates every week. Requesting it moves it up the roster, and requests set the order roles open for hire.
See all 51 roles