Four Things I Learned Sitting Next to Founders for 4 Years
I've spent 4 years in rooms where the decisions actually get made. Not boardrooms with presentations, but small offices where a founder says "we're changing direction" and the whole company pivots by lunch. That proximity changed how I think about building products.
Here are four things I took away that I couldn't have learned any other way.
1. Speed of Decision Beats Quality of Decision
At Finvestfx, I watched the founder make a pricing decision in 20 minutes that our team had been debating for three weeks. He had less data than we did. But he understood something we didn't: at the pace the market was moving, a wrong decision made quickly was better than the right decision made slowly.
This doesn't mean being reckless. It means recognizing that most product decisions are reversible. You can change a pricing tier, roll back a feature, or pivot a campaign. The cost of delay is almost always higher than the cost of being slightly wrong.
As a PM, I now ask myself: "Is this a one-way door or a two-way door?" One-way doors (irreversible decisions) deserve careful analysis. Two-way doors (most product decisions) deserve speed.
2. Resource Constraints Are Features, Not Bugs
At Sonic Linker, we had a small team and limited runway. My instinct was to see this as a limitation. The founder saw it as a filter. When you can only build one thing this sprint, you're forced to build the right thing.
Constraints kill scope creep. They force prioritization. They make you question every feature: "Is this really the most important thing we could be doing right now?" Companies with unlimited resources build bloated products because they never have to make hard choices.
I've started applying this to how I think about roadmaps. Instead of asking "what should we build?" I ask "if we could only ship one thing this quarter, what would it be?" The answer is usually obvious, but it gets buried under a backlog of nice-to-haves.
3. Know When to Ignore Customer Requests
This sounds counterintuitive, but I learned it watching how founders handle enterprise clients. At Finvestfx, we had 20+ enterprise clients, and every single one had feature requests they called "critical." If we had built everything they asked for, we'd have built 20 different products.
The founder taught me to listen to the problem, not the solution. When a client says "I need a custom report builder," the real problem might be "I can't find the data I need to make my quarterly presentation." Those are very different product directions.
The prioritization framework we built scored requests by revenue impact and churn risk. It gave us a language to say no with data. But the deeper lesson was that customers are experts on their problems, not on your product's solution space.
4. Conviction Without Data Is Sometimes Necessary
Every PM framework says "be data-driven." And most of the time, that's right. But there are moments, especially at zero, where you have to make a call without data.
At Sonic Linker, we decided to build for marketing teams at B2B companies before we had a single customer in that segment. The data said nothing because we had no data. What we had was a strong hypothesis based on conversations, market observation, and the founder's conviction that AI visibility would become a category.
That bet paid off. But it required something data-driven decision-making frameworks don't teach you: the ability to make a call when the data isn't there yet. The best founders I've worked with know when to follow the data and when to trust their gut. That instinct is harder to learn, but watching them make those calls taught me to recognize the moments when it's needed.
The Through Line
These aren't abstract principles. They're patterns I noticed by being in the room when decisions got made. The founders I worked with weren't smarter than everyone else. They were faster, more focused, more comfortable with uncertainty, and better at distinguishing signal from noise.
That's the education no course can give you. You have to sit next to the people making the calls and watch how they think.