Decide Whether to Build, Change, or Stop

Made for Founders

Decide Whether to Build, Change, or Stop

Also useful for: people in Founders

90 min Advanced Business & Entrepreneurship Grow a Business Need to Make a Decision

Pressure-test the evidence behind a product direction and choose the next move without letting enthusiasm, sunk costs, or isolated feedback drive the call.

Create a free account to save your progress and use this Playbook.

Use this when

You need to decide whether to keep building, change the offer or market, stop the work, or gather one more piece of evidence first.

You'll need

  • Current offer
  • Decision window
  • Customer evidence
  • Payment signals
  • Repeated objections
  • Acquisition friction
  • Founder constraints
  • Decision options

You'll get

  • Customer evidence sorted by signal strength
  • Repeated objections classified by likely cause
  • Acquisition friction separated from demand risk
  • Founder constraints applied to every realistic option
  • One next move selected with a confidence level
  • A time-boxed action plan with pass and fail thresholds

By the end of this playbook

You will have:

  • Customer evidence sorted by signal strength
  • Repeated objections classified by likely cause
  • Acquisition friction separated from demand risk
  • Founder constraints applied to every realistic option
  • One next move selected with a confidence level
  • A time-boxed action plan with pass and fail thresholds

Sample

This is sample data, not your prompt. Pro unlocks this higher-stakes Playbook. On Free Playbooks you can still copy the assembled prompt into any AI.

Sample input

Current offer: A reporting tool for small marketing agencies priced at a planned $149 per month.
Decision: Choose within three weeks whether to build integrations, change the offer, or stop.
Evidence: 18 interviews, five examples of current reports, three prototype trials, and two repeat uses.
Payment signals: One $300 manual reporting purchase and no software subscriptions.
Objections: White-label output, security concerns, and resistance to connecting accounts.
Acquisition: Nine replies from 110 cold emails; six calls from warm introductions.
Constraints: 15 hours per week, eight weeks of runway, limited security expertise, and a need for revenue within 60 days.
Options: Build self-serve software, offer concierge reporting, narrow to white-label reports, or stop.

Sample assembled prompt

Recommendation: Change from self-serve software to...
Confidence: Medium.
Decisive evidence: A real payment exists...
Repeat prototype use supports the problem,...
Main risk: The manual purchase may...
14-day test: Offer a $400 white-label...
Pass with three paid pilots.
Fail with fewer than two paid...
Build restriction: Don't add integrations...

Part of a collection

Find What People Will Pay For

10 playbooks

Validate a business idea with customer evidence instead of guesswork. Move from discovery and price testing to early sales, follow-up, and a clear build, change, or stop decision.

Next: Customer Discovery Bias Repair Kit

View collection

Best next playbooks

Suggest an idea

What should we add?

Loading the suggestion form…