Ankit Kapoor
All work

Project 03

What do the economics require?

Priced In

A workbench that turns a valuation into the operating performance a business would have to deliver to justify it.

Status: PrototypeEvidence: IllustrativeA working demo runs. Results are reported by the evidence label.

Concept preview

Concept preview — the expectations map the workbench produces: growth and margin combinations consistent with one valuation target. Axes are unitless and the target is hypothetical; no company, price, or forecast is shown.

Drawn wider than this screen — scroll the figure sideways, or read it in words below.

What this figure shows, in words
  • The horizontal axis is revenue growth and the vertical axis is operating margin. Both are unitless and carry no tick values.
  • A band crosses the grid from upper left to lower right. Every point on it satisfies the same hypothetical enterprise-value target, so higher required growth trades against lower required margin.
  • Two points on the band are annotated. One sits at modest growth with high margin; the other at fast growth with thin margin. They are alternative futures consistent with the same target, not a prediction of either.
  • Selecting a point feeds the operating bridge, which states three requirements: the customers the business must add, the price it must hold per customer, and the contribution the AI initiative must make.
  • There is no company, price, forecast, or return in the drawing, and the target is hypothetical.

Original SVG drawn for this repository from the Priced In brief (docs/03_Priced_In_BRD.md, sections 1 and 4). No third-party imagery.

The 30-second brief

Evidence: Illustrative

Decision
A company's valuation embeds a forecast that nobody has written down. Before arguing about whether it is too high, work out what it actually requires the business to do.
Position
Investigation in progress. The workbench now computes a valuation and draws the expectations map, and its arithmetic agrees with golden fixtures worked out by hand. But no real company has been analysed, no finance professional has looked at the method, and no case has been authored, so there is nothing to conclude. The proposed test is unchanged: reconcile the five-year cash-flow model against an independent golden model within a stated tolerance, then publish one fully worked synthetic case with every input traced to its source.
Evidence
None measured. The workbench runs and its output matches fixtures computed by hand, but a fixture checks arithmetic rather than establishing a finding, and the synthetic sample company is a calculation fixture, not a company. No real company has been analysed, no end-to-end reconciliation against an independent model has been run, no finance professional has reviewed anything, and no case has been authored.
Trade-off
Running the valuation backwards removes the false precision of a single point forecast and shows a whole surface of futures that satisfy the same price. It also gives up the thing people want from a model, which is one number, and it makes the output harder to summarise in a meeting.
Uncertainty
Whether the operating bridge stays honest for businesses that do not decompose cleanly into customers and price, and whether a reader takes the expectations map as a set of requirements or misreads it as a forecast.

Context and decision

Most arguments about whether an AI investment is worth it are arguments about narrative. One side describes a transformation, the other describes a bubble, and neither writes down what the numbers would have to do. The question that settles more of these than it should is simply: what has to be true?

A valuation already contains an answer to that question; it is just not written down anywhere. Run the model backwards and the implicit forecast becomes an explicit requirement — this much revenue growth sustained for this long at this margin, or some other combination on the same curve. Once the requirement is visible, the disagreement becomes concrete: not whether the company is overvalued, but whether that particular combination is achievable.

The AI-specific version follows directly. If a company is spending on an AI initiative, that spend has to earn its place in the requirement. The workbench asks what contribution the initiative would have to make — in revenue, in margin, or in capital efficiency — for the case to hold, which is a much sharper question than whether the strategy sounds forward-looking.

Alternatives considered

  • Build a conventional forward DCF

    ForIt is the expected format, and every reviewer already knows how to read one.

    AgainstA forward DCF invites the analyst to reverse-engineer assumptions until the output matches their prior, then present the result as a finding. Starting from the price makes the required assumptions the visible output instead of the hidden input.

  • Report one fair-value estimate

    ForA single number is what most readers want, and it makes the tool feel decisive.

    AgainstIt would misrepresent what the analysis can support. Many growth and margin combinations satisfy the same price; collapsing that surface to a point discards the actual finding.

  • Let a model read the filings and answer questions

    ForConversational statement analysis would remove almost all of the intake work.

    AgainstAn unauditable number is worse than no number in a valuation context. Every reported input has to be traceable to a source locator or an explicit user entry, and normalisation has to be visible rather than silent.

Method and model

Inputs arrive through a long-form CSV template where each row carries a company, fiscal year, period, statement type, metric, value, unit, scale, and source locator. Three to five complete fiscal years are preferred; one baseline year is technically sufficient and the interface marks the limited history rather than hiding it.

The model is a five-year FCFF projection with an explicit terminal assumption. From a chosen enterprise-value target, the expectations map plots the growth and margin combinations consistent with that target. Selecting a cell makes that scenario active, and the operating bridge decomposes it into the customer, price, or volume requirements it implies — but only when the supplied data actually permits that decomposition.

One AI initiative can be overlaid on the active scenario to test the contribution it would need to make. Break My Thesis then works in the opposite direction, searching for the assumption changes that would invalidate the selected case, so the strongest objection is generated by the tool rather than left to the reader.

Market data, reported financials, normalised adjustments, and future assumptions are visually distinct everywhere they appear. Editing an input marks dependent calculations stale until they are recomputed; the previous valid result stays on screen, labelled, rather than being silently mixed with new numbers.

