The problem
A freelancer juggling 5–7 active projects at once: client deadlines, invoices, follow-ups on deliverables, SaaS subscription renewals. Everything lived in Google Calendar and his head — and things kept slipping.
A missed billing alert meant getting charged $49 for a tool he stopped using. A forgotten follow-up meant a client going cold. An overlooked deadline meant a stressful Friday night. He didn't need another project management app — he needed a second brain that watches everything and alerts him only when it actually matters. No noise.
What I built
Deployed OpenClaw on a VPS with Orchestrator via OpenRouter — this allows flexible model selection per task and granular cost control. Set up a full ops monitoring system:
1. Calendar monitoring
The agent connects to Google Calendar API and scans all events and deadlines. Every morning at 8:30 it checks what's scheduled for today and the next 3 days — nothing sneaks up.
2. Context-aware reminders
Not generic "you have an event in 1 hour" alerts. These are contextual nudges that actually help:
- Billing alert — "Hetzner renewal tomorrow ($5.39). Card ending 4821 — check balance."
- Project deadline — "Landing page for [client] due in 2 days. Status: in progress. Last touched: yesterday."
- Follow-up — "Alex hasn't responded to your proposal (sent 3 days ago). Want me to draft a follow-up?"
- Upcoming call — "Call with [client] tomorrow at 2 PM. Prep: Q3 KPI report."
3. Daily summary at 8 PM
Every evening, a compact Telegram digest lands:
- What was planned today vs. what got done
- Approaching deadlines (next 72 hours)
- Pending follow-ups and their age
- Billing events this week
30 seconds to read. Full picture. No need to open 5 tabs to piece it together.
4. Weekly review on Mondays
Every Monday at 9 AM — a longer-form review: status per project, financial events of the week, things that need attention before they become urgent. Like a weekly standup, but the agent writes it for you.
Result
Why OpenRouter
This case uses Orchestrator via OpenRouter instead of a direct API. Here's why:
- Model flexibility — simple reminders use a cheaper, faster model. Weekly reviews use a more capable one. OpenRouter lets you route without changing config.
- Cost control — single dashboard to monitor AI spend, per-model budgets, usage alerts. Important for a freelancer watching every dollar.
- Fallback — if one model is down or slow, OpenRouter routes to an alternative automatically. No missed morning digest because of an API outage.
Stack
- VPS: Hetzner CX11 (Ubuntu 22.04, 1 vCPU / 1 GB RAM) — ~$4/mo
- OpenClaw + Telegram Gateway
- Orchestrator via OpenRouter (GPT-4o / Claude 3.5 Sonnet depending on task)
- Google Calendar API (via skill)
- Cron: morning check at 8:30 + daily summary at 8 PM + weekly review Mon 9 AM
Setup time
6 hours — Calendar integration, reminder priority logic, summary templates, and testing across different scenarios (empty days, overloaded days, billing edge cases).
Deadlines and follow-ups keep slipping?
I'll set up an agent that acts as your ops controller — reminds, reports, doesn't spam.
Message on Telegram