Product Brainstorm
Tell Seba what you want to build and it runs a YC-style office-hours brainstorm — six forcing questions that separate real demand from wishful thinking — then hands back a structured design doc. Billed per run.
A brainstorm that pressure-tests the idea, not flatters it
Demand reality, not vibes
Seba pushes past “people think it’s interesting” to the evidence that matters — who would be upset if it vanished tomorrow, and would anyone pay this week.
Find the narrowest wedge
Instead of the full platform vision, Seba names the smallest version someone pays real money for now — the sharp entry point you expand from.
Names the failure pattern
Solution in search of a problem, hypothetical users, waiting for perfect — Seba calls the common trap by name so you fix it before you build.
Ends with one assignment
Not a 30-page strategy. One concrete action to take next — the experiment or conversation that tells you whether to keep going.
What the brainstorm pushes on
The same forcing questions a YC partner asks in office hours.
- Demand reality — the strongest evidence someone genuinely wants this, not just signed up
- Status quo — what your user does today to cope, and what that workaround costs them
- Desperate specificity — the actual human who needs it, by name, role and consequence
- Narrowest wedge — the smallest version someone pays for this week
- Watch, don’t demo — where to sit behind a real user and learn what they actually do
- Future-fit — your thesis on how this market shifts to make the product more essential
- Hidden assumptions — what the framing takes for granted and whether it’s verified
- Specificity over category — turning “marketing teams” into a person you can email
- One assignment — the single next action that produces real signal
From a one-line idea to a design doc in three steps
Open Seba in Telegram
One tap into @meetseba_bot. No install, no signup forms.
Describe the idea
“I want to build X for Y.” Seba asks the forcing questions one at a time and pushes for specifics.
Get the design doc
Seba returns a structured doc — demand read, wedge, the real user, failure patterns named, and one concrete assignment — with the exact credit cost.
When to run a product brainstorm
Pressure-test the thinking before you write a line of code.
- +You have an idea and want to know if it’s worth building
- +Deciding between three directions and need a sharper read
- +Sizing up a side project, hackathon or weekend build
- +Validating an internal project before pitching your sponsor
- +Reframing a vague “platform” into a shippable wedge
- +Talking yourself out of a solution in search of a problem
Frequently asked questions
What does the brainstorm actually produce?+
A structured design doc — not code. It captures the demand read, the narrowest wedge, the real user, the failure pattern you’re at risk of, and one concrete next action.
Will it just tell me my idea is great?+
No. The whole point is rigor over encouragement. Seba takes a position on every answer and pushes for specifics — comfort usually means you haven’t gone deep enough.
Does Seba build the product?+
No. This skill produces thinking, not implementation. You leave with a sharper idea and an assignment — building comes after, on your terms.
What do I need to bring?+
Just a description of what you want to build and who it’s for. The more honestly you answer the forcing questions, the sharper the doc comes back.
How much does a brainstorm cost?+
You spend credits per run, and Seba shows the exact cost before it starts. Start free with welcome credits; credits never expire.
Is this for startups only?+
No. It adapts — startup ideas get the hard demand questions; side projects, hackathons and learning builds get an enthusiastic design-thinking collaborator.
Pressure-test your idea in one message
Describe what you want to build and get a YC-style brainstorm and design doc back. Pay only for the run.
No install · no signup forms