Philip Roigard

We often hear that users want fewer tools, fewer tabs, and everything in one place.
But does that really mean they want an all-in-one product?

There s an interesting trade-off between all-in-one and best-in-class.

There s probably a line where an all-in-one product becomes too complicated.

Adding more features can mean fewer tools, less context switching, and a more connected workflow.

I'll go first.

Six months ago I was running growth for a small team. Seven tools open at once. I'd draft something in Notion, paste it into the CRM, copy the numbers from Analytics into a Sheets report nobody read, then schedule the post in a different tab. Every week the same loop. Nothing talked to each other, so I was the integration layer.

We all know someone who just keeps building: One more feature, One more improvement, One more thing to fix before starting sales.

And to be fair, it s easy to fall into that loop. Building feels productive, and there s always something that could be better.
But at some point, you have to ask yourself: are you really improving the product or just delaying sales?

From your experience:
When is the right time to stop building and start selling?