@rubytech/create-maxy-code 0.1.167 → 0.1.170

package/payload/platform/plugins/venture-studio/skills/zero-to-prototype/references/boolean-search.md

@@ -1,308 +0,0 @@
-# Boolean Search Mastery
-
-## Purpose
-Find and identify prospects, competitors, and market data using advanced search operators on LinkedIn, Google, and other platforms—the core skill of outbound prospecting.
-
-## When to Use
-- Finding earlyvangelists and prospects
-- Researching competitors and their customers
-- Building targeted outreach lists
-- Finding industry experts and influencers
-- Market sizing through company/role counts
-
-## Process
-
-### 1. Understand Boolean Basics
-
-**Core operators:**
-
-| Operator | Meaning | Example |
-|----------|---------|---------|
-| AND | Both terms required | `marketing AND manager` |
-| OR | Either term | `CEO OR founder` |
-| NOT | Exclude term | `engineer NOT senior` |
-| "" | Exact phrase | `"product manager"` |
-| () | Group operators | `(CEO OR founder) AND startup` |
-| * | Wildcard | `market*` matches marketing, marketer |
-
-**Operator precedence:** NOT > AND > OR
-Use parentheses to control order: `(A OR B) AND C`
-
-### 2. LinkedIn Search Patterns
-
-**Finding decision-makers:**
-```
-"VP" OR "Vice President" OR "Director" AND marketing
-AND (SaaS OR "B2B software")
-```
-
-**Finding specific titles:**
-```
-"Head of Growth" OR "Growth Lead" OR "VP Growth"
-```
-
-**Finding by company size:**
-```
-"product manager" AND (startup OR "series A" OR "seed stage")
-```
-
-**Excluding irrelevant results:**
-```
-"content marketing" NOT intern NOT coordinator NOT entry
-```
-
-**Industry targeting:**
-```
-"sales director" AND (fintech OR "financial services" OR banking)
-```
-
-### 3. Google Search Patterns
-
-**Finding companies:**
-```
-site:linkedin.com/company "AI powered" "customer support"
-```
-
-**Finding competitor customers:**
-```
-site:*.com "powered by [competitor]" OR "uses [competitor]"
-```
-
-**Finding job postings (reveals hiring companies):**
-```
-site:lever.co OR site:greenhouse.io "product marketing manager" "B2B SaaS"
-```
-
-**Finding industry blogs/content:**
-```
-intitle:"state of" "[industry]" 2024 filetype:pdf
-```
-
-**Finding case studies:**
-```
-"[competitor name]" + "case study" OR "customer story"
-```
-
-### 4. Building Prospect Lists
-
-**Step 1: Define your ICP criteria**
-- Title/role
-- Company size
-- Industry
-- Geography
-- Technologies used
-
-**Step 2: Build the search string**
-
-Example ICP: Marketing leaders at B2B SaaS companies (50-500 employees)
-
-```
-LinkedIn search:
-("VP Marketing" OR "Head of Marketing" OR "Director Marketing")
-AND (SaaS OR "B2B software" OR "cloud software")
-```
-
-**Step 3: Add filters**
-- Company size: 51-200, 201-500
-- Industry: Computer Software, Technology
-- Geography: United States
-
-**Step 4: Refine based on results**
-- Too many results → Add more specific terms
-- Too few results → Remove restrictions
-- Wrong results → Add NOT exclusions
-
-### 5. Finding Earlyvangelists
-
-**People with the problem:**
-```
-LinkedIn:
-"struggling with" OR "looking for" OR "need help with"
-AND "[problem area]"
-```
-
-**People who built workarounds:**
-```
-Google:
-"built a spreadsheet for" OR "hacked together"
-AND "[problem area]"
-```
-
-**People asking questions:**
-```
-site:reddit.com OR site:quora.com
-"how do I" OR "best way to" AND "[problem area]"
-```
-
-**People complaining:**
-```
-site:twitter.com "[competitor]" AND
-("frustrated" OR "hate" OR "worst" OR "annoying")
-```
-
-### 6. Competitive Research
-
-**Find competitor customers:**
-```
-site:g2.com/products/[competitor]/reviews
-site:capterra.com/software/[competitor]/reviews
-"we switched from [competitor]" OR "we use [competitor]"
-```
-
-**Find competitor employees:**
-```
-LinkedIn: current company:[competitor] AND
-("sales" OR "customer success" OR "account executive")
-```
-
-**Find competitor content:**
-```
-site:[competitor.com] AND (whitepaper OR ebook OR webinar)
-site:[competitor.com] intitle:"state of" OR "trends"
-```
-
-**Find competitor pricing:**
-```
-"[competitor name]" AND (pricing OR "how much" OR cost)
-site:[competitor.com] pricing OR plans
-```
-
-### 7. Market Research
-
-**Industry size/companies:**
-```
-"[industry]" AND ("number of companies" OR "market size" OR "TAM")
-```
-
-**Industry publications:**
-```
-"[industry]" AND (magazine OR journal OR publication OR newsletter)
-```
-
-**Industry conferences:**
-```
-"[industry] conference" OR "[industry] summit" 2024
-```
-
-**Industry influencers:**
-```
-LinkedIn: "[industry]" AND ("thought leader" OR "speaker" OR "author")
-AND (10K+ followers filter)
-```
-
-### 8. Platform-Specific Tips
-
-**LinkedIn Sales Navigator:**
-- Use Boolean in Lead search, not keyword search
-- Save searches for alerts
-- Use "Posted on LinkedIn" filter for active users
-- Use "Changed jobs" filter for receptive prospects
-
-**Google:**
-- Use site: to restrict to specific domains
-- Use filetype: for documents (pdf, xlsx)
-- Use intitle: for page titles
-- Use daterange: for recent content
-- Use "" for exact phrases
-
-**Twitter/X:**
-- Use from: for specific accounts
-- Use to: for replies to accounts
-- Use since: and until: for date ranges
-- Use -filter:replies to exclude replies
-
-### 9. Building Search Templates
-
-Create reusable templates for common searches:
-
-**Template: Find [Role] at [Industry] companies**
-```
-("[Role1]" OR "[Role2]" OR "[Role3]")
-AND ("[Industry1]" OR "[Industry2]")
-NOT (intern OR entry OR junior OR assistant)
-```
-
-**Template: Find [Competitor] customers**
-```
-"[Competitor]" AND ("customer" OR "user" OR "we use")
-OR "switched to [Competitor]"
-OR site:g2.com/products/[competitor]
-```
-
-**Template: Find [Problem] discussions**
-```
-("[Problem keyword1]" OR "[Problem keyword2]")
-AND ("help" OR "advice" OR "recommend" OR "looking for")
-site:reddit.com OR site:quora.com OR site:community.*
-```
-
-### 10. Synthesis
-
-When building a search:
-- Start broad, then narrow
-- Check first page of results for relevance
-- Iterate the query based on results
-- Save successful queries for reuse
-- Track which queries yield best prospects
-
-## Example
-
-**Goal**: Find earlyvangelists for AI-powered legal document review
-
-### Search Development
-
-**Attempt 1: Too broad**
-```
-"legal document" AND "AI"
-```
-Result: 50,000+ results, mostly news articles
-
-**Attempt 2: More specific**
-```
-"contract review" AND ("time consuming" OR "tedious" OR "manual")
-AND (lawyer OR legal OR attorney)
-```
-Result: Better, but still mostly content marketing
-
-**Attempt 3: Finding complainers**
-```
-site:reddit.com/r/law* "contract review" AND
-("hate" OR "tedious" OR "takes forever" OR "junior associates")
-```
-Result: Found 3 discussions with lawyers complaining
-
-**Attempt 4: LinkedIn prospects**
-```
-("General Counsel" OR "Legal Ops" OR "VP Legal")
-AND (startup OR "tech company" OR SaaS)
-NOT ("big law" OR partner)
-```
-Result: 500 relevant prospects
-
-**Attempt 5: Finding budget owners**
-```
-("Legal Tech" OR "Legal Operations") AND
-("Director" OR "Manager" OR "Head of")
-AND ("evaluating" OR "looking for" OR "implementing")
-```
-Result: 50 highly qualified prospects
-
-### Final Search Library
-
-| Search Name | Query | Platform | Results |
-|-------------|-------|----------|---------|
-| GC at startups | ("General Counsel" OR "VP Legal") AND startup | LinkedIn | 500 |
-| Legal ops managers | "Legal Operations" AND (Director OR Manager) | LinkedIn | 200 |
-| Complainers | site:reddit.com "contract review" tedious | Google | 20 threads |
-| Competitor users | site:g2.com/products/contractpodai/reviews | Google | 100 reviews |
-| Job postings | site:lever.co "legal operations" | Google | 30 companies |
-
-### Prospect Building Workflow
-
-1. Run "GC at startups" search on LinkedIn
-2. Export to Sales Navigator list
-3. Cross-reference with "Job postings" companies (hiring = budget)
-4. Prioritize companies also found in "Competitor users"
-5. Research from "Complainers" threads for messaging
-
-**Insight:** Boolean search isn't just about finding names—it's about finding the right names with the right context. The search evolution from 50,000 generic results to 50 highly qualified prospects demonstrates the power of iterative refinement.

