ventureos 1.0.0

package/templates/pivot-log.md

@@ -0,0 +1,117 @@
+# Pivot Log
+<!-- Venture Master / Venture Evaluator Agent — created at each pivot decision -->
+<!-- Purpose: Document pivot decisions with rationale, preserved work, and re-entry plan -->
+
+## Pivot #___
+
+- **Date:**
+- **Triggered By:** [ ] Check-in Gate  [ ] Final Gate  [ ] Team Decision  [ ] Sponsor Direction
+- **Pivot Type:** [ ] Customer  [ ] Problem  [ ] Solution  [ ] Business Model  [ ] Market
+- **Gate Score at Pivot:** ___
+- **Re-entry Phase:**
+
+---
+
+## What Led to This Pivot
+
+### Evidence That Triggered the Pivot
+_(What specific findings, scores, or signals made it clear the current direction was not working?)_
+
+1.
+2.
+3.
+
+### Original Hypothesis (that is being abandoned)
+- **Customer hypothesis was:**
+- **Problem hypothesis was:**
+- **Solution hypothesis was:**
+
+### Why This Hypothesis Failed
+_(Root cause — was it the ICP, the pain, the solution, the business model, the market?)_
+
+---
+
+## Pivot Decision Details
+
+### Pivot Type: [Type]
+**Definition:** _(e.g., "Same customer, different problem to solve")_
+
+**New Hypothesis Being Tested:**
+- **New customer hypothesis (if changed):**
+- **New problem hypothesis (if changed):**
+- **New solution hypothesis (if changed):**
+- **New market hypothesis (if changed):**
+
+**Re-entry Phase:** Phase ___ — _(phase name)_
+
+---
+
+## Artifacts Preserved (Still Valid After Pivot)
+
+| Artifact | File Path | Why Still Relevant |
+|---------|----------|-------------------|
+| | | |
+| | | |
+
+## Artifacts Regenerated (Starting Fresh)
+
+| Artifact | Why Must Be Regenerated |
+|---------|------------------------|
+| | |
+| | |
+
+---
+
+## Pivot Archive
+
+**Archive Location:** `{output_folder}/{venture_name}/pivots/pivot-{N}/`
+
+**Files Archived:**
+- [ ] All completed artifacts up to pivot date
+
+---
+
+## What We Learned from the Previous Direction
+
+### Key Learnings
+1.
+2.
+3.
+
+### What to Watch Out for in Next Direction
+
+### Hypothesis Adjustments Based on Learnings
+
+---
+
+## Plan for Re-entry
+
+| Week | Activity | Owner | Output |
+|------|---------|-------|--------|
+| | | | |
+| | | | |
+
+**Timeline to next gate from re-entry:** ___ weeks
+
+**Sponsor briefed on pivot:** [ ] Yes  [ ] No — date to brief: ___
+
+---
+
+## Pivot #___ Summary (for venture-state.yaml)
+```yaml
+pivot:
+  number:
+  date:
+  type:
+  from_hypothesis:
+    customer: ""
+    problem: ""
+    solution: ""
+  to_hypothesis:
+    customer: ""
+    problem: ""
+    solution: ""
+  reentry_phase: ""
+  gate_score:
+  key_learning: ""
+```

package/templates/pricing-model.md

