Grow SaaS Without Hiring: Credit Pricing, AI Support, One FTE

You are deciding whether the next dollar of SaaS revenue should buy a person or a meter. It can buy a meter, if the product is built to stop needing a team before the team is needed.

Adam Robinson, founder of RB2B, said the company reached $10 million in annual recurring revenue with only one full-time employee. A public revenue dashboard for RB2B showed subscription MRR at $799,115.49 as of August 31, 2026. RB2B crossed $2 million ARR in August 2024, $6 million in July 2025, and $7 million in November 2025 without raising venture capital.

One FTE is the cap, not the goal

A one-person software company can move from its first dollar to $10K MRR and then to $1M ARR while avoiding a co-founder and a team for the longest practical period. Solo founders can deliver 5 to 10 times faster than teams because their communication overhead is zero. Speed is the byproduct; the shape of the product is the constraint.

One-FTE SaaS rule: cap each product at one FTE, meter usage in credits, and keep support AI-only until the math forces a hire. That rule keeps growth from becoming a payroll problem.

Build the product that fits one week

Start with a micro-niche where the buyer is easy to find and the job is narrow. Gartner Q4 2025 market data indicated that micro-niches expanded 340% relative to broad-market platforms. The signal is a short promise you can explain to a prospect without a deck.

Make the idea self-funding within 6 months at $5K MRR or secure at least $30K in letters of intent. If you cannot get there, the product is too broad or the buyer is too weak. You are done when you have a payment, a signed intent, or a clear no.

Cap the product before it needs a team. The core workflow, the billing, the onboarding, and the support path must all fit inside an operator's week. If a feature would require another operator, it is a candidate for a separate product.

A solo web-app stack can cost between $0 and $50 per month while serving fewer than 100 users, and operators should reach at least $1K MRR before outgrowing free tiers. Keep the bill smaller than the revenue it supports.

Use credit-based pricing so the customer pays for the value they consume. A credit should map to a unit the buyer already understands, such as a report, a contact, a message, or a workflow run. Let the plan page show the customer how to estimate cost before buying and why a heavy user pays more.

The mistake is treating credits as a discount. A plan is too generous when a customer can use the whole plan without feeling the cost. Review the credit unit often. A unit that is too small makes customers feel overcharged; a unit that is too large gives heavy users a free ride.

Put AI customer support in front of the inbox before the team exists. RB2B relies on an AI support agent for its support operation, and it has no human support team. Build a support flow that answers the common questions, escalates the rare ones, and leaves a log you can review. Keep the AI answers short, and make the escalation path obvious so the operator's load stays down.

By day 184, RB2B had $2.63 million ARR, 809 payers, and monthly user churn of 14.1%. The churn number belongs in the same review as the revenue number.

Let hours, not revenue, force a hire

Do not hire because the revenue looks impressive. Hire when the hours stop fitting. A product that needs more than one FTE has failed the cap; support that needs a human has failed the AI stack; a stack bill larger than the margin has failed the pricing.

Make the test regular. Count the hours spent on billing, support, and maintenance, then compare them to the margin the product returns.