PromptBase
Upgrade
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
(claude-4-6-sonnet)
Token size
722
Example input
[STARTUP_STAGE]: Post-seed B2B SaaS, building core product, 8 months into 12-month runway [SPEED_DECISION]: Hired 3 engineers in 6 weeks before product-market fit was confirmed [CURRENT_SYMPTOMS]: Missing sprint deadlines, team morale dropping, board asking for traction metrics we cannot show yet [ORIGINAL_TIMELINE]: Planned to launch in 8 months, currently at month 7 with 40% of features complete
Example output
TRAP DETECTION What you are describing is not a execution problem. It is a direction problem wearing the costume of an execution problem. You hired three engineers in six weeks because the board wanted to see headcount grow, and growth looked like progress. That is sunk cost momentum at work. You cannot stop now because stopping feels like admitting the last four months were wasted. So you keep going in the same direction, faster. The symptom is missed deadlines. The disease is that the direction was never confirmed before the spending started. HOW THE TRAP WORKS HERE When you made the decision to hire before product-market fit was confirmed, your brain was doing something specific. It was treating the hiring decision as proof that the business was real. Spending money on salaries made the vision feel more solid. But the planning fallacy was already embedded in your original eight-month timeline. Eight months assumed everything would work the first time — the product, the market response, the team coordination. None of those assumptions were tested before the timeline was set. So the timeline was not a plan. It was an optimistic wish with a deadline attached. CORRECTED EXECUTION PLAN Stop treating headcount as a progress signal. Your three engineers are working on features that have not been validated with paying customers yet. Before the next sprint begins, identify one feature that a customer has agreed to pay for — not just said they like. Pause the two features with the least direct customer input and redirect one engineer to talk directly to ten prospects this week. Your timeline does not need to be extended. It needs to be replaced with a milestone structure based on customer behavior, not internal activity. ONE THING TOMORROW Tomorrow morning at 9am, before opening your laptop, write the name of one customer who has told you they would pay for what you are building. If you cannot write that name in thirty seconds, that is the only piece of information you need right now. Take that result into your first meeting of the day.
🌀 Claude

Speed Trap Detector For Founders

Add to Cart
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
CLAUDE-4-6-SONNET
Tested icon
Guide icon
4 examples icon
Free credits icon
You launched fast, hired fast, spent fast. Now you are burning cash and missing every deadline. Most founders fail at execution not because they moved too slowly — but because they confused speed with direction. This prompt detects Speed Trap patterns in your startup and gives you a corrected execution plan for tomorrow. Built on behavioral economics and Harvard Business School startup failure research. For founders who want to stop running fast in the wrong direction.
...more
Added 6 days ago
Report
Browse Marketplace