Microsoft-Decision-1

Microsoft-Decision-1

10/10/2026
Sponsored Link

Microsoft-Decision-1 Investment Report

Category: Structured decision models for AI agents and software workflows

Stage: Public preview; available through Microsoft Foundry and OpenRouter

Company: Microsoft Corporation; Microsoft-Decision-1 is a company product, not a standalone startup

Founder(s): No startup founders. Microsoft identifies Achint Srivastava, VP of Software Engineering in the Office of the CTO, as the author of the launch post

Funding: No product-specific financing disclosed; Microsoft is the parent and capital provider

Business Model: API usage at $0.042 per million input tokens; output tokens are listed as free

Product Hunt Launch Date: 2026-10-10 (spreadsheet date; Microsoft announced the model October 9, 2026)

Research Date: 2026-10-13

Valuation: No product-level valuation or investable security

Final Decision: Pass

Executive Summary

Microsoft-Decision-1 is a small model for fixed-choice decisions in software: classification, routing, ranking, and agent control. It returns structured choices and probabilities rather than prose. Microsoft says it post-trained Qwen3.5-9B and offers it in Foundry and OpenRouter.

Microsoft reports strong performance and internal tests, but product-level usage, external customers, retention, and revenue are undisclosed. The listed price is $0.042 per million input tokens, with free output.

This is a Microsoft product, not a venture-backed company: it has no separate founders, cap table, financing, or security. Pass on the model as a standalone venture opportunity; Microsoft equity requires a separate parent-company analysis.

Product Overview

Announced October 9 for public preview, the model accepts text or JSON plus typed questions. It returns a yes/no probability, a choice among options, or a rubric score. Uses include ticket triage, routing, content filtering, model selection, and agent evaluation. It does not provide free-form rationale, so applications must set thresholds and human-review paths.

Microsoft says it post-trained Qwen3.5-9B and may later rebase on MAI or OpenAI models. In its own tests, Microsoft reports highest accuracy across 36 benchmarks and nearly 150,000 held-out questions, 1.3% average flips across eight input perturbations, and 2.5x the speed of H2O-Lightning-4B v1.1 / 35x GPT-6 Sol (results). These comparisons are issuer-reported, not independent validation.

Founder and Team Assessment

There is no standalone founding team. Microsoft’s launch post is authored by Achint Srivastava, VP of Software Engineering in the Office of the CTO; Product Hunt lists Rohan Chaubey as hunter. The product benefits from Microsoft’s research, Azure infrastructure, Foundry marketplace, and enterprise relationships. That is a strong parent platform but does not create an independent management team or product-specific equity thesis. The founder/team score below reflects the lack of a separately investable venture, not Microsoft’s overall capabilities.

Market Opportunity

The market is decision steps embedded in AI applications: classifying content, routing requests, prioritizing items, and choosing tools. A dedicated model can reduce latency and cost when applications need a bounded answer rather than generated prose.

No standalone TAM or customer base is disclosed. Opportunity depends on how many agent workflows tolerate fixed-choice outputs and whether developers trust scores enough to automate or reduce review. Azure and Foundry offer distribution, but buyers can choose among a rapidly changing model catalog. No defensible product-specific TAM can be calculated from public information.

Traction and Growth Signals

Product Hunt’s current homepage snapshot listed the launch at #4 with 174 points among the previous day’s top products. That is launch interest, not recurring use.

Microsoft describes internal use: Xbox Research classified over 10,000 feedback items with quality it says was comparable to GPT-6 Sol, 14x faster and 200x cheaper; Copilot and Microsoft Discovery teams also report internal gains. These are company-reported evaluations, not external adoption. The model is in public preview. No third-party customer count, API volume, repeat-use rate, retention, or product revenue was found.

Competitive Position

OpenAI’s Decisions API offers typed probabilities for classification and scoring at $0.10 per million input tokens in public beta, versus Microsoft’s $0.042. Products differ in quality, data controls, and deployment, so price alone is not decisive. H2O-Lightning-4B and other open-weight models let buyers self-host; Microsoft includes such models in its own comparisons.

Microsoft advantages are Azure distribution, enterprise procurement, low list price, and claimed speed. Defensibility is limited: model designs are replicable, open alternatives are developing, and Microsoft’s own plan to rebase the model suggests the underlying implementation may shift. No exclusive data, external benchmark lead, or switching cost is public.

Business Model and Economics