@@ -0,0 +1,118 @@
+# Pricing Model
+<!-- Business Architect / Growth Strategist Agent — Phase 6 -->
+<!-- Purpose: Design and test the pricing strategy and tier structure -->
+
+## Context
+- **Venture:**
+- **Product / Wedge:**
+- **ICP:**
+- **Date:**
+
+---
+
+## Pricing Strategy Selection
+
+| Strategy | Description | Fit for Our Venture | Score (1-5) |
+|---------|-------------|--------------------|-----------:|
+| **Value-based** | Price based on value delivered to customer | | |
+| **Cost-plus** | Cost of delivery + margin | | |
+| **Competitor-anchored** | Anchor to competitor pricing | | |
+| **Freemium** | Free tier + paid upgrade | | |
+| **Usage-based** | Price per unit consumed | | |
+| **Outcome-based** | Price tied to customer result | | |
+
+**Selected strategy:**
+
+**Rationale:**
+
+---
+
+## Willingness to Pay (WTP) Research
+
+| Method | Finding |
+|--------|---------|
+| Customer interview signals | |
+| Competitor pricing research | |
+| Van Westendorp price sensitivity | |
+| Conjoint analysis (if run) | |
+
+**Estimated WTP range:** $___/month to $___/month
+
+**"Acceptable" price point:** $___
+**"Too expensive" threshold:** $___
+**"Too cheap to trust" threshold:** $___
+
+---
+
+## Pricing Tiers
+
+### Tier 1: [Name, e.g., Starter / Wedge / Free]
+- **Target Segment:**
+- **Price:** $___/month (or $___/year)
+- **Annual Discount:** ___%
+- **What's Included:**
+  - Feature A
+  - Feature B
+  - Limit: up to ___ [users/seats/units]
+- **What's Excluded:**
+- **Purpose of this tier:** (customer acquisition / revenue / upsell path)
+
+### Tier 2: [Name, e.g., Growth / Professional]
+- **Target Segment:**
+- **Price:** $___/month
+- **What's Included:**
+  - Everything in Tier 1, plus:
+  - Feature C
+  - Feature D
+  - Limit: up to ___ [users/seats/units]
+- **Expected % of Revenue:**
+
+### Tier 3: [Name, e.g., Enterprise / Custom]
+- **Target Segment:**
+- **Price:** Custom / Starting at $___
+- **What's Included:** Full platform + dedicated support + custom integrations
+- **Sales Motion:** Enterprise (outbound, demo, contract)
+
+---
+
+## Pricing Mechanics
+
+- **Billing frequency:** [ ] Monthly  [ ] Annual  [ ] Usage-based  [ ] Milestone-based
+- **Contract length:** [ ] Month-to-month  [ ] Annual  [ ] Multi-year
+- **Seat-based or company-wide:** [ ] Per seat  [ ] Per company  [ ] Per usage unit
+- **Free trial:** [ ] Yes — ___ days  [ ] No
+- **Freemium tier:** [ ] Yes  [ ] No
+
+---
+
+## Pricing Validation Plan
+
+| Test | Hypothesis | Method | Success Criteria | Status |
+|------|-----------|--------|-----------------|--------|
+| Price page A/B test | | Landing page variant | | |
+| Customer interview | | Ask directly in interviews | | |
+| Pilot pricing | | Offer to first pilot customers | | |
+
+---
+
+## Competitive Pricing Benchmarks
+
+| Competitor | Price | Tier / Model | Our Positioning vs. Them |
+|-----------|-------|-------------|--------------------------|
+| | | | |
+| | | | |
+
+---
+
+## Revenue Implications
+
+| Tier | Target # Customers (Year 1) | ARPC | ARR Contribution |
+|------|---------------------------|------|-----------------|
+| Tier 1 | | | |
+| Tier 2 | | | |
+| Tier 3 | | | |
+| **Total** | | | |
+
+**Pricing risks:**
+1.
+2.

package/templates/product-roadmap.md

