# The one question to ask before you open Cursor

*Mindset · 4 min read · [Read on intentdocs.com](https://www.intentdocs.com/blog/one-question-before-cursor)*

> Most builders ask: how long will this take? The right question is: will someone pay for this? They're very different bars.

The question most builders ask before starting a new project is: *how long will this take?*

It's the wrong question. The right question is: *will someone pay for this?*

Not "would someone use this" — that bar is too low. Not "is this a good idea" — that's too abstract. Will someone reach for their card? Will they switch from whatever they're doing now? Will they pay, repeatedly, for this specific thing?

Most builders don't ask it explicitly. They feel it — a vague confidence that the idea has merit — and then start building. The feeling is real. The confidence is usually unfounded.

## Why it's easy to skip

Validation used to be hard. You had to talk to users, build prototypes, run discovery sprints. By the time you had signal, you'd already spent weeks on something that might pivot.

Now that building is fast, the temptation is to use building itself as the validation. Ship it, see what sticks. The logic is: I can build an MVP in a weekend, so why not just try it?

The problem is that a weekend still costs something — your time, your attention, the opportunity to have built something else. And when the MVP doesn't convert, you rarely know why. Was the market too small? The positioning wrong? The timing off? The feature set incomplete? The signal from a failed launch is ambiguous at best.

## The faster validation loop

There's a faster approach: describe the problem before you write code, and publish it to see who responds.

Not a landing page. Not a fake door. Just a clear articulation of the problem, who has it, and what solving it would be worth — and a simple way for people to signal "I'd pay for this."

> If strangers back the idea, you have demand signal before a single line of code. If nobody backs it, you've learned something important in 10 minutes instead of two weekends.

## What to do with the answer

**If you get signal:** build it. Now you're building with confidence rather than hope. The spec you used to validate becomes the context you hand to Claude Code.

**If you don't:** investigate before committing. Is the problem not real? Is the audience wrong? Is the timing off? A no-signal result isn't a failure — it's the cheapest lesson you can learn.

The question isn't whether your idea is good. Most ideas are good enough to build. The question is whether it's good enough to pay for. That's a different bar, and finding out early is worth everything.

Open Cursor after you have the answer. Not before.

---

*IntentDocs is a spec-driven development platform: an AI interview turns your idea into a structured spec — story map, data model, build order — and your coding agent builds from it over MCP, with an audit trail of built versus planned. 7-day free trial at [intentdocs.com](https://www.intentdocs.com).*