When a software product exists but traction is not yet proven, asking “what is it worth?” produces false precision.
AstroAI has real software, a live product surface, operating workflows, and a growing body of product knowledge. It does not follow that all of those things collapse into one defensible valuation. Different people asking about value are usually asking different questions.
I now use four separate lenses: replacement cost, strategic value, sale value, and venture value. They can share inputs, but they should never be treated as interchangeable.
I am deliberately not publishing private valuation amounts, ownership considerations, or unpublished commercial decisions here. The useful part for other builders is the framework and the measurement discipline behind it.
1. Replacement Cost: What Would It Take to Rebuild?
Replacement cost estimates the time and money required to recreate the current capability from a clean start.
The rough structure is simple:
replacement cost = rebuild effort × realistic loaded rate + direct recreation costs
The difficult part is the inventory. A product is more than its visible screens. AstroAI's replacement inventory includes categories such as:
- deterministic chart calculation and its validation;
- account, data, and consent flows;
- generated readings and chart-aware conversation;
- sharing and user-controlled data features;
- payment and subscription plumbing;
- product copy, legal surfaces, and accessibility work;
- automated tests, deployment, monitoring, and recovery paths;
- the private content-production workflow; and
- the accumulated knowledge of failed approaches and edge cases.
Replacement cost is not the market price. Buyers do not reimburse every hour a founder spent learning. It is still useful because it establishes that a functioning, integrated system is not equivalent to an idea or a prototype screenshot.
The estimate should include a discount for what can now be rebuilt faster with modern tools and a premium for work that requires domain judgment, integration, validation, or operational learning.
2. Strategic Value: What Does This Unlock for a Specific Owner?
Strategic value is contextual. The same product may be worth little to a general buyer and substantially more to an organization that already has an audience, complementary data, distribution, or a related product line.
I ask what the asset changes for a hypothetical operator:
- Does it shorten time to market?
- Does it add a capability that would otherwise require hiring or integration work?
- Can existing distribution lower the cost of reaching the right users?
- Does the trust and privacy posture remove adoption friction?
- Can the content and product systems support a broader portfolio?
These are value drivers, not valuation conclusions. Strategic value becomes credible only when tied to a concrete fit and a realistic path to realizing it. “A large company could use this” is not analysis.
This lens is also where confidentiality matters most. Specific counterparties, internal plans, and ownership scenarios do not belong in a public framework post.
3. Sale Value: What Would Transfer Today?
Sale value asks what a buyer would pay for the asset under current uncertainty. Before traction is proven, that is usually a risk-discounted view of the transferable product, not a reward for the builder's effort.
The inventory includes code, brand assets that can legally transfer, domains, documented operations, contracts, product data that can lawfully transfer, and the ease of handing the system to someone else. Then come the discounts:
- key-person dependency;
- undocumented operations;
- uncertain retention or acquisition economics;
- vendor and platform concentration;
- incomplete evidence for demand;
- legal or data-transfer constraints; and
- the cost of maintaining the product after handoff.
This is why documentation and clean operational boundaries create economic value. They reduce the gap between “the product works for me” and “the product can work for a new operator.”
Sale value can be lower than replacement cost without either number being wrong. A rational buyer may prefer to build, buy something else, or wait for more evidence.
4. Venture Value: What Could This Become?
Venture value is the most tempting lens and the easiest to abuse. It asks about a future company, not merely the product that exists today.
A simple model considers possible future outcomes, the probability of reaching them, the capital and time required, and dilution or execution risk. The arithmetic is less important than the assumptions:
- How large is the reachable market for this specific product?
- What activation event predicts that a user receives value?
- Do activated users return?
- Can the product acquire them at a sustainable cost?
- Does monetization preserve trust and usefulness?
- Which advantages persist if competitors copy the visible features?
Without traction, small changes in those assumptions can move the output dramatically. A venture estimate should therefore be shown as scenarios and sensitivities, not a single impressive number.
Track Drivers, Not Just a Headline
The valuation becomes more honest when it is refreshed from recurring measurements. My measurement sheet groups evidence by lens:
- Build evidence: shipped capabilities, test coverage, operational maturity, and estimated rebuild effort.
- User evidence: activation, return behavior, qualitative feedback, and unresolved friction.
- Commercial evidence: conversion behavior, support burden, and unit-economics assumptions.
- Transfer evidence: documentation, dependency concentration, data rights, and handoff readiness.
- Market evidence: comparable products, distribution access, and changes in the competitive landscape.
Each input gets a source, an “as of” date, and a confidence level. Assumptions are not promoted to facts just because they live in a spreadsheet.
I revisit the drivers on a regular cadence and after material product evidence. The goal is not to make the number move upward every month. The goal is to make uncertainty shrink.
Value Is a Decision Tool
The four-lens framework helps answer different decisions:
- Replacement cost informs build-versus-buy and insurance against undercounting the asset.
- Strategic value identifies which capabilities matter to a particular operator.
- Sale value exposes transfer risk and current market reality.
- Venture value tests whether the upside justifies continued investment.
Keeping the lenses separate prevents a common founder mistake: using the highest answer to every question. A product can be expensive to rebuild, strategically interesting, difficult to sell today, and still have meaningful venture upside. Those statements can all be true at once.
Before traction is proven, honest ranges and explicit assumptions are more useful than a precise private figure. The next job is not defending the spreadsheet. It is creating user evidence that changes it.