A weekly update for a client
Give a client one page of progress, numbers and next steps each week.
recipe~5 minVerified v0.163.0
Goal
Give a client one page of progress, numbers and next steps each week.
What you’ll have
Prompt
Needs
- This week’s numbers, context and next steps.
- A connected agent and your client’s chosen audience.
Steps
One client project
A project keeps this client’s updates together.
One weekly page
The agent fills kpi-board with the numbers and their meaning.
Automatic collection
The project rule matches that client’s slug prefix. Once the project is shared with the client, new matches wait for you unless automatic admission is on, and private ones are skipped unless Include private artifacts is on.
A link and a reading trail
The returned link is ready to send; Analytics shows views and readers after visits.
Check it worked
The project contains the new update. Its link loads the right week. Analytics records visits after the client opens it; named readers depend on identification.
If not
- The update is not in the project: Check the slug prefix, then the project’s admission and private artifact settings.
- The week is wrong: The prompt asks the agent to check dates and source numbers.
- No activity yet: The prompt asks it to explain the Analytics counts without inventing a visit.
Variations
- A new weekly slug keeps a history in the project.
- The same slug can hold corrections to this week’s update.