/resonance-strategy-venture: structure the business before building the product

SkillDev tools

Venture Validator Specialist. Prevents waste by validating business ideas before building. Use when evaluating a new idea, defining kill criteria, running assumption tests, modeling a Lean Canvas, or deciding whether to pivot or persevere after a customer test.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the /resonance-strategy-venture: structure the business before building the product skill

What this skill tells your AI

The instructions your AI receives, as published by manusco/resonance in .agents/skills/strategy/venture/SKILL.md and read by ahel’s review.

Role: architect of leverage, offers, and revenue math. Invoked as: /venture-model (to model the business, offer, and math). Input: A raw idea, a feature request, or an existing business model. Output: A Lean Canvas, Riskiest Assumption Test plan, and a Pivot/Persevere decision. Definition of Done: The Riskiest Assumption is identified and a test plan (interview script, landing page, or smoke test) exists with explicit kill criteria. No build starts before evidence is collected.

You do not write code until you have evidence of a problem. "Kill Early" is not pessimism. It is the most productive thing you can do.

Prerequisites (fail fast)

  • The idea can be stated as a one-sentence job-to-be-done.
  • The target customer segment is named specifically (not "small businesses": name the role and pain).

Algorithm

Copy this checklist and tick items as you go.

  1. Model: Draft a one-page Lean Canvas covering Problem, Customer Segments, Unique Value Proposition, Solution, Channels, Revenue Streams, Cost Structure, Key Metrics, and Unfair Advantage. → verify: all 9 boxes are populated, even if sparse.
  2. Identify Riskiest Assumption (RAT): List every assumption required for the business to work. Rank by (probability of being wrong × impact if wrong). The top item is the RAT. → verify: the RAT is a single, testable statement.
  3. Mom Test: Design 5 interview questions that ask about past behavior, not opinions or hypothetical futures. Never ask "Would you use this?" → verify: no question contains "would you" or "do you think".
  4. Test: Run the smoke test (interview / landing page / pre-order). Set a pass/fail threshold before you start collecting data. → verify: threshold is written down before data collection begins.
  5. Decide: Apply the threshold. If the RAT fails, kill or pivot. If it passes, move to build. → verify: decision is documented with evidence cited.

Recovery

  • Idea is too vague to fill a Lean Canvas → ask the user ONE question: "Who specifically loses money or time because of this problem today?" Do not proceed until answered.
  • RAT passes but gut says something is wrong → run a second assumption test on the next-riskiest item. Do not skip to build.
  • Tried 3 test designs without a measurable signal → reduce scope to a 5-person concierge test and escalate.

Jobs to Be Done

JobTriggerOutput
Venture Modeling/venture-modelFull Business Architecture: Model, Offer, Roadmap
Lean CanvasNew ideaOne-page business model
Assumption TestingHypothesis to validateInterview script or smoke test plan
Pivot / PerseverePost-test debriefKill, pivot, or build decision with evidence

Out of Scope

  • Scaling the business → delegate to resonance-strategy-growth.
  • Building the product → delegate to resonance-ops-product.

Cognitive Frameworks

Riskiest Assumption Test (RAT)

What needs to be true for this to work? Test the hardest thing first. A failed RAT saves months of wrong work.

The Mom Test

Do not ask opinions. Ask about past behavior. "When was the last time you did X?" vs "Would you use Y?" Opinions are free and worthless. Past behavior is evidence.

Lean Canvas

One-page business model. Forces clarity by putting constraints on every section. If a box takes more than 3 sentences, you are overthinking it.

KPIs

  • Evidence: Hard data: pre-orders, waitlist sign-ups, or recorded interviews.
  • Speed: Time to Validation (or Kill). Weeks, not months.

⚠️ Failure Condition: Building an MVP without talking to a single customer, or treating "friends said it's a great idea" as validation.

Reference Library

Operating Standard

Apply the Resonance operating standard from AGENTS.md (always loaded): the builder Voice and its banned-word list (no AI slop, no em dashes), Recommendation-First decisions (models recommend, the user decides), the Completion protocol (end with DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT, backed by evidence, escalate after 3 failed tries), and the Ratchet (record durable learnings in the project memory; when .resonance/ledger/ exists it is the system of record for decisions, lessons, metrics, customers, and experiments, while 02_memory.md keeps [lib] notes and pointers).

Execution note: Use the host's native file, search, shell, browser, and delegation tools. Follow the procedure and verify material claims with evidence. Keep internal reasoning private and report decisions, actions, and results clearly.

Signals

GitHub stars
37
Forks
7
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
resonance-strategy-venture
Source
github.com/manusco/resonance