How Claude Code Changed My Career

I spent ten years making videos. Corporate work, documentaries, brand films for good people doing good things. I was decent at it. Travelled the world with a camera. Built a portfolio. Shot 55 projects you can still watch on Vimeo.

Then I moved to a farm in the Hutt Valley with my family and started building something different.

---

The farm needed everything. A website. A shop. Email marketing, event management, impact reporting, social media scheduling, customer journeys, inventory tracking. Basically all the things a small business needs but can't afford to hire a team for.

I couldn't code. Not really. I'd hacked together WordPress sites. I knew enough HTML to be dangerous and not enough JavaScript to be useful.

Then I found Claude Code. And honestly — this is changing the trajectory of my career.

---

The first thing I built was a newsletter pipeline. Not a template — an actual system. Voice note on my phone → transcription → draft → review → send. The whole thing runs while I'm feeding animals.

Then I built an MCP server that connects Claude to everything we use. Airtable. Shopify. Google Drive. Klaviyo. 52 tools that let me say "check the shop" or "draft the board report" and get real answers from real data.

Then a booking system. A signal media pipeline that turns farm content into social posts. An impact dashboard that tracks our predator catches and tree plantings. A hypercerts system for environmental claims.

Then an overnight agent. Literally works while I sleep. I wake up to completed tasks — pages updated, emails sorted, content scheduled.

I built all of it with Claude Code. Every line.

---

Here's what people get wrong about AI coding tools. They think it's about generating code faster. Like it's a speed boost for developers.

It's not.

It's about building things you couldn't build before.

I'm not a developer. I'm a farmer and filmmaker who needed systems and couldn't afford to hire for them. Claude Code didn't make me a faster developer. It made me a developer at all.

The gap isn't "AI vs no AI." The gap is between people who connect AI to their actual tools and people who use it as a chatbot. The chatbot people ask questions. The connected people build systems.

---

Here's what my setup looks like today:

• Mac Mini running 24/7 in the office
• Claude Code as the core — terminal-first, connected to everything
• MCP servers bridging Claude to Airtable, Shopify, Google Workspace, Klaviyo, and more
• Telegram bot so I can message Claude from my phone while I'm on the farm
• Voice bot that transcribes voice notes and turns them into tasks, meeting notes, or content
• Dayshift — an autonomous agent that picks up tasks during the day
• Nightwatch — runs overnight, completing work while I sleep

Total team: me. And Claude.

---

I'm not saying this to flex. I'm saying it because two years ago I didn't know what an API was. I didn't know what a webhook did. I couldn't read a stack trace.

Now I run five projects across multiple organisations, all from a farm in Mangaroa. The systems work. The code ships. The emails send. The reports generate.

Claude Code didn't replace my creativity. It gave me a new medium. Instead of cameras and edit suites, I work with terminals and tools. The storytelling instinct is the same — understanding what matters, cutting what doesn't, building something that moves people.

If you're watching from the sidelines thinking "I'm not technical enough" — that was me. The tools are ready. The barrier isn't skill. It's starting.

---

Stay human,

Billy