Technical red flags in pitch decks almost never show up on slides. They show up in pauses, in evasive answers, and in who leans forward when the talk reaches production. Investors who learn to read seven signals walk into the round holding information the deck leaves out.
Where is the technical co-founder?
The product is software and none of the founders writes software. Outsourced development means the core asset walks out the door when the contract ends. Ask who decides architecture today and who remains after the Series A. Decks without a concrete answer trade at a discount.
Is "we'll rebuild it properly after funding" a plan?
A rebuild mentioned in passing hides the most expensive problem on the list: rebuilding during growth kills startups more often than debt does. Swapping foundations while scaling 3x per year breaks systems that serve 10k users. Treat the rebuild promise as a standing yellow flag.
Does the demo run in production?
A demo on localhost with seeded data exposes an earlier stage than claimed. Ask about production readiness and watch the reaction: deflection weighs more than slide metrics. A founder with a live system quotes URL, uptime, and provider on the spot.
How many people know the system?
One engineer who knows everything sets bus factor at one, and bus factor one caps valuation: the asset depends on one person staying motivated. Ask how many engineers shipped a deploy last week. A single name answers the round.
Do security and LGPD get concrete answers?
"We take it seriously" answers nothing. Regulated markets demand specifics on data residency, audit trails, and breach response. A healthtech or fintech startup without that vocabulary transfers regulatory risk straight into the investor's cap table.
Do AI claims have evaluation methodology?
AI claims need eval methodology. Ask how output quality is measured and wait for the silence. Mature teams produce the test suite, pass rates, and regression history without asking for prep time. AI products without evals are luck demos.
Which questions make the truth surface?
- Average deploys per week over the last quarter?
- Latest production incident, and how long did resolution take?
- Which specific people does the system depend on?
- Where does cost per active user trend?
Is a technical session before the term sheet worth it?
A two-hour technical session with the founding engineers before the term sheet costs two hours. A write-off afterward costs the entire round. A confident founder books the session the same day; reluctance to book informs the decision too. We sit on the investor side of these sessions every month, and the pattern holds: secure teams finish inside an hour, fragile teams reschedule twice.
