← HUBCOMMUNITY/NEED PLANNING
13 · PLANNING · TURNS IDEAS INTO BUILDS

Vague AI idea?
Five questions and you're shipping.

Most "I want to build something with AI" stops at the idea. This intake forces you through 5 questions that scope, sequence, and time-box the work — output is a specific build, the right weekly guide, and a ship-by date. Takes 6 minutes.

INTAKE TOOL LIVE · 2 OF 5 QUESTIONS DRAFTED IN DETAILFUNCTIONAL
the intake · 5 questions

A sample run, end-to-end.

This is what filling out the intake actually looks like — questions, sample answers, the routing output at the end. The live form prefills your selections to skip the second time around.

~/need-planning · intake-form
SESSION 09:14 ET
Q 01 / 5 · DETAILED

What outcome do you need by Friday?

Not "learn AI." Not "build an agent." The actual change in your day or your business. "I'd like 2 hours back from research" or "I want client onboarding to run without me touching it."

I want 2 hours back per day on competitive research — right now I check 8 sources manually.
Q 02 / 5 · DETAILED

What's blocking you today?

Pick all that apply. The intake routes around whatever blockers you flag.

DON'T KNOW WHICH AI MODEL DON'T KNOW HOW TO DEPLOY NO BUDGET FOR PAID API CAN'T CODE TIME — < 1 HR/DAY NONE — JUST STARTED
Q 03 / 5 · OUTLINED

What inputs do you already have?

URLs, account access, existing prompts, source documents — anything that means we're not starting from zero.

Q 04 / 5 · OUTLINED

Which skills + tools are you willing to use?

Constrains the recommendation. If you won't write code, the intake routes to a no-code variant. If you're a Claude Code user, it routes to that.

Q 05 / 5 · OUTLINED

What ship date forces a scope cut?

No date = no shipping. Pick a real date. The intake cuts scope to fit.

ROUTING OUTPUT — BASED ON YOUR ANSWERS
RECOMMENDED BUILD
Week 21 · Automate competitive research with Claude + Vercel cron — matches your outcome, fits your time budget
SUPPORTING SKILL
Claude Code MCP servers — addresses your "don't know which model" blocker
ESTIMATED BUILD TIME
28 min · fits within 1 hr/day cap
SHIP-BY
Friday 5pm ET · 3 days from now
OPEN THE WEEK 21 GUIDE →

why this works

The intake replaces three weeks of wandering.

Most people who say "I want to build with AI" spend 3 weeks reading content before deciding what to build. The intake compresses that to 6 minutes.

PROBLEM

Idea inflation

You start with "automate research." Then "build a research agent." Then "build a research platform with auth and a UI." By week 2 you've shipped nothing.

INTERVENTION

Force a scope cut

Q5 demands a real ship date. The intake auto-trims your scope to what fits. The platform version goes on the "next quarter" list.

OUTPUT

A specific build, picked + scheduled

You leave with: a weekly guide link, an estimated build time, a ship-by date, and the supporting skill cheatsheet. Now you just execute.