@@ -0,0 +1,101 @@
+# Product / Service Roadmap
+<!-- Product Strategist Agent — Phase 4 -->
+<!-- Purpose: Map the wedge-to-vision product evolution across three phases -->
+
+## Context
+- **Venture:**
+- **Wedge:**
+- **Date:**
+
+---
+
+## Roadmap Philosophy
+- **Phase 1 (Wedge):** The smallest thing that validates the riskiest assumption and generates real customer value
+- **Phase 2 (Expand):** Deepen and broaden based on validated learnings from the wedge
+- **Phase 3 (Vision):** The full platform / ecosystem / market-leading position
+
+---
+
+## Phase 1 — The Wedge
+**Timeline:** Months 0–6 (within incubation)
+**Goal:** Validate that customers will pay for the core value we create
+
+### Core Features (must-have for wedge)
+
+| Feature | User Story | Priority | Effort | Status |
+|---------|-----------|---------|--------|--------|
+| | As a [ICP], I want to [action] so that [benefit] | Must-have | S/M/L | |
+| | | Must-have | | |
+| | | Must-have | | |
+
+### Wedge Success Metrics
+- **Primary metric (the one thing that matters):**
+- **Secondary metrics:**
+- **What defines "wedge validated":**
+
+### What We Explicitly Are NOT Building in Phase 1
+- (scope boundary — important for focus)
+
+---
+
+## Phase 2 — Expand
+**Timeline:** Months 6–18 (post-acceleration)
+**Goal:** Scale the wedge — deepen for current customers and/or expand to adjacent segments
+
+### Expansion Options to Explore
+
+| Direction | What It Adds | Segment | Hypothesis to Validate |
+|-----------|-------------|---------|----------------------|
+| Deepen | More features for current ICP | Same | |
+| Broaden | Same product for new segment | Adjacent | |
+| Extend | New product for same ICP | Same | |
+
+### Features Planned for Phase 2
+_(Based on evidence — not fully designed yet)_
+
+| Feature Area | Hypothesis | Evidence Needed Before Building |
+|-------------|-----------|-------------------------------|
+| | | |
+
+---
+
+## Phase 3 — Vision
+**Timeline:** Months 18+ (acceleration stage)
+**Goal:** Build the platform/ecosystem/market-leading position described in the vision story
+
+### The Big Vision
+_(What does the full product/platform look like at scale?)_
+
+### Key Milestones to Vision
+1.
+2.
+3.
+
+---
+
+## Dependency Map
+
+| Feature / Phase | Depends On | Risk if Dependency Fails |
+|----------------|-----------|--------------------------|
+| | | |
+
+---
+
+## Technology Decisions by Phase
+
+| Decision | Phase 1 Choice | Phase 2 Implication | Phase 3 Implication |
+|----------|---------------|--------------------|--------------------|
+| Build vs. buy | | | |
+| Core infrastructure | | | |
+| AI/ML | | | |
+| Data architecture | | | |
+
+---
+
+## Roadmap Risks
+
+| Risk | Phase | Likelihood | Mitigation |
+|------|-------|-----------|-----------|
+| Wedge too narrow to expand | 1→2 | | |
+| Technical debt from fast build | 1→2 | | |
+| Competition launches before Phase 2 | | | |

package/templates/sales-process-map.md

@@ -0,0 +1,117 @@
+# B2B Sales Process Map
+<!-- Business Architect / Growth Strategist Agent — Phase 6 -->
+<!-- Purpose: Map the B2B sales process from first touch to closed deal -->
+
+## Context
+- **Venture:**
+- **ICP:**
+- **Date:**
+
+---
+
+## Sales Process Overview
+
+**Sales Motion:** [ ] Product-Led Growth (PLG)  [ ] Sales-Led Growth (SLG)  [ ] Channel-Led  [ ] Hybrid
+
+**Average Sales Cycle Length (estimated):** ___ days/weeks
+
+**Average Deal Size (ACV):** $___
+
+---
+
+## Stage-by-Stage Sales Process
+
+### Stage 1: Awareness / Lead Generation
+- **Goal:** Target customer becomes aware of the venture
+- **Activities:**
+  - [ ] Inbound (content, SEO, referrals)
+  - [ ] Outbound (cold email, LinkedIn outreach)
+  - [ ] Paid (ads)
+  - [ ] Events / conferences
+  - [ ] Mothership introductions
+- **Success Metric:** # of qualified leads per week
+- **Owner:**
+
+### Stage 2: Qualification
+- **Goal:** Confirm the lead is the right ICP with real pain and budget
+- **BANT Criteria:**
+  - Budget: does this company have budget for solutions like ours?
+  - Authority: are we talking to the decision maker?
+  - Need: do they have the specific pain we solve?
+  - Timeline: are they actively looking to solve this now?
+- **Disqualification signals:**
+- **Success Metric:** % leads that pass qualification
+- **Time in stage:** ___ days
+
+### Stage 3: Discovery / Pain Validation
+- **Goal:** Understand the customer's specific pain, context, and success criteria
+- **Key questions to ask:**
+  1.
+  2.
+  3.
+- **Discovery call structure:** _(minutes per section)_
+- **Success Metric:** Discovery score (1-5) — do they have strong FIP pain?
+- **Time in stage:** ___ days
+
+### Stage 4: Solution Presentation / Demo
+- **Goal:** Show the wedge in the context of their specific pain
+- **Demo structure:**
+  - Open: confirm the pain they described
+  - Show: core solution flow
+  - Connect: how this solves their specific situation
+  - Probe: what questions do they have?
+- **Success Metric:** % that proceed to evaluation
+- **Time in stage:** ___ days
+
+### Stage 5: Evaluation / Pilot
+- **Goal:** Customer tests the solution; confirms value
+- **Pilot structure:**
+  - Duration: ___ weeks
+  - Scope: _(what features, how many users)_
+  - Success metric for customer: _(how they will judge the pilot)_
+  - Success metric for us: _(what we want to learn)_
+- **Exit criteria:** _(what makes a pilot a "pass")_
+- **Time in stage:** ___ weeks
+
+### Stage 6: Negotiation / Close
+- **Goal:** Agree terms and sign
+- **Typical objections:**
+  1. Price → Response:
+  2. "We need to think about it" → Response:
+  3. "We need board approval" → Response:
+  4. Security / compliance concern → Response:
+- **Decision makers involved:**
+- **Time to close from pilot:** ___ weeks
+
+---
+
+## Decision Maker Map
+
+| Role | Decision-Making Authority | Pain Type | Objection |
+|------|--------------------------|-----------|----------|
+| Economic Buyer | Budget sign-off | ROI / cost | Price |
+| Champion | Day-to-day pain | Operational pain | Feature gaps |
+| Technical Evaluator | Security / integration | Technical | Complexity |
+| End User | Usability | Workflow pain | Change management |
+
+---
+
+## Sales Metrics & Targets
+
+| Metric | Month 1-3 Target | Month 4-6 Target | Source |
+|--------|-----------------|-----------------|--------|
+| Outreach per week | | | |
+| Discovery calls per week | | | |
+| Demos per week | | | |
+| Pilots started | | | |
+| Pilots converted to paid | | | |
+| Estimated CAC | | | |
+
+---
+
+## Mothership Sales Leverage
+
+- **Existing relationships we can use:**
+- **Mothership customers who are ICP:**
+- **Mothership sales team we can leverage:**
+- **Events / channels mothership has access to:**

