ventureos 1.0.0

package/workflows/4-define-solution/wedge-design/step-3-prototype.md

@@ -0,0 +1,78 @@
+# Step 3: Prototype
+<!-- Phase 4, Step 3 — Weeks 5-6 -->
+<!-- Agent: Product Strategist -->
+
+## Objective
+Build the earliest testable version of the wedge product. Progress from low-fidelity (wireframe) to a working prototype using vibe coding (AI-assisted rapid build). Use the prototype for solution testing in Step 4.
+
+---
+
+## 3.1 Choose Prototype Fidelity
+
+Based on wedge complexity and time available:
+
+| Fidelity | What it is | Best for | Time |
+|---------|-----------|---------|------|
+| **Lo-fi** | Sketches / wireframes / Figma mockup | Early concept testing | 1-2 days |
+| **Clickable mockup** | Figma/Framer prototype | Flow testing | 2-5 days |
+| **Vibe-coded prototype** | Working app (AI-assisted) | Usability + desirability testing | 3-7 days |
+| **MVP** | Functional product | Real usage data | 2-4 weeks |
+
+For the incubation timeframe: aim for a **vibe-coded prototype** as the target.
+
+---
+
+## 3.2 Lo-Fi Specification
+
+Before building, produce a clear specification:
+
+**Core user story:** "As a [ICP user], I want to [action] so that [benefit]."
+
+**Core flow (3-5 steps):**
+1.
+2.
+3.
+
+**Key screens / states:**
+- Screen 1: [what the user sees and does]
+- Screen 2:
+- Screen 3:
+
+**What we explicitly are NOT building in the prototype:**
+(scope boundary — what to fake / stub out)
+
+---
+
+## 3.3 Vibe Code the Wedge Prototype
+
+Using the "vibe-code-wedge" tool from `synthetic-tools.csv`:
+
+Reference: Claude Code / Cursor / Replit
+
+**Prompting guidance for vibe coding:**
+
+Prompt 1 (Setup):
+> "I'm building a prototype of [wedge description] for [ICP]. The core flow is [steps]. Build [tech stack — e.g., a Next.js app / React app / Python Flask app] with [key features]."
+
+Prompt 2 (Core feature):
+> "Build the [core feature name] — it should [behavior]. The data model is [description]. Keep it simple — this is a prototype."
+
+Prompt 3 (UI/UX):
+> "Style this for [ICP context — e.g., enterprise SaaS, clean and minimal]. Add [specific UI elements]."
+
+Produce a prompting guide with 5-8 prompts that will build the prototype when used in Claude Code / Cursor. Save to `{output_folder}/{venture_name}/prototype/build-guide.md`.
+
+---
+
+## 3.4 Checkpoint
+
+**GUIDED MODE:** Review prototype specification. Ask: "Does this capture the core value prop? Is there anything critical that's not in scope that we need for testing?"
+
+**YOLO MODE:** Proceed to Step 4 with prototype specification in hand.
+
+---
+
+## Step 3 Outputs
+- `prototype/wireframes.md` (lo-fi specification + flow)
+- `prototype/build-guide.md` (vibe code prompting guide)
+- Prototype built and ready for testing (via Claude Code / Cursor)

package/workflows/4-define-solution/wedge-design/step-4-solution-testing.md

