How We Evaluate Seed-Stage SaaS Metrics That Actually Matter

One of the most common mistakes early-stage founders make when pitching enterprise SaaS companies is presenting metrics that sound impressive but do not actually tell investors anything useful about the business. Registered users, monthly active users, total conversations processed, API calls served — these numbers can grow impressively while the underlying business is fundamentally broken. At Moberg Analytics Ventures, we spend a significant portion of our diligence process cutting through the noise to identify the metrics that actually signal whether an early-stage enterprise SaaS business has genuine product-market fit.

This essay lays out the framework we use and the specific signals we look for at the seed stage. It is not a universal truth — every company is different, and context matters enormously. But it reflects the patterns we have observed across hundreds of seed-stage enterprise SaaS evaluations and the distilled lessons we have learned from backing companies that succeeded and companies that did not.

Why Vanity Metrics Are Worse Than No Metrics

Vanity metrics are not merely uninformative — they are actively harmful to the decision-making process. When a founding team is organized around optimizing for metrics that do not predict business success, they allocate their most precious resources (time and talent) toward activities that generate impressive-looking numbers rather than genuine value. We have seen companies with tens of thousands of registered users and a growth rate that looks compelling on a slide deck turn out to have zero paying customers and a product that no one actually depends on.

The structural problem with vanity metrics in enterprise SaaS is that they are easy to optimize for independently of value creation. You can drive user registration with broad-based top-of-funnel marketing. You can inflate engagement numbers by gamifying onboarding workflows. You can generate impressive API call volumes by building integrations with high-frequency automation systems. None of this tells you whether the enterprise is getting meaningful value from your product or whether they would notice if it disappeared tomorrow.

The metrics that matter in enterprise SaaS are the ones that are structurally hard to inflate without creating genuine value. Our evaluation framework is built around identifying and rigorously examining those metrics.

The Metrics That Matter at Seed Stage

Number of paying customers and contract value. At the seed stage, we want to see between three and ten paying enterprise customers with contract values that are meaningful relative to the complexity of the problem being solved. A single $200K ARR contract with a Fortune 500 customer tells us far more about product-market fit than 500 self-serve signups at $100/month. We are looking for evidence that sophisticated enterprise buyers have evaluated the product, found it valuable enough to write a check, and authorized it through their procurement process. Every step of that process is a filter that validates genuine value.

Net Revenue Retention (NRR). If there is a single metric that most reliably distinguishes exceptional early-stage enterprise SaaS companies from mediocre ones, it is NRR. For companies with enough customer history to measure it (typically 12 months), we want to see NRR above 110%. This means that a cohort of customers that paid $100 in year one is paying $110 or more in year two, after accounting for churn and expansion. Companies with NRR above 110% have a business that grows even without adding new customers. That is a fundamentally different and more powerful business model than one that requires constant new customer acquisition to offset churn.

Time to value and activation rate. In enterprise SaaS, particularly AI analytics, the gap between signing a contract and actually getting the customer to a point where they are using the product and seeing value is often the most dangerous phase of the customer relationship. We look carefully at how long it takes customers to go from contract signing to active use, and what percentage of deployed seats or licensed users are genuinely active. A product with fast activation and high seat utilization has a fundamentally different competitive position than one that requires six months of professional services to get to value and then sees low adoption rates within customer organizations.

Customer references and qualitative depth. Raw metrics are necessary but not sufficient. We call customer references for every company we are seriously evaluating, and we ask questions designed to surface the depth and authenticity of the relationship. Is this product on the customer's critical path? Would the customer go out of their way to advocate for this company in a procurement conversation at another enterprise? Have they given the founding team direct access to their internal stakeholders, data systems, or workflow processes? The answers to these questions often tell us more about product-market fit than any quantitative metric.

The Burn and Efficiency Signal

We pay close attention to how efficiently a seed-stage company has acquired its early customers and built its product. This is not primarily about burn rate in absolute terms — it is about what the founding team has learned about resource allocation and the relationship between spending and value creation.

A company that has signed three enterprise customers while spending $2M and maintaining an 18-month runway is in a very different position than a company that has signed the same three customers after spending $8M on sales and marketing. The first company has demonstrated capital efficiency that is a strong predictor of their ability to scale efficiently as they raise larger rounds. The second company has a much harder path ahead, because the unit economics of customer acquisition are not favorable.

We are specifically looking for founding teams that have developed an intuition for capital-efficient growth — teams that can articulate clearly which activities drove customer acquisition, which experiments failed and what they learned, and what they would do differently with more capital. This intuition is a form of organizational learning that compounds over time and becomes a structural advantage as the company scales.

Product Usage Depth vs. Breadth

In enterprise SaaS, the distinction between breadth and depth of usage is critical. Breadth — the number of users within a customer organization who log in — is a useful signal, but it is depth that predicts retention and expansion. We look for evidence that the product is embedded in core workflows in a way that would make it genuinely painful to remove.

Depth signals include: integration with mission-critical systems (CRM, ERP, data warehouse), daily active usage by key decision-makers (not just power users), and the creation of internal processes or reports that depend on the product. When a customer has built their quarterly business review process around outputs from your AI analytics platform, removing that platform requires not just a technical migration but an organizational change management process. That stickiness is worth far more than a large number of casual users who log in occasionally.

For AI analytics companies specifically, we look for evidence of what we call "insight dependency" — the state in which a customer's decision-makers are actively changing their behavior based on AI-generated recommendations from the product. When a VP of Sales is routing their pipeline review process based on churn scores from an AI analytics platform, that product has achieved insight dependency. Insight dependency is the highest form of product stickiness in this category.

The Team Signal in the Numbers

Metrics do not exist in isolation from the team that generated them. When we see strong metrics at the seed stage, one of our first questions is whether the founding team understands why those metrics are strong and can articulate a credible theory for how they will maintain and improve them at scale.

Founders who can trace every NRR point back to a specific product decision, customer relationship, or market dynamic are founders who are operating with a genuine understanding of their business. Founders who present strong metrics but cannot explain the mechanisms that generated them are often riding a wave of early-adopter enthusiasm that is unlikely to persist as the company moves toward mainstream enterprise buyers.

The team signal in the numbers is also about what founders choose to show us and in what order. Founders who lead with their most substantive metrics — ARR, NRR, customer count, activation rates — and are transparent about the metrics that are not yet strong have demonstrated a level of intellectual honesty that is a strong predictor of their ability to be candid partners through the challenges ahead. Founders who bury the important metrics behind impressively large but ultimately uninformative numbers raise our skepticism about what they are not telling us.

What We Do Not Look For at Seed Stage

It is worth being explicit about what we do not require at the seed stage. We do not require a complete, polished product. We do not require a large sales team or a formal go-to-market motion. We do not require evidence of enterprise procurement compliance certifications (SOC 2, HIPAA, etc.), though a plan to achieve them is helpful. And we do not require scale — we are investing at the seed stage precisely because the company is too early to have scale.

What we do require is evidence that the core value proposition has been validated by real customers making real commitments. A founding team with three enterprise customers paying meaningful ARR, high NRR, and deep product integration is an exceptional seed-stage company regardless of whether their MRR is growing at 20% or 50% in any given month. The underlying quality of those customer relationships tells us far more about the long-term potential of the business than growth rates calculated from small absolute numbers.

Conclusion: Signal Over Noise

Evaluating seed-stage enterprise SaaS metrics is an exercise in separating signal from noise. The noise is loud — there are many metrics that look impressive at the seed stage and that are easy to optimize for without creating genuine business value. The signal is quieter — it lives in the depth of customer relationships, the quality of NRR, the efficiency of customer acquisition, and the degree to which the product is embedded in critical workflows.

Our job as investors is to be relentlessly focused on the signal. When we find it, we move quickly and with conviction. When we cannot find it, no amount of impressive-sounding numbers will change our assessment.

If you are a founder building an enterprise SaaS or AI analytics company at the seed stage and want to understand how we would evaluate your business, we are always happy to have that conversation. Reach out to the Moberg Analytics team — honest, direct feedback is something we take seriously as a core part of how we engage with founders.

Key Takeaways

• Vanity metrics are actively harmful — they direct attention and resources away from genuine value creation.
• The metrics that matter most at seed stage: paying customer count and contract value, NRR (target above 110%), activation rate, and customer reference quality.
• Capital efficiency in early customer acquisition is a strong predictor of long-term unit economics.
• Product depth (insight dependency, workflow integration) predicts retention far better than breadth of user adoption.
• Founders who understand the mechanisms behind their metrics are a stronger signal than the metrics themselves.
• At seed stage, we require evidence of validated value, not scale — three committed enterprise customers beat ten thousand free users.