package/templates/solution-feasibility.md

@@ -0,0 +1,122 @@
+# Solution Feasibility Assessment
+<!-- Product Strategist Agent — Phase 4: Feasibility Assessment -->
+<!-- Purpose: Evaluate whether the wedge solution can be built via build/buy/partner/invest -->
+
+## Context
+- **Venture:**
+- **Solution / Wedge Being Assessed:**
+- **Date:**
+
+---
+
+## 1. Solution Description for Feasibility Assessment
+
+**What we need to build:**
+_(High-level technical and functional description of the wedge)_
+
+**Core capabilities required:**
+1.
+2.
+3.
+4.
+
+---
+
+## 2. Build / Buy / Partner / Invest Analysis
+
+### Option A: Build (Internal Development)
+- **What would be built:**
+- **Technical requirements:**
+- **Estimated build time:**
+- **Estimated cost:**
+- **Skills / talent required:**
+- **Do we have the skills in-house?** [ ] Yes  [ ] Partially  [ ] No
+- **Mothership tech assets that could accelerate this:**
+- **Feasibility score (1-5):**
+- **Key risks:**
+
+### Option B: Buy (Acquire existing technology)
+- **Candidate technologies / products:**
+- **Acquisition / licensing cost estimate:**
+- **Integration complexity:**
+- **Feasibility score (1-5):**
+- **Key risks:**
+
+### Option C: Partner (Use a partner's technology or service)
+- **Candidate partners:**
+- **Partnership model (API, white-label, resell):**
+- **Revenue share / cost implications:**
+- **Dependency risk:**
+- **Feasibility score (1-5):**
+- **Key risks:**
+
+### Option D: Invest (Take a stake in an existing company)
+- **Candidate companies:**
+- **Investment thesis:**
+- **Timeline to access technology:**
+- **Feasibility score (1-5):**
+- **Key risks:**
+
+---
+
+## 3. Recommended Approach
+
+**Chosen route:** [ ] Build  [ ] Buy  [ ] Partner  [ ] Invest  [ ] Hybrid
+
+**Rationale:**
+
+**Hybrid approach (if applicable):**
+_(e.g., Build core IP, partner for X component, buy Y capability)_
+
+---
+
+## 4. Technical Feasibility Dimensions
+
+| Dimension | Assessment | Evidence / Notes |
+|-----------|-----------|-----------------|
+| **Data availability** | Available / Partial / Unavailable | |
+| **AI/ML requirements** | None / Achievable / Complex | |
+| **Integration complexity** | Low / Medium / High | |
+| **Regulatory compliance** | Clear / Needs work / Blocker | |
+| **Security requirements** | Standard / Elevated / Complex | |
+| **Scalability** | Straightforward / Needs design | |
+
+**Overall technical feasibility:** Low / Medium / High
+
+---
+
+## 5. Ecosystem Map
+
+### Key Players in the Technology Ecosystem
+
+| Player | Role | Relationship Opportunity | Priority |
+|--------|------|--------------------------|---------|
+| | | | |
+| | | | |
+
+### Systems the Solution Must Integrate With
+
+| System | Integration Type | Complexity | Status |
+|--------|----------------|-----------|--------|
+| | | | |
+
+---
+
+## 6. Build Plan (if Build route selected)
+
+| Phase | What Gets Built | Timeline | Resources Required |
+|-------|----------------|----------|-------------------|
+| Prototype | | | |
+| Alpha | | | |
+| Beta | | | |
+| Wedge launch | | | |
+
+---
+
+## 7. Feasibility Summary
+
+- **Overall feasibility verdict:** Feasible / Feasible with caveats / Not feasible
+- **Biggest technical risk:**
+- **Biggest dependency risk:**
+- **Critical path item (must resolve before building):**
+- **Recommended next action:**

