Insight
Product builders, specialists and why my roof leaked
Anyone who has listened to me blather on about hiring lately has probably heard this extended metaphor at least once. Not one to stop whilst ahead (or behind), I thought I’d treat you to my stream of consciousness here.
A year or so ago, I got a builder in to do some work on my house. He was great. He got a lot of key things done: fixed some structural issues, built a gate and a fence, and sorted out a verandah. He had better ideas for the place than I could have come up with. Whilst he was there, he offered to put a new roof over the verandah, and it seemed like an easy yes. I would love to say at this point that I did my due diligence. I did not.
To me, it looked great. I mean, it was a roof. Tick.
Then the storm came in, and so did the water. If anyone is thinking about a water feature in their home, a quick tip: don’t put it over the sofa.
After trying to fix it with the help of YouTube (I couldn’t), I brought in a few roofing specialists to take a look. It turned out the roof had been pitched wrong, there was no condensation membrane, the guttering wasn’t working properly and the skylight was the wrong size. None of this was visible on a dry day, but here I was being told I needed to rip it all off and start again.
So when that same builder offered to do the bathroom, I thanked him kindly and called a plumber.
What this has to do with product
There’s a lot of talk at the moment about product builders: people who can take an idea from concept to something working, often across product, design and engineering at once, with AI tools doing a lot of the heavy lifting. I’m a big believer in them. Like my builder, they move fast, they get the structure up, and they often bring ideas the rest of the team wouldn’t have had.
But somewhere around the (finger in the air) 80% mark, you need your specialists.
Building products is a lot like building a house. Software can look fine until real users arrive at scale, doing things nobody planned for. That’s the storm, and it brings the problems that didn’t show up on a dry day.
So, to extend this metaphor to the point of absolute exhaustion, a specialist is a specialist for a reason.
The roofer is the engineer who knows what has to hold under pressure. You only really notice their work when it’s missing.
The plumber is your back-end engineer. Everything flows through what they build, behind the walls, and you only think about it when it leaks.
The electrician is your data or platform engineer. Everything relies on the wiring, and it’s the last thing you want done by someone who watched a YouTube video once. Ask me how I know.
The architect is your product designer. They work out how the place should look, how you move through it, and why the front door shouldn’t open onto the laundry.
The surveyor is your strategic designer. They’re the one who asks whether you need a new roof at all, or whether the real problem is that you bought a house at the bottom of a hill.
The site manager is your product manager, keeping the trades in the right order, making the trade-offs and getting it finished on time. In fairness, nobody did that last part on my house. I was told it would take a couple of weeks, which in construction, I’ve since learnt, means a couple of months.
So, builders or specialists?
Both. The teams I see doing this well use product builders to get moving quickly and prove an idea, then bring in specialists at the point where getting it wrong gets too expensive.
That said, things are moving quickly. Tools like Cursor, Codex and Claude Code get noticeably better every few months, and the product managers and designers I speak to are becoming more T-shaped all the time. What this looks like in a few years, or even a few months, could be very different. For now, I’d still get a roofer in.
If you’re working out which parts of your team need a builder and which need a specialist, I’m always happy to talk it through. I know a lot of very good specialists. And I now know a bloody good roofer, too.