Pricing is $0.042 per million input tokens with free output. Low cost may attract high-volume uses and increase Azure consumption, but list price is not revenue after discounts, distribution, and inference cost. Microsoft discloses no model-level margin, call volume, or revenue.

At list price, one billion input tokens generate $42. A standalone API would need about 5.95 quadrillion billable input tokens annually to reach $250 million revenue, assuming no discounts and excluding other revenue. This scale suggests the model’s value is more plausible inside Microsoft’s broader cloud business than as an independent venture.

Unicorn Path

No independent company, security, or revenue stream exists to support a standalone unicorn path. For scale only, the 4.0x Q2 2026 median SaaS M&A multiple would imply $250 million annual revenue for a $1 billion enterprise value. This is not a valuation method for Microsoft or necessarily for a model API. Microsoft may gain indirect value through Azure use and agent-platform retention, but it reports no product-attributed impact.

Valuation Assessment

There is no product-level company, round, cap table, security, or revenue to value. Microsoft is a large public parent, so its stock is not a clean exposure to this one model. An investment in Microsoft requires a separate company-wide valuation and thesis.

Key Risks

  • Benchmark risk: Microsoft’s comparisons are not independently reproduced on customer workloads.
  • Calibration drift: Microsoft’s documentation says calibration is strongest on familiar task types; production data changes.
  • No rationale: Applications need audit and escalation paths for opaque scores.
  • Fairness and safety: Microsoft’s documentation warns about bias and wording sensitivity; sole reliance is unsafe for consequential decisions.
  • Competition: Open models and rival APIs can pressure price and performance.
  • Attribution: Parent scale and bundling obscure product-level economics.
  • Model dependency: The Qwen base and planned future rebasing may change.

Final Assessment

Venture Potential: 51/100

CategoryScore
Market Size and Expansion Potential15/20
Traction and Growth Evidence7/20
Founder and Team as a Standalone Venture4/15
Product Strength9/10
Distribution Potential9/15
Business Model and Economics4/10
Defensibility3/10
Total51/100

The model targets frequent, real software tasks and has an attractive price and parent distribution. The score is capped by absent third-party traction, product-level economics, and a standalone investment vehicle.

Evidence Confidence: 82/100

Microsoft’s official sources document product behavior, access, pricing, and internal tests. Confidence is lower for comparative performance and external demand because Microsoft produced the benchmarks and no independent production cohort is public.

Final Decision: Pass

Pass on Microsoft-Decision-1 as a standalone venture. Consider Microsoft only through a separate parent-company investment review.

Upgrade Conditions

  • Independent, reproducible evaluations across representative customer workloads and task types.
  • Third-party production usage, repeat rates, and retention by deployment cohort.
  • Published cost, latency, calibration, and error rates under real traffic.
  • Evidence that customers pay for or expand Azure usage because of the model.
  • Clear governance for human review, sensitive decisions, data retention, and model updates.

Downgrade Conditions

  • Independent testing fails to reproduce Microsoft’s quality or latency claims.
  • Confidence scores drift materially under ordinary prompt and traffic changes.
  • Buyers prefer self-hosted or competing decision models at lower total cost.
  • Pricing or access changes remove the model’s cost advantage.

Questions for Further Diligence

  1. Which exact 36 benchmarks and task distributions support the reported accuracy result?
  2. What are independent accuracy, calibration, and latency results on production data?
  3. What are p50 and p95 latencies by region, input length, and deployment tier?
  4. What share of Foundry deployments make repeated production calls after initial testing?
  5. What customer or Azure revenue is attributable to Microsoft-Decision-1?
  6. What are serving costs and gross margins at the listed $0.042 per million input tokens?
  7. How are calibration drift and distribution shifts monitored in production?
  8. What safety, privacy, and retention controls apply to Foundry and OpenRouter requests?
  9. What licensing and technical constraints apply to the Qwen-based model and future re-basing?
  10. Which use cases require human review, and what escalation mechanisms are recommended?

Sources

Conclusion

Microsoft-Decision-1 is a promising low-cost model with internal use cases and broad parent distribution. External performance and adoption remain unverified, and the model is not a separately investable company. Pass on it as a standalone venture target.

Conclusion

Microsoft-Decision-1 is a promising low-cost decision model with useful internal applications and broad parent distribution. Its results still need independent validation and external adoption evidence. More fundamentally, the launch is a Microsoft product rather than a separately investable company. Pass on the product as a standalone venture target.