@@ -0,0 +1,107 @@
+# Step 4: Solution Testing and Refinement
+<!-- Phase 4, Step 4 — Weeks 6-7 -->
+<!-- Agent: Product Strategist + Customer Discovery -->
+
+## Objective
+Test the prototype with target customers. Gather usability and desirability feedback. Refine the wedge definition, value proposition, feasibility assessment, and product roadmap. Complete Phase 4.
+
+---
+
+## 4.1 Solution Testing Interviews
+
+Using the solution testing section of `interview-script.md`:
+
+**Conduct 5-10 solution testing interviews:**
+1. Walkthrough the prototype with the ICP persona
+2. Ask participants to think aloud as they interact
+3. Probe: What's confusing? What's delightful? What would you do next?
+4. After walkthrough: "Would you use this in your current work? Under what conditions?"
+5. "What would you need to see to recommend this to your team?"
+6. Desirability score: "On a scale of 1-5, how valuable would this be in your work?"
+
+**Synthetic Solution Testing (if needed):**
+Using "synthetic-solution-testing" tool from `synthetic-tools.csv`:
+1. Generate ICP personas from interview data
+2. Simulate 5+ personas experiencing the prototype walkthrough
+3. Label ALL output: "⚠️ SIMULATED — Not real user testing"
+
+---
+
+## 4.2 Solution Testing Synthesis
+
+Compile solution testing results:
+- Usability issues (what confused people)
+- Desirability signals (what delighted people)
+- Feature gaps (what they expected but didn't see)
+- Average desirability score (1-5)
+- % who would use in current work
+- % who would recommend to team
+- Key quotes
+
+Update `wedge-definition.md` with testing insights.
+
+---
+
+## 4.3 ICP Refinement from Solution Testing
+
+Based on who responded best to the prototype:
+- Refine the ICP: which specific profiles showed the strongest positive reaction?
+- Update `icp-profile.md` with solution testing signals
+- Narrow or expand the ICP based on new evidence
+
+---
+
+## 4.4 Product Roadmap
+
+Using the `product-roadmap.md` template, create the wedge-to-vision roadmap:
+- **Phase 1 (Wedge):** Core features, success metrics, scope boundary
+- **Phase 2 (Expand):** How the wedge deepens or broadens
+- **Phase 3 (Vision):** The full platform/ecosystem
+
+Note what we explicitly are NOT building in Phase 1.
+
+Save: `{output_folder}/{venture_name}/product-roadmap.md`
+
+---
+
+## 4.5 Vision Story
+
+Using the `vision-story.md` template, write the From/To narrative:
+- ACT 1: The world before — the customer's pain state
+- ACT 2: The shift — the enabling insight / technology
+- ACT 3: The world after — the transformed customer experience
+
+Save: `{output_folder}/{venture_name}/vision-story.md`
+
+---
+
+## 4.6 Phase 4 Completion Gate
+
+Verify all guiding questions are answered:
+
+| Guiding Question | Answered? | Evidence |
+|-----------------|-----------|---------|
+| Can the team describe the wedge? | | wedge-definition.md |
+| Can the team articulate the big vision? | | vision-story.md |
+| Is the solution technically feasible? | | solution-feasibility.md |
+| What makes the solution special? | | value-proposition.md |
+| Wedge-to-vision scaling hypothesis? | | wedge-definition.md + product-roadmap.md |
+| Can the target customer use the product? | | Solution testing results |
+
+Update `venture-state.yaml`:
+- `hypotheses.solution` and `hypotheses.wedge`
+- `guiding_questions.solution` — mark all answered
+- `completed_artifacts` — add all Phase 4 artifacts
+- `category_progress.venture` — Phase 4 complete
+
+---
+
+## Step 4 Outputs
+
+| Output | File |
+|--------|------|
+| Solution testing synthesis | `solution-testing-synthesis.md` |
+| Updated wedge definition | `wedge-definition.md` |
+| Updated ICP profile | `icp-profile.md` |
+| Product roadmap | `product-roadmap.md` |
+| Vision story | `vision-story.md` |

package/workflows/4-define-solution/wedge-design/workflow.md

@@ -0,0 +1,69 @@
+# Wedge Design Workflow
+<!-- Phase 4: Define the Solution — Weeks 4-7 -->
+<!-- Agent: Product Strategist -->
+<!-- Step-file architecture: 4 sequential steps -->
+
+## Overview
+
+Design the solution wedge — the smallest part of the bigger vision that can be quickly brought to market, validated with customers, and scaled toward the full vision. This workflow covers: wedge hypothesis generation, value proposition development, prototype creation, and solution testing.
+
+**Pre-requisites from Phase 3:**
+- `pain-atomization.md` — primary pain with FIP ≥ 3.0
+- `icp-profile.md` — defined Ideal Customer Profile
+- `pain-journey-map.md` — solution entry points identified
+
+**Execution mode:**
+- **Guided:** Pause at every template-output checkpoint
+- **Yolo:** Run all 4 steps autonomously
+
+---
+
+## Pre-flight Check
+
+Load from venture-state.yaml:
+1. Primary pain hypothesis (hypotheses.problem)
+2. ICP hypothesis (hypotheses.customer)
+3. Load `pain-atomization.md`, `icp-profile.md`, `pain-journey-map.md`
+4. Load `{project-root}/ventureOS/data/techniques/brainstorming-techniques.csv` for wedge-storm and value-prop-sprint techniques
+5. Load `{project-root}/ventureOS/data/techniques/synthetic-tools.csv` for vibe-code-wedge and synthetic testing tools
+
+---
+
+## Step 1: Wedge Hypothesis Generation
+**File:** `step-1-wedge-hypothesis.md`
+
+## Step 2: Value Propositions and Concept Cards
+**File:** `step-2-value-propositions.md`
+
+## Step 3: Prototype
+**File:** `step-3-prototype.md`
+
+## Step 4: Solution Testing and Refinement
+**File:** `step-4-solution-testing.md`
+
+---
+
+## Phase 4 Completion Criteria
+
+All guiding questions answered with evidence:
+- [ ] Can the team describe the wedge? (wedge-definition.md)
+- [ ] Can the team articulate the big vision? (vision-story.md)
+- [ ] Is the solution technically feasible? (solution-feasibility.md)
+- [ ] What makes the solution special? (value-proposition.md)
+- [ ] Wedge-to-vision scaling hypothesis? (wedge-definition.md)
+- [ ] Can the target customer use the product? (solution testing results)
+
+---
+
+## Key Outputs
+
+| Artifact | File |
+|---------|------|
+| Wedge definition | `wedge-definition.md` |
+| Value proposition canvas | `value-proposition.md` |
+| Concept cards | `concept-cards/` |
+| Prototype / vibe code | `prototype/` |
+| Solution feasibility | `solution-feasibility.md` |
+| Ecosystem map | `ecosystem-map.md` |
+| Product roadmap | `product-roadmap.md` |
+| Vision story | `vision-story.md` |

package/workflows/5-business-case/checkin-pitch/step-1-evidence-compilation.md

@@ -0,0 +1,78 @@
+# Step 1: Evidence Compilation for Check-in Pitch
+<!-- Phase 5, Check-in Pitch Step 1 -->
+<!-- Agent: Pitch Master + Venture Master -->
+
+## Objective
+Compile all validated evidence from Phases 1-4 into a structured evidence brief. This becomes the backbone of the check-in pitch deck.
+
+---
+
+## 1.1 Load All Completed Artifacts
+
+Load and review the following from venture-state.yaml (completed_artifacts):
+- `team-charter.md` — team setup
+- `mothership-asset-map.md` — mothership assets
+- `market-sizing.md` — market opportunity
+- `competitive-analysis.md` — competitive context
+- `interview-synthesis.md` — customer research
+- `pain-atomization.md` — pain validation and FIP scores
+- `icp-profile.md` — ICP definition
+- `wedge-definition.md` — solution hypothesis
+- `value-proposition.md` — value prop testing results
+- `experiment-plan.md` — Phase 6 plan
+
+---
+
+## 1.2 Compile Evidence by Check-in Gate Criteria
+
+Structure evidence against the three check-in gate focus criteria (from gate-rubric.yaml):
+
+### Customer Pain Validation Evidence
+- Number of interviews conducted:
+- Interview types (pain-point / expert / concept card / synthetic):
+- Primary pain validated: [statement] | FIP Score: ___
+- Top 3 evidence quotes:
+- ICP defined: Yes/No
+- Buyer vs. user mapped: Yes/No
+- Score estimate (1-5):
+
+### Market Opportunity Evidence
+- TAM: $___B (source)
+- SAM: $___M (methodology)
+- Market growth rate: ___% CAGR
+- Key barrier to entry identified:
+- Score estimate (1-5):
+
+### Wedge Clarity and Differentiation Evidence
+- Wedge defined: [one sentence]
+- Value prop tested: Yes/No | Average resonance score: ___/5
+- Top differentiation from alternatives:
+- Scaling hypothesis articulated: Yes/No
+- Score estimate (1-5):
+
+---
+
+## 1.3 Identify Gaps and Honest Limitations
+
+Be honest about what is NOT yet validated:
+- What do we still not know?
+- What assumptions remain untested?
+- What are the top 2-3 risks going into Phase 6?
+
+These go into the check-in pitch as "what we need from the NVB."
+
+---
+
+## 1.4 Draft Evidence Summary
+
+Write a 1-page evidence brief:
+- What we set out to learn
+- What we found (3-5 bullets with evidence)
+- What we still don't know (honest gaps)
+- Our recommendation: do we think we should proceed to Phase 6?
+
+Save: `{output_folder}/{venture_name}/checkin-evidence.md`
+
+---
+
+## Proceed to Step 2 (Pitch Deck Creation)

package/workflows/5-business-case/checkin-pitch/step-2-pitch-creation.md

@@ -0,0 +1,87 @@
+# Step 2: Check-in Pitch Deck Creation
+<!-- Phase 5, Check-in Pitch Step 2 -->
+<!-- Agent: Pitch Master -->
+
+## Objective
+Create the check-in pitch deck (7-8 slides, progress-focused) using validated evidence from the evidence compilation. This deck is for the NVB, not investors — focus on evidence gathered, honest gaps, and a clear ask.
+
+---
+
+## 2.1 Load Context
+
+Load:
+- `checkin-evidence.md` (from Step 1)
+- `pitch-deck.md` template — CHECK-IN PITCH DECK section (7-8 slides)
+- `experiment-plan.md` for the "Plan for next 4 weeks" slide
+
+---
+
+## 2.2 Build the Check-in Pitch Deck
+
+Using the CHECK-IN PITCH DECK section of the `pitch-deck.md` template, build all 7-8 slides:
+
+**Slide 1: Title + Venture Hypothesis**
+- Venture name and tagline
+- The starting hypothesis: customer + problem + solution in one sentence each
+- Week # and date
+
+**Slide 2: What We Set Out to Learn**
+- The guiding questions from venture-state.yaml
+- Methodology: how many interviews, what types, what tools used
+- Timeline: what happened in which weeks
+
+**Slide 3: Customer Evidence Gathered**
+- Interview stats: # conducted, # types
+- Key pain themes from synthesis
+- FIP scores (table or visual)
+- 2-3 representative customer quotes (direct or labeled as synthetic)
+
+**Slide 4: Pain Validated + ICP Defined**
+- Primary pain statement with FIP score
+- ICP profile (brief — role, company type, pain intensity)
+- Buyer vs. user: same or different?
+- Pain journey map highlight (one key insight)
+
+**Slide 5: Solution Hypothesis**
+- Wedge definition (one clear sentence)
+- Value proposition(s) tested and resonance scores
+- Differentiation vs. alternatives (2-3 points)
+- Prototype / concept card (if available — screenshot or description)
+
+**Slide 6: What We Need from the NVB**
+- Specific questions we have for the NVB
+- Concerns or risks we want board input on
+- Resources needed to run Phase 6 experiments
+- Any directional decisions needed (pivot a hypothesis?)
+
+**Slide 7: Plan for Next 4 Weeks**
+- Phase 6 experiment plan (load from experiment-plan.md)
+- Key experiments to run (landing page, pilots, business model)
+- Pilot customer pipeline status
+- Final pitch preparation timeline
+
+**Slide 8 (optional): Market Opportunity**
+- TAM/SAM from market-sizing.md
+- Why this market is worth the continued investment
+
+---
+
+## 2.3 Review and Refine
+
+**GUIDED MODE:**
+Present draft to user slide by slide. Ask:
+- "Does this accurately represent what we found?"
+- "Is there any claim here we can't back up with evidence?"
+- "Is the ask to the NVB clear?"
+
+**YOLO MODE:** Complete deck and proceed to Step 3.
+
+---
+
+## 2.4 Save Deck
+
+Save: `{output_folder}/{venture_name}/pitch/checkin-pitch.md`
+
+---
+
+## Proceed to Step 3 (NVB Review)

package/workflows/5-business-case/checkin-pitch/step-3-nvb-review.md

@@ -0,0 +1,111 @@
+# Step 3: NVB Check-in Review Simulation
+<!-- Phase 5, Check-in Pitch Step 3 -->
+<!-- Agent: Venture Evaluator -->
+
+## Objective
+Simulate the New Venture Board check-in review. The Venture Evaluator acts as the NVB Chair, reviews the check-in pitch, evaluates the evidence against the gate rubric (focus criteria), asks hard questions, and produces a Go / No-Go / Revise decision.
+
+---
+
+## 3.1 Activate NVB Review Mode
+
+Load:
+- `pitch/checkin-pitch.md` (the deck)
+- `checkin-evidence.md` (supporting evidence)
+- `{project-root}/ventureOS/data/scoring/gate-rubric.yaml` (rubric + checkin_gate focus criteria)
+- All completed artifacts from venture-state.yaml
+
+Note: For the check-in gate, focus evaluation on:
+- Customer Pain Validation (weight: 20%)
+- Market Opportunity (weight: 15%)
+- Wedge Clarity & Differentiation (weight: 15%)
+
+Other criteria (business model, traction, feasibility, mothership/team) are noted but not decisive at this gate.
+
+---
+
+## 3.2 NVB Review Simulation
+
+The Venture Evaluator simulates the NVB board session:
+
+**Opening (as NVB Chair):**
+"Thank you for the presentation. We've reviewed the deck. Let's go through each area..."
+
+**For each of the 3 focus criteria:**
+1. Read the evidence presented for this criterion
+2. Assign a score (1-5) with rationale
+3. Ask 2-3 probing NVB-style questions
+4. Note the strongest evidence and the biggest gap
+
+**NVB Hard Questions to ask (examples):**
+- "You've done ___ interviews. How confident are you that ___ more interviews would change your view of the primary pain?"
+- "The FIP score of ___ is [strong/moderate]. What's the riskiest assumption in that score?"
+- "Your ICP is [description]. How do you know this is the right customer to target first?"
+- "The market is sized at $___B TAM. What's your source, and how have you filtered to SAM?"
+- "The wedge is [description]. Who would build this if you didn't?"
+
+---
+
+## 3.3 Weighted Score Calculation (Check-in Focus)
+
+Calculate score for the 3 focus criteria:
+- Customer Pain Validation: score × 0.20
+- Market Opportunity: score × 0.15
+- Wedge Clarity: score × 0.15
+
+Note scores on other criteria (not weighted decisively at this gate):
+- Technical Feasibility: score × 0.10
+- Mothership & Team: score × 0.10
+
+**Overall check-in score:** (sum of focus criteria weighted scores + other criteria)
+
+Apply thresholds from gate-rubric.yaml:
+- ≥3.5 → **GO: Continue to Phase 6**
+- 2.5-3.49 → **REVISE: Specific gap must be addressed before Phase 6**
+- <2.5 → **NO-GO: Not enough evidence. Revisit pain discovery or kill.**
+
+---
+
+## 3.4 Decision Output
+
+Produce the NVB check-in decision record:
+
+**Decision:** GO / REVISE / NO-GO
+
+**Score Summary:**
+| Criterion | Score | Weight | Weighted |
+|-----------|-------|--------|---------|
+| Customer Pain Validation | | 0.20 | |
+| Market Opportunity | | 0.15 | |
+| Wedge Clarity | | 0.15 | |
+| Other criteria | | | |
+| **Total** | | | |
+
+**Key strengths:**
+1.
+2.
+
+**Key concerns:**
+1.
+2.
+
+**NVB Questions for the team to answer:**
+1.
+2.
+3.
+
+**If REVISE:** What specific evidence or work must be completed before Phase 6 can begin?
+
+**If NO-GO:** Is this a Kill or a return to Phase 3 for further discovery?
+
+---
+
+## 3.5 Update Venture State
+
+Save: `{output_folder}/{venture_name}/pitch/checkin-nvb-decision.md`
+
+Update `venture-state.yaml`:
+- `gate_history[0].date` and `gate_history[0].decision`
+- If GO: `current_phase: "6-design-business"`, `current_week: 10`
+- If REVISE: note what must be done, stay in Phase 5
+- If NO-GO/KILL: trigger kill or pivot flow via Venture Master

package/workflows/5-business-case/checkin-pitch/workflow.md

@@ -0,0 +1,49 @@
+# Check-in Pitch Workflow
+<!-- Phase 5: Build Initial Business Case — ~Week 8 -->
+<!-- Agent: Pitch Master + Venture Evaluator -->
+<!-- Step-file architecture: 3 sequential steps -->
+
+## Overview
+
+The check-in pitch is the first NVB decision gate (~Week 8). The venture team presents progress to the New Venture Board (simulated) and receives a Go / No-Go / Revise decision.
+
+**Focus of the check-in gate:**
+- Customer pain validation evidence
+- Market opportunity assessment
+- Solution hypothesis (early wedge concept)
+- Plan for next 4 weeks (Phase 6)
+
+**Note:** Full business model, traction data, and financials are NOT required at this gate. The focus is: "Is there enough validated evidence to justify 4 more weeks of incubation?"
+
+---
+
+## Pre-requisites
+
+From `venture-state.yaml`, confirm these are complete:
+- `interview-synthesis.md` (Phase 3)
+- `pain-atomization.md` (Phase 3)
+- `icp-profile.md` (Phase 3)
+- `wedge-definition.md` (Phase 4)
+- `market-sizing.md` (Phase 2)
+- `experiment-plan.md` (Phase 5)
+
+---
+
+## Step 1: Evidence Compilation
+**File:** `step-1-evidence-compilation.md`
+
+## Step 2: Check-in Pitch Deck Creation
+**File:** `step-2-pitch-creation.md`
+
+## Step 3: NVB Review Simulation
+**File:** `step-3-nvb-review.md`
+
+---
+
+## Outputs
+
+| Artifact | File |
+|---------|------|
+| Evidence compilation | `checkin-evidence.md` |
+| Check-in pitch deck | `pitch/checkin-pitch.md` |
+| NVB decision record | `pitch/checkin-nvb-decision.md` |

package/workflows/5-business-case/initial-business-case/instructions.xml

@@ -0,0 +1,83 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<workflow-instructions name="initial-business-case">
+
+  <overview>
+    Build the initial business case for the venture before the check-in gate. Identify and remove venture killer risks. Create the operating and experiment plan for Phase 6. Establish the pilot customer pipeline.
+  </overview>
+
+  <step n="1" name="reverse-pitch">
+    <title>Reverse Pitch — Surface Hidden Risks</title>
+    <agent>venture-ops</agent>
+    <instructions>
+      Run the "reverse-pitch" brainstorming technique from brainstorming-techniques.csv:
+      1. Each team member (or persona if solo) argues WHY this venture should be KILLED
+      2. Collect all kill arguments — the more uncomfortable, the better
+      3. Group kill arguments into categories (market, competitive, technical, business model, regulatory, team/mothership)
+      4. Assess each: is this a real risk or a manageable one?
+      5. Identify the top 5 venture killer risks that require active mitigation
+
+      Record all kill arguments in venture-killer-risks.md (Reverse Pitch section).
+    </instructions>
+  </step>
+
+  <step n="2" name="risk-registry">
+    <title>Venture Killer Risk Registry</title>
+    <agent>venture-ops</agent>
+    <instructions>
+      Using the venture-killer-risks.md template, build a comprehensive risk registry:
+      1. Market and customer risks
+      2. Competitive risks
+      3. Technical and product risks
+      4. Business model risks
+      5. Regulatory and legal risks
+      6. Mothership and organizational risks
+
+      For each risk: likelihood (1-5), impact (1-5), risk score, priority, owner, mitigation action.
+      Identify the Top 5 Venture Killer Risks and assign mitigation owners and deadlines.
+    </instructions>
+    <template-output file="{output_folder}/{venture_name}/venture-killer-risks.md">
+      Save completed risk registry.
+    </template-output>
+  </step>
+
+  <step n="3" name="experiment-plan">
+    <title>Operating and Experiment Plan</title>
+    <agent>venture-ops</agent>
+    <instructions>
+      Create the experiment and operating plan for the next phase (Weeks 10-12) using experiment-plan.md:
+      1. Phase objectives: what must we prove in Phase 6?
+      2. Experiments to run: landing page test, paid acquisition, outbound/B2B demos, pilot engagement
+      3. For each experiment: hypothesis, metric, success threshold, owner, timeline, budget
+      4. KPIs for the plan period
+      5. Pilot customer pipeline targets
+      6. Budget and resource requirements
+      7. Decisions needed from NVB / Sponsor
+
+      This plan feeds directly into the check-in pitch.
+    </instructions>
+    <template-output file="{output_folder}/{venture_name}/experiment-plan.md">
+      Save operating and experiment plan.
+    </template-output>
+  </step>
+
+  <step n="4" name="pilot-pipeline">
+    <title>Pilot Customer Pipeline</title>
+    <agent>growth-strategist</agent>
+    <instructions>
+      Build the initial pilot customer pipeline:
+      1. Define target account criteria (based on ICP)
+      2. Identify 15-20 target accounts by name
+      3. For each: company name, contact name/role, source, status, next action
+      4. Outreach strategy: what message, what channel, what offer?
+      5. Pilot structure: what do pilot customers get? What do we get? Timeline?
+      6. Success metric for the pilot: what defines a successful pilot?
+
+      Save pilot pipeline to experiment-plan.md (Pilot section).
+      Update venture-state.yaml with guiding_questions.business_case answers.
+    </instructions>
+    <state-update file="{project-root}/ventureOS/_memory/venture-sidecar/venture-state.yaml">
+      Update: completed_artifacts, guiding_questions.business_case
+    </state-update>
+  </step>
+
+</workflow-instructions>

package/workflows/5-business-case/initial-business-case/workflow.yaml

@@ -0,0 +1,28 @@
+# VB Workflow: Initial Business Case (Phase 5 — Weeks 7-10)
+name: initial-business-case
+description: "Build the initial business case: identify and mitigate venture killer risks, create the operating and experiment plan for Phase 6, establish budget and operational support, build a pilot customer pipeline."
+author: "VB"
+
+config_source: "{project-root}/ventureOS/config.yaml"
+output_folder: "{config_source}:output_folder"
+venture_name: "{config_source}:venture_name"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+date: system-generated
+
+installed_path: "{project-root}/ventureOS/workflows/5-business-case/initial-business-case"
+instructions: "{installed_path}/instructions.xml"
+
+templates:
+  - "{project-root}/ventureOS/data/templates/venture-killer-risks.md"
+  - "{project-root}/ventureOS/data/templates/experiment-plan.md"
+
+tags:
+  - business-case
+  - risk-assessment
+  - experiment-plan
+  - phase-5
+
+execution_hints:
+  interactive: true
+  autonomous: false