The guided interview is optional, but it's the single highest-leverage step in the whole intake — because unlike your description, it's built to keep asking about specifically whatever is still thin. Rushing it defeats the entire point.
Start a project →The interview runs up to three rounds. Round one is generic by necessity — there's nothing to react to yet. But every round after that is generated specifically from what you answered in the round before, digging into whichever half (business goals or concrete functionality) is still thinner. The model itself judges when there's genuinely enough real, concrete depth to build from — and it's explicitly told that vague, generic, or one-word answers mean it isn't ready yet, no matter how many questions have technically been answered.
That means a rushed round one doesn't just produce a slightly worse round one — it produces a worse round two as well, since round two is built on top of it. The payoff of taking round one seriously compounds.
Every multiple-choice option is deliberately written to teach you something is possible just by reading it — the instruction behind these questions explicitly rejects vague choices like "Yes" or "Somewhat" in favor of concrete ones like "Let people book and pay at 2am" or "Auto-remind past customers every season." That means the options themselves are doing real work: reading all of them, not just picking the first one that's roughly in the right direction, is how you find out what's actually on the table for a project like yours.
Clicking fast isn't wrong, exactly — but it turns a genuinely useful moment (discovering a capability you didn't know to ask for) into a formality.
Every question includes a free-text "Something else" option specifically because the offered choices aren't meant to be exhaustive. If none of them actually describe your situation, picking the closest one anyway isn't a shortcut — it's telling the AI something that isn't quite true about your business, and because later rounds and the final draft both build directly on your literal answers, a close-but-wrong answer becomes a wrong assumption baked into the plan, not a rounding error that gets corrected later.
One extra typed sentence in "Something else" costs you a few seconds. A plausible-but-wrong multiple-choice answer costs you a plan built on the wrong premise.
You can stop the interview at any point, even mid-round, and it will build a real draft from whatever you've answered so far — it's designed to never leave you stuck. But understand what that trades away: readyToBuild is always false on round one by design, meaning the AI itself has judged, at that point, that there's more real depth worth digging into. Stopping there isn't broken, it's just choosing speed over the plan the later rounds were built to produce. If you're in a hurry, that's a legitimate choice — just make it knowingly, not by accident.
Looking for what a specific screen or button does instead? Check the Help Center.