Founder Diary · Day 3 ·
Why I'm Proud of My Head of Product
The product finally works the way I wanted. Alan, our head of product, took over the dev team, cut it from nine people to three, and he's crushing it.
Day 3 of my founder journey launching the RevyOps AI CRM.
Here's the raw video. I only cut the ums this time.
Fewer bugs, a product I actually enjoy using, every mistake it took to get here, and the call where I told my head of product I was proud of him.
Read the full transcript
It is Day 3 of launching the AI CRM for Claude. One thing I realised today, and it was actually a very nice feeling, was how far the product has come along.
Most people won't tell you about the ups and downs of product development. Everyone thinks it's a breeze because AI has taken over everything and writing code is super simple, right? The answer is wrong. There are so many edge cases. It's very difficult to build enterprise-grade software that can handle tens of thousands of customers and scale well. There's design, product management and what they call DevOps. There are a thousand little things that can go wrong, and I can tell you personally, I have encountered every single one of them. I've made every stupid mistake you can make.
This morning I was on with my product team. We usually meet twice a week for two hours in the morning. I was going over the product with them, there were fewer bugs, it was working really well, and I was actually enjoying using it. I was like, oh my God, this is so cool. I was excited like a little kid to play with the product we were building.
It led me to reflect on all the places we've been. When we launched in July 2025, we took on a bunch of agencies for the GTM database part of the product, and the thing would take 10 seconds to load. It wouldn't even load. We had multiple crashes, because we didn't know we needed something called a columnar database, which is just a fancy way of saying a database that can handle the amount of activity we were pushing through it. We didn't know anything about certain parts of scaling this type of application. Even though I've done five SaaS companies now, every single application requires different things technically, and we ran into some big gotchas we just didn't know. It was a dummy tax we had to pay. And we solved it.
When I was reviewing this internally, I realised my head of product is really our chief technology officer. He started as a GTM engineer, but it turns out he's an amazing developer too. I didn't know that when I hired him. He took over from the development agency we hired to build the first prototype over two years ago, and now he runs the entire development team. We've reduced the dev team from nine people down to three. He runs it, and he's crushing it.
So I'll share the Fathom recording from our call this morning. I'm trying to be open about what we're going through, and this was one of the wins. I'm super proud of him.
That's Day 3. I think we're around 40 sign-ups on the waitlist right now, so we're slowly getting there. I haven't fully ramped content yet, but let's go. I'll see you tomorrow on Day 4.
Ben: I know this is a little mushy, but I want to say that I'm proud of you.
Alan: Thanks, man. I appreciate it.
Ben: You've come a long way. You've evolved in your abilities, but more importantly, as a human. This time last year I had to give you pep talks every day, and you've come a long way since then. The product is a reflection of that. You did a lot better than our previous developer was capable of, and he had 30 years of experience on you. You're a pleasure to work with, you're doing a good job, and the product's looking really solid. You'll deserve a lot of credit if this ends up working. You'd deserve a lot of credit either way, but especially if it works.
Alan: I appreciate it. With that situation, it was a bit of a gamble. To be honest, Ben, this could have ended up an absolute disaster when he left. I'm not going to lie, it actually worked in our favour, low-key. We're still getting there.