Time to First Revenue: How Long Does It Actually Take?

Revenue is the clearest signal that someone values what you've built. Before revenue, you're operating on faith and hypotheses. After revenue, you have proof that customers will pay.

Understanding realistic timelines helps with planning. If B2B SaaS typically takes 6-12 months to first revenue and you're planning for 3 months, you'll run into trouble. Setting accurate expectations prevents unnecessary panic and poor decisions.

This data examines thousands of startups to understand how long the journey to first revenue actually takes across different business models.

B2B SaaS:

• Median time to first revenue: 6-12 months
• 25th percentile: 3-6 months
• 75th percentile: 12-18 months
• Factors: sales cycle length, product complexity, market education

Consumer apps (subscription):

• Median time to first revenue: 3-9 months
• 25th percentile: 1-3 months
• 75th percentile: 9-15 months
• Faster to launch, but monetization experimentation takes time

E-commerce:

• Median time to first revenue: 1-4 months
• 25th percentile: <1 month
• 75th percentile: 4-8 months
• Fastest to revenue but often small initial amounts

Marketplace:

• Median time to first revenue: 9-18 months
• 25th percentile: 6-9 months
• 75th percentile: 18-30 months
• Chicken-and-egg problem extends timeline significantly

First month revenue amounts:

B2B SaaS:

• Median first month: $500-$3,000 MRR
• Early adopter pricing often discounted
• First customers often from network
• Path to $10K MRR: typically 3-6 months after first customer

Consumer subscription:

• Median first month: $100-$1,000 MRR
• High variance based on price point and launch
• Often starts with organic/word-of-mouth
• Path to $10K MRR: typically 6-12 months after first revenue

E-commerce:

• Median first month: $1,000-$10,000 GMV
• Highly dependent on marketing spend and inventory
• Can scale quickly with paid acquisition
• Path to consistent revenue: 3-6 months

The pattern: First revenue is typically small. The important milestone is first revenue, not first significant revenue. Scaling comes later.

Team factors:

• Domain expertise in the problem space
• Prior startup experience
• Existing customer relationships
• Technical founders who can ship quickly

Product factors:

• Simple MVP that solves clear pain point
• Low technical complexity for V1
• Integration with existing workflows
• Clear differentiation from alternatives

Market factors:

• Obvious, well-understood problem
• Buyers with budget and authority
• Short sales cycles in category
• Limited competition for attention

Process factors:

• Customer discovery before building
• Iterating quickly based on feedback
• Charging early (even for beta)
• Focus on one customer segment

The fastest paths to revenue combine founder-market fit with a simple product that solves an obvious problem.

Common delays:

Building too much:

• Waiting for 'complete' product before selling
• Adding features instead of launching
• Perfectionism over pragmatism
• Typical delay: 3-12 months

Wrong customer target:

• Targeting enterprise when SMB would pay faster
• B2B when prosumer would work
• Needing to educate market on problem
• Typical delay: 3-9 months

No existing relationships:

• Cold outreach to first customers
• Building trust from zero
• No network to tap
• Typical delay: 2-6 months

Technical complexity:

• Integration requirements with other systems
• Compliance or security requirements
• Hardware or physical components
• Typical delay: 6-18 months

Marketplace dynamics:

• Need both supply and demand
• Can't monetize until liquidity exists
• Manual operations until scale
• Typical delay: 6-18 months

What the data shows:

• Faster time to revenue weakly correlates with survival
• But many successful companies took years to revenue
• The relationship is non-linear

Fast revenue companies:

• Often solving obvious, proven problems
• May face more competition
• Revenue validates market but not defensibility
• Examples: many e-commerce, agency-to-productized-service transitions

Slow revenue companies:

• Often building new categories
• May have stronger moats once established
• Higher risk but potentially higher reward
• Examples: deep tech, platform businesses, marketplaces

What actually predicts success:

• Revenue growth rate after first revenue matters more
• Customer quality and retention matter more
• Path to scaled revenue matters more
• Time to revenue is one signal, not the signal

Arguments for charging early:

• Validates willingness to pay, not just interest
• Attracts serious users, filters tire-kickers
• Creates revenue to extend runway
• Sets expectation that product has value
• Forces prioritization of valuable features

Arguments for free first:

• Reduces friction for early adoption
• Lets you iterate with more users
• Builds network effects or content
• Some models require scale before monetization

What the data suggests:

• B2B SaaS should charge early (even discounted)
• Consumer freemium often makes sense (monetize later)
• Marketplaces often delay monetization for liquidity
• Service businesses should always charge

The hybrid approach: Many successful companies charge early but at reduced rates. 'Design partner' pricing of 50-70% off gives you real revenue while giving early customers a discount for their feedback.

Positive signals before revenue:

• Users actively using product (engagement)
• Users asking when they can pay
• Organic word-of-mouth growth
• Clear feedback on what would make it valuable
• Competitive interest in what you're building

Warning signals:

• Building for 12+ months with no user engagement
• Users sign up but don't use product
• Feedback is polite but not actionable
• No one asks about pricing or timeline
• Pivoting repeatedly without traction

Timeline checkpoints:

• 3 months: should have clear customer conversations
• 6 months: should have users engaged with product
• 12 months: should have some revenue or strong evidence of coming revenue
• 18 months without revenue: seriously evaluate whether to continue

These are guidelines, not rules. Hardware, biotech, and new categories may have longer timelines. But most software products should hit revenue within 12 months.

Does first revenue need to be from a 'real' customer? Ideally yes. Revenue from friends, family, or your own company doesn't validate market demand. Revenue from strangers who found you organically is the strongest signal.

How much revenue do I need before raising? For seed: some revenue helps but isn't required. For Series A: typically $1M+ ARR or strong growth trajectory. First revenue and fundable revenue are different milestones.

Should I focus on revenue or users first? Depends on model. B2B: revenue validates more than users. Consumer: users and engagement may validate before revenue. Marketplaces: liquidity matters before monetization.

What if competitors are giving it away free? Either find a segment that will pay, offer something differentiated worth paying for, or accept you're in a market where free is the entry point and monetize differently.

Is consulting/services revenue 'real' revenue? It's revenue but not scalable product revenue. Many successful companies start with services, learn from customers, then productize. Just don't confuse service revenue with product-market fit.