Evidence and results

The workbench runs. It computes a valuation from the supplied inputs and renders the expectations map as a forty-one by forty-one grid, drawn off the main thread, with the band that lands near the chosen target marked and the cells whose inputs are invalid hatched rather than quietly filled in. It is deployed and open to anyone, so the map can be explored directly rather than described here.

There are still no results. Golden fixtures worked out by hand agree with what the model returns, which establishes that the arithmetic does what it claims — and nothing whatsoever about a company. The model has not been reconciled against an independent implementation end to end, no real company has been analysed, no finance professional has reviewed the method, no case has been authored, and no valuation has been published.

The evidence on this page is the synthetic fixture, the input-provenance rules, and the concept schematic. The fixture is a calculation fixture: its purpose is to exercise arithmetic, and it is labelled fictional wherever it appears.

  • Synthetic sample company

    IllustrativeA complete set of statement inputs used as a calculation fixture, labelled fictional wherever it appears. It exists so the model can be exercised end to end without implying an opinion about a real company.

    Sources: src-priced-brief

  • Source-mapped inputs

    IllustrativeEvery input carries its original amount, unit, period, source locator, and status, shown beside the normalised value. No missing number is assumed to be zero without explicit confirmation.

    Sources: src-priced-brief

  • Concept preview schematic

    IllustrativeThe labelled hypothetical expectations map shown on this page. The axes are unitless and the target is hypothetical; it depicts the shape of the output, not a computed result for any company.

    Sources: src-priced-schematic

Interpretation

The interpretation this project is set up to test is that most disagreements about AI valuations are disagreements about required operating performance that neither side has stated, and that making the requirement explicit resolves more of the argument than better forecasting would.

The clearest way this fails is if the required combinations turn out to be so wide that almost any narrative fits inside them. That result would be worth publishing too: it would mean the price constrains the story far less than either side of the argument assumes.

  • Trade-offA surface over a point estimate

    Showing every growth and margin pair that satisfies a target is more faithful and much harder to quote. A single fair value would travel further and mean less.

  • Trade-offA narrow scope over broad coverage

    USD-reporting, US-GAAP, non-financial operating businesses with positive normalised operating profit. Banks, insurers, and pre-revenue companies are refused at intake instead of being forced through a model that was not built for them.

  • Trade-offVisible normalisation over clean output

    Showing the original figure beside every adjustment clutters the review screen. Hiding it would make the model unauditable, which defeats the purpose.

Limitations

All financial examples are synthetic calculation fixtures. Nothing here is a valuation of, or an opinion about, any real company.

This is an educational strategy-analysis tool. It does not execute trades and does not infer one objectively correct market forecast from a share price.

Scope is limited to USD-reporting US-GAAP non-financial operating businesses with positive baseline revenue and positive normalised operating profit. Banks, insurers, REIT-specific valuation, pre-revenue firms, and distressed restructurings are out of scope and are refused at intake.

Automated statement retrieval and PDF extraction are a later release stage. Until they exist, upload support should not be described as broad.

  • OpenWhether the operating bridge generalises

    Translating a growth requirement into customers and price works for subscription-shaped businesses. For businesses that do not decompose that way, the bridge may need to stay switched off rather than approximate.

  • OpenWhether readers hear 'requirement' or 'forecast'

    The entire value of the framing depends on that distinction. If the map reads as a prediction, the tool is actively misleading and the interface has failed.

  • OpenWhether terminal value swamps the analysis

    In a five-year model, most of the value typically sits past the horizon. If the terminal assumption dominates every case, the interesting decisions may be somewhere the model does not look.

Next test

The five-year model and the expectations map are live. The rest of the first release scope in the brief is still outstanding.

Then reconcile the model against an independently built golden model and publish the agreed tolerance. Hand-computed fixtures check individual figures; they are not a reconciliation, and an unreconciled valuation model is not evidence about a company.

Then author one complete worked case on the synthetic company, with every input traced to a source and every conclusion attributable to a stated assumption.

Sources

  • src-priced-brief Priced In — business requirements, version 1.0

    Owner-authored specification dated 6 September 2026, held in this repository at docs/03_Priced_In_BRD.md. Defines the intake format, the canonical metrics, the model structure, the scope boundaries, and the release stages. All financial examples in it are explicitly synthetic calculation fixtures.

  • src-priced-schematic Concept preview schematic (original)

    Original SVG drawn for this site from the specification above, held at components/schematics/priced-in.tsx. Axes are unitless and the target is hypothetical.

Authorship and review

Ankit's contribution
I chose the reverse-valuation framing, specified the model structure and the terminal treatment, designed the expectations map, the operating bridge, and the Break My Thesis stress test, and set the scope boundaries that keep the tool from being applied where it does not belong.
AI-assisted implementation
The workbench has been implemented with AI coding assistance against a specification I authored. Calculations are required to reconcile against an independent golden model within a stated tolerance before any figure is published; assistance is not accepted as verification, which is why no figure the workbench computes appears on this page.
Human review
Reviewed by me on 7 September 2026 for accuracy of status and claims. No external review, and no review by a finance professional. No end-to-end numerical reconciliation has been run and no case has been authored.
Status
A working demo runs. Results are reported by the evidence label.

Published . Last updated .