4 min read ·
Build a Why Now Slide Around a Real Change
A practical why now slide template for technical founders, with evidence standards, an applied-AI example, and tests for a credible timing argument.

A why now slide explains what changed to make your startup’s solution feasible, economical, or worth buying today. It connects an external shift to a specific customer opportunity—not merely to a growing market.
Sequoia’s business-plan guide frames the question directly: “why hasn’t your solution been built before now?” Your slide should answer that question without pretending the customer’s problem is new.
The useful distinction is:
- Problem: Why does the customer need a better solution?
- Why now: What changed so that a better solution can work or sell?
- Why us: What gives this team or product an advantage?
“AI is growing” answers none of these precisely. “A constrained model now meets our accuracy and cost thresholds for this workflow” gives the reader something to evaluate.
Build one causal chain
Use this structure:
Previous blocker → dated change → customer consequence → evidence
Start with the blocker. Was the required computation too expensive? Were integrations unavailable? Did buyers lack a budget owner? Was the workflow too infrequent to justify switching?
Then identify what removed—or materially reduced—that blocker.
| Possible trigger | Mechanism to explain | Evidence to bring |
|---|---|---|
| Technical capability | A previously unreliable task now meets a defined acceptance threshold | Comparable evaluations on representative customer work |
| Cost reduction | Serving the workflow now fits the customer’s willingness to pay | Before-and-after cost per successful task, including review and retries |
| Workflow or distribution change | A new integration or purchasing route reduces deployment friction | Availability date, eligibility constraints, and observed deployment or procurement time |
| Buyer urgency | A new obligation or operating change makes the old workaround inadequate | Applicable requirement or customer operating data, plus evidence of budget and action |
Choose the strongest trigger. Add a second only if the opportunity depends on both. A slide listing five unrelated trends makes the causal explanation harder to inspect.
A change can make something possible without making it commercially attractive. An API launch proves availability; it does not prove that customers will deploy your product. A regulatory deadline can establish urgency; it does not establish a budget for your particular solution.
A copy-ready slide structure
Write a headline that states the consequence, not the category:
[Specific change] now makes [customer workflow] viable for [target buyer].
Below it, use three compact blocks:
- Before: “[Blocker] prevented [buyer] from achieving [outcome].”
- Changed: “Since [date], [capability, cost, access, or obligation] has changed from [baseline] to [current condition].”
- Now: “This enables [specific action or economic result], supported by [evaluation, pilot, purchase, or deployment evidence].”
Use a chart only when it shows the threshold that matters. Label dates, units, workload, and source. An impressive curve without a connection to the buyer’s decision belongs in neither the headline nor the argument.
Keep detailed methodology in the appendix, but leave material limits visible: “human approval still required” or “tested on English-language tickets only.” Those limits define the opportunity you are actually claiming.
For placement, put timing after the solution when it explains feasibility, or after the problem when it explains urgency. The broader Sequoia pitch deck outline can help organize the surrounding slides.
Worked example: an applied-AI workflow
There is a real macro-level timing signal here: Stanford’s 2025 AI Index reports that inference cost for a system performing at GPT-3.5 level fell more than 280-fold between November 2022 and October 2024. That is a dated historical finding, not a forecast or a measurement of your product’s costs. Source: Stanford HAI.
A weak slide would stop at “AI inference is cheaper.” A stronger slide would connect the change to a measured workflow.
Illustrative slide copy—not actual company results:
Lower inference costs put support-ticket classification within our delivery-cost target.
Before: Our prior pipeline cost $2.40 per accepted classification, above a proposed $0.90 selling price.
Changed: A newly available, lower-cost model meets the same acceptance criteria on our held-out customer dataset. Using it brings the pipeline cost to $0.45 per accepted classification, including hosting, retries, and human review.
Now: The workflow clears our delivery-cost threshold. Paid pilots must still establish willingness to pay and renewal behavior.
Replace the illustrative figures with dated measurements from your own workload. The external research establishes context. The product evaluation establishes the claimed threshold crossing. Neither substitutes for the other.
The broader cost decline is also available to competitors. Explain proprietary workflow knowledge, integrations, or another durable advantage elsewhere in the deck; do not label the industry-wide change your moat.
Pressure-test before sending
Ask four questions:
- Why not earlier? Name a real blocker, not simply your founding date.
- What changed for this buyer? Connect the trigger to their workflow, budget, or deployment decision.
- What would disprove the timing thesis? Examples include review costs erasing the savings or customers continuing to defer purchases.
- Does the argument justify starting now—or merely predict a future market? If it depends on capabilities or approvals that do not yet exist, present them as dependencies, not facts.
If there is no sharp external trigger, say so. An enduring problem plus a distinct technical insight is more credible than invented urgency. Keep the timing explanation brief, or integrate it into the solution slide rather than forcing a standalone one.