This site gets a new issue every Sunday, and I don’t sit down to write it. Here’s what happens instead.
1. All week, things get collected
- What I build. The work I do with Claude Code on my laptop gets summarised every night.
- What I tell it. I send a Telegram bot voice notes (English or Urdu), photos, links and half-formed thoughts. It transcribes, sorts and files them.
- What’s already public. Posts I’ve made and show appearances.
2. A privacy filter reads everything first
Before a word gets near a draft, a filter strips passwords and keys and drops anything on my “never publish” list. Some topics are allowed only inside a story I’ve approved. My family, for example, stays out. Always.
3. Saturday evening, the bot writes
It drafts the week as one issue, with segments like Built this week, Tested, Field notes and One lesson. Then it cuts that into a newsletter, a LinkedIn post, an X thread and an Instagram caption. The voice guide it follows is short: witty, blunt, reflective, and never make anything up.
4. I approve, edit, or kill it
Every piece arrives in Telegram with four buttons: Approve, Edit, Skip, Schedule. To edit, I just reply in plain words, like “less dramatic” or “drop the second paragraph”, and it rewrites.
5. Sunday, it ships
Approved pieces publish to this site, go out as the newsletter, and get queued for socials through the week.
What it runs on
Python, a small server, Telegram, and Claude doing the reading and drafting. The whole thing was built in a few days by someone who, for the record, is not an engineer.
If you want one of these for your business or your own brand, that’s a conversation I’m happy to have.