I Automated My 6-Hour Weekly Client Report (Claude Code + VPS)
My old 6-hour manual client report is now a self-scheduling Claude Code agent on a VPS — it regenerates every Monday and I can control it from my phone. Here's the full build.
June 12, 2026
Hey, freelancer 👋
Every week I used to spend about 6 hours on the same client report — pulling data, building charts, writing insights. Pure repetitive work. So I turned it into a Claude Code agent that lives on a VPS — I can run it from my desktop or my phone, and it regenerates the report by itself every Monday.
Here’s the high-level walkthrough of the build. (All data shown is synthetic / anonymized Amazon-seller data — no real client info — so I can show the system without breaking confidentiality.)
The setup: a self-contained project on the VPS
Each project = its own folder + a persistent tmux session, with Claude Code inside. One session per project — so I can disconnect and come back anytime without losing state. One bootstrap prompt and Claude takes over the whole folder: its own .claude/, a Python venv, .credentials/, .env, deliverables/, and a hardened .gitignore so nothing sensitive gets pushed.
Controlled from anywhere
With /remote-control, I pair the session to Claude Desktop — or my phone. I detach the terminal, the agent keeps running on the VPS, and I come back through a cleaner interface. Same session, controlled from anywhere.
From data warehouse → branded report
I connected Claude to BigQuery (service-account key), then just said in plain language: read the warehouse and build a dark-mode HTML analytics report — a KPI strip, a trend chart, a top/bottom SKU table, with a short plain-English narrative. It inspected the schema first, then wrote the queries and the HTML.
I left one real mistake in the video — a wrong column on the first pass — because that one-line correction is exactly what proves this works on real work, not just a demo. 😅
The game-changer: turn it into a skill
Instead of re-prompting every week, I had Claude package the whole workflow as a reusable skill — queries, layout, narrative rules. Now one command brings the report back. Teach it once, it never forgets. Then a cron job runs it every Monday night. That 6-hour manual task → a scheduled deliverable that runs even when I’m away.
Why this matters for freelancers
Here’s the pattern: take the repetitive work you do for clients, hand the mechanical parts to an AI agent, and keep your judgment for the parts that actually need a brain. Less manual work, more time for the things that matter (or in my case — more lakwatsa).
▶️ Watch the full build (Taglish, step-by-step)
Every step — from an empty folder to the Monday cron — is in the video:
👉 https://youtu.be/4ic0wJ2IpyM
If you just want the VPS part (1-click Claude Code install on Hostinger), it’s at 18:12 in the video.
— Arvin Less manual work, more lakwatsa.
P.S. To run your setup 24/7, I use a Hostinger VPS → hostinger.com/lakwatseros (code: LAKWATSEROS)