A Competitor Existed, So I Built an AI SDR Over the Weekend
I saw that a rival had a shiny feature. By Sunday night I had designed, built, and demo-recorded an entire new product surface that precisely zero of my users had requested. I called it conviction. It was a flinch.
It started, as these things do, with a browser tab I should have closed. A competitor's site. They had a glossy new capability — let's keep it vague and call it The Shiny Thing — presented with the serene confidence of a company that had clearly thought about it for longer than a weekend.
A healthy founder closes the tab and goes back to their own customers. I am not that founder. I felt the specific, hot little jolt of they have a thing and I do not have the thing, and my entire weekend reorganized itself around acquiring the thing.
The FOMO build
By Friday night I had a plan. By Saturday I had screens. By Sunday I had a whole new surface bolted onto my product — pipelines, stages, the works — plus a demo recording where I narrated it in the calm voice of a man who had always intended to build this and was definitely not reverse-engineering a rival's homepage forty hours earlier.
I didn't build it because a customer was in pain. I built it because a competitor wasn't.
And it was good work! Genuinely. The thing functioned. It demoed well. If you'd watched the video you'd have thought, "ah, a thoughtful, deliberate product team made this." That's the trap. Competence is a fantastic disguise for panic. You can build something real and impressive and still have built it for the dumbest possible reason, and the quality of the work will happily cover for the stupidity of the motive.
What FOMO actually optimizes for
Here's the thing about building from envy instead of evidence: you don't end up with your product. You end up with a slightly-worse, slightly-late tribute to theirs. You've handed your roadmap to a competitor and let them drive. Every feature they ship becomes your homework. You're not building a company anymore; you're running a very expensive cover band.
My users — the few, the patient — had not been quietly suffering from a lack of The Shiny Thing. They had real, boring, specific complaints about the things I'd actually built. None of those complaints got addressed that weekend, because I was busy chasing a problem a stranger had decided was important.
The redeeming twist, and the only reason this feature survived contact with Monday: I forced myself to find the version of it that only my product could do — the angle that flowed from my own thesis instead of from theirs. The shape that, if a competitor saw it, would make them open the panicked browser tab. If I couldn't find that, it didn't ship. A lot of weekend builds don't pass that test. This one barely did.
So the new rule, taped metaphorically to my monitor: a competitor's feature is a question, not an instruction. The question is "why did they think this mattered?" The instruction — "build this now, build it like them" — is how you spend a weekend becoming a worse version of someone else.
I still have the tab-closing problem. I'm working on it. Right after I check what they shipped this week.
— Ridha, who promises this is the last confession (it is not the last confession)