Evidence vs. Opinion III
The Price Got in the Way
The problem of building a model while staring at the answer.
A small-cap under a pending takeover. The share price sat at $55.08. The standalone business sat in a trough: revenue down 30%, margins compressed to 5.6%.
Sharpe AI evidence floor
$15.03/share
Sharpe scenario band
$11.91–$18.94
Claude Run 1
$36.66/share
Claude Run 2
$27.06/share
Market / bid price
$55.08/share
Core issue
Anchoring
$55.08
The bid
Control price / market anchor
$36.66
Claude Run 1
Recovery thesis
$27.06
Claude Run 2
Recovery thesis
$15.03
Sharpe AI
Evidence-led standalone base case
Not every number belongs in the base case.
When the price is not the business
This company was not trading normally.
The share price was pinned by a pending takeover. That matters because a takeover price is not just a view on standalone cash flows. It can include control value, strategic value, scarcity value, and negotiation dynamics.
A DCF built from the company's own operating history should not automatically bend toward that price.
In fact, if the fundamentals are weak and the price is high, the model should be allowed to say:
I cannot get there from here.
That is what made this workbook valuable as a test.
It was not just a valuation exercise.
It was an anchoring experiment.
The business had just come through a trough year. Revenue was down 30% to $110.5m. EBIT margin had compressed to 5.6% from a much stronger historical level. Bookings had declined from 192m to 115m over four years. Yet the stock was sitting at $55.08/share, roughly 58x trough EBIT, because a control transaction was pending.
The share price walked into the room wearing a very expensive suit.
The model's job was not to be impressed.
Standalone fundamentals
- Revenue down 30% to $110.5m
- EBIT margin compressed to 5.6%
- Bookings down from 192m to 115m over four years
- Trough operating year
Market context
- Pending takeover
- $55.08/share
- Roughly 58x trough EBIT
- Control-price dynamics
The share price was not always evidence. Sometimes it was the thing the model had to be protected from.
This was not one valuation. It was three different kinds of value.
The most important part of this case is that the numbers should not collapse into one answer.
There were three different layers:
The three layers
| Layer | Number | What it represents | How to read it |
|---|---|---|---|
| Evidence floor | $15.03/share | What the workbook's own historical evidence supported | Standalone base case |
| Recovery thesis | $27.06–$36.66/share | What the company could be worth if you underwrite a recovery | Scenario / thesis case |
| Takeover price | $55.08/share | What the market price reflected during the transaction | Control price, not pure DCF evidence |
A weak model tries to make these numbers collapse into one answer.
A serious model keeps them separate.
The base case should show what the evidence supports.
The thesis case should show what the analyst believes could happen.
The market price should be compared, not smuggled into the assumptions.
Takeover price
What the deal context is pricing
$55.08
Recovery thesis
What could happen if the business recovers
$27.06–$36.66
Evidence floor
What the data supports
$15.03
The mistake is not having a thesis. The mistake is letting the thesis pretend to be the base case.
Claude produced two recovery theses. Both were reasonable. That was the problem.
Claude did not simply copy the market price.
That would be the lazy criticism, and it would be wrong.
Both Claude runs actually concluded that the market price was above standalone value. That is good.
But Claude's base case still carried a recovery thesis: revenue rebounding after a bad year, margins improving toward prior levels, and cash flows rising materially over the forecast period.
The problem was not that the thesis was absurd.
The problem was that the thesis could not hold still.
Same workbook. Same task. Two runs.
One answer: $36.66/share. Another answer: $27.06/share.
That is a 26% gap inside the same tool.
What changed between Claude runs?
| Choice | Claude Run 1 | Claude Run 2 | Why it matters |
|---|---|---|---|
| WACC | 8.45% | 10.3% | Run 2 added a 2.0% size / illiquidity premium |
| EBIT margin ramp | 7.0% → 12.0% | 7.0% → 11.5% | Same recovery thesis, different endpoint |
| Revenue path | 8 / 7 / 5 / 4 / 3% | 8 / 7 / 6 / 5 / 4% | Growth path changed |
| Capex | 1.5% of revenue | 2.0% of revenue | Reinvestment assumption moved |
| Working capital | 15% of revenue growth | 11.5% of revenue | Method family changed |
| Value/share | $36.66 | $27.06 | 26% apart |
The WACC change is the cleanest exhibit.
A size premium is not a ridiculous choice. For a small-cap company, it can be perfectly defensible.
That is exactly the problem.
A defensible choice appeared in one run and disappeared in another. The user did not choose a policy. The model chose a mood.
Two defensible analysts lived inside the same tool, and you got whichever one woke up.
Claude's output was not useless. In fact, this was one of its strongest performances in the series. It recognized the takeover distortion. It built a plausible recovery case. It produced a useful first-pass valuation. It even said the market price likely reflected a control situation rather than standalone cash flows.
That is good analyst instinct.
But a first-pass valuation is not a controlled model.
A recovery thesis needs to be labeled as a thesis.
It cannot quietly become the base case.
Sharpe AI kept the base case price-blind.
Sharpe AI's base case did not try to explain the market price.
That was the point.
It read the workbook, tested the company's own history, and built the base case from what the evidence could support. The result was much lower: $15.03/share.
This does not mean Sharpe AI "knew" the company was only worth $15.
It means the system refused to put a recovery story into the base case unless the workbook evidence supported it.
The recovery story belongs somewhere else: in a named scenario.
That is the product lesson.
Sharpe AI should not eliminate human judgment. It should force judgment to wear a name tag.
What each number was allowed to mean
| Number | Where it belongs | Why |
|---|---|---|
| $15.03 | Evidence-led base case | Built from what the workbook history could support |
| $27.06–$36.66 | Recovery scenario | Requires underwriting a rebound in revenue and margin |
| $55.08 | Market / bid comparison | Reflects a transaction price, not pure standalone cash-flow evidence |
This is why the output is useful to a finance team.
It does not merely say "low" or "high."
It separates evidence, thesis, and market price.
Judgment is allowed. Hidden judgment is not.
Anchoring is not stupidity. It is physics.
Anchoring does not mean the analyst is foolish.
It means the analyst sees a number and then builds around it.
Everyone in finance does this. That is why process matters.
If you know the company is trading at $55.08/share, and you also know your standalone DCF is coming out far below that, your brain starts asking helpful-sounding questions.
$55.08
The anchor: takeover-pinned market price
Maybe margins recover faster?
Maybe revenue rebounds from the trough?
Maybe the right WACC should be lower?
None of these questions is crazy. That is exactly why they are dangerous.
Anchoring does not feel like bias. It feels like insight.
The careless version of the claim would be: Claude copied the market price.
That is false.
Claude did not back-solve to $55.08/share. Both runs concluded the market was expensive relative to standalone value.
The real issue is subtler and more universal:
Claude wrote a recovery thesis while the price was already in the frame.
That is how human analysts behave too. The point is not that Claude is unusually biased. The point is that a finance workflow needs architecture that protects the base case from the anchor.
Sharpe AI's driver-fitting machinery did not read the market capitalization while building the operating forecast. The price came later, as a comparison.
That is not superior discipline.
It is architecture.
The model refused to compute what the data could not support.
This was one of the strongest parts of the Sharpe AI run.
The system first tried to build a fundamental terminal value. It did not simply jump to a convenient terminal growth assumption.
But the stable-state checks rejected the fundamental build.
The reinvestment rate was −256.9%. Terminal capex / D&A was 0.29. In plain English: the terminal year did not look like a sustainable steady-state business. So Sharpe AI refused to let that method quietly flow into the model.
Instead, it used the sanctioned fallback: a 2.0% terminal growth rate anchored inside the permitted macro / risk-free range. Crucially, it printed the failed diagnostics next to the number actually used.
That is the product.
Not: AI picked 2%.
But: AI tried the stronger method, rejected it, explained why, used a fallback, and left the evidence on the page.
Attempted method
Fundamental terminal build, tested first, not skipped
Stable-state check failed
Reinvestment rate −256.9% · terminal capex / D&A 0.29
Fallback used under policy
2.0% terminal growth, anchored inside the permitted macro / risk-free range
Reviewer visibility
Failed diagnostics printed on the sheet, next to the number actually used
Why terminal value needs a steady state
A terminal value assumes the company has reached a stable long-term pattern.
That means growth, reinvestment, depreciation, capex, and returns should make economic sense together.
If the model says depreciation is much higher than replacement capex forever, or reinvestment is negative in a way that does not represent a sustainable business, then the terminal value is not a steady-state valuation.
It is a spreadsheet pretending the future has settled down.
Claude's bull case saw something Sharpe's base case should not.
This case should not pretend Sharpe AI was perfect and Claude was useless.
That would be less credible.
Claude's recovery thesis was not worthless. In fact, Claude's bull case was useful because it captured the upside regime that a simple evidence-led base case should not automatically include.
If the business was at a trough, and if margins could normalize, and if the takeover price reflected strategic value, then a recovery scenario mattered.
Claude surfaced that intuition quickly.
That is useful.
But the question is where that intuition belongs.
It does not belong inside the base case without being labeled.
It belongs in a scenario.
Claude's useful contribution
- Identified the takeover distortion
- Created a recovery thesis
- Surfaced upside intuition quickly
- Produced a useful pitch-room sketch
Sharpe AI's useful contribution
- Kept the base case evidence-led
- Refused an unsupported terminal method
- Labelled weak assumptions
- Preserved reviewability
Claude was useful as a thesis generator. Sharpe AI was useful as the control system that decides where the thesis belongs.
The right answer was not one number. It was the separation of numbers.
If this were a live investment banking assignment, the right conclusion would not be: Sharpe says $15, Claude says $27–$37, market says $55. Pick one.
The right conclusion would be:
Standalone evidence supports roughly $15. A recovery thesis could support $27–$37. The takeover price at $55 likely reflects control value, strategic value, or deal dynamics beyond the standalone base case.
That is an actual finance memo.
And Sharpe AI makes that memo stronger because it gives you the floor.
Without a defensible floor, the recovery thesis floats.
Without a labeled recovery thesis, the base case gets contaminated.
Without separating the takeover price, the model starts explaining a number it should be challenging.
The floor is the product.
What the finance team should take away
| Question | Poor answer | Better answer |
|---|---|---|
| What is the company worth on evidence alone? | Force the model toward the market price | Start with the evidence-led base case |
| What if the company recovers? | Hide recovery inside base assumptions | Show a named recovery scenario |
| What does the bid mean? | Treat it as validation of the DCF | Treat it as a transaction price to compare against |
| What should the committee see? | One confident number | Evidence floor, thesis case, and market context |
This is where Sharpe AI stops being a spreadsheet assistant and starts becoming a decision-support layer.
The Evidence vs. Opinion trilogy
The three cases now tell one story.
What each case proved
| Case | Situation | What happened | What it proved |
|---|---|---|---|
| I: The Captive Finance Trap | Auto OEM with finance arm | Claude gave $170.88 / $185.48; Sharpe gave $125.68 | Hard structures break when bridge logic is loose |
| II: When the Numbers Agree | Cleaner bioethanol company | Claude gave $23.41; Sharpe gave $25.33 | When answers agree, the evidence underneath matters |
| III: The Price Got in the Way | Takeover-pinned small-cap | Claude gave $36.66 / $27.06; Sharpe gave $15.03; market was $55.08 | The model must separate evidence, thesis, and market price |
Sharpe AI is not trying to be the most confident model in the room.
It is trying to make the model's logic inspectable.
Sometimes that means finding a structural bridge issue.
Sometimes it means proving the evidence underneath a similar answer.
And sometimes it means telling the model:
No, you do not get to chase the share price.
That is exactly what financial model control should do.
Final takeaway
The most dangerous model is not the one that is obviously broken.
It is the one that makes a reasonable story sound like evidence.
This case showed why Sharpe AI needs to exist.
In high-stakes finance, a model should separate what the evidence supports, what the analyst believes, and what the market is currently pricing.
Those are not the same thing.
When they get mixed together, the output becomes persuasive but fragile.
When they are separated, the model becomes useful.
The price got in the way. Sharpe AI moved it back where it belonged: outside the base case.
Want to see what Sharpe AI would do with your model?
Bring a DCF, a messy workbook, a first draft from AI, or a model your team needs to defend.
For product demonstration only. Not investment advice.