Running a declining business on purpose

Groove pays for everything at Helply. 85% of R&D, 100% of marketing.

It does that while slowly shrinking, which is deliberate. We're not trying to grow it. We're running a 12 year old help desk in managed decline as a funding mechanism for the company that replaces it.

That's a weird sentence to write about something you built. It's also the best financial structure I've ever had.

Why not just grow both

Because the thing that would make Groove grow again is the thing we already proved we can't do.

18 months of trying to make it agentic ended with the conclusion that the architecture won't support it. Growing Groove now means competing in an AI-era category with a pre-AI product. You can spend a lot of money on that and get a slightly better version of flat.

So the alternative uses of that cash are: pour it into a product that can't win, take it out as profit, or point it at the rebuild. We pointed it at the rebuild.

What managed decline actually means operationally

Not neglect. That's the distinction I'd draw hardest.

The product stays up, secure, and supported. Customers who are happy stay happy. We fix bugs, we answer tickets, we don't let quality rot, because the whole strategy depends on churn staying gentle and predictable rather than turning into a cliff.

What we don't do is add features, chase new segments, or spend on acquisition. New logos are whatever comes in organically, which is not nothing after 12 years of content.

The number I care about on Groove is churn rate stability, not growth. If it declines slowly and predictably it's a bond. If it declines unpredictably it's a problem, because Helply's runway is calculated off it.

The team question

This is the hard part and I don't have a clean answer.

Telling a team the product they've maintained for years is now a cash engine for a different product is not a fun conversation, and there's no framing that makes it fun. I didn't try to dress it up. What I said was the honest version: the market moved, this product can't follow it, here's what it's for now, and here's what we're building with the money.

Some people moved over to Helply. Some stayed on Groove because they like the work and there's less chaos in it, which is a completely legitimate preference and I'd stop calling it a lesser choice.

What doesn't work is pretending. If you tell a team the legacy product is still a growth priority while every hire and every dollar goes to the new thing, they figure it out in about 6 weeks and now they don't trust you either.

Why this beats the alternatives

The three ways to fund a rebuild are outside money, profit you're not taking, or an existing business.

An existing business is by far the best of the three if you have one. No dilution, no board, no clock other than the one your own churn sets. We got 12 months of 10 engineers building with no revenue and no pressure to ship a demo early, and that's the single biggest reason Helply is architecturally what it is rather than a compromise.

The cost is attention. Two products, two codebases, two sets of customers, and a founder who has to keep caring about the one that isn't the future. Some weeks I'm bad at that.

What I'd watch if you're considering it

Model the decline properly and pessimistically, then subtract another 10%, because your runway is that number and it's the only number.

Decide what "supported" means and write it down, so the team isn't guessing every time a customer asks for something.

And be honest with customers who ask. Some Groove customers have asked where it's going. I tell them the truth: it's maintained, it's not getting new features, and here's what we're building. A few moved to Helply. A few moved to competitors. Both are better than finding out from a blog post.

Groove funded a company that's now at $1M arr growing 7% a month. It's the most useful thing a flat business has ever done for me.

I still don't love saying it out loud.