A feasibility report that only lists features is a brochure. We look for four red flags: no named owner for architecture decisions, milestones with no dependency map, “we will hire later” as the only capacity plan, and integrations treated as a footnote.
Risk lines, not footnotes
Each flag becomes a risk line with a mitigation or a kill criterion. If the stack cannot support the GTM timeline, we say so in the same pack as the marketing study — not in a separate engineering email that never reaches the founder.
Reports you can execute against
Technical ventures deserve a report they can execute against. Pretty architecture diagrams without delivery constraints are how burn gets spent on the wrong sprint.