Invisible work looks like no work
A month where nothing broke is a month of successful maintenance that reads, to a client, like an invoice for nothing.
Client reports that write themselves.
From real site data.
If you maintain WordPress sites for clients, the reporting is the part that eats margin. The work itself is an hour; assembling evidence that it happened, per client, per month, is the rest of the afternoon. Talos compiles the report from the site itself and emails it to a recipient list the agent is not allowed to change.
WNorthstar Studio+ New
Howdy, Alex
The reporting tax
Assembling evidence is manual
Screenshots of update screens, notes on what you checked, numbers copied out of five different places.
It does not scale past a handful of sites
Per-client monthly reporting is linear work, and it is the first thing to slip when you are busy.
What actually happens.
Report from the site, not from memory
Updates applied, Site Health status, error volume, cron state and database growth, all read directly rather than recalled.
Show the trend
Diagnostic snapshot comparisons and inline charts turn "we maintained it" into a visible before-and-after.
Send to a locked recipient list
Report recipients are fixed when you enable the workflow, up to ten addresses. The agent cannot add or change them mid-run.
Know it was delivered
Delivery records are durable and idempotent, so a report is not sent twice and you can confirm it went out.
The exact tools it uses.
Talos does not improvise. Each of these is a defined tool with validated inputs, a declared risk level and its own policy setting.
Fixed recipients are a deliberate constraint. A prompt injected into content the agent reads cannot redirect a client report to a different address.
See the full tool cataloginspect_site_health
ReadRuns bounded WordPress Site Health direct tests and returns structured findings.
list_plugins
ReadList installed plugins with status, version and available updates.
inspect_cron
ReadWP-Cron events, overdue items, schedules and unusually frequent hooks.
inspect_database_health
ReadDatabase server metrics, connection pressure and the largest prefixed tables.
compare_diagnostics
ReadDiff two diagnostic snapshots to show what actually moved.
create_report
ReadInline structured report cards for security, SEO, health and other audits, with file and line evidence.
create_chart
ReadInline bar, line, area and pie charts built from real site data.
send_workflow_email_report
WriteEmail a workflow report to its fixed recipients. The agent cannot change the To list.
get_job_status
ReadDurable job status, result and history.
Or set it once and forget it.
Any of this can become a workflow. You write the prompt, choose the trigger, and lock the permissions before it ever runs.
How workflows workMonthly client maintenance report
WorkflowTrigger
Monthly · 1st at 07:00 · site timezone
Prompt
“Compile a client-facing maintenance report for last month: plugin and theme updates applied, current Site Health status, error log volume compared to the previous month, cron health, and database growth. Keep it plain-language and non-technical. Email it to the report recipients.”
Pre-authorized scopes
- site:read
- plugins:read
- email:send
Delivery
Emailed to a fixed list, with durable delivery records.
The outcome.
Reports compiled from real site data, not recollection
Trends shown with snapshot comparisons and charts
Recipient list locked at enable time
Durable, idempotent delivery records
Before you rely on it.
Can the report go to the client directly?
Yes. Set the client’s address as a fixed recipient when you enable the workflow. Up to ten recipients are supported, and the agent cannot change the To list during a run.
How is the email actually sent?
Through wp_mail, so it uses whatever mail configuration the site already has, including any SMTP plugin. Delivery is recorded durably and idempotently to prevent duplicate sends.
Is one license enough for all my client sites?
That depends on your plan. Solo covers one site, Studio covers ten, and Agency covers unlimited activations. Each activation is a separate install with its own settings and policies.
Keep reading
Use case
For agencies
Maintenance retainers break at scale. Talos gives every client site the same scoped automation, evidence-backed diagnostics and client reporting.
Read moreUse case
Update plugins safely
Talos reviews what an update changes, applies it inside a tracked change set with checksums, verifies the site afterwards, and rolls back if it went wrong.
Read moreUse case
Run your site on autopilot
Put recurring WordPress work on a schedule. Talos runs scoped workflows in the background, emails you a report, and never expands its own permissions.
Read morePut an agent to work in WordPress.
Spend less time clicking through admin and more time moving your site forward.