Prudence Report · No. 04 167
Illustrative exampleSubject
Halcyon Robotics
Growth-stage warehouse automation · Columbus, OH · Founded 2019
Prepared for a candidate weighing a VP offer
“Should I take the VP of Engineering offer?”
Verdict
Take the role; value the equity at half the story you were told.
Updated 2026·05·30 · 13 sources cited
Capital
↑
66
/ 100
Team
↑
79
/ 100
Market
↑
81
/ 100
Risk
→
52
/ 100
Strengths
- Deployed sites doubled in twelve months while installation cost per site fell 31%.
- Three-year contracted backlog covers the burn through profitability under the base case.
- The engineering org you'd inherit has shipped on schedule for six consecutive quarters — rare at this stage.
Risks
- The preference stack from the 2024 down-round means common needs a very large exit to clear your strike meaningfully.
- The CTO you'd report to has had three VPs of Engineering in four years; understand why before signing.
- Hardware margin is still negative at current volumes; the model depends on the next platform landing on time.
The dissent
One analyst weights the reporting-line churn heavier than the market pull: three predecessors in four years is a pattern about the seat, not about the people who sat in it. They would negotiate scope in writing or decline.
Open questions
- Q·1Ask for the 409A and the full preference stack — the offer letter's ownership percentage is not the number that matters.
- Q·2Why did the last VP leave, in their words? Request the conversation directly.
- Q·3How much of the contracted backlog is cancellable for convenience?
Audio briefing · 10:48 — included with the Prudence Report.
↳ Continues — 29 pages · 7 exhibitsVide antequam vadas