Keep a One-Person Business Alive: Recurring Revenue and Scope Cuts

When you open the monthly balance, the first number to check is the recurring minimum. By October 2025, Tony Dinh had the option to stop working entirely.

Tony Dinh, a solo developer, built TypingMind, and its income mix changed as it matured. For a solo operator, the first decision is a recurring-versus-one-off mix target: recurring revenue covers the fixed costs of running the business, while one-off work stays small enough not to eat the margin.

Recurring revenue sets the monthly minimum

Set the target before adding another feature. A useful starting point is a share of monthly income that covers hosting, payments, support tools, taxes, and a buffer for slow weeks. Check it every week, not at year end.

Start with the costs you cannot avoid. When the target covers them and leaves room for taxes, you can make decisions without panic. When it does not, reduce scope instead of adding features.

TypingMind reached $1 million in cumulative revenue 20 months after launching in March 2023. By October 2025, TypingMind was making $130,000 to $160,000 a month, with B2B Team subscriptions making up more than 50% of subscription revenue and B2B Team recurring revenue accounting for more than 50% of monthly revenue.

In November 2024, one-off TypingMind revenue accounted for about 50% of monthly revenue, while the Team version provided subscription revenue. Tony Dinh had earlier reached roughly $45,000 in monthly recurring revenue as a solo developer. The move from one-off to recurring was a sequence of smaller, repeatable decisions.

A one-person business can look healthy while the owner spends hours on one-off work. Every new customer that needs a custom build, a manual onboarding call, or a special invoice adds time instead of buying back time.

Cut the scope that uses your hours

Map the hours before cutting features. Put support, outages, invoicing, and growth decisions in separate rows, with a weekly total for each. The finished map shows where the owner's time goes before a new feature is justified.

• Support first: turn repeated questions into a short help page, a default setting, or a clearer error message. A customer that needs a human to make the product work shows the product is doing the owner's job. The queue shrinks after a short period, not after a new release.
• Outages next: a one-person business cannot afford a feature that needs constant attention. A component that requires manual checks, a fragile integration, or a nightly fix must justify its recurring cost. Recovery happens without the owner intervening.
• Invoicing third: manual invoices, custom contracts, and special payment terms turn revenue into administrative work. Prefer subscriptions, standard seat counts, and a small set of plans. Billing takes minutes, not an afternoon of handling exceptions.
• Growth last: a paid campaign can look exciting until the math says otherwise. Tony Dinh's latest paid ad campaign had spent $600 and produced only 2 conversions. Treat that kind of result as a scope decision, not a creative problem. The growth channel pays for itself before the owner spends more on it.

Make the next growth decision a no

Review the mix monthly. Compare recurring revenue against one-off revenue, then compare both against the hours each one consumes. The note has the numbers and a decision: keep, fix, or stop.

Large B2B deals can change the mix quickly. In November 2024, Tony Dinh reported closing a 3,000-seat TypingMind Custom contract and several 1,000-seat contracts. Make the deal fit the operating model: the contract should fit the existing billing and support process, not the other way around.

Scope cuts can also mean removing a product line. Tony Dinh sold Xnapper, an earlier product, in March 2024 for $150,000 to concentrate effort on TypingMind. The exit removes a line before it consumes the owner's attention.

The practical test is whether the owner can step away for a short period and the business still pays.