Technology

Technology

What each tool I build must never be able to do

Across my CMS, my CRM and the iPad panel for my Mac, one kind of decision shaped the design: what the tool must never be able to do. Here is how it played out in each build.

Technology

My CRM's morning message was a mess. Now it is a remote control.

My CRM sends its updates to Telegram. The first morning summary was a wall of quoted email and AI paragraphs. Fixing it led somewhere more useful: menus and buttons that take me from a list of leads to one lead and act on it, without opening a laptop.…

Technology

My old iPad is now the control panel for my Mac

I wanted my old iPad to run my Mac from across the desk: apps, sites, my Outlook calendar, music, Claude and voice notes, all over Wi-Fi, free and with no apps to install. Nothing on offer met all three rules, so I built it in an afternoon and spent the evening fixing what only real use shows up.…

Technology

I replaced my sales spreadsheet with a CRM I built in two days

My outreach leads lived in a Google Sheet fed by a script. I built my own CRM instead. It reads Explee, my mailbox and my calendar, never writes to any of them, and uses AI to read replies, research companies and draft follow-ups that I send myself.…

Technology

Building my own CMS, part 3: locking down the admin

The public blogs are plain files, so the admin is the only thing worth attacking. The layers in front of it, the checks behind it, and the Cloudflare setting that locked out everyone except me.…

Technology

Building my own CMS, part 2: publishing through git

Pressing Publish turns into one git commit, pushed straight to GitHub, which my host deploys. Why git, why I stopped using GitHub's API, and the one folder the CMS may touch.