Product skill · Strategy

Strategy Review

Share your plan or strategy and Seba reviews it founder-mode — challenges the premises, tests whether the scope is right, and surfaces the 10-star version — then returns a critique with a clear recommendation. Billed per run.

9:41
Seba
bot · online
PremisesScope10-star productReversibility
Review my plan to add a dashboard before we know users want it9:41
Review done. The founder-mode read:
Core premise unverified — no signal users want a dashboard
Scope is wide where a one-screen wedge would prove it
Decision is a two-way door — ship small, learn fast
strategy_review.md
Critique · scope + premises · ranked
Strategy Review skill · 25 credits
9:41
Message

A critique that rethinks the plan, not just checks it

Challenges the premises

Seba names the assumptions your plan takes for granted — “users want this,” “we need to raise” — and flags which ones are verified and which are guesses.

Right-sizes the scope

Expand to the 10-star product, hold the line, or cut to the essential wedge — Seba picks a posture and tells you what to add, keep or strip, and why.

Reversibility lens

Every call gets sorted by one-way vs two-way door. Most things are reversible — Seba tells you where to move fast and where to slow down.

A recommendation, not a shrug

Seba takes a position on every issue with the tradeoff spelled out, so you leave with a decision to make, not a list of maybes.

What the review pressure-tests

The cognitive moves a 10x founder makes on a plan, applied in one pass.

  • Premise challenge — which assumptions are verified and which are wishful
  • Scope posture — expand to 10-star, hold, or reduce to the essential
  • The 10-star version — what would make this dramatically better for 2x the effort
  • Reversibility — one-way vs two-way doors, where to move fast
  • Focus as subtraction — what to NOT do so the core gets sharper
  • Proxy skepticism — are the metrics still serving users or gone self-referential
  • Temporal depth — does this solve today but create next quarter’s problem
  • Narrative coherence — is the “why” legible enough to align the team
  • Wedge vs platform — the smallest version that earns the right to expand

From a plan to a founder-mode critique in three steps

01

Open Seba in Telegram

One tap into @meetseba_bot. No install, no signup forms.

02

Share the plan

Paste your strategy, roadmap or one-pager. Tell Seba whether you want it bigger, held, or trimmed.

03

Get the critique

Seba returns a founder-mode review — premises challenged, scope tested, the 10-star version surfaced — each issue with a recommendation and the exact credit cost.

When to run a strategy review

Catch the strategic mistake before it costs a quarter.

  • +Before committing a roadmap or quarterly plan
  • +Deciding whether the scope is too big or too small
  • +Questioning whether the idea is ambitious enough
  • +Pitching a plan and want the holes found first
  • +Choosing between expanding and cutting a feature set
  • +Sanity-checking a premise everyone’s assuming is true

Frequently asked questions

What does the strategy review produce?+

A founder-mode critique — premises challenged, scope tested, the 10-star version surfaced — with an opinionated recommendation on each issue. It’s a document you act on, not a rubber stamp.

Does Seba just tell me to do more?+

No. It picks the right posture for what you need — expand, hold, or reduce — and commits to it. Sometimes the recommendation is to strip the plan to its essential wedge.

Does Seba change my plan for me?+

No. Seba returns a critique you decide on. You stay in control of every scope change; the review gives you the tradeoffs, not the keys.

What should I share?+

Whatever captures the plan — a roadmap, a strategy doc, a one-pager, even a few paragraphs in chat. More context gives a sharper review.

How much does a review cost?+

You spend credits per run, and Seba shows the exact cost before it starts. Start free with welcome credits; credits never expire.

How is this different from an architecture review?+

Strategy Review is founder-mode — premises, scope, ambition. Architecture Review is eng-manager-mode — data flow, edge cases, failure modes. Run strategy first, then architecture.

Pressure-test your strategy in one message

Share a plan and get a founder-mode critique with a clear recommendation back. Pay only for the run.

No install · no signup forms