data analyst → AI builder

I figured it out the hard way, so you don't have to.

Ten years of data analysis, now spent building AI agents, automations and the odd drone. Every build goes up on YouTube and Substack, mistakes included.

The short version

From spreadsheets to agents.

01

The spreadsheet years

Marketing, e-commerce and influencer analytics. A decade of dashboards, late exports and the quiet worry that AI was coming for the job.

02

Then I started building

Instead of waiting, I learned to make AI do the boring parts: agents that clean data, scripts that write the report, sites that ship themselves.

03

Now I show the work

Each week I take one real problem, build the fix with Claude Code, and publish what worked and what broke. No fluff, no fear-mongering.

What I build

Machines that explain the work.

Every drawing below is live. Hover it, type on it or drag it: the numbers come from the same model that moves the parts.

Hardware + AI

Drones that measure

Small drones, sensors and robots wired to agents. The lidar here is real physics: range is half the pulse's round trip at the speed of light.

340
Laser pulses and the points they hitTargets of known height: 34, 26/18/10, 28, 12 and 20 cmGround-control targetsRange is half the pulse's round trip at the speed of light: 0.90 m down to the plate is 6.00 ns. The scanner sweeps 100 lines a second at 100,000 pulses a second, so at 0.5 m/s a line lands every 5 mm. The cloud drawn here keeps one line every 4 cm and 9 of each line's 200 pulses inside ±36°.
Agents

Read, decide, act. Repeat.

Most useful AI agents are this loop with good rules. Rows go in, a decision gets stamped on each one, and the work ends up in the done tray.

The decision: the press marks every row, solid = keep, outline = skipRows of data, moved one pitch at a timeRead, think, act: scanner, press and photo-eyeAn AI agent is a production line with judgement: it reads a row, decides what to do with it and acts, over and over. Here a row advances every 2.6 s; of every 7, 5 are kept and 2 skipped, and the counter runs on the same rule that drives the press.
Data

Where it started

Ten years of asking data the right questions. Now the AI does the typing, and I check the answer.

>
The screen: a bar chart and what you typeFifty-eight keys; each one goes down as it is typedA coiled cord from the keyboard to the side portWhere it started: ten years of asking data questions. Focus it and type: each key you press goes down on the keyboard and the character lands on the screen. Backspace and Return work; Escape or a click on the case switches it off and the picture collapses to a line and a dot, as a CRT does.
Content

One session, a week of content

One recording feeds the YouTube video, the short cuts and the newsletter.

LED panel and REC lamp: lit while it recordsCamera on a slider with 19 cm of travelThe set: laptop, lamp, mug and notebookOne recording session feeds the week: the long video goes to YouTube, the cut-downs go vertical, and the write-up goes to Substack. Each pass of the slider is one 8-second take.
How I work

From the first call to hours back.

The same path for every automation: map the process, check the data, build the agent, review it with you, ship it, and measure the hours it saves.

Drag to pan, scroll to zoom.Open full screen ↗
Latest videos

Built in public.

New videos land here on their own every week.

Videos load from YouTube (privacy-enhanced mode) only when you press play.

Behind the scenes

How one video becomes a week of content.

Idea, draft with Claude Code, one recording, then the cuts. The site checks YouTube weekly and adds the new video by itself.

Drag to pan, scroll to zoom.Open full screen ↗
Resources

Coming soon.

Tools I use every week, cleaned up so you can use them too.

Coming soon

AI roadmap for analysts

One page: where to start, what to skip, and the order that worked for me.

Coming soon

Claude Code cheatsheet

The commands, flags and shortcuts I actually use, with a one-line example each.

Coming soon

Agent pattern diagrams

The five agent patterns worth knowing, drawn so a non-technical team gets them.

Get the build notes.

One email a week on Substack: what I built, what broke, and the prompts behind it.

Subscribe on Substack →

Work with me.

Have a process that eats hours every week? Tell me about it. I build AI automations for small teams.

Email me →