package/payload/platform/plugins/venture-studio/skills/zero-to-prototype/references/build-measure-learn.md

@@ -1,262 +0,0 @@
-# Build-Measure-Learn Loop
-
-## Purpose
-Systematically test business hypotheses through rapid iteration, turning ideas into products, measuring customer response, and learning whether to pivot or persevere.
-
-## When to Use
-- Running experiments to validate product ideas
-- Deciding what to build next
-- Measuring progress when traditional metrics don't apply
-- Avoiding "building in the dark" based on assumptions
-- Accelerating time to product-market fit
-
-## Process
-
-### 1. Understand the Loop
-
-The Build-Measure-Learn loop is the fundamental feedback cycle:
-
-```
-       IDEAS
-         ↓
-      [BUILD]  → Minimize time through the loop
-         ↓
-      PRODUCT (MVP)
-         ↓
-     [MEASURE]  → Focus on actionable metrics
-         ↓
-       DATA
-         ↓
-      [LEARN]  → Validated learning is the goal
-         ↓
-       IDEAS ←─┘
-```
-
-**Critical insight:** Work BACKWARDS through the loop when planning:
-1. What do we need to LEARN?
-2. What do we need to MEASURE to learn that?
-3. What do we need to BUILD to measure that?
-
-### 2. Start with Learning Goals
-
-Before building anything, define:
-
-**What hypothesis are we testing?**
-- Be specific: "Customers will pay $50/month" not "People will like this"
-- Make it falsifiable: There should be a clear way to be wrong
-- Make it meaningful: If wrong, it changes your strategy
-
-**What would validate this hypothesis?**
-- Specific numbers: "30% conversion rate"
-- Specific behaviors: "Use feature 3+ times per week"
-- Specific commitments: "5 pre-orders in 30 days"
-
-**What would invalidate this hypothesis?**
-- Define failure criteria upfront
-- "If conversion is below 10%, we abandon this direction"
-- Prevents moving the goalposts later
-
-### 3. Design the Measurement
-
-**Choose metrics that are:**
-
-**Actionable** - Shows cause and effect
-- Bad: "Traffic increased" (why? what do we do about it?)
-- Good: "Signup rate increased 20% after headline change"
-
-**Accessible** - Everyone can understand
-- Use real units (customers, revenue) not abstractions
-- If a new employee can't understand your dashboard, simplify it
-
-**Auditable** - Can be verified
-- Can you manually check the numbers?
-- Can you talk to the actual customers represented?
-
-### 4. Build the Minimum Required
-
-**Only build what's needed to test the hypothesis:**
-
-- Does the hypothesis require a full product? (Usually no)
-- Does it require that feature? (Often no)
-- Does it require that level of polish? (Rarely)
-
-**Types of build:**
-- Conversation: Sometimes you just need to ask questions
-- Landing page: Test demand without building
-- Wizard of Oz: Manual fulfillment behind automated facade
-- Single feature: Build one thing well
-- Full MVP: Minimum complete experience
-
-### 5. Run the Experiment
-
-**Set time boundaries:**
-- "We'll run this for 2 weeks, then evaluate"
-- Prevents experiments from running indefinitely
-- Creates forcing function for decision
-
-**Maintain discipline:**
-- Don't change the experiment mid-way (unless it's clearly failing)
-- Don't add features "while we're at it"
-- Don't extend timeline without re-scoping
-
-**Gather data systematically:**
-- Track the metrics you defined
-- Collect qualitative feedback too
-- Note unexpected observations
-
-### 6. Analyze and Learn
-
-**Compare results to hypothesis:**
-- Did we hit our success criteria?
-- Did we miss our failure criteria?
-- Were we in the gray zone?
-
-**Extract insights:**
-- What did we learn that we didn't expect?
-- What questions do we have now?
-- What should we test next?
-
-**Make a decision:**
-- **Persevere:** Results support hypothesis, continue direction
-- **Pivot:** Results invalidate hypothesis, change direction
-- **Iterate:** Results unclear, refine and test again
-
-### 7. Accelerate the Loop
-
-The goal is to minimize total time through the loop:
-
-**Reduce build time:**
-- Use no-code tools
-- Manual before automated
-- Templates and existing components
-
-**Reduce measure time:**
-- Instrument from the start
-- Use real-time analytics
-- Talk to customers directly
-
-**Reduce learn time:**
-- Daily/weekly reviews (not monthly)
-- Predefined decision criteria
-- Team alignment on interpretation
-
-### 8. Common Mistakes
-
-**Building before knowing what to learn:**
-"Let's build it and see what happens" = expensive randomness
-
-**Measuring vanity metrics:**
-Page views and registrations feel good but don't indicate product-market fit
-
-**Not setting success criteria upfront:**
-Leads to confirmation bias: "Well, it wasn't a complete failure..."
-
-**Slow loops:**
-Monthly iterations when weekly is possible = 4x slower learning
-
-**Ignoring negative results:**
-"Users didn't engage, but maybe if we add this feature..."
-
-### 9. Synthesis
-
-After each loop:
-- What did we learn?
-- Was the hypothesis validated, invalidated, or unclear?
-- What's our next hypothesis to test?
-- Are we making progress toward product-market fit?
-- Should we pivot or persevere?
-
-## Example
-
-**Idea**: "AI-powered meal planning app for busy parents"
-
-### Loop 1: Test Demand
-
-**Hypothesis:** Busy parents will sign up for AI meal planning
-
-**Success Criteria:** 100 signups in 2 weeks from $200 ad spend
-
-**Build:** Landing page with value prop and email capture
-- "Stop asking 'What's for dinner?' - AI plans your week"
-- Simple email signup form
-- Built in 2 days using Carrd
-
-**Measure:**
-- Visitors: 2,400
-- Signups: 156 (6.5% conversion)
-- Source breakdown: Facebook 60%, Google 40%
-- Demographics: 80% women, 25-44, suburban
-
-**Learn:**
-- ✓ Demand exists (exceeded 100 signups)
-- Facebook > Google for this audience
-- Messaging resonated more with moms than dads
-- Several signups asked about dietary restrictions
-
-**Decision:** Persevere → Next hypothesis
-
----
-
-### Loop 2: Test Willingness to Pay
-
-**Hypothesis:** Parents will pay $10/month for AI meal planning
-
-**Success Criteria:** 10 paid signups ($10/month) in 2 weeks
-
-**Build:** Updated landing page with:
-- Pricing tier: $10/month or $80/year
-- Stripe checkout integration
-- 7-day free trial
-- Built in 3 days
-
-**Measure:**
-- Existing list emailed: 156
-- Clicked through: 48 (31%)
-- Started trial: 18 (12%)
-- Converted to paid: 3 (2%)
-- Revenue: $30/month
-
-**Learn:**
-- ✗ Below target (3 vs 10 paid)
-- Trial to paid conversion very low (17%)
-- Feedback: "I liked it but forgot to use it"
-- Feedback: "Recipes were too complicated"
-
-**Decision:** Iterate → Test simplified recipes
-
----
-
-### Loop 3: Test Retention Mechanism
-
-**Hypothesis:** Daily push notification with simple recipes increases engagement
-
-**Success Criteria:** 50% of users engage 3+ times per week
-
-**Build:**
-- Mobile-optimized version
-- Push notification system
-- Simplified 5-ingredient recipes
-- Built in 5 days
-
-**Measure:**
-- Active trial users: 25
-- Engaged 3+ times/week: 9 (36%)
-- Trial to paid conversion: 5 (20%)
-
-**Learn:**
-- Getting closer (36% vs 50%)
-- Push notifications helped (+3% engagement)
-- Simplified recipes resonated
-- Users who engaged 3+ converted 60%
-
-**Decision:** Iterate → Focus on driving engagement
-
----
-
-**Insight:** Three Build-Measure-Learn loops in 6 weeks taught us:
-1. Demand exists for the concept
-2. Pricing works but retention is the bottleneck
-3. Engagement predicts conversion
-4. Simple recipes + notifications help but aren't sufficient
-
-Next hypothesis: Test grocery list integration (user feedback suggests this is missing value)