www.ycombinator.com/apply/dropbox

Separate: Why did we choose this idea? What makes us unusually equipped to solve it? What do we know that others miss? Use personal experience, domain expertise, customer observation, distribution access or a technical breakthrough. Reject vague claims of passion or fascination with a hot sector.

A useful structure: "Most people assume X. We observed Y, supported by Z. That changes our approach: we do A rather than B." Only use this when truthful; not every startup needs an artificially contrarian insight. Show how insight affects product design, buying process or go-to-market. For "Why now?", identify a causal shift such as technical cost/performance, regulation, distribution, buyer behavior or economics. "AI is growing fast" alone is not sufficient.

FICTIONAL EXAMPLE: "The bottleneck isn't extracting invoice fields; it is reconciling inconsistent purchase orders, so we focus on matching before reporting." Verify before asserting it for a real company.

JUST-IN-TIME INPUT: Here, ask about the founders' relevant experiences, surprising observations and product decisions. Don't require a full founder biography at intake.

List direct competitors, indirect alternatives, manual processes, internal tools and the option to do nothing. Include credible future entrants. For each: users, strengths, weaknesses for your specific initial customer, evidence and switching costs. Never say "no competitors" when users currently accomplish the job somehow. Do not caricature large competitors or rely on unsupported claims that the product is simpler or faster.

Draft the competitive answer: "Customers currently use A and B. These work for X, but struggle with Y in our target workflow. We use Z approach because [evidence or causal explanation]." Define a specific initial wedge and explain how it could survive incumbent responses. Identify what observation would disprove your differentiation. Review the Dropbox original application for an historical example of a clear abstraction-level difference; do not copy its claims or treat its 2007 technology landscape as current.

JUST-IN-TIME INPUT: Ask what users currently use instead and which alternatives have actually been tested. Research additional relevant competitors as needed; if evidence is absent, mark comparisons as hypotheses.