cd /news/ai-agents/the-one-page-monthly-report-my-codin… · home › topics › ai-agents › article
[ARTICLE · art-172212] src=dev.to ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

The one-page monthly report my coding agent writes for every client site

A freelance developer described building a monthly client reporting workflow in which a coding agent (Claude Code, Cursor or Codex) connected to the Novence MCP pulls cookieless, edge-side analytics for each Astro-hosted client site, compares them to the prior month, and drafts a sub-150-word plain-English email of at most three bullets. The agent also logs high-traffic 404s to a fix list that the developer turns into redirects and redeploys, after an early run without a no-guessing rule invented a percentage for a site with analytics disabled.

recommendation

Store each client's goal and notes alongside their site config and instruct the agent never to guess missing numbers, so reports stay grounded and specific.

more in playbook: Designing agent systems
by read4 min views16 publishedNov 19, 2026

Most of my clients came off WordPress with a Jetpack stats widget or a Google Analytics property nobody had logged into since 2019. When I move them to Astro I dont rebuild that. Instead they get one short email a month that my coding agent writes, and honestly its the thing that keeps them on the care plan.

Here is how I set it up.

I tried that. Nobody logs in. A small business owner does not want to learn what a "session" is. They want to know three things:

So the report answers those three questions and nothing else. If it takes more than a minute to read, I've failed.

I host all my client sites on novence.ai and the analytics there are opt in, cookieless and done at the edge. No script in the HTML, so no cookie banner just for stats and no extra JS slowing the page down. I get pageviews, top pages, referrers, countries and 404s, which is genuinely all a plumber or a cafe needs.

The bonus of no-script analytics: ad blockers dont eat the numbers, so they are closer to real than what GA was showing.

I already keep a sites.json in my agency repo (one entry per client). For reports I added a few fields:

{
  "slug": "harbour-plumbing",
  "contact": "Dave",
  "email": "dave@example.com",
  "goal": "quote form submissions",
  "keyPages": ["/", "/services/hot-water", "/contact"],
  "notes": "Wants more hot water jobs, not blocked drains"
}

The goal and notes fields matter more than the numbers. They let the agent write "your hot water page got 40% more visits" instead of a generic stat dump.

On the first of the month I open Claude Code in the repo (Cursor or Codex works the same) with the Novence MCP connected and run this:

For each site in sites.json:
- Pull last month's analytics (pageviews, top pages, referrers, countries, 404s)
  and the same numbers for the month before.
- Count form submissions for the month.
- Write a plain english report, max 150 words, to reports/<slug>/<yyyy-mm>.md
Rules:
- Lead with the client's goal from sites.json.
- Max 3 bullet points. No jargon (no "sessions", "bounce rate", "CTR").
- If a 404 has more than 5 hits, add it to a fix list, don't put it in the email.
- Never round up or guess a number. If data is missing say so.
- End with one suggestion we could do next month.

The "never guess a number" line is there because the first time I ran it without that, it happily invented a percentage for a site with analytics switched off. Lesson learnt.

After a WordPress to Astro move there are always a couple of old URLs I missed in the redirect map. Some random PDF from 2016, an old ?page_id= link a supplier still uses. The 404 report catches them.

The agent puts anything with real traffic into reports/fix-list.md, then I let it add the lines to /_redirects, build and redeploy with:

npx novence deploy ./dist

Client never sees a broken link and I never have to explain what a 404 is.

Here is the shape of one (example numbers, made up client):

Hi Dave, quick one for October.

  • Your hot water page had 312 visits, up from 221 in September. Most came from Google.
  • 9 quote requests came through the site form.
  • A few people were hitting an old link to your price list, I've pointed it to the new services page. Next month: I'd like to add a short FAQ to the hot water page, it's getting the traffic so lets give it more to rank for.

That's it. Three bullets and one idea. I read every draft before it goes out, fix the odd thing, and send it myself. Takes me maybe 10 minutes for all clients.

The report is basically a monthly reminder that I'm doing something. The "next month" suggestion turns into small paid jobs surprisingly often. And when a client does churn, it's never because they forgot what they were paying me for.

If you're moving clients off WordPress, dont rebuild their old stats setup. Pick the three questions they care about, let the agent do the counting, and keep the email short.

── more in #ai-agents 4 stories · sorted by recency
── more on @claude code 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/the-one-page-monthly…] indexed:0 read:4min 2026-11-19 · —