package/templates/stakeholder-map.md

@@ -0,0 +1,94 @@
+# Stakeholder Map
+<!-- Domain Explorer / Venture Ops — Phase 1-2 -->
+<!-- Purpose: Map who matters in the venture's ecosystem — buyers, users, influencers, blockers -->
+
+## Context
+- **Venture:**
+- **Domain:**
+- **Date:**
+
+## Stakeholder Categories
+
+### Primary Stakeholders (directly experience the pain or benefit from the solution)
+
+| Stakeholder | Role / Title | Organization Type | Primary Pain | Buying Power | Research Priority |
+|-------------|-------------|-------------------|--------------|--------------|-------------------|
+| | | | | High/Med/Low | High/Med/Low |
+| | | | | | |
+| | | | | | |
+
+### Secondary Stakeholders (influence the decision or are affected by the solution)
+
+| Stakeholder | Role / Title | Influence Type | What They Care About | Relationship to Build |
+|-------------|-------------|---------------|---------------------|----------------------|
+| | | | | |
+| | | | | |
+
+### Buyers vs. Users Analysis
+- **Primary USER (who uses the solution):**
+- **Primary BUYER (who pays for the solution):**
+- **Are they the same person?** [ ] Yes  [ ] No
+- **If different — implication for sales motion:**
+
+### Influencers & Champions
+
+| Name / Role | Organization | Why They Matter | How to Reach | Priority |
+|------------|-------------|----------------|-------------|---------|
+| | | | | |
+
+### Blockers & Detractors
+
+| Stakeholder | Why They Might Block | Their Concern | Mitigation Strategy |
+|-------------|---------------------|---------------|-------------------|
+| | | | |
+
+## Stakeholder Persona Hypotheses
+_(Initial AI-synthesized personas — to be validated via real interviews)_
+
+### Persona 1: [Name / Role]
+- **Archetype:**
+- **Day in the life:**
+- **Primary pain related to our domain:**
+- **How they solve it today:**
+- **What success looks like for them:**
+- **What would make them change behavior:**
+
+### Persona 2: [Name / Role]
+- **Archetype:**
+- **Day in the life:**
+- **Primary pain related to our domain:**
+- **How they solve it today:**
+- **What success looks like for them:**
+- **What would make them change behavior:**
+
+## Interview Prioritization
+
+| Stakeholder | Reason to Interview | Target # of Interviews | Status |
+|-------------|--------------------|-----------------------|--------|
+| | | | Not started |
+| | | | In progress |
+| | | | Complete |
+
+## Stakeholder Map — Power / Interest Grid
+
+```
+HIGH INTEREST
+      |
+      |  Keep Satisfied        |  Key Players (manage closely)
+      |  (inform regularly)    |
+      |                        |
+------+------------------------+------
+      |                        |
+      |  Monitor               |  Keep Informed
+      |  (minimal effort)      |  (keep updated)
+      |
+LOW INTEREST
+      LOW POWER          HIGH POWER
+```
+
+_(Place each stakeholder in the appropriate quadrant above)_
+
+## Key Insights
+- **Most critical stakeholder to win:**
+- **Biggest stakeholder risk:**
+- **Stakeholder relationships the mothership already has that we can leverage:**