When a startup has no revenue, a spreadsheet tells you almost nothing—and in deep tech, where development cycles are long and capital-intensive, that problem is sharpest. I believe the answer is not to guess at a number, but to weight three non-financial drivers deliberately: team expertise, technical validation, and intellectual property strength. The best-known structured approach, the Scorecard Method attributed to angel investor Bill Payne, gives the team the heaviest weight at 25%, product and technology 18%, and bundles IP into an "Other" category at 12% alongside competition and timing. For deep tech, those generic categories need specialized inputs, and that is exactly what metrics like the System Maturity Milestone Index provide.

Introduction: Beyond Revenue - Valuing Deep Tech Startups

Generic pre-revenue valuation advice assumes a software-style world of sign-ups and waitlists. Equidam's guidance on valuing pre-revenue startups, written by Dan Gray, does note that early traction can come from prototypes, key technical milestones, and pilot programs—but deep tech demands more precision than "achieved a milestone." Which milestone? At what readiness level? At what cost?

That is where the two lenses in this article meet. The Scorecard Method, described by Tucker McKay writing for Mercury, is best suited to pre-revenue seed-stage companies and works by adjusting a regional median pre-money valuation up or down based on how the target compares to peers across weighted factors. Specialized deep tech metrics, outlined in a venture capital metrics discussion on Thinkstorm's blog, translate vague notions of "technical progress" into observable signals. Used together, they form a framework—but not a formula that outputs a single definitive number.

Adapting the Scorecard Method for Deep Tech

The Scorecard Method starts with a regional and sector-specific median—say, a hypothetical $8 million for B2B SaaS seed deals in the U.S., using McKay's illustrative figure. You then score the target against comparable companies on each weighted factor and adjust the median accordingly.

For deep tech, I would argue the adaptation happens in the inputs, not the weights. The "Product / technology" factor at 18% should be fed by concrete readiness evidence—not a demo video, but integration test completion, supply chain maturity, and repeatable manufacturing processes. The "Other" factor covering IP at 12% deserves unusually detailed due diligence in deep tech, because defensibility often substitutes for the revenue you cannot yet see. And the team's 25% weight should be read against founders' relevant technical experience and their ability to execute a long R&D roadmap, the same criteria Equidam says investors probe through reference checks and assessment of team dynamics.

Technical Validation: Measuring Progress with SMMI and CETD

The System Maturity Milestone Index, or SMMI, is designed to be more demanding than the standard Technology Readiness Level scale. As the Thinkstorm discussion explains, it integrates technical readiness with subsystem interdependencies, tracking three things TRL alone misses: completion of integration tests rather than just component tests, maturity of supply chain or fabrication pipelines (especially for space-graded or ITAR-controlled parts), and evidence of repeatable manufacturing processes.

The index's illustrative example shows the texture: a company reporting progression from TRL 4 to TRL 6, a validated hot-fire test in vacuum conditions, and a passed ISO 14644-1 Class 7 cleanroom qualification for engine assembly. That is a milestone vocabulary, not a revenue vocabulary.

Its companion metric, Capital Efficiency per Technical Delta (CETD), measures dollars spent per meaningful technical advancement—not per time period. The distinction matters: a deep tech company can burn capital for eighteen months with little to show, or achieve a genuine capability jump on a lean budget. CETD lets you compare those two companies on effort, not calendar.

IP Strength: Beyond Patents

In due diligence, Equidam's guidance identifies IP review as part of product and technical due diligence: verifying IP ownership and protection, and understanding the technical roadmap and potential challenges. Verification is the operative word. For a pre-revenue deep tech company, a patent the founders do not clearly own is not an asset—it is a liability in waiting.

Within the Scorecard Method, IP sits in the "Other" bucket at 12%, grouped with competition and timing. McKay's presentation treats this as a catch-all, but in a deep tech context the grouping arguably understates what is often the company's primary moat. My view: keep the weight, but do the work behind it—confirm who owns the underlying technology, what protection exists, and whether the technical roadmap extends the moat or exhausts it. Note that this article is not legal advice on intellectual property protection; ownership and protection questions belong with qualified counsel.

Team Expertise: The Deep Tech Differentiator

The Scorecard Method's heaviest weight—25%—goes to the strength of the team, and in deep tech that ordering makes sense. When the technology is pre-product and the commercialization path runs through years of R&D, the founders' relevant experience and ability to execute are often the primary asset investors are actually buying.

Equidam's framework points to what to examine: founders' backgrounds, relevant experience, expertise, and commitment, plus team dynamics, completeness, and capacity to execute the plan, typically validated through reference checks. For deep tech specifically, the SMMI example above also hints at what expertise looks like in practice—a team that can pass cleanroom qualification and run vacuum-condition testing is demonstrating executional capability that no pitch deck can fake. I would watch whether the team's claimed specialists match the subsystems the SMMI says are immature.

Deep Tech Startup Evaluation Framework

Use this table as a structured due diligence checklist, comparing the three core non-financial metrics side by side with the signals to request from founders:

Evaluating the three core non-financial drivers of a pre-revenue deep tech startup
Evaluation MetricKey Criteria / SignalsDeep Tech Application / Example
Technical Validation SMMI progress (integration tests, supply chain maturity, repeatable manufacturing) and CETD: dollars spent per meaningful technical advancement, not per time period. Feeds the Scorecard Method's "Product / technology" factor (18%); example: TRL 4 to TRL 6 progression, vacuum-condition hot-fire test, ISO 14644-1 Class 7 cleanroom qualification.
IP Strength Verified IP ownership and protection; technical roadmap and potential challenges, per product and technical due diligence. Sits in the Scorecard Method's "Other" factor (12%, with competition and timing); often the primary competitive moat pre-revenue.
Team Expertise Founders' backgrounds, relevant experience, expertise, commitment, team dynamics, completeness, and ability to execute; reference checks. Heaviest Scorecard Method weight (25%); in deep tech, the team's capabilities are often the primary asset.

The comparison works because each metric pairs an observable signal with a place in the valuation arithmetic: SMMI and CETD evidence fills the 18% technology factor, verified ownership fills the 12% IP factor, and demonstrated execution fills the 25% team factor. None of the three is optional; a company strong on one and weak on the others should adjust the regional median down, not up.

A Unified Framework for Deep Tech Investment Decisions

Putting it together: start with the regional median pre-money valuation for comparable companies in your region and sector, as the Scorecard Method prescribes. Then score the three core metrics against peers. For the technology score, request SMMI-style milestone evidence rather than TRL claims alone, and compute a rough CETD—capital consumed divided by meaningful technical deltas achieved—to see whether progress is being bought efficiently. For the IP score, require ownership and protection verification plus a roadmap walkthrough. For the team score, run reference checks and assess whether the founding team's expertise maps to the subsystems that remain immature.

Two caveats frame everything. The Thinkstorm discussion itself cautions that these metrics create common terminology for due diligence and calibration across subsectors, not direct cross-comparisons—every deep tech subsector is different. And the Scorecard Method is explicitly a framework for analysis, not a formula that produces a single definitive number.

Making Informed Deep Tech Investment Decisions

Investors should adopt a multi-faceted valuation approach that integrates adapted qualitative frameworks like the Scorecard Method with specialized deep tech metrics such as SMMI and CETD. The generic weights—25% team, 18% technology, 12% IP and other factors—become genuinely useful only when each factor is scored on deep tech-specific evidence rather than software-era proxies.

The measurable indicator to watch between rounds is straightforward: a consistent increase in the System Maturity Milestone Index alongside a favorable Capital Efficiency per Technical Delta indicates strong technical progress and efficient resource use. If the next diligence pass shows rising SMMI on flat or improving CETD, the qualitative case is compounding. If SMMI stalls while spending accelerates, the median valuation adjustment should go down—no matter how impressive the team remains on paper.

Sources