A weekly update for a client

Goal

Give a client one page of progress, numbers and next steps each week.

What you’ll have

Prompt

A weekly update for a client

Your agent builds the page and checks the result with you.

Copy promptCopiedMake a weekly client update in Super Artifacts. Ask for the client, week, verified numbers, context, next steps and audience. Read kpi-board with super_templates and fill its dataset slot. Use super_project for one project per client, with rule.match.slugStartsWith matching a unique client prefix such as harbour-weekly-. Publish privately with super_publish using that prefix and the week, and keep it private with super_artifact_set. Ask before widening the project audience; arrange access for the client I name. Return a link I can send. Check dates and numbers before publishing. For reading activity, ask for a screenshot of Analytics and explain views, readers and named readers without claiming missing activity.

Needs

• This week’s numbers, context and next steps.
• A connected agent and your client’s chosen audience.

Steps

1. 01

   One client project

   A project keeps this client’s updates together.

2. 02

   One weekly page

   The agent fills kpi-board with the numbers and their meaning.

3. 03

   Automatic collection

   The project rule matches that client’s slug prefix.

4. 04

   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 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.

Next

• More on analytics
• More on projects