Expansion revenue signals — when usage is telling you to ask for more.
Expansion revenue is the half of revenue most solo founders ignore. The signals — usage spikes, seat-count growth, feature-adoption breadth — are usually visible in the data, but they require a watcher to surface them at the right moment. Lou handles this on PorchOps; the patterns below are what to watch for whether you build it yourself or use PorchOps.
Expansion revenue signals
Expansion is the half of Revenue that compounds quietly. Recovering failed payments keeps existing revenue from leaking; expansion grows it. Most $5K-$500K ARR solo founders run a flat pricing structure (a few tiers, no usage-based component) because the operational layer for tracking expansion signals doesn't exist yet — and without that layer, you can't price for usage.
The four expansion signals worth watching. First, usage spikes — a customer whose API call volume, seat count, or feature usage jumps 50% over their rolling 30-day baseline. Second, feature-adoption breadth — a customer who was using one feature suddenly uses three or four. Third, paying-team-size growth — a customer who added two seats in the last month. Fourth, requested integrations — a customer who's asking about new connectors or API endpoints in support emails.
Each signal has a different conversation pattern. A usage spike on an existing tier suggests pricing-tier upgrade — "saw your API volume hit 12x your plan limit; want to talk about Scale?" Feature-adoption breadth suggests cross-sell — "you're using Lou and Frankie now; want to add Hank for silent-churn watching?" Paying-team-size growth suggests seat expansion or volume discount conversation depending on direction. Requested integrations are the most actionable — the customer is telling you what they'd pay more for.
The trick is timing. The expansion conversation needs to happen when the signal is fresh — within 2-3 weeks of the spike — and from a no-pressure framing. "Saw you've been using {feature} more this month, want to talk about your plan?" is the right framing; "upgrade to Scale to unlock more usage" is wrong. The first is a question, the second is a pitch. Founders who get this consistently close 30-50% of expansion conversations they have; those who don't get to 5-10%.
False positives are the failure mode. Not every usage spike means expansion intent; some customers are just exploring, some are doing one-time integrations, some are running internal tests. The conservative approach: a 50%-over-baseline threshold combined with a 14-day sustained-pattern requirement. If usage spikes for 3 days and returns to baseline, that's noise. If usage spikes and stays elevated for two weeks, that's a signal.
Lou handles this end-to-end on PorchOps. He watches usage in 7-day rolling windows, applies the 50%-over-30-day-baseline threshold, requires a sustained pattern (configurable: default 14 days), and drafts a no-pressure note when the signal fires. The founder reviews and decides whether to send. Lou doesn't replace your sense of when to talk to a customer — he gives you the context you'd otherwise need to assemble by hand.
What to ignore: vanity metrics. Login frequency alone is a poor expansion signal (some customers log in daily out of habit, not value); page-view counts are similarly weak. The strongest signals are tied to the resource the customer is actually paying for — API calls, seats, runs, storage. If your pricing isn't usage-based, watch the closest proxy.
Common questions.
What's the right expansion threshold?
50% over rolling 30-day baseline, sustained for 14 days. Lower thresholds catch noise from integration testing and one-off bursts; higher ones miss real usage growth. 14 days of sustained pattern is what separates the two.
How do I frame the expansion email?
As a question, not a pitch. "Saw you've been using Lou more this month — want to talk about your plan?" works. "Upgrade to Scale to unlock more usage" doesn't. The customer is the one deciding to expand; your job is to surface the moment, not push them.
What conversion rate should I expect?
Founders who handle expansion conversations consistently close 30-50% of them. Those who don't (or who pitch instead of ask) close 5-10%. The framing matters more than the timing, but both matter. Lou's drafts are calibrated to the question framing.
