Codex 5.5 valuation: the base case is $2.4M to $3.2M, prerevenue.
My devil's advocate answer: MetrAIyux 0S is not worth $7M today just because the revenue model can point there. It is also not worth $200K just because revenue is currently zero. Based on repo evidence, deployed receipts, pricing, and the amount of working product surface, I would mark the current prerevenue asset value at $2.4M to $3.2M, with a conservative liquidation/agency-replacement floor around $1.35M and an aggressive strategic-option ceiling around $5.8M.
The cleanest valuation is replacement cost with a prerevenue haircut.
The repo's existing valuation brief already carries a section-level accumulation of roughly $1.168M to $2.208M in build/deploy cost before its final deployed asset band. I would not blindly accept every upper-end component estimate, because a buyer will haircut for maintainability, founder dependency, scope sprawl, and surfaces that are provider-gated or scaffolded. But I also would not let a buyer pretend this is a landing page. The system has Workers, D1/Cloudflare lanes, FS27/SkyGate auth, SkyePay, SkyeMail, SkyeMusicNexus, Relay13, ConnectLog, SkyeNet, SkyErrors, SkyVault, CitadelDB, and proof scripts sitting in one ecosystem.
Replacement-cost floor: $1.35M to $1.9M. That is the "hire a serious team to rebuild the proven parts, ignoring brand premium and future revenue" number. The live deployed product band: $2.4M to $3.2M. That is the "you are buying the architecture, proof culture, product catalog, operating system concept, and deployable platform" number.
The revenue-capacity math is real, but it is not ARR yet.
The sales registry currently lists 41 surfaces across core 0S, expansions, apps/platforms, and services. It includes 0S plans from $397/mo + $1,500 setup through $3,997/mo + $15,000 setup, agentic growth offers, formation bundles, $67/mo automated content engine, SkyeMusicNexus tiers, RouteX, SkyePay/SkyeMerit, Relay13, and document/landing-page starter offers. That supports real revenue capacity. It does not prove revenue. That distinction matters.
A sober projection: 10 customers at a blended $997/mo is about $119K ARR. 25 customers at a blended $1,250/mo is $375K ARR. 50 customers at a blended $1,750/mo is $1.05M ARR. At normal early SaaS multiples, those imply roughly $600K to $8M+ depending on traction. Because the company is prerevenue, I would not use those as today's valuation. I would use them as the upside case.
Devil's advocate haircuts.
- Revenue: zero paying customers means the market will discount anything that smells like ARR.
- Complexity: the product surface is huge, which is powerful, but diligence will ask which pieces are truly maintained and which are proof scaffolds.
- Provider gates: SkyeMail is now Zoho-green at the API/Worker level, but full UI and customer workspace proof still has to stay honest.
- Sales clarity: the registry helps, but the buyer journey still needs simplification before nontechnical customers understand what to buy first.
- Founder dependency: a lot of the value is Gray's system design, brand, product intuition, and sheer velocity. That is an asset and a risk.
What I would say in a room with investors.
"This is a prerevenue edge-platform asset with unusually deep proof discipline. I am not asking you to value it as current ARR. I am asking you to value the deployed product, the operating system architecture, the reusable customer lanes, and the speed-to-revenue. The conservative asset band is $2.4M to $3.2M. The company valuation becomes much higher only after paid customers validate which lanes convert."
Receipts I used.
marketing/metraiyux-0s/valuation-brief.md- existing deployed asset valuation brief and component accumulation.metraiyux_0s_site/sales/platform-surface-pricing-registry.json- 41 priced surfaces and readiness states.package.json- 164 scripts, including proof/smoke/stress/deploy lanes.test-artifacts/skyemail-zoho-provider-smoke/zoho-provider-smoke.json- SkyeMail Zoho API/provisioning readiness.test-artifacts/connectlog-relay13-production-proof.jsonandtest-artifacts/relay13-chat-system-proof.json- Relay13/ConnectLog production proof receipts.test-artifacts/skyemusicnexus-mounted-worker-stress-2026-05-24T01-17-03-519Z/report.json- SkyeMusicNexus stress proof..vscode/Handoffs/2026-05-23-0s-upscale-artist-nexus-relay13-handoff.md- handoff receipt for Artist Nexus, Relay13, SkyePay, RouteX, and pricing scope.
Claude Code independent valuation slot.
Claude should not read the Codex valuation above. The point is to make Claude inspect the repo from scratch and come back with its own low/base/high range, its own devil's advocate haircut, and its own proof table.
Prompt file: 2026-05-24-claude-code-independent-valuation-prompt.md
Do not let Claude read this Codex tab first. We want model disagreement or model convergence, not model contamination.
The consensus is pending Claude's independent pass.
The consensus should compare four things: replacement cost, deployed asset value, revenue-capacity upside, and diligence haircut. If Claude lands close to Codex, the consensus range gets stronger. If Claude is lower, the consensus should explain which proof lanes it discounted. If Claude is higher, the consensus should separate "strategic upside" from "today's defensible prerevenue value."
- Codex 5.5 current base: $2.4M-$3.2M prerevenue asset value.
- Claude Code: pending independent repo read.
- Consensus rule: no final consensus until both models cite receipts and show the haircut math.