You can build your own tools. Yes, you.

I need to be honest with you before we go any further: I don't really know how any of this works. I'm a wedding photographer. I do not have a tech background. I could not, if you put me on the spot, tell you the difference between Python and HTML. A year ago the word “terminal” made my palms sweat.

And yet. This entire website, the one you're reading right now, and every little tool on it, the timer, the tracker, all of it, I built. Not a developer I hired. Not a template I wrestled into shape. Me, mostly at my kitchen table, in plain English, by asking a lot of questions and figuring it out as I went.

I'm not a developer. Not even close.

I want to be really clear about that, because I think the biggest thing standing between photographers and building their own tools is a quiet belief that this stuff is for other people. Clever people. Technical people. People who did computing at school. I am none of those things. I still couldn't tell you what most of the code is called, let alone write it from a blank page.

What I do have is the only thing that turned out to matter: I'm curious, I'm happy to ask daft questions, and I'll poke at something until it works. That's the whole skill set. Genuinely.

You're not learning to code. You're learning to describe what you want, which you already do all day long with your couples.

So what actually is it?

The tool I use is called Claude Code. The easiest way I can describe it is this: it's like having a brilliant, endlessly patient developer sitting right next to you. One who never sighs, never makes you feel daft for asking, and does all the fiddly typing for you. You tell it what you want in normal words. It builds it. You look and say “can you make that bit warmer, or bigger, or move it to the top?” and it changes it. That's the whole loop, and you just go round it until you're happy.

Every single time I didn't understand something, I asked. “What does that mean?” “Is that safe to change?” “Why did it do that?” Not once did it make me feel small for not knowing. That's the bit that unlocked it for me: I was allowed to be a total beginner, out loud, the entire way through.

The three things you actually need

Not a course. Not a computing degree. Not even a clear idea of what you're doing when you start. Honestly, just these:

• Curiosity. A willingness to poke about and see what happens. You really can't break anything that can't be put back.
• A real problem. Something small and specific that bugs you most weeks. That's your perfect first project.
• Plain words. The ability to say “when I click this, I want that to happen.” If you can brief a second shooter, you can do this.

What could a photographer actually build?

Start small and personal. The best first project solves one specific annoyance in your own week. A few that are genuinely within reach on day one:

• A timer that tracks how long you actually spend editing each gallery, so you finally know your real hourly rate.
• A little checklist for shoot days, so you never forget the confetti shot again.
• A tool that renames and sorts your exported files exactly the way you like them.
• A simple page that works out your travel fee from a postcode.

None of those need you to understand a single line of code. They need you to explain the annoyance clearly, and then keep asking questions until it's fixed. That is a skill you already have.

That's the whole reason The Co Lab exists, and the reason I keep banging on about it. The barrier was never the technology. It was the belief that this wasn't for people like me. It turns out the door was never locked. It just looked heavy from the outside.