Building Retently to Last, Not to Spike
How a bootstrapped customer-feedback SaaS treats longevity, customer trust, and independence as the real strategy
Key Lessons
- •Win a focused lane instead of matching funded incumbents feature for feature
- •Outlasting the category beats out-launching it
- •Bootstrapped and profitable means your roadmap answers to customers, not investors
- •Be ready to help teams migrate safely when a tool they relied on shuts down
- •A feedback platform's value compounds with the data and integrations built on it
I run Retently, a customer feedback platform. It measures NPS, CSAT, and CES, collects reviews, and turns the raw responses into insights for Ecommerce stores and B2B SaaS teams. It is bootstrapped, profitable, and has been running for more than a decade. I have never raised money and never chased a launch-week spike. The thing I am most proud of is unglamorous: it is still here, customers still trust it with their feedback program, and it keeps getting better.
Retently was not where I started. I built and sold a previous company, Noction, and afterward went looking for the next thing. The customer success category was just taking off then, with companies like Gainsight and Totango defining it, and I wanted in. I chose to enter through the piece I could do exceptionally well rather than the whole sprawling suite: measuring how customers actually feel. Retently began as an NPS tool and grew into a full feedback platform spanning NPS, CSAT, and CES, focused squarely on Ecommerce and B2B SaaS rather than trying to become another all-in-one customer success platform.
Win a focused lane, not the whole suite
Entering a category that funded incumbents were racing to define, the instinct is to match them feature for feature. I went the other way. Instead of building a sprawling customer success suite I could never out-resource, I went deep on the part every one of those teams needs and few do really well: the measurement layer. NPS first, then CSAT and CES, done properly for Ecommerce and B2B SaaS. A focused product that nails one job beats a broad one that does ten jobs adequately, and that edge is sharpest when you are bootstrapped and the people across the table have raised serious money.
When Greg entered the customer success category, well-funded incumbents were racing to define it, and the obvious move was to match them feature for feature. He did the opposite: rather than build a sprawling suite he could never out-resource, he went deep on the one layer every team in that category needs and few do really well, customer feedback measurement (NPS, then CSAT and CES). A focused product that nails a single job beats a broad one that does ten jobs adequately, and that edge is sharpest when you are bootstrapped and your competitors have raised serious money. Pick the wedge you can be the best in the world at, and let the incumbents carry the cost of trying to be everything to everyone.
Longevity is the strategy, not the byproduct
Most SaaS advice optimizes for the first eighteen months: the launch, the growth curve, the round. I optimized for year ten. A product that is still standing after a decade has something a new competitor cannot clone by shipping a flashier version next month: it has aged into reliability. Customers have integrated it, trusted it with their feedback data, and built workflows on top of it. That accumulated durability is the asset, and everything else is in service of keeping it strong.
Greg built Retently to be standing in year ten, not to win launch week. A product that has run profitably for more than a decade earns something a faster competitor cannot copy on demand: it has aged into reliability and trust, customers have integrated it and built workflows on top of it, and that accumulated durability becomes the real moat. Optimizing for longevity instead of the early growth curve looks slow in a market obsessed with spikes, but the company that is still there after ten years, still trusted by its customers, is the one that compounded. Build for the decade, and durability stops being luck and becomes the strategy.
Independence is a feature customers can feel
Retently is bootstrapped and profitable, which means the people it answers to are its customers, not a board chasing a quota or an investor who wants an exit on a schedule. That independence keeps the product stable and present for the long run. There is no pressure to pivot away from the people who rely on it, and no risk of it being sold out from under them and shut down. A team trusts a feedback platform far more when they know it will still be there next year, run by the people who built it. Owning the business outright is what lets me optimize for the customer’s decade instead of an investor’s quarter.
Retently is bootstrapped and profitable, so the people it answers to are its customers rather than a board or an investor with an exit timeline. Greg treats that independence as a feature customers can feel: the product stays stable and present, there is no pressure to pivot away from the people who depend on it, and there is no risk of it being sold off and shut down. Teams trust a feedback platform more when they know it will still be there next year, run by the people who built it. Owning the business outright is what lets a founder optimize for the customer’s decade instead of an investor’s quarter.
Be the safe place to land when a tool shuts down
When Delighted announced it was winding down, thousands of teams suddenly needed a new home for their NPS and feedback programs. The right response is not to treat that as a windfall to harvest, it is to be genuinely ready to receive those teams: a clean migration path, clear positioning, and the least possible friction for someone who already knows exactly what they need and just lost the tool that did it. Helping a displaced team move without losing their history earns trust that a cold pitch never will. When an incumbent in your category exits, the work is making the switch safe and easy, and the customers follow.
When Delighted wound down, thousands of teams needed a new home for their feedback programs overnight, and Greg’s read is that the right move is to be the safe place to land rather than to gloat over a windfall. A clean migration path, clear positioning, and the least possible friction for a buyer who already knows what they need can move more revenue than any cold-acquisition push, and helping a team migrate without losing their history earns trust a pitch cannot. Watch the incumbents in your category and be ready to receive their customers the moment one exits. Make the switch safe and easy, and the customers follow.
Value that compounds with use
The longer a customer runs Retently, the more it is worth to them. Years of NPS and CSAT history to trend against, integrations wired into their stack, and workflows their team relies on day to day. I built around the idea that the real value of a feedback platform is not any single screen, it is everything that accumulates on top of it over time. That compounding is good for the customer, because their data gets richer and more useful, and it is what makes the product something teams genuinely stay with for years rather than something they shop around every renewal.
The longer a customer runs Retently, the more it is worth to them: years of NPS and CSAT history to trend against, integrations wired into their stack, and workflows the team relies on. Greg built around the idea that the real value of a feedback platform is not any single screen but everything that accumulates on top of it over time. That compounding is good for the customer, whose data only gets richer and more useful, and it is what turns a tool into something teams stay with for years instead of reshopping every renewal. Build for the value that deepens with use, not just the feature that demos well on day one.
Advice extracted from this journey
ProductWin a focused lane instead of matching funded incumbents feature for feature
When Greg entered the customer success category, well-funded incumbents were racing to define it, and the obvious move was to match them feature for feature. He did the opposite: rather than build a sprawling suite he could never out-resource, he went deep on the one layer every team in that category needs and few do really well, customer feedback measurement (NPS, then CSAT and CES). A focused product that nails a single job beats a broad one that does ten jobs adequately, and that edge is sharpest when you are bootstrapped and your competitors have raised serious money. Pick the wedge you can be the best in the world at, and let the incumbents carry the cost of trying to be everything to everyone.
MindsetOutlasting the category beats out-launching it
Greg built Retently to be standing in year ten, not to win launch week. A product that has run profitably for more than a decade earns something a faster competitor cannot copy on demand: it has aged into reliability and trust, customers have integrated it and built workflows on top of it, and that accumulated durability becomes the real moat. Optimizing for longevity instead of the early growth curve looks slow in a market obsessed with spikes, but the company that is still there after ten years, still trusted by its customers, is the one that compounded. Build for the decade, and durability stops being luck and becomes the strategy.
Business & LegalBootstrapped and profitable means your roadmap answers to customers, not investors
Retently is bootstrapped and profitable, so the people it answers to are its customers rather than a board or an investor with an exit timeline. Greg treats that independence as a feature customers can feel: the product stays stable and present, there is no pressure to pivot away from the people who depend on it, and there is no risk of it being sold off and shut down. Teams trust a feedback platform more when they know it will still be there next year, run by the people who built it. Owning the business outright is what lets a founder optimize for the customer's decade instead of an investor's quarter.
DistributionBe ready to help teams migrate safely when a tool they relied on shuts down
When Delighted wound down, thousands of teams needed a new home for their feedback programs overnight, and Greg's read is that the right move is to be the safe place to land rather than to gloat over a windfall. A clean migration path, clear positioning, and the least possible friction for a buyer who already knows what they need can move more revenue than any cold-acquisition push, and helping a team migrate without losing their history earns trust a pitch cannot. Watch the incumbents in your category and be ready to receive their customers the moment one exits. Make the switch safe and easy, and the customers follow.
ProductA feedback platform's value compounds with the data and integrations built on it
The longer a customer runs Retently, the more it is worth to them: years of NPS and CSAT history to trend against, integrations wired into their stack, and workflows the team relies on. Greg built around the idea that the real value of a feedback platform is not any single screen but everything that accumulates on top of it over time. That compounding is good for the customer, whose data only gets richer and more useful, and it is what turns a tool into something teams stay with for years instead of reshopping every renewal. Build for the value that deepens with use, not just the feature that demos well on day one.