# LEANSpark
> LEANSpark is an AI-powered startup validation coach built on the Continuous Innovation Framework by Ash Maurya, author of Running Lean. It helps founders stress-test business models, run customer discovery, and achieve product/market fit through structured 90-day validation cycles.
## Guides
### App Navigation
Learn how the sidebar, context bar, and two-pane layout help you move through LEANSpark
URL: https://leanspark.ai/guides/navigation/
## What it is
The LEANSpark app uses a left sidebar for navigation, a context bar across the top, and a two-pane layout where your chat (Sparks) lives underneath feature pages like Dashboard and Library.
## How to get there
The sidebar is always visible on the left side of the screen. On mobile it collapses into a hamburger menu.
## What you'll find
### Sidebar (top to bottom)
1. **Idea Switcher** (top) — dropdown showing all your Ideas (business models). Click to switch between them, rename, or delete. "Start a New Idea..." at the bottom creates a fresh canvas.
2. **Sparks** — your AI chat. This is where you talk with LEANSpark.
3. **Dashboard** — validation cycles, sprints, and progress tracking.
4. **Library** — all your artifacts and deliverables. Shows a count badge.
5. **Journal** — timeline of your sessions and activity.
6. **Skills** — lesson plans across 7 dimensions. Shows a progress badge.
### Sidebar footer
- **Invitations** — pending team invitations (badge shows count)
- **Invite Teammates** — add people to your workspace
- **Community** — community discussion board (badge for unread)
- **Help** — contact support, changelog, workshops
- **Your avatar** — profile, theme toggle, workspace switching, subscription info, sign out
### Context bar (top)
Shows your current business model name and variant. You can rename inline, switch variants, and access chat actions.
## Common questions
**Q: How do I switch between Ideas?**
Click the Idea name at the top of the sidebar to open the dropdown, then select a different Idea.
**Q: How do I switch workspaces?**
Click your avatar at the bottom of the sidebar. Under "Switch Workspace," pick a different workspace.
**Q: Where do I change my theme (light/dark)?**
Click your avatar → use the theme toggle (light / system / dark).
**Q: How do I get back to chat from the Dashboard or Library?**
Click "Sparks" in the sidebar. The chat is always loaded underneath — it just becomes visible when you switch to it.
## Related features
- [Getting Started](/guides/getting-started) — creating your first Idea
- [Workspace](/guides/workspace) — managing teams and billing
---
### Getting Started
Import your business model and set up your first Idea with the Welcome Wizard
URL: https://leanspark.ai/guides/getting-started/
## What it is
When you first sign in or create a new Idea, the Welcome Wizard walks you through importing your business model so LEANSpark has context to work with.
## How to get there
Click "Start a New Idea..." at the bottom of the Idea Switcher dropdown in the sidebar.
## What you'll find
### Step 1 — Choose your import method
- **Tell me about your idea** — start a conversation and LEANSpark will build your canvas from what you describe.
- **Import from LEANSTACK** — connect an existing Lean Canvas from leanstack.com.
- **Landing Page URL** — paste a URL and LEANSpark extracts your business model from it.
- **Pitch Deck PDF** — upload a pitch deck and LEANSpark reads it into a canvas.
- **Canvas PDF** — upload a photo or scan of an existing Lean Canvas.
- **Blank Canvas** — start with an empty canvas and fill it in yourself.
- **Example (Airbnb / Uber)** — try the app with a pre-built example business model.
### Step 2 — Provide your input
Depending on the method you chose, you'll paste a URL, upload a file, or describe your idea in a text box.
### First-time onboarding
On your very first sign-in, you'll see a short onboarding flow that asks about your role (founder or coach), project type, product stage, and team size. This helps LEANSpark personalize your experience.
## Common questions
**Q: Can I change my import after creating an Idea?**
You can always update your canvas directly — go to the Canvas editor and modify any section. The import just gives you a starting point.
**Q: How many Ideas can I have?**
There's no hard limit on Ideas. Each Idea represents a separate business model you're exploring.
**Q: What happens with a Pitch Deck upload?**
LEANSpark reads your PDF, extracts key information (problem, solution, customer segments, etc.), and maps it onto a Lean Canvas for you to refine.
**Q: I chose the wrong option — can I start over?**
Click "Start a New Idea..." from the sidebar to begin a fresh import. You can also delete an existing Idea from the Idea Switcher dropdown.
## Related features
- [App Navigation](/guides/navigation) — finding your way around
- [Canvas](/guides/canvas) — editing your Lean Canvas
---
### Dashboard
Track your validation progress with 90-day cycles, sprints, and PDCA phases
URL: https://leanspark.ai/guides/dashboard/
## What it is
The Dashboard shows your validation progress organized into 90-day cycles and sprints. It's where you track what you've accomplished and what's next in your business model validation journey.
## How to get there
Click "Dashboard" (chart icon) in the left sidebar.
## What you'll find
### Three dashboard states
1. **Empty state** — before you've started any validation work. Shows guidance on getting started.
2. **Sprint 0 (BMD Phase)** — your Business Model Design retrospective. Shows assessment progress across dimensions and your current canvas state.
3. **Campaign view (Sprint 1+)** — full cycle overview with sprint cards, a journey visualization, and PDCA (Plan-Do-Check-Act) phases.
### Sprint 0 — BMD Retrospective
- Assessment progress for each business model dimension
- Business model design summary
- Links to start your first validation sprint
### Campaign view
- **Cycle overview** — high-level status of the current 90-day cycle
- **Sprint cards** — each sprint shows its focus, tasks, interview count, and status
- **Sprint detail** — click into a sprint to see tasks, interviews, study insights, and PDCA notes
- **Info modals** — contextual explanations for concepts like Lean Canvas, Traction Roadmap, GTM Plan
## Common questions
**Q: What is a 90-day cycle?**
A 90-day cycle is a structured validation period broken into sprints. Each sprint focuses on specific experiments and customer discovery tasks.
**Q: How do I start a cycle?**
LEANSpark will guide you through creating your first cycle when your business model design is ready. You can also ask LEANSpark "help me plan my next cycle."
**Q: What's the difference between Sprint 0 and Sprint 1?**
Sprint 0 is your Business Model Design phase — getting your canvas right. Sprint 1+ are validation sprints where you run experiments and talk to customers.
**Q: Where do I see my interview data?**
Interview summaries appear within each sprint on the Dashboard. For full interview details, check the sprint detail view or the Library.
## Related features
- [Interviews](/guides/interviews) — customer discovery interviews
- [Traction Roadmap](/guides/traction-roadmap) — milestone planning
- [Library](/guides/library) — artifacts generated during sprints
---
### Library
Browse, search, and organize all your artifacts and deliverables in one place
URL: https://leanspark.ai/guides/library/
## What it is
The Library is your collection of every artifact and deliverable LEANSpark creates for you — study insights, discovery decisions, pitch decks, and more. Think of it as your project's knowledge base.
## How to get there
Click "Library" (stacked layers icon) in the left sidebar. The badge shows how many artifacts you have.
## What you'll find
### Search and filter
- **Search bar** — find artifacts by name or content
- **Filter chips** — narrow by artifact type (e.g., study insights, decisions, pitches)
### Artifact list
Each artifact card shows its title, type, creation date, and a preview. Click to open the full artifact.
### Artifact actions
- **Download** — save as a file
- **Export** — export in various formats
- **Regenerate** — ask LEANSpark to recreate the artifact with updated context
- **Reanalyze** — re-run analysis on interview artifacts
- **Archive / Unarchive** — hide artifacts you no longer need, bring them back when needed
- **Deck view** — pitch deck artifacts open in a presentation view
### AI-powered Organize
Click "Organize" to let LEANSpark clean up your library — it can suggest renames, group related artifacts, and archive stale items.
## Common questions
**Q: Where are my artifacts?**
Everything LEANSpark generates is saved to your Library automatically. Click "Library" in the sidebar to see them all.
**Q: Can I delete an artifact?**
You can archive artifacts to hide them. Archived artifacts can be restored anytime from the archive view.
**Q: How do I find a specific artifact?**
Use the search bar at the top of the Library, or use filter chips to narrow by type.
**Q: What types of artifacts does LEANSpark create?**
Common types include study insights from customer interviews, discovery decisions, pitch decks, canvas exports, and assessment reports.
**Q: Can I organize my artifacts?**
Yes — use the AI-powered "Organize" feature. LEANSpark will analyze your library and suggest cleanup actions like renaming, grouping, and archiving.
## Related features
- [Canvas](/guides/canvas) — your Lean Canvas (also exportable)
- [Dashboard](/guides/dashboard) — artifacts appear within sprint context
- [Interviews](/guides/interviews) — interview analysis creates artifacts
---
### Canvas
Create, edit, and version your Lean Canvas with AI-powered suggestions
URL: https://leanspark.ai/guides/canvas/
## What it is
The Canvas is your Lean Canvas editor — a one-page business model that captures your problem, solution, customer segments, unique value proposition, and more. It's the core artifact that LEANSpark helps you build and refine.
## How to get there
Click the canvas preview in chat, or ask LEANSpark "show me my canvas." The canvas opens as a full-screen overlay.
## What you'll find
### Canvas editor
- **Grid layout** — the classic Lean Canvas grid with all 9 sections (Problem, Customer Segments, Unique Value Proposition, Solution, Channels, Revenue Streams, Cost Structure, Key Metrics, Unfair Advantage)
- **Inline editing** — click any section to edit its contents directly
- **AI quick actions** — contextual suggestions from LEANSpark for improving each section
- **Dimension filters** — filter chips to highlight sections by dimension (Clarity, Desirability, Viability, etc.)
### Versions
Your canvas is versioned automatically. You can view past versions and restore any previous state.
### Variants
Your business model can have multiple variants — different pivot directions or market segments you're exploring. Switch between variants from the context bar at the top.
### Panzoom view (experimental)
A Miro-style zoomable canvas view for exploring your business model spatially.
## Common questions
**Q: How do I edit my canvas?**
Open the canvas and click on any section to edit it. You can also ask LEANSpark to update specific sections during chat.
**Q: Can I undo changes to my canvas?**
Yes — go to canvas Versions to see your history and restore any previous version.
**Q: What are variants?**
Variants are alternative versions of your business model. For example, you might have one variant targeting consumers and another targeting businesses. Switch between them from the context bar.
**Q: How do I export my canvas?**
From the chat, ask LEANSpark to export your canvas, or use the export option from the canvas view.
**Q: Can LEANSpark fill in my canvas for me?**
Yes — during chat, LEANSpark can suggest content for any canvas section based on your conversation. You can also import from a URL, pitch deck, or description to auto-populate.
## Related features
- [Getting Started](/guides/getting-started) — importing your initial canvas
- [Dashboard](/guides/dashboard) — canvas state feeds into your validation dashboard
- [Library](/guides/library) — canvas exports saved as artifacts
---
### Journal
Review a chronological timeline of your sessions, decisions, and progress
URL: https://leanspark.ai/guides/journal/
## What it is
The Journal is a chronological timeline of your sessions and activity with LEANSpark. It gives you a birds-eye view of your progress over time.
## How to get there
Click "Journal" (notebook icon) in the left sidebar.
## What you'll find
### Timeline view
- **Session entries** — grouped by time period, showing what you worked on in each session
- **AI-generated summaries** — LEANSpark creates concise summaries of each session highlighting key decisions, insights, and next steps
- **Lazy-loaded history** — older entries load as you scroll down
### Journal entries
Each entry captures:
- What was discussed
- Key decisions made
- Artifacts created
- Next steps identified
## Common questions
**Q: How are journal entries created?**
LEANSpark automatically generates journal entries at the end of meaningful chat sessions. You don't need to write them manually.
**Q: Can I see my full conversation history?**
The Journal shows summarized entries. For the full conversation, go to Sparks (chat) and scroll through your message history.
**Q: How far back does the Journal go?**
The Journal keeps your entire history. Older entries load as you scroll.
**Q: Can I search the Journal?**
You can scroll through entries chronologically. For finding specific artifacts or topics, the Library search may be more effective.
## Related features
- [App Navigation](/guides/navigation) — how Sparks and Journal relate
- [Library](/guides/library) — artifacts referenced in journal entries
- [Dashboard](/guides/dashboard) — sprint-level progress view
---
### Skills
Work through structured lesson plans across 7 dimensions of the Continuous Innovation Framework
URL: https://leanspark.ai/guides/skills/
## What it is
Skills is your learning hub. It organizes the Continuous Innovation Framework into 7 skill dimensions, each with structured lesson plans you can work through at your own pace.
## How to get there
Click "Skills" (lightning bolt icon) in the left sidebar. The badge shows your progress.
## What you'll find
### Seven skill dimensions
1. **Clarity** — articulating your business model clearly
2. **Desirability** — validating customer demand
3. **Viability** — ensuring the business model works financially
4. **Feasibility** — confirming you can build and deliver
5. **Timing** — market timing and readiness
6. **Defensibility** — building lasting competitive advantages
7. **Mission** — aligning with purpose and long-term vision
### Skill states
- **Available** — ready for you to start
- **In Progress** — you've started but haven't completed all lessons
- **Completed** — all lessons in the skill are done
### Lesson plans
Click into any skill to see its lesson plan — a series of lessons with video content, reading materials, and exercises. Each lesson includes:
- Duration estimate
- Video content (where available)
- Practical exercises tied to your actual business model
### Starting a skill
Click "Start" on any available skill. Lessons use credits — each lesson start deducts from your credit balance.
## Common questions
**Q: How do I learn about a specific topic like pricing or customer interviews?**
Go to Skills and find the relevant dimension. You can also ask LEANSpark "teach me about pricing" in chat and it'll point you to the right lessons.
**Q: Do Skills cost credits?**
Yes — starting each lesson uses credits. The skill overview shows the credit cost before you begin.
**Q: Can I do Skills in any order?**
Yes, you can start any available skill. However, LEANSpark may recommend a specific order based on your business model's current state.
**Q: How do Skills relate to my canvas?**
Skills teach you the frameworks behind each canvas section. What you learn directly applies to improving your business model.
## Related features
- [Dashboard](/guides/dashboard) — skill progress feeds into your overall validation progress
- [Canvas](/guides/canvas) — apply what you learn to your canvas
- [Library](/guides/library) — exercises may generate artifacts
---
### Prospects
Manage your pipeline of potential customers to interview or pitch
URL: https://leanspark.ai/guides/prospects/
## What it is
Prospects is your pipeline for tracking potential customers you want to interview or pitch. LEANSpark helps you manage who to talk to next as part of your customer discovery process.
## How to get there
Prospects are managed through your chat with LEANSpark and appear within your Dashboard sprints. Ask LEANSpark about your prospect pipeline during any conversation.
## What you'll find
- **Prospect tracking** — keep a list of people you plan to interview
- **Pipeline stages** — see who you've contacted, scheduled, and completed
- **Sprint integration** — prospects tie into your current sprint's interview goals
## Common questions
**Q: How do I add prospects?**
Tell LEANSpark about people you want to interview during chat. You can also add them when planning a sprint.
**Q: Where do I see my prospect list?**
Ask LEANSpark "show me my prospects" or check the interviews section within your current sprint on the Dashboard.
**Q: How are prospects different from interviews?**
Prospects are people you plan to talk to. Once you conduct an interview, it becomes an interview record with transcript and analysis.
## Related features
- [Interviews](/guides/interviews) — conducting and analyzing customer interviews
- [Dashboard](/guides/dashboard) — sprints track interview goals
---
### Pitches
Create and refine pitch decks using proven frameworks from Running Lean
URL: https://leanspark.ai/guides/pitches/
## What it is
Pitches captures the pitch decks and pitch frameworks LEANSpark helps you create. From elevator pitches to mafia offer stories, your pitches evolve as your business model gets validated.
## How to get there
Pitch artifacts live in your Library. You can also work on pitches through chat by asking LEANSpark to help you craft or refine a pitch.
## What you'll find
- **Pitch deck artifacts** — generated pitch decks you can view in deck mode, download, or export
- **Pitch templates** — LEANSpark uses proven templates like the Elevator Story Pitch, Problem/Solution Pitch, and Mafia Offer Pitch
- **Deck view** — pitch deck artifacts open in a presentation-style view
## Common questions
**Q: How do I create a pitch deck?**
Ask LEANSpark "help me build a pitch deck" or "create a pitch" in chat. LEANSpark will generate one based on your current canvas.
**Q: Can I edit my pitch after it's generated?**
You can ask LEANSpark to regenerate the pitch with updated context. Each version is saved in your Library.
**Q: What pitch formats are available?**
LEANSpark supports several pitch frameworks from the Running Lean methodology, including Elevator Story Pitch, Problem/Solution Pitch, Demo Pitch, and Mafia Offer Pitch.
**Q: Where do I find my pitch decks?**
Go to the Library and filter by pitch type, or ask LEANSpark "show me my pitches."
## Related features
- [Library](/guides/library) — where pitch artifacts are stored
- [Canvas](/guides/canvas) — pitches are built from your canvas data
- [Skills](/guides/skills) — learn pitching frameworks in the Clarity and Desirability dimensions
---
### Interviews
Log, transcribe, and analyze customer discovery conversations with AI-powered insights
URL: https://leanspark.ai/guides/interviews/
## What it is
Interviews is where you log, analyze, and learn from customer discovery conversations. LEANSpark can transcribe recordings, extract insights, and map findings back to your business model.
## How to get there
Interviews are managed within each sprint on your Dashboard, and interview artifacts appear in your Library.
## What you'll find
### Creating interviews
- **Upload a recording** — LEANSpark transcribes and analyzes it automatically (uses AssemblyAI)
- **Manual entry** — log interview notes directly
- **YAML import** — bulk import interview data
- **From chat** — attach an audio file during chat for inline analysis
### Interview analysis
Each interview gets:
- **Full transcript** — searchable text from your recording
- **Customer Forces story** — forces of progress, anxieties, habits mapped from the conversation
- **Study insights** — key findings extracted and saved as artifacts
- **Sprint integration** — interviews are linked to the sprint they belong to
### Interview actions
- **Reanalyze** — re-run the AI analysis with improved context
- **Move between sprints** — pull interviews from one sprint into another
- **View Forces Story** — see the customer forces diagram for each interview
## Common questions
**Q: How do I add an interview?**
From chat, upload an audio recording or tell LEANSpark about an interview you conducted. You can also create interviews directly from the Dashboard sprint view.
**Q: What audio formats are supported?**
Most common formats work — MP3, M4A, WAV, and others supported by AssemblyAI.
**Q: How long does transcription take?**
Usually a few minutes depending on recording length. You'll get a notification when it's ready.
**Q: Can I see insights across multiple interviews?**
Yes — LEANSpark can run a study analysis across all interviews in a sprint to identify patterns. Check your sprint detail view on the Dashboard.
**Q: Where are my interview insights?**
Interview insights are saved as artifacts in your Library. They also appear within the sprint on your Dashboard.
## Related features
- [Dashboard](/guides/dashboard) — interviews organized by sprint
- [Library](/guides/library) — interview insights saved as artifacts
- [Prospects](/guides/prospects) — tracking who to interview
---
### Customer Forces Story
Every completed discovery interview retold as a six-scene storyboard of your customer's switching journey.
URL: https://leanspark.ai/guides/customer-forces-story/
## What it is
Every completed discovery interview is retold as a six-scene storyboard of your customer's switching journey. Each scene is one state transition, explained by the Customer Force that caused it (Push, Pull, Friction, Inertia), with the verbatim quote and a napkin-sketch panel. A movie-poster hero personalizes the story, and a journey map traces the customer's sentiment as terrain.
## Where it lives
Open any completed interview. The **Customer Forces Story** tab is the default view. The page also has Insights, Transcript, and Interview Assessment tabs.
## How to read it
Six panels in fixed order: old way breaks, job requirements, hiring, first use, repeat use, switching. The force chip on each scene tells you what did the work. The journey map underneath shades the switching window: the span from the trigger to the deadline, when this customer was actually hireable.
Scenes the interview never reached render as ghost panels, dimmed, each holding the canonical question to ask next time. That is a built-in interviewing prompt, not a gap.
## What it needs
Interviews analyzed by the v2 extractor. Panel art appears minute-by-minute after analysis, with sketch placeholders until then. Verbatim quotes require an uploaded transcript. Older interviews gain the story via admin re-extraction.
---
### Traction Roadmap
Visualize your validation journey from problem/solution fit through product/market fit
URL: https://leanspark.ai/guides/traction-roadmap/
## What it is
The Traction Roadmap is your milestone plan for achieving traction — moving from problem/solution fit through product/market fit. It visualizes your validation journey as a series of measurable milestones.
## How to get there
Access from the Dashboard or ask LEANSpark "show me my traction roadmap."
## What you'll find
- **Milestone timeline** — a visual roadmap showing key validation milestones
- **Chart visualization** — progress data plotted over time
- **Editable milestones** — update milestone details as your understanding evolves
- **Stage progression** — track your movement through the three stages: Problem/Solution Fit, Product/Market Fit, and Scale
## Common questions
**Q: What is a traction roadmap?**
It's a tool from the Running Lean methodology that maps out the key milestones you need to hit to validate your business model, from early customer interviews through achieving product/market fit.
**Q: How do I create my traction roadmap?**
Ask LEANSpark "help me build my traction roadmap" or it may suggest creating one as part of your validation planning.
**Q: Can I update milestones?**
Yes — the roadmap is editable. Update milestones as you learn from customer discovery and experiments.
**Q: How does the traction roadmap relate to sprints?**
Sprints are the short-term execution plan. The traction roadmap is the big-picture view showing where those sprints are taking you.
## Related features
- [Dashboard](/guides/dashboard) — sprints execute toward roadmap milestones
- [Interviews](/guides/interviews) — interview insights validate roadmap assumptions
- [Canvas](/guides/canvas) — roadmap milestones map to canvas sections
---
### Workspace
Manage your team, subscription, credits, and billing in one place
URL: https://leanspark.ai/guides/workspace/
## What it is
A Workspace is your team's home in LEANSpark. It holds your Ideas, team members, subscription, and credits. You can have multiple workspaces and switch between them.
## How to get there
Click your avatar at the bottom of the sidebar. Under "Switch Workspace," pick a different workspace. Click the workspace name or "Team Details" to manage it.
## What you'll find
### Team management
- **Members** — see who's on your team, invite new members, manage roles
- **Invitations** — send email invitations to teammates
- **Roles and permissions** — control who can manage the workspace vs. just use it
### Subscription and billing
- **Current plan** — see your plan type (solo, team) and status
- **Upgrade** — move from solo to team plan, or change plan tiers
- **Billing portal** — manage payment methods and view invoices through Stripe
- **Credits** — see your credit balance and purchase more
### Credits
- Credits are used for AI interactions (chat messages, lesson starts, artifact generation)
- Purchase credit bundles from the workspace settings
- The credits balance is shown in the sidebar footer
### Switching workspaces
If you belong to multiple workspaces, switch between them from your avatar dropdown under "Switch Workspace."
### Creating a new workspace
Available from your avatar dropdown as "Create New Workspace" (when enabled).
## Common questions
**Q: How do I invite a teammate?**
Go to your workspace settings and click "Invite" in the Members section. Enter their email address. They'll receive an invitation link.
**Q: How do I buy more credits?**
Click "Buy Credits" from the workspace settings, or use the credits link in the sidebar footer.
**Q: Can I be in multiple workspaces?**
Yes — you can belong to multiple workspaces and switch between them from the avatar dropdown.
**Q: How do I change my subscription?**
Go to workspace settings → Subscription. You can upgrade, change plans, or access the Stripe billing portal for payment management.
**Q: What happens when I run out of credits?**
A banner appears at the top prompting you to purchase more. AI features are paused until credits are replenished.
**Q: How do I create a new workspace?**
Click your avatar → "Create New Workspace" at the bottom of the workspace section.
## Related features
- [App Navigation](/guides/navigation) — workspace info in sidebar footer
- [Skills](/guides/skills) — lessons consume credits
- [Getting Started](/guides/getting-started) — workspace is set up during onboarding
---
### Customer Forces Dojo
Train your ear to hear the forces of progress on real, expert-run interviews — before you run your own.
URL: https://leanspark.ai/guides/customer-forces-dojo/
## What it is
The Customer Forces Dojo is where you train your *ear* before you run your own interviews. You can't elicit a force you can't yet hear — so instead of reading about the forces of progress, you practice catching them in a real, recorded interview, at no stakes, until you can hear them cold.
The forces you're learning to hear, on the timeline of a customer's struggling moment:
- **Trigger** — the switching moment that made the old way untenable.
- **Push** — dissatisfaction with the current state.
- **Pull** — the desired outcome of the new solution.
- **Inertia** — allegiance to the old way.
- **Anxiety** — fear or uncertainty about the new solution.
The subtle miss the dojo trains hardest is **Push ↔ Pull** — and taking a customer's stated pull at face value.
## Where it lives
The dojo runs on a real interview opened in simulation mode. You reach it three ways:
- **Ask LEANSpark to teach you** — "I want to learn customer forces," "teach me customer interviews," "help me get better at discovery." You get a one-click chip into the dojo.
- **The Skills page** — the "Customer Forces" capability card on `/skills` shows your current rung and the right next action.
- **Before a discovery experiment** — when you start planning a customer-discovery interview, LEANSpark may offer a practice rep first. It's an offer, never a gate.
## How to use it
The dojo opens on an orientation splash, then runs one step at a time — review before you drill:
1. **Review the interview.** Listen to the recording (player and emotional-trajectory graph pinned at the top) and read the transcript. Just get a feel for the customer's story.
2. **Tune your ear.** A discrimination warm-up — commit to a force, point at the word that tells you, then the answer is revealed.
3. **Find it.** Spot the force in a stretch of real transcript, or correctly reject a stretch that carries none.
4. **Label.** Highlight the soundbites and write the three-act story into a blank canvas, graded against the interview's real forces.
Once you've shown you can hear the forces, the drills fade — you go straight from Review to labeling an interview unscaffolded.
## How it grades you
The dojo tracks a real capability, separate from lesson completion, that advances forward-only:
- **Training** — you did your first discrimination rep.
- **Recognized** — you completed one full labeled rep, with coaching, and a judge confirmed you caught the trigger and the forces (including the subtle Push ↔ Pull).
- **Demonstrated** — across **two different interviews and markets**, you independently reconstructed the causal story and attributed the forces with sound reasoning.
Grading is justification-based, not tag-matching, and it's anti-gaming by design: only your own work advances the rung — never a rep where LEANSpark supplied the answer, and never a passed lesson.
## Common pitfalls
- **Skipping ahead.** The stepper is forward-locked — you can't jump to labeling before you've reviewed and drilled. You can always step back.
- **Letting LEANSpark do the read for you.** Coached help is fine for learning, but only your own independent reps move the rung.
- **Stopping at one interview.** Hearing the forces once isn't the same as hearing them cold on a fresh market — Demonstrated requires a second, different interview.
- **Trusting stated pull at face value.** The most common miss is mistaking what the customer *says* they wanted for the force that actually moved them.
---
### Interview Assessment
Grades how you ran a discovery interview as a skill you build — one focus habit, a redlined transcript, and a prime for next time.
URL: https://leanspark.ai/guides/interview-assessment/
## What it is
After LEANSpark processes a discovery interview transcript, it grades **how well you conducted the interview** against five Running Lean habits — Setup, Learning Frame, Facts Over Fiction, Depth, and Drama & Context. Rather than a pass/fail grade, it frames your technique as a **skill level — Beginner, Intermediate, or Advanced** — so your first interview reads as the start of a practice, not a failure. It also shows which of the four customer forces (Push / Pull / Inertia / Friction) your questions surfaced.
## Where it lives
The **Interview Assessment** tab of any interview that has a transcript.
## What you see
- **Your skill level** and a **mastery strip** — five segments, one per habit, that fill in as you demonstrate each habit across *all* your interviews, with your current growth edge highlighted. The level and strip compound over reps, so practice is visible.
- **One focus habit**, expanded by default — the single highest-leverage thing to work on next, shown with the exact moment from your transcript and a stronger move you could have made.
- **"See this in your conversation"** — jumps straight to that moment in the Transcript tab and highlights it, so you hear it in context.
- **A redlined transcript** — your real conversation marked up where it matters: a red note where a habit slipped, an amber note where a customer opened a door you could have explored. Toggle with **Show coaching annotations** (on the first time, off thereafter for a clean read).
- **A win** — when you ran a habit well, the assessment surfaces that moment in your own words, so you hear what good sounds like.
- **A forward step** — **Try this in your next interview** carries the focus habit into your next upload.
## Before your next interview
When you start your next interview, the upload step shows a short **prime** — the one cue carried from your most recent interview's focus habit (e.g. *"Last time, when your customer showed emotion, ask what that felt like before moving on."*) — so feedback becomes something you can actually try.
## How grading runs
Every interview with a full transcript — uploaded audio, an audio URL, or a pasted transcript — is graded automatically once processing finishes. Older interviews open on a default state with an **Analyze this interview** button to grade on demand. Running the assessment uses a few credits (cost scales with transcript length).
---
### Pitch Stories
The visual home for your four pitches: assembled from your stress-tested canvas, told as stories, and matured through an evidence journey.
URL: https://leanspark.ai/guides/pitch-stories/
## What it is
The Pitch page is the home for the four pitches every founder eventually needs: the **Elevator** pitch, the **Business Model Story**, the **Founder Story**, and the **Mafia Offer**. Each is assembled from your stress-tested canvas rather than a blank template, then rendered as a story: a narrative arc of beats, each colored by the Customer Force doing the work (Push, Pull, Friction, Inertia), with napkin-style storyboard panels that illustrate every version.
## Where it lives
Open **Pitch** from the navigation. The collection page shows your lead pitch up top and the other three alongside, each labeled with the worldview it speaks to. Click any pitch to enter its story view.
## How to use it
1. **Assemble.** Generate the pitch you need next. The beats come from your canvas and evidence, in narrative order, so it's your story from the first draft.
2. **Workshop.** Edit beats inline (each version is kept, so you can always look back) or refine the pitch in chat. Short concept notes on the load-bearing beats explain why each one exists, and writing scaffolds give you a guiding question and a worked example when you're stuck.
3. **Watch it mature.** Every pitch carries a journey rail: **drafted → grounded → practiced → resonating**. The ladder is strict. A pitch practiced on assumed ingredients still reads Drafted; it climbs only as its ingredients get grounded in evidence and its delivery gets real reps.
4. **Deliver.** When you pitch it, the delivery pins the exact version you used, so debriefs point at what you actually said.
## What it needs
Generating a **new** pitch requires your business model to pass its four core stress-test gates. If it doesn't yet, the page steers you into the 7-dimension assessment instead of handing you words that aren't earned. Pitches you've already written are always visible; only new generation is gated.
---
### Create Your First Canvas
Four ways to get your business model into LEANSpark — from a 60-second import to a guided conversation.
URL: https://leanspark.ai/guides/tutorial-create-canvas/
## What you'll learn
Four ways to create a Lean Canvas in LEANSpark, and when to use each one. By the end, you'll have your first canvas ready to stress-test.
## Before you start
You need a LEANSpark account. If you haven't signed up yet, [start here](https://app.leanspark.ai).
## Steps
### Step 1 — Start a new idea
From your dashboard, click **Start a New Idea**. LEANSpark will ask how you'd like to create your canvas.
### Step 2 — Choose your method
#### Method A: Paste a URL (fastest — under 60 seconds)
Best for: Businesses with a landing page or public description online.
Paste the URL and LEANSpark reads the page, identifies the business model elements, and generates a canvas from what it finds.
#### Method B: Upload a PDF (under 60 seconds)
Best for: Existing Lean Canvases, business plans, or pitch decks in PDF format.
Upload your document and LEANSpark extracts the relevant information into canvas format.
#### Method C: Import from Lean Stack
Best for: Users who already have a Lean Canvas on leanstack.com.
Connect your Lean Stack account and import an existing canvas directly — no re-entry needed.
#### Method D: Describe your idea (most thorough)
Best for: Ideas that exist in your head but aren't documented anywhere yet.
Tell LEANSpark about your business in plain English. This is a multi-turn conversation — LEANSpark will ask follow-up questions to fill in the gaps, so expect a few minutes of back-and-forth. The result is typically the most nuanced canvas because it captures how you actually think about your business.
### Step 3 — Review your canvas
Regardless of method, LEANSpark maps your input to the 9 sections of a Lean Canvas: Problem, Customer Segments, Unique Value Proposition, Solution, Channels, Revenue Streams, Cost Structure, Key Metrics, and Unfair Advantage.
## What to look for
- **Coverage**: Did LEANSpark fill all 9 sections? Empty sections often signal gaps in your thinking — that's useful information.
- **Accuracy**: Does the canvas reflect what you actually meant? Edit any section that feels off — the generated canvas is a starting point, not the final word.
- **Method matters**: Import methods (URL, PDF, Lean Stack) are fast but may over-index on marketing language. The conversational method is slower but captures how you actually think about the business. Choose based on what you need right now.
## What's next
Your canvas is the foundation — now stress-test it to find the blind spots. Continue to [Run Your First Stress-Test](/guides/tutorial-stress-test).
---
### Run Your First Stress-Test
Evaluate your canvas across 7 dimensions and surface the risks hiding in your business model.
URL: https://leanspark.ai/guides/tutorial-stress-test/
## What you'll learn
How to run a stress-test assessment that evaluates your business model across 7 dimensions and surfaces your riskiest assumptions.
## Before you start
You need a canvas in LEANSpark. If you don't have one yet, [create one first](/guides/tutorial-create-canvas).
## Steps
### Step 1 — Open your canvas chat
Navigate to your canvas and open the chat panel. This is where you interact with LEANSpark about your business model.
### Step 2 — Ask LEANSpark to stress-test
Type something like "stress-test my canvas" or "run an assessment." LEANSpark will begin evaluating your business model.
### Step 3 — Watch the assessment run
LEANSpark evaluates your canvas across 7 dimensions: Clarity, Desirability, Viability, Feasibility, Defensibility, Mission, and Timing. You'll see it working through each one in real time.
### Step 4 — Review the results card
When the assessment completes, you'll see a results card with color-coded ratings for each dimension — red, yellow, or green.
## What to look for
- **Red dimensions** are existential risks — things that could kill your business if left unaddressed. These get priority.
- **Yellow dimensions** are known unknowns — you have a hypothesis but no evidence yet. These need experiments.
- **Green dimensions** are validated or low-risk — move on to higher-priority items.
- **"Risk" here means uncertainty, not danger.** A red rating doesn't mean your idea is bad. It means you have untested assumptions that need validation.
## What's next
You've got your results — now learn how to read them properly. Continue to [How to Read Your Stress-Test Results](/guides/tutorial-read-results).
---
### How to Read Your Stress-Test Results
Interpret your assessment scores — which risks matter most and what to tackle first.
URL: https://leanspark.ai/guides/tutorial-read-results/
## What you'll learn
How to interpret your stress-test results so you know which risk to tackle first — not just which score to "fix."
## Before you start
You need a completed stress-test assessment. If you haven't run one yet, [do that first](/guides/tutorial-stress-test).
## Steps
### Step 1 — Open your dashboard
Navigate to your canvas dashboard where your assessment results are displayed. You'll see the 7 dimension scores with color-coded ratings.
### Step 2 — Read the dimension scores
Each dimension has a rating (red, yellow, green) and a brief explanation of why LEANSpark scored it that way. Read the explanations, not just the colors.
### Step 3 — Identify your top risk
Look at your red dimensions first. Among those, find the one LEANSpark flags as most critical. This is typically the assumption that, if wrong, invalidates the rest of your model.
### Step 4 — Understand the recommendation
LEANSpark doesn't just score — it recommends what to do next. Read the recommendation for your top risk. It will point you toward a specific type of experiment or validation activity.
## What to look for
- **Sequence matters more than scores.** A business model with three red dimensions isn't three times worse than one with a single red — it just has more untested assumptions. The key is tackling them in the right order.
- **Existential risks first.** If your Customer Segment is wrong, nothing else matters. If your Problem isn't real, your Solution is irrelevant. LEANSpark helps you find the domino that topples everything else.
- **Common misread: "fixing" a score.** The goal isn't to turn red into green on a screen. It's to reduce uncertainty through real-world evidence. A red score that leads to a pivotal interview is more valuable than a green score you never tested.
## What's next
Turn your top risk into action. Continue to [Generate an Interview Guide](/guides/tutorial-interview-guide).
---
### Generate an Interview Guide
Create a structured interview guide from your riskiest assumption — the right questions, in the right order.
URL: https://leanspark.ai/guides/tutorial-interview-guide/
## What you'll learn
How to generate a structured customer interview guide tailored to your specific business model and its riskiest assumption.
## Before you start
You need a completed stress-test assessment with at least one identified risk. If you haven't done that yet, [run your first stress-test](/guides/tutorial-stress-test).
## Steps
### Step 1 — Start from your assessment
Open your canvas chat where your assessment results are visible. The interview guide builds directly on what the stress-test surfaced.
### Step 2 — Ask LEANSpark to generate an interview guide
Type something like "generate an interview guide" or "help me validate my riskiest assumption." LEANSpark will create a guide based on your top risk.
### Step 3 — Review the questions
The guide includes three sections:
- **Opening questions** — Build rapport and understand context without leading the interviewee.
- **Probing questions** — Dig into the specific assumption you're testing. These are the core of the interview.
- **Closing questions** — Capture anything you missed and leave the door open for follow-up.
### Step 4 — Understand the structure
Each question is designed to avoid confirmation bias. Notice how they're open-ended, not leading. They ask about past behavior, not hypothetical futures.
## What to look for
- **Questions map to your specific risk.** If your top risk is Customer Segment, the questions focus on understanding who actually has the problem. If it's Viability, they probe willingness to pay.
- **What good answers sound like.** LEANSpark includes notes on what to listen for — signals that validate or invalidate your assumption.
- **The anti-pattern.** If you find yourself wanting to "explain your product" during the interview, you're selling, not learning. The guide is designed to prevent this.
## What's next
Ready to explore alternative directions? Continue to [Compare Business Model Variants](/guides/tutorial-variants).
---
### Compare Business Model Variants
Create a variant of your canvas and compare two business models side-by-side with data.
URL: https://leanspark.ai/guides/tutorial-variants/
## What you'll learn
How to create a business model variant and compare it against your original — so you can make pivot-or-persevere decisions with data instead of gut feel.
## Before you start
You need at least one canvas with a completed stress-test. If you haven't done that yet, [start here](/guides/tutorial-create-canvas).
## Steps
### Step 1 — Open your existing canvas
Navigate to the canvas you want to explore alternatives for. This becomes your baseline for comparison.
### Step 2 — Create a variant
Ask LEANSpark to create a variant. A variant is a copy of your canvas with one or more key changes — a different customer segment, a different pricing model, a different solution approach.
Tell LEANSpark what you want to change: "What if I targeted enterprise teams instead of freelancers?" or "What if this was a one-time purchase instead of a subscription?"
### Step 3 — Stress-test the variant
Run the same assessment on your new variant. This gives you comparable data across both models.
### Step 4 — Compare dimensions
Look at both assessments side by side. Where do they diverge? Which model has lower risk in the dimensions that matter most to you?
## What to look for
- **Where the variants diverge** tells you what's actually different about the two approaches. If both models have the same red dimensions, the change you made might not address the real risk.
- **Pivot-or-persevere with data.** Instead of debating whether to pivot, you now have two assessed models to compare. The data won't make the decision for you, but it'll make the decision clearer.
- **Variants compound.** You're not limited to two. Create multiple variants to explore the solution space systematically.
## What's next
You've got the core toolkit. Continue to [Your First 14 Days with LEANSpark](/guides/tutorial-first-14-days) for a roadmap of how it all fits together.
---
### Your First 14 Days with LEANSpark
A day-by-day checklist to get the most out of your first two weeks — each step builds on the last.
URL: https://leanspark.ai/guides/tutorial-first-14-days/
## What you'll learn
A practical checklist for your first 14 days with LEANSpark. Each activity builds on the previous one, creating a compounding loop of clarity.
## Before you start
You need a LEANSpark account. Everything else, you'll build along the way.
## Steps
### Step 1 — Day 1: Create your canvas
Start with a description of your idea. Don't polish it — capture what's in your head right now. [How to create a canvas →](/guides/tutorial-create-canvas)
### Step 2 — Day 3: Run your first stress-test
Give yourself a day or two to sit with your canvas, then stress-test it. The gap lets you notice things you'd miss if you rushed. [How to run a stress-test →](/guides/tutorial-stress-test)
### Step 3 — Day 5: Interpret your results
Read your assessment carefully. Identify your top risk — not the lowest score, but the assumption that matters most. [How to read your results →](/guides/tutorial-read-results)
### Step 4 — Day 7: Generate an interview guide
Turn your top risk into a structured conversation. Even if you're not ready to interview yet, having the guide clarifies what you need to learn. [How to generate an interview guide →](/guides/tutorial-interview-guide)
### Step 5 — Day 10: Explore a variant
Create at least one variant of your canvas. Change the thing you're most uncertain about — customer segment, pricing, solution — and stress-test the alternative. [How to compare variants →](/guides/tutorial-variants)
### Step 6 — Day 14: Iterate
Update your original canvas with what you've learned. Run a fresh stress-test. Compare it to your Day 3 assessment. This is the compounding loop in action.
## What to look for
- **The compounding loop.** Each artifact feeds the next: canvas → assessment → interview guide → updated canvas. By Day 14, you're not starting over — you're building on validated understanding.
- **Progress over perfection.** Your Day 1 canvas will look naive by Day 14. That's the point. The goal isn't a perfect canvas — it's a less wrong one.
- **Momentum matters.** The founders who get the most from LEANSpark are the ones who use it consistently, not the ones who use it perfectly.
## What's next
You've completed the tutorial sequence. Explore the full [User Guide](/guides) for deeper dives into specific features like the [Traction Roadmap](/guides/traction-roadmap), [Prospects](/guides/prospects), and [Pitches](/guides/pitches).
---
## MCP
LEANSpark exposes your validated business model to any MCP-compatible AI tool. Connect with: claude mcp add --transport http leanspark https://leanspark.ai/mcp
Overview & connect: https://leanspark.ai/mcp-server
### Build a landing page that uses your real positioning
Generate a landing page in Claude Code, Cursor, or Claude that pulls your actual offer, competitive alternatives, and voice — not placeholder copy.
### Draft content in your own voice
Have any AI tool write posts, emails, and threads that sound like you — using your extracted LEANSpark voice profile.
### Write a sales page or pitch from real evidence
Generate sales copy and pitch narratives grounded in your offer and the exact alternatives and pains your interviews surfaced.
### Prep customer interviews from your segments
Generate an interview guide grounded in your real customer segments and the forces driving their behavior.
## Building LEANSpark
Real-time documentation of building an AI co-founder — from idea spark to product launch.
### Episode 1: The Idea Spark — How LEANSpark Was Born
From ChatGPT's launch in November 2022 to building an AI co-founder in 2025. The 3-year backstory behind LEANSpark.
URL: https://leanspark.ai/building-leanspark/01-the-idea-spark/
When it comes to AI and startups, most people treat AI one of two ways: as an all-knowing oracle or as a tool for automating tasks. LEANSpark is built on a different premise entirely — AI as a co-founder. A thinking partner that can run experiments, learn from feedback, and iterate alongside you.
## The Story
The LEANSpark story started three years before we wrote a single line of code. When ChatGPT launched in November 2022, the world went crazy. Services popped up overnight that could generate startup ideas, Lean Canvases, landing pages, and even starting code. People were already declaring the end of customer research and validation.
I was skeptical. An LLM cannot come up with a successful startup idea on its own with a one-shot prompt. Startups are inherently uncertain — going from 0 to 1 requires non-linear thinking, and that is not how current LLMs work. Challenge an LLM's answer with a different point of view, and instead of holding its ground, it changes its answer to match yours. That does not generate breakthrough thinking — it creates an echo chamber.
So while everyone chased generative AI — asking machines for answers — I was more interested in predictive AI. Not oracles that tell you what to do, but tools and workflows that speed up things hard for humans but simple for machines. One of those things was transcribing customer interviews and finding patterns across them. We built Customer Forces AI in early 2023 to do exactly that, and it became a foundational tool in our demand validation playbook.
Then in early 2025, vibe coding agents changed the game again. Services like Lovable, Replit, and Claude Code could build real working apps autonomously using an agentic loop — a Plan-Code-Test cycle where agents figured out how to complete tasks on their own. I wondered: could we build a similar agentic loop for business model development? The Continuous Innovation Framework already follows a model-prioritize-test cycle. Could an agent help founders run through these steps?
We ran three parallel proof-of-concept approaches. Deterministic workflows were too rigid. But the agentic loop — giving an agent simple tools, a goal, and a way to measure success — was the breakthrough. I prototyped business model stress tests and watched the agent take a Lean Canvas, determine which tests to run, score them, and move to the next one. That derisked the solution in my mind. Dozens of validation recipes I had cataloged over the years could be turned into tools and plugged into this harness.
With 80% confidence we could build it, I shifted to pre-selling it. I launched a Demo-Sell-Build campaign in October and started dogfooding LEANSpark to validate itself — a meta-recursive approach I have used with every product, from my first book to Lean Canvas.
## Key Frameworks
- **Predictive AI vs. Generative AI**: Rather than asking AI for answers (generative), use AI to accelerate analysis humans find slow — like pattern-matching across interview transcripts (predictive).
- **The Agentic Experiment Loop**: Inspired by coding agents, this PDCA-based loop gives an AI agent tools, a goal, and success criteria, then lets it iterate autonomously through business model experiments.
- **Meta-Recursive Dogfooding**: Using your own product to validate itself — becoming both the entrepreneur and the power user to speed up learning cycles.
## Key Takeaways
- The real opportunity in AI for startups is not generating ideas but accelerating the validation process through systematic experimentation.
- Three years of false starts and proof-of-concepts were necessary to find the right approach — agentic loops, not deterministic workflows.
- Dogfooding your own product creates a powerful feedback loop where you experience every friction point your customers will face.
- Selling before building (Demo-Sell-Build) tests whether founders will pay for something before you invest months building it.
- The best AI products are not oracles — they are thinking partners that help you run experiments and learn from the results.
---
### Episode 2: Business Model Stress Testing
Why you should stress test your business model before testing with customers. The 7-dimension framework in action.
URL: https://leanspark.ai/building-leanspark/02-business-model-stress-testing/
You cannot test a vague idea. Most founders rush to validate with customers, but if your business model has obvious cracks in it, you will waste months chasing signals that lead nowhere.
## The Story
I learned this the hard way. Back in 2009, I was building a photo-sharing product. I lined up customer interviews, got enough people to "validate the problem," built an MVP, and even got paying customers. By all accounts, I was doing everything by the book.
Then an advisor destroyed my business model in five minutes. Using a handful of key metrics, he showed me the model was fundamentally broken. The bad news was painful, but what bothered me more was the nine months I wasted pursuing a flawed model that a simple stress test could have caught.
That five-minute conversation became the first of seven foundational stress tests I now apply to every new idea. Think of them as business model simulations — each one applies stress on a specific dimension like desirability, viability, or feasibility, exposing flaws you can fix before investing real resources.
When I loaded my own LEANSpark canvas into the tool and asked it to stress test my idea, the agent immediately flagged something: "Your canvas contains 3 distinct business models mixed together." It identified a founder model, a B2B coach platform, and an investor segment. It was right — I had been keeping placeholders that needed to be split into focused variants. The agent generated three variant canvases in parallel, recommended starting with the founder canvas (the most developed), and then ran the full clarity assessment, scoring it 13 out of 15.
The most transformative stress test was viability. Using my $1M ARR minimum success criteria and rough pricing assumptions, LEANSpark ran a Fermi estimation to check whether my target market was large enough. The math worked for $1M — but it also revealed something bigger. Given the agentic loop's potential and a total addressable market of tens of millions of startups globally, I decided to 10x my goal to $10M ARR. That meant 10,000 customers paying $1,000 per year, which was ambitious but feasible given my growing YouTube channel and the market size.
## Key Frameworks
- **The PDCA Agentic Loop**: Plan-Do-Check-Act applied to business model experiments. LEANSpark reviews your canvas (Plan), runs the stress test (Do), scores results against success criteria (Check), and makes recommendations (Act). This is what makes it different from just chatting with an LLM.
- **7-Dimension Stress Testing**: Mission (why this idea for you), Clarity (is the model focused), Desirability (customer demand signals), Viability (can the math work), Feasibility (can you build it in time), Defensibility (moat building), and Timing (market readiness).
- **The Fermi Viability Test**: Uses your pricing assumptions and minimum success criteria to quickly estimate whether your target market is large enough to hit your goal — a rapid estimation that kills or pivots more ideas than any other test.
## Key Takeaways
- Stress tests do not replace customer validation — they prepare you for it by exposing cracks in your business model design.
- Most starting canvases are "big idea canvases" with multiple business models mixed together that need to be split into focused variants before testing.
- The viability stress test is the most consequential — it either kills your idea, validates it, or pushes you to think bigger about your minimum success criteria.
- Value-based pricing (anchoring against existing alternatives) beats cost-based pricing (anchoring against token costs) every time, especially with AI products.
- Two hours of stress testing can save you months of pursuing a fundamentally flawed business model.
---
### Episode 3: 90-Day Cycle Planning
How to bridge the gap between your 3-year vision and daily tasks. The missing middle that turns strategy into execution.
URL: https://leanspark.ai/building-leanspark/03-90-day-cycle-planning/
Of all the resources in a startup, time is the scarcest. Unlike money or people, which can fluctuate up and down, time only moves in one direction. The theme of this episode is "right action, right time" — how to stay focused on the few key actions that drive the biggest impact and ignore the rest.
## The Story
After stress-testing the LEANSpark business model across all seven dimensions, I had a validation-ready canvas and a $10M ARR minimum success criteria. But having a validated canvas is where most founders get tripped up. Everything on the Lean Canvas is a risk that needs testing, and too many founders spread their limited resources thin by taking on too many things at once. Weeks turn into months with slow progress on everything.
The problem is the Missing Middle. Your 3-year goal is too far out to drive daily decisions, and your daily tasks, without structure, fail to connect to that big goal. 90-day cycles bridge this gap. They are long enough to make meaningful traction progress — you can actually reach 10, 50, or even 100 customers if you stay focused. They are short enough to maintain urgency. And they force prioritization because you simply cannot do everything in 90 days.
There are only twelve 90-day cycles between you and your 3-year goal. Each cycle is driven by a clear traction milestone from your roadmap. For LEANSpark, my first 90-day goal was starting 200 paid trials. Each goal drives specific campaigns — sequences of experiments designed to hit that goal. And each campaign is broken into 2-week sprints, which are long enough to make meaningful progress on an experiment but short enough to maintain focus.
When I asked LEANSpark to design my 90-day cycle, it did not produce a generic template. It analyzed my business model, traction roadmap, and current metrics to identify my primary constraint — acquisition, since we were starting from zero customers. It matched this constraint to the demand validation playbook and suggested a Mafia Offer campaign, then broke the cycle into a planning phase, five core sprints covering problem discovery through offer delivery, and a 3P Progress Review (pivot, persevere, or pause).
The plan was intentionally high-level because no plan survives contact with reality. Only when I accepted the plan and started Sprint 1 did LEANSpark kick off its experiment-level PDCA loop, helping me design the first broad-match problem discovery interviews — building prospecting criteria, drafting an interview script, and suggesting prospecting recipes from our validation cookbook.
The result: 142 founding members and $3,550 in monthly recurring revenue within the first few weeks of execution.
## Key Frameworks
- **The Missing Middle**: The gap between your 3-year vision and daily execution. 90-day cycles provide the intermediate planning horizon that connects strategy to action: Goal leads to Campaign leads to Sprint leads to Experiment leads to Task.
- **Nested PDCA Cycles**: Your startup journey is made up of PDCA cycles running at different time horizons — the outer startup cycle (3 years), the 90-day cycle, and the sprint/experiment cycle (2 weeks). Each level serves as a checkpoint to ensure you are heading the right way.
- **The 3P Review**: Every 90-day cycle ends with a pivot, persevere, or pause decision. This forces honest assessment of progress before committing to the next cycle.
## Key Takeaways
- 90-day cycles are the right planning horizon — long enough for traction, short enough for urgency, and they force you to prioritize ruthlessly.
- The Missing Middle between your 3-year vision and daily tasks is where most founders lose focus and waste time on low-signal experiments.
- Do not over-plan — keep the 90-day plan at a strategic level and only detail experiments when you start each sprint.
- Timeboxing saved LEANSpark from scope creep: the original plan called for 7 specialized agents, but the 90-day constraint forced us down to 3 that could actually ship.
- Every 90-day cycle should end with an honest 3P review — pivot, persevere, or pause — before committing to the next cycle.
---
### Episode 4: Demo-Sell-Build — 0 to 209 Customers in 40 Days
How we validated demand before building the product. The messy middle of going from prototype to paying customers.
URL: https://leanspark.ai/building-leanspark/04-demo-sell-build/
The messy middle is where the real learning happens — the part where you are not 100% sure things will work, you are building the product while talking to customers, and you are figuring out whether founders will even pay for this.
## The Story
It was mid-September. After two weeks of intensive prototyping, I had validated that building an agentic AI co-founder was technically possible. But three massive unknowns remained: Do founders actually want this? Will they pay for it? And can we build enough of it to launch in 2-3 months?
My secret weapon was the Concierge MVP. Instead of building the product first, I became the product. I offered free business model reviews where founders could submit their Lean Canvas and receive a personalized diagnostic. But the real value was not filling my calendar with reviews — it was twofold. First, using each review to learn from customers. Second, incrementally replacing myself with LEANSpark by running each canvas through the prototype first, then tweaking the product to match how I would actually coach a founder.
I used a "give before you get" approach. Instead of emailing founders a diagnostic report, I offered to walk them through it on a call. That was the give. Then at the end, I asked if I could interview them separately — the get. This generated some of the most revealing conversations about how founders were actually validating their ideas.
When I had enough signal from 10 problem discovery interviews, I kicked off the broader Demo-Sell-Build campaign in October. Using my 10x Product Launch playbook, I scaled the hockey stick systematically: 10 customers first, then 100, then aim for 1,000.
For the landing page, I needed a demo — but the product was not built yet. This is where founders get confused. You do not need a working product to build a real-looking demo. I used Claude Code to build a demo runner that could simulate conversations between a founder and LEANSpark. The demos on the landing page were screencasts of these simulated exchanges. Everything shown was not working code at the time, but I was 80-90% confident we could build it.
The campaign ran in stages. Stage 1 launched October 9th with just 10 spots — handpicked from our most active customers. It filled in 6 days. Stage 2 sold out by October 30th. By the time I had stacked an email campaign, a Black Friday bundle, and a referral program in November and December, we had crossed 209 customers and roughly $35,000 in revenue — in about 40 days instead of the 90 I had planned.
The whole time, every Tier 2 customer who paid for a canvas assessment was actually getting a disguised problem discovery interview. The Concierge MVP was not just a sales tactic — it was a continuous learning engine.
## Key Frameworks
- **The Concierge MVP**: You become the product. Deliver value through high-touch services while simultaneously learning from customers and incrementally building the real product to replace yourself.
- **The 10x Product Launch**: Scale the hockey stick instead of letting it play you. Go from 10 to 100 to 1,000 customers, with each level surfacing your riskiest assumption. At 10 customers, you maximize learning. At 100, you start automating. At 1,000, you go self-serve.
- **Offer Stacking**: Incrementally transition from high-touch offers (concierge reviews) to more scalable offers (email campaigns with landing pages) as you gain confidence in your positioning and product.
## Key Takeaways
- You do not need a working product to build a convincing demo — you need to design the product, and a demo runner can simulate real interactions.
- When a customer buys a demo, the demo becomes the best marketing requirements doc: all you need to deliver is what the customer bought.
- The Concierge MVP is the most underrated prospecting recipe — it simultaneously validates demand, generates problem discovery interviews, and iteratively derisks your product.
- Offer stacking lets you transition from learning-focused high-touch campaigns to scalable campaigns without losing the customer insights pipeline.
- Selling in 10x stages (10, then 100, then 1,000) prevents you from drowning in scale problems before you have validated the fundamentals.
---
### Episode 5: Problem Discovery — What Interviews Actually Revealed
The Customer Forces framework applied to real founder interviews. The insight that changed LEANSpark from a tool to a co-founder.
URL: https://leanspark.ai/building-leanspark/05-problem-discovery/
Founders do not struggle with a shortage of things to do. They struggle with focusing on the right things to do, at the right time. That single insight changed everything about how we designed LEANSpark.
## The Story
Throughout October and November, I conducted problem discovery interviews using the Concierge MVP reviews as my entry point. Every founder who signed up for a canvas assessment got a personalized walkthrough — and at the end, I asked if I could interview them separately to understand how they were currently validating their idea.
I used the Customer Forces framework, which views every customer journey through four lenses: Push (what drives them to seek a new solution), Pull (what attracts them toward a specific solution), Inertia (what keeps them stuck with their current approach), and Friction (what creates anxiety about switching).
The framing was deliberately broad. I did not ask "Tell me how you use AI." Instead, I asked "Tell me how you are currently validating your idea" — what occupies their attention, what tools they use, and how they use them. This broad-match approach prevented me from falling into the local maxima trap of only talking to AI enthusiasts and missing the bigger market.
Three findings shaped everything that followed. First, every founder I spoke with had already tried some AI tools in their startup process. This was relevant for positioning — if everyone was already using AI, then AI tools were the true competition to anchor against. Second, the use cases were scattered: research with Perplexity, brainstorming with Claude Projects, interview analysis, coding, marketing campaigns. No single dominant use case.
But the third finding was the breakthrough: the Context Switching Tax. Founders context-switch constantly between building, talking to customers, fundraising, managing teams, and learning new frameworks. And on top of that, they have to manage the context window of their AI tools. Every conversation starts from scratch. They are constantly re-explaining who they are, what their startup does, what they have already tried, and what they are trying to do now.
I started calling this the Memento problem, after the movie where Guy Pearce wakes up every day with no short-term memory, relying on notes and tattoos to remember who he is. That is what using most AI tools feels like for founders — a constant re-orientation with no memory of past sessions.
The counterpoint was the Matrix. In the movie, characters download programs just-in-time and instantly learn new skills. That is what good AI should feel like. Load massive context in seconds, remember everything, and learn new skills on the fly.
This insight shifted LEANSpark from being a collection of discrete workflow tools — run a stress test here, generate a pitch there — to being an AI co-founder that remembers who you are, where you are in your journey, and what your next right action should be. Every session starts with a summary of where you left off, not a blank prompt.
## Key Frameworks
- **Customer Forces**: Innovation is about causing a switch from an old way to a new way. Map the four forces — Push, Pull, Inertia, and Friction — to understand why customers switch (or do not).
- **Broad-Match vs. Narrow-Match Interviews**: Start broad to map the opportunity space without selection bias, then narrow to validate specific use cases and go deeper on struggles, pet peeves, and workarounds.
- **The Context Switching Tax**: The compounding cost of constantly re-establishing context — both at the founder level (switching between roles) and at the AI tool level (re-explaining everything each session).
## Key Takeaways
- Good problem discovery is not about validating a list of problems — it is about naturally uncovering struggles by focusing on specific workflows customers are already running.
- Start broad with interviews to avoid selection bias, then narrow once you identify underserved problems your product can address.
- The Memento problem — every AI session starting from scratch with no memory — was the single biggest pain point founders experienced across all tools.
- The shift from "AI coaching tool" to "AI co-founder" came directly from understanding that founders want continuous context, not discrete interactions.
- Not all discovered use cases need to fit your product — explore adjacent workflows (what happens before and after) to find where your unique value lies.
---
### Episode 6: Solution Design — From Insights to MVP
How customer insights shaped the actual product. The framework for prioritizing wants over needs.
URL: https://leanspark.ai/building-leanspark/06-solution-design/
Most products fail not because they lack features, but because they confuse needs with wants. Features are needs — they live in the solution context. Outcomes are wants — they live in the bigger context. And customers care far more about their wants than their needs.
## The Story
After weeks of problem discovery interviews, the insights were clear. Founders were not lacking frameworks or tools. They knew about Lean Startup, Jobs-to-be-Done, and a dozen other methodologies. The problem was putting it all into practice consistently, while managing the crushing context-switching tax of startup life.
This led to the most important design decision in LEANSpark: wants before needs. Originally, we had been thinking about building discrete workflow tools — an elevator pitch generator, a business model assessment, a specific stress test. These are needs. They are the broccoli of startup validation — good for you, but not what gets founders excited in the morning.
What founders actually want is traction. If you have not launched, how do you go from idea to first paying customers? If you have launched, how do you acquire more? Time-boxing that outcome to 90 days made the promise specific and actionable: helping founders run 90-day validation cycles became the primary job to be done for LEANSpark.
Using the Customer Forces model, I visualized this as a hill. The desired outcome — traction in 90 days — sits at the top. To get there, founders need to do hard things: create business models, stress-test them, talk to customers, design experiments, run campaigns. Each of those is a friction point on the path to the summit. The secondary jobs to be done became about reducing friction around those hard things, not adding more features.
This reframing shaped the Demo-Sell-Build landing page: a clear UVP targeting the want (validate faster, build with confidence), with three core features addressing the top three friction points — learning the framework, stress-testing business models, and running 90-day experiments.
With the product direction set, we shifted to achieving Product/Launch Fit. Most founders think launch day is about finishing the MVP and doing a big-bang release. But there is much more to it. We designed the value delivery journey using a Progress Reward Loop — mapping what a customer can experience in the first 30 seconds, first few minutes, first hours, days, and weeks. We worked through pricing models that balanced value-based pricing against real AI usage costs. And we planned a batched rollout — 10 customers at high-touch concierge, then 100 in semi-automated cohorts, then 1,000 at self-serve — with each batch giving us time to learn, fix issues, and improve.
The 100X Founder workshop emerged from this same principle. Rather than just handing founders a tool, we offered a 13-week cohort-based program to guide teams through a complete 90-day validation cycle using LEANSpark — the done-with-you layer on top of the do-it-yourself product.
## Key Frameworks
- **Wants vs. Needs**: Features are needs (solution context); outcomes are wants (bigger context). Good products target the want as the destination and remove friction from the needs standing in the way.
- **Product/Launch Fit**: The short game before Product/Market Fit. Scale in 10x stages — 10 customers (high-touch, manual), 100 (semi-automated, cohort-based), 1,000 (automated, self-serve) — proving you can deliver value at each level before scaling further.
- **The Progress Reward Loop**: Map the customer journey from first touch to habit formation using a doubling progression. What value can you deliver in 30 seconds, a few minutes, a few hours, a day, a week?
## Key Takeaways
- Target the want (traction), not the need (features). Founders do not wake up wanting to run a stress test — they want paying customers.
- Features equal needs, outcomes equal wants. Good product design reduces friction on the path to the desired outcome rather than adding more features.
- Product/Launch Fit is the short game before Product/Market Fit — prove you can deliver value to 10, then 100, then 1,000 customers before trying to scale.
- Batched rollouts beat big-bang launches because each batch gives you time to learn and improve before the next wave of customers arrives.
- The best launches combine a self-serve product tier with a done-with-you coaching tier — meeting customers where they are in their readiness to adopt.
---
## Blog
### Your Pitch Is a Story. Stop Reciting a Script.
Template pitches all sound the same because they are the same. LEANSpark now builds your four pitches as stories, assembled from your stress-tested canvas.
URL: https://leanspark.ai/blog/your-pitch-is-a-story/
Investors can smell a template from the second slide.
Here's how it happens. A founder downloads the ten-slide deck outline everyone recommends. Problem, solution, market size, team. She fills in her nouns, rehearses the transitions, and delivers it clean. The investor nods politely and passes. So does the next one.
That's the mad-libs pitch. You borrowed someone else's structure and poured your words into the blanks. It's grammatically correct and completely forgettable, because the person across the table has heard the same skeleton forty times this month. A script tells them about your product. Only a story makes them feel the switch.
But here's the thing. A pitch was never a summary of your business. It's the story of a customer moving from an old way that stopped working to a new way that does, and why now. You already have the raw material. It's sitting in your canvas.
So LEANSpark now builds your pitches as stories.
## Four pitches, one home
The Pitch page is now the visual home for all four pitches you'll need: the **Elevator** pitch for the hallway, the **Business Model Story** for the whole model, the **Founder Story** for why you, and the **Mafia Offer** for the moment you ask someone to buy. Each is assembled from your stress-tested canvas, not from a blank template, so the beats are your evidence, in narrative order.
Open any of them and you get a story view, not a slide list: a narrative arc with each beat colored by the Customer Force doing the work (Push, Pull, Friction, Inertia), inline editing, and short concept notes that teach why each beat exists.
Your pitch even illustrates itself: every version gets napkin-style storyboard panels, and when you edit a beat, only that panel redraws.
## Here's the kicker: you have to earn the pitch
Generating a new pitch requires your model to pass its four core stress-test gates first. If it can't, LEANSpark doesn't hand you prettier words. It steers you into the assessment to fix the model, because you can't pitch your way out of an unvalidated business. Polish on top of a broken model is just a better-lit collapse.
## A pitch isn't done when it's written
Every pitch carries a journey: **drafted, grounded, practiced, resonating**. Writing it is the start. Grounding it in evidence, practicing the delivery, and watching it land with real audiences is the work. And the ladder is strict: a pitch you've practiced on assumed ingredients still reads Drafted, because rehearsing a guess doesn't make it true.
Startups are stories. Your customer's interview is one. Your pitch is one. The founders who win are the ones who can tell the story of the switch better than anyone else in the room.
Open your Pitch page, pick the pitch you'll need next week, and read it out loud. If it doesn't sound like a story, you now have the tool to fix that.
---
### Your Customer Interview Isn't Data. It's a Story.
You ran the interview and got a transcript and a pile of quotes. But your customer's decision to switch was never data. It was a story. Now LEANSpark tells it back to you as six scenes.
URL: https://leanspark.ai/blog/startups-are-stories/
Watch an interview become a story.
A customer bought a new phone. It didn't have a headphone jack. Just like that, the wired earbuds he loved were useless, and he was shopping for something he never wanted to shop for.
That's not a data point. That's a Push, and it's scene one. Then came the search for a USB-C adapter he couldn't find at a price he'd pay. That's Friction. He gave up and accepted Bluetooth. He texted friends on the way to the store, spent ten minutes comparing, and hired a mid-tier pair on price and ear-tip shape. And the ending isn't clean: they slip when he runs, so he's still hunting for a way back to his old earbuds for workouts.
Six scenes. A beginning, a middle, and an unfinished end. A person feeling something the whole way through.
Here's the thing. You ran interviews exactly like this one. You have the transcript, the highlighted quotes, the notes. But you can't *see* the story in a transcript, and the story is the thing you interviewed to find: why they moved, in what order, and the moment the old way stopped being good enough.
So we stopped flattening it.
## The interview, retold as six scenes
LEANSpark now takes a completed discovery interview and rebuilds it as a Customer Forces Story. Same spine every time: old way breaks, job requirements form, they hire something, first use, repeat use, the switch. Because switching decisions actually follow that arc, whether the customer can name it or not.
Each scene is driven by one of the four forces. Push, when the old way fails. Pull, when the new way calls. Friction and Inertia, the two that keep people stuck. The panel names the force that did the work and puts the verbatim quote right under it, drawn in napkin-sketch style so it reads like a comic strip, not a report. Underneath runs a journey map where the terrain is the customer's sentiment: it climbs on hope, dips at every wall.
## Why a story beats a spreadsheet
You can't feel a spreadsheet, and you can't put one in front of your co-founder and end the argument about who the customer is and why they'd switch. A story does both.
It also shows you your gaps. The scenes the interview never reached render as ghost panels, dimmed, each holding the question you should have asked. That's your next interview's opening question, handed to you.
## What to do with it
Run your next discovery interview. When the analysis finishes, open the Customer Forces Story tab and read the decision as the story it always was. Then look at the ghost panels and write down what you didn't ask.
Startups are stories. We're going to keep saying that and keep building it into the product, because the founders who win are the ones who can tell their customer's story better than the customer can. This is where we start.
---
### You Can't Elicit a Force You Can't Hear
AI made building easy. The bottleneck is now knowing what to build — and the skill that gets you there is harder than it looks. Here's a better way to learn it.
URL: https://leanspark.ai/blog/customer-forces-dojo/
AI made building easy. That's the problem.
When a founder can ship a working app over a weekend, building stops being the bottleneck. Knowing *what* to build becomes the whole game. And the only reliable way to figure that out is the same as it's always been: talk to the people with the problem.
So you'd think customer interviews would be the first skill every founder masters. They're not.
## The skill everyone says they have and almost no one does
I've spent over a decade teaching founders to run interviews. The advice fits on an index card. Chase the problem, not your solution. Don't ask leading questions. Learn, don't pitch.
Every founder nods. Then I sit in on a real interview and watch the same thing happen.
The customer mentions, in passing, the thing they did right before they went looking for a new tool — the actual switching moment — and the founder skips right past it to ask whether they'd pay $49 a month. The signal was right there. They couldn't hear it.
That's the gap nobody warns you about. The tactics are easy to memorize and hard to execute, because the hard part isn't knowing the rules. It's *perception* — catching the force in real time, in a messy conversation, fast enough to act on it.
## Memorize-then-drown
Here's how most people try to close that gap: read a book on interviewing, write down a list of questions, then book a call with a real customer and hope.
It's the equivalent of reading about swimming and jumping into the deep end. You don't come up with technique. You come up flailing — and worse, you've burned a real customer conversation you can't get back.
You can't learn to hear something by reading about it. You learn it by hearing it. Over and over. On examples where someone already knows the right answer.
## Perceptual learning: how you actually build an ear
There's a name for this, and it's not new. Pilots, radiologists, and musicians all train it: **perceptual learning**. You expose yourself to many real examples, make a fast call on each, get immediate feedback, and let your brain quietly tune itself until the pattern jumps out at you.
A radiology resident doesn't learn to spot a tumor by memorizing a definition. They read thousands of scans with the answer key next to them, until the anomaly stops hiding. The knowing becomes seeing.
Customer interviews work the same way. The forces behind a customer's decision — the trigger that started their search, the push of their old frustration, the pull of the new outcome, the inertia and anxiety holding them back — are all sitting in the recording. Hearing them is a perceptual skill. And perceptual skills are trainable, at no stakes, before you ever talk to a real person.
## The Customer Forces Dojo
That's what we just built into LEANSpark.
The Customer Forces Dojo is a no-stakes place to train your ear on a real, expert-run interview before you run your own. You open a recorded interview in simulation mode and work through a short, stepped flow:
1. **Review the interview.** Listen to the recording and read the transcript. No labeling yet — just get a feel for the customer's story.
2. **Tune your ear.** A discrimination warm-up: commit to which force you're hearing, point at the exact word that tells you, *then* see the answer. Evidence first, no peeking.
3. **Find it.** Spot the force in a real stretch of transcript — or correctly call out a stretch that carries none.
4. **Label.** Highlight the soundbites and write the customer's three-act story into a canvas, graded against the interview's own forces.
A judge reads *why* you attributed each force — not whether your tag matched a label. The most common miss it's built to catch is the subtle one: mistaking what a customer *says* they wanted (the stated pull) for the force that actually moved them.
Once you can hear them cold, the scaffolding fades. You go straight from review to labeling an interview unassisted.
## It grades the skill, not the busywork
The dojo tracks a real capability that advances forward-only: Training → Recognized → Demonstrated.
And it's deliberately hard to game. Only your *own* reps move the needle — never a rep where LEANSpark handed you the answer, never a lesson you clicked through. To reach Demonstrated, you have to reconstruct the story and attribute the forces yourself, with sound reasoning, across **two different interviews in two different markets**. Hearing it once on one customer isn't proof you can hear it cold on a stranger.
When you get there, LEANSpark doesn't hand you a trophy. It replays your own growth: "on the first interview you missed the inertia; on the second you caught it cold."
## Train the ear before the conversation
Building was never the hard part. Hearing the customer is. And the founders who win the AI era won't be the ones who ship fastest — they'll be the ones who know what's worth shipping.
The dojo is live now. Open it from the **Skills** page, or just tell LEANSpark you want to get better at customer interviews.
Listen to an expert interview. Capture what you hear. Let your brain do the rest.
[Train your ear in the Customer Forces Dojo →](https://leanspark.ai/guides/customer-forces-dojo/)
---
### Your First Customer Interview Doesn't Deserve an F
A grade tells you that you failed. It doesn't teach you the skill. Here's how we rebuilt interview feedback into a coaching loop that compounds.
URL: https://leanspark.ai/blog/interview-assessment/
A founder works up the nerve to run their first real customer interview. They get through it. Then the tool hands back a grade: C-minus. "You pitched instead of learning. You asked leading questions."
All true. And almost completely useless.
## A grade is not feedback
A letter grade tells you one thing: you failed. It doesn't tell you what to do differently, and it lands hardest on exactly the person who needs encouragement most — the founder who just did the scary thing and talked to a stranger about their problem.
I've spent over a decade teaching founders to run interviews. The hard part was never naming the mistakes. Everyone can recite them: chase the problem, don't pitch, don't lead the witness, learn instead of sell. The hard part is that *knowing* you lead the witness doesn't stop you from doing it again in the next conversation. Skills don't transfer from a report card. They're built one rep at a time.
So we threw out the grade.
## From report card to coach
LEANSpark already assessed how you ran a discovery interview — across five habits drawn from Running Lean: Setup, Learning Frame, Facts Over Fiction, Depth, and Drama & Context. What changed is everything about how that assessment talks to you.
**A skill level, not a grade.** Your technique now reads as Beginner, Intermediate, or Advanced — so your first interview is the start of a practice, not a failure. A **mastery strip** shows five segments, one per habit, that fill in as you demonstrate each one across *all* your interviews. Your growth edge is highlighted. The level and the strip compound over reps, so practice is something you can see.
**One focus habit, not ten faults.** The assessment expands the single highest-leverage thing to work on next — shown with the exact moment from your transcript and a stronger move you could have made. One thing. The one that will change the most.
**A redlined transcript.** Your real conversation, marked up where it matters: a red note where a habit slipped (pitching instead of learning), an amber note where a customer opened a door you could have explored. "See this in your conversation" jumps you straight to that moment in the transcript and highlights it, so you hear it in context. Coaching notes default on the first time so they're easy to find, and toggle off after for a clean read.
**A win, too.** When you ran a habit well, the assessment surfaces that moment in your own words — so you also hear what good sounds like.
## The part that makes it compound
Feedback you read once and forget changes nothing. So the loop closes forward.
When you start your next interview, the upload step shows a short **prime** — the one cue carried from your most recent interview's focus habit: *"Last time, when your customer showed emotion, you moved on. This time, ask what that felt like before moving on."*
That's the whole difference between a grade and a coach. A grade ends the conversation. A coach hands you one thing to carry into the next rep — and then checks whether you did it. Each interview makes the next one sharper.
## Why this matters now
When anyone can build in a weekend, the bottleneck isn't building — it's knowing what to build. And the only way to know is to talk to customers and actually hear them. Last week we shipped the [Customer Forces Dojo](https://leanspark.ai/blog/customer-forces-dojo/) to train that ear *before* you interview. This is the other half: a coach that works *after*, on your real conversations, and compounds.
Talking to customers is the most important skill a founder can build right now. It deserves to be taught like a skill — not graded like an exam.
Open the **Interview Assessment** tab on any interview with a transcript. Run one, read the one habit it hands you, and carry it into the next.
[See your interview assessment →](https://leanspark.ai/guides/interview-assessment/)
---
### Time is the Forcing Function
Why founders get stuck mid-cycle, and how letting the calendar own your sprint timing turns a 90-day plan into a system that actually advances.
URL: https://leanspark.ai/blog/time-is-the-forcing-function/
You write down a 90-day plan. You break it into sprints. You pick the first experiment.
Two weeks later, you're supposed to run a small ceremony — review what landed, adjust what didn't, advance the sprint. Instead, you find a reason. The week is busy. The data isn't conclusive yet. You'll catch up next week.
Procrastination compounds. The cycle drifts. By week six you're running on inertia, not learning.
If you've felt that shape in your own work, you're not alone. We see hundreds of founders inside LEANSpark hit this same wall — not at the *experiment*, but at the *transition between sprints*. They have the canvas, the campaign, the first experiment. The mechanism that's supposed to advance the sprint waits for them to push a button. They don't push it.
The fix isn't more discipline. It's a different theory of how time should work in a validation cycle.
## Time as a container vs. time as a forcing function
Most validation frameworks treat time the same way most calendars do — as a container. You decide when to start. You decide when to advance. You decide when to wrap. Time bends to you.
That sounds founder-friendly. In practice it does the opposite.
When the founder owns every transition, every transition becomes a decision. Every decision becomes a moment to procrastinate. And procrastination — not failure — is what kills most validation cycles.
The reframe: **time isn't a container, it's a forcing function.**
A forcing function is any external constraint that converts a someday-decision into a now-decision. A flight at 7 a.m. forces the packing. A demo on Friday forces the build. The deadline doesn't *help* you decide — it *makes* you decide.
The same logic applies inside a validation cycle. If the calendar advances on the dot, you don't decide whether to move forward. You decide what you learned in the last fourteen days.
Parkinson's law does the rest: work compresses to fit the time you actually give it.
## Why founders procrastinate transitions (and not the work itself)
Most founders aren't lazy at the *work*. They run interviews, ship MVPs, talk to customers. The procrastination clusters at a specific moment — when one block of work ends and the next is supposed to begin.
Three things make transitions hard:
**1. The data is never quite "ready."** You always feel like one more day, one more interview, one more iteration would clarify things. So you stall the transition rather than admit you've learned what you're going to learn this round.
**2. The next decision feels heavier than it is.** Advancing a sprint isn't actually a one-way door — you can refine, split, or abandon at the next boundary too. But in the moment, it feels final, so you defer.
**3. There's no external cost to deferring.** A self-managed sprint doesn't end if you don't end it. Nothing happens. The cost shows up weeks later, as drift you can't trace back to a specific day.
A forcing function neutralizes all three. The boundary fires whether the data is ready or not. The decision becomes "what did I learn?" instead of "is it time?" And the cost of *not* showing up to the boundary is that the sprint advances anyway, with whatever evidence you have.
## What this looks like as a practice
Three rules turn time into a forcing function inside a 90-day cycle:
### 1. Lock cycles to a calendar boundary you don't control
The cleanest boundary is the calendar quarter — every founder runs the same dates, every cycle starts on a Monday, every cycle ends on a Sunday thirteen weeks later. But the principle is platform-independent. Pick a recurring boundary you can't easily move and align your cycles to it.
Why "can't easily move" is the operative phrase: a boundary you can renegotiate isn't a forcing function. The point is to give up that flexibility on purpose.
### 2. Make sprints fixed time slots, not playbook steps
Most founders equate sprints with playbook steps — *Sprint 1 is discovery, Sprint 2 is narrow match, Sprint 3 is solution design*. The trouble: real experiments don't respect that mapping. Some discovery work takes one sprint, some takes three. When the playbook says "advance," reality often says "I'm still learning."
Decouple them. Sprints are two-week time slots — empty containers. Experiments are the work — variable-length, owned by campaigns that span multiple sprints.
When the boundary fires, the experiment doesn't have to be done. It just has to be *reflected on*. The default action is "continue with what we learned this sprint."
That decoupling is what lets you run multiple campaigns in parallel — say, a Mafia Offer campaign and a content-marketing campaign in the same two-week window — without the schedule collapsing.
### 3. Force a renewal conversation at every cycle boundary
For every active campaign, force a four-way decision at the end of each 90-day cycle: **continue, pause, complete, or abandon.** No defaults. No "we'll see."
Inertia is what turns a 90-day cycle into a 270-day cycle that nobody can audit. Campaigns that can't survive a "is this still paying off?" conversation shouldn't carry over. The renewal conversation is what turns inertia off.
## What the grid looks like
The structure is deliberately boring.
One grid. Every founder. The same cadence.
Six 2-week sprints plus one review week is 13 weeks, which is 91 days, which is the actual length of a calendar quarter. The review week is for the retrospective and the next-cycle setup — no new work scheduled there. It's structural rest with a purpose.
The grid does a lot of quiet work. It tells you the boundaries are real. It tells you exactly when the next forcing function fires. And it makes the question "should I advance?" disappear, because the answer is "the calendar already did."
## The objections, answered honestly
**"What if I'm not ready when the quarter starts?"**
Join the quarter that's running. Your first cycle might be six weeks instead of thirteen. Treat it as a practice run. Your next cycle is a full thirteen — and by then you've already absorbed the rhythm.
**"What if my experiment isn't done at the sprint boundary?"**
Most experiments aren't. The default action at every boundary is *continue* — the experiment carries forward. The boundary doesn't kill the work. It forces a conversation about what you learned in the last fourteen days. That conversation is the point.
**"Won't I feel rushed?"**
Probably. That's the trade. Most founders aren't suffering from too little time — they're suffering from too few decisions. A fixed deadline compresses decisions. Compressed decisions surface the constraint. The constraint is what you came here to find.
**"What if I'm a side-project founder with two hours a week?"**
The cadence is the same; the work density is yours to set. A 2-hours-a-week founder running on the calendar still gets the same biweekly forcing function — they just run smaller experiments inside it. The pace adapts. The structure doesn't.
## How this works inside LEANSpark
Inside LEANSpark, calendar cycles run on autopilot:
- Every founder lands on the current quarter at signup. The Universal Calendar above is the actual onboarding view — you can see exactly where you sit on the grid before you commit to anything.
- Sprints **auto-advance** at midnight in your local timezone on the boundary day. There's no button to push.
- At each sprint boundary, every active experiment surfaces a short reflection prompt: *Continue, Split, Complete, or Abandon?* The default is **Continue**, with this sprint's learnings appended.
- Multiple campaigns can run in parallel — useful when your traction work and your content work both need to ship in the same two weeks.
- At the cycle boundary, the renewal conversation fires automatically for each active campaign. Don't renew? It auto-pauses. Inertia is off by default.
The methodology underneath — Continuous Innovation, Lean Canvas, problem/solution interviews, mafia offers, traction roadmaps — is unchanged. What's different is the timing layer that runs underneath it.
## The takeaway
Validation programs don't fail because founders don't know what to do. They fail because founders carry the timing — and humans procrastinate transitions.
Take the timing off the founder. Put it on the calendar. The work that compounds on top of that is yours. The procrastination that used to compound on top of it isn't.
The next sprint boundary fires Monday. Ready or not.
That's the point.
If you want the structural argument for *why* 90 days is the right cycle length to begin with, start with [The 90-Day Validation Cycle](/blog/90-day-validation-cycle).
---
### The 90-Day Validation Cycle
How to bridge the gap between your 3-year vision and daily tasks. The missing middle that turns strategy into execution.
URL: https://leanspark.ai/blog/90-day-validation-cycle/
You have a validated canvas. Fifty possible experiments you could run. Ninety days until you run out of money.
Which experiment do you run first?
Most founders either freeze from analysis paralysis or, worse, try to run all fifty experiments at once and make slow progress on everything. I used to do this myself. Of all the resources in a startup, time is the scarcest -- because unlike money or team size, which can fluctuate up and down, time only moves in one direction.
## The Missing Middle
Every startup operates between two planning extremes.
At one end, you have your 3-year Minimum Success Criteria. For LEANSpark, that was building a $10M ARR business with 10,000 customers paying $1,000/year.
At the other end, you have daily execution -- the specific experiments and tasks you run to make progress.
The problem is that your 3-year goal is too far out to drive daily decisions. And your daily tasks, without structure, fail to connect to that big goal.
That gap is the Missing Middle. And the 90-day validation cycle is how you bridge it.
## Why 90 Days
Ninety days is the perfect planning horizon for three reasons:
1. **It's long enough to make meaningful traction progress.** You can actually get to 10, 50, or even 100 customers in 90 days if you're focused.
2. **It's short enough to maintain urgency.** There's no time to waste on low-signal experiments.
3. **It forces prioritization.** You can't do everything in 90 days. You have to pick your riskiest assumptions and test them systematically.
Think of your startup journey as a series of 90-day cycles toward your 3-year goal. There are only 12 of them. Each one matters.
## The Structure: Goal to Task
Every 90-day cycle follows a clear hierarchy:
### Goal
A traction milestone that comes from your traction roadmap. For LEANSpark, this was starting 200 paid trials in 90 days.
### Campaign
A sequence of experiments designed to hit the goal. Think of the Mafia Offer campaign from my Demand Validation Playbook -- it's a campaign made up of many smaller experiments.
### Sprint
Two-week timeboxes that make campaigns actionable. Long enough to make meaningful progress on an experiment, short enough to maintain focus and urgency.
### Experiment
Each sprint contains experiments structured around the PDCA cycle -- Plan (design the experiment), Do (run it), Check (measure results), Act (decide next steps).
### Task
The atomic units of work within each experiment. Planning tasks, execution tasks, measurement tasks, and decision tasks.
## Timeboxing Forces Prioritization
In a 90-day cycle, you can fit roughly 5 core sprints (plus time at the beginning for cycle planning and the end for review). Every 90-day cycle ends with a 3P review: Pivot, Persevere, or Pause.
This constraint is the entire point. You cannot run 50 experiments in 5 sprints. You might get through 5 well-designed experiments. That means you have to choose the 5 that matter most -- the ones that test your riskiest assumptions first.
When I ran LEANSpark through cycle planning, the system analyzed my business model, found that my primary constraint was acquisition (we were starting with 0 customers), matched on the Demand Validation Playbook, and suggested a mafia offer campaign broken into:
- Broad-match problem discovery
- Narrow-match problem discovery
- Solution design
- Mafia offer delivery
- A 3P progress review
## Nested PDCA Loops
If you zoom out, the entire system is made up of PDCA cycles running at different time horizons:
**The Startup Loop** -- Plan your big idea, then iterate to a plan that works within your 3-year timebox.
**The 90-Day Loop** -- Plan the cycle, run 5 core sprints, review progress, and make a 3P decision.
**The Sprint Loop** -- Design an experiment, declare expected outcomes, run it, learn, and decide what comes next.
These nested cycles serve as checkpoints to make sure you're frequently pausing to verify you're heading the right way -- instead of blindly speeding at a hundred miles an hour toward a cliff.
## The Takeaway
Strategy without execution is just a wish list. Execution without strategy is just busyness. The 90-day cycle connects the two by giving you a structured, timeboxed system for turning your 3-year vision into focused weekly action.
Start with your MSC. Break it into 90-day goals. Design campaigns to hit each goal. Execute in 2-week sprints. Review and adjust every 90 days.
The structure is simple. The discipline of sticking to it is what separates founders who make progress from those who stay busy.
I walk through this in detail in [Episode 3 of Building LEANSpark](/building-leanspark/03-90-day-cycle-planning).
---
### The 7-Dimension Business Model Stress Test
Why you should stress test your business model before testing with customers. A framework for systematic validation across 7 dimensions.
URL: https://leanspark.ai/blog/7-dimension-business-model-stress-test/
Most founders think the first step after getting an idea is to build an MVP or run outside the building to start testing with customers.
I used to think the same way. Back in 2009, when I first learned about customer development and lean startups, I immediately started lining up customer interviews for a photo sharing product I was working on. I got enough people to "validate the problem," built an MVP, and even got paying customers. By all accounts, I was doing everything by the book.
Then an advisor destroyed my business model in less than 5 minutes. Using just a handful of key metrics, he showed me the model was broken. While this was certainly bad news, the conversation helped me confront reality and make a hard pivot. But what bothered me even more was the 9 months I wasted pursuing a flawed business model that I could have avoided if I knew about this 5-minute stress test.
That experience changed how I approach every new idea.
## Why Stress Test Before You Validate
The problem with rushing to validation is two-fold.
First, most starting ideas are too vague or fuzzy. You can't test a vague idea.
Second, many foundational risks can and should be stress-tested inside the building because they make your idea more bulletproof and validation-ready. They help you avoid wasting resources on sub-optimal ideas.
Think of stress tests as business model simulations. Each one applies stress on a specific dimension of your business model -- like desirability, viability, or feasibility -- and helps you expose obvious cracks so you can fix them before you invest significant time, money, and effort.
The best part: these tests can be done as thought experiments. They don't replace customer validation. They prepare you for it.
## The 7 Dimensions
Here are the seven dimensions I now apply to every new idea:
### 1. Mission
Why this idea, for you? The primary deliverable here is a concrete Minimum Success Criteria (MSC) -- the smallest outcome that would deem your project a success 3 years from now. For LEANSpark, my initial MSC was $1M ARR, which I later 10x'd to $10M ARR after running the viability stress test.
### 2. Clarity
Most ideas start out as many possibilities mixed together. The clarity test splits them into focused variants so each canvas has a single business model that is concise, precise, and complete.
### 3. Desirability
This dimension checks for customer demand using the Innovator's Gift concept: all new problems worth solving come from addressing old problems with new innovative solutions. It ensures you have an old way defined, you outline what's broken with it, and you articulate how you're significantly better to cause a switch.
### 4. Viability
This is the dimension that kills or pivots more ideas than any other. The rapid viability or Fermi test uses your pricing model assumptions and MSC to check if your target market is big enough to hit your goal. Simple math, but it forces hard decisions.
### 5. Feasibility
This is where you turn your big, ambitious goal into smaller, more actionable 90-day goals and experiments. It helps you chart a year-by-year traction roadmap and confront whether the scope is realistic.
### 6. Defensibility
Moat building is about creating deterrents to being copied by incumbents or copycats. Good unfair advantages don't come from features but from things that cannot be easily copied or bought -- personal authority, proprietary data, network effects.
### 7. Timing
Hard to time perfectly, but you can check for markers: inflections (technology shifts), impacts (new possibilities customers are already realizing), and insights (contrarian founder beliefs that shape product and strategy).
## How This Played Out with LEANSpark
When I ran LEANSpark through these stress tests, the very first one -- clarity -- flagged something immediately: my canvas contained 3 distinct business models mixed together. One for founders, one for coaches (incomplete revenue model), and one for investors (no clear monetization).
If I had skipped stress testing and gone straight to customer interviews, I would have gotten confusing signals. Some would want self-service. Some would want white-label. I would have been validating 3 businesses at once without realizing it.
The viability test was equally eye-opening. At $1,000/year pricing and a $10M ARR goal, I need 10,000 customers. With a 1% conversion rate, that requires a top-of-funnel of 1 million founders. The total addressable market of founders is 10-100 million startups created globally each year. Hard numbers, but not impossible.
Most founders take 2-4 weeks to work through all seven stress tests. With structured tooling, I believe you can compress that to hours or days.
## The Takeaway
Slow down just enough to ensure you're not blindly rushing into a hairpin turn on a race track. Stress tests don't replace customer validation -- they make it dramatically more effective by ensuring you're testing a focused, viable, and well-designed business model.
That 5-minute stress test from 2009 became the first of 7 foundational stress tests I now apply to every new idea. They have saved me far more time than they have ever cost.
I walk through this framework in detail in [Episode 2 of Building LEANSpark](/building-leanspark/02-business-model-stress-testing).
---
### Customer Forces: The 4-Lens Interview Framework
Push, Pull, Inertia, Friction — the four forces that determine whether customers switch. A practical framework for customer interviews.
URL: https://leanspark.ai/blog/customer-forces-interview-framework/
Good problem discovery isn't about asking customers what they struggle with. It's about uncovering struggles naturally by focusing on specific workflows they're already running.
When I ran problem discovery interviews for LEANSpark, I didn't sit founders down and ask "What are your top 3 problems?" That kind of question invites rehearsed answers and surface-level responses. Instead, I asked them to walk me through how they were currently validating their idea -- what was occupying their attention, the tools they used, and how they used them.
The struggles revealed themselves.
## The Customer Forces Framework
Customer Forces is built on the Innovator's Gift concept: innovation is fundamentally about causing a switch from some old way (the status quo solution people are using) to a new way (your product).
You don't cause this switch by solving problems no one cares about. You cause it by solving existing problems customers are already facing with their current solutions.
The framework views a customer's switching journey through four lenses:
### 1. Push
What's pushing them away from their current solution? These are the frustrations, struggling moments, and unmet needs with the status quo. Without a push, there's no motivation to switch.
### 2. Pull
What's pulling them toward a new solution? This is the desired outcome -- the promise of something better. Pull creates the aspiration to change.
### 3. Inertia
What keeps them stuck with their existing alternatives? Habits, sunk costs, familiarity, "good enough" -- inertia is the gravitational pull of the status quo. It's often the most underestimated force.
### 4. Friction
What makes them anxious about switching? Learning curves, migration costs, uncertainty about whether the new thing will actually work. Friction stops people at the last mile.
For a switch to happen, Push + Pull must exceed Inertia + Friction. Understanding all four forces is what separates effective interviews from superficial ones.
## Broad-Match vs Narrow-Match
One of the biggest mistakes in problem discovery is going too narrow too early. Since LEANSpark is an AI product, it would have been tempting to only interview founders already using AI tools and try to get them to switch to LEANSpark.
But that creates selection bias. If you only talk to a narrow segment, you fool yourself into thinking the market is bigger -- or shaped differently -- than it actually is.
I intentionally went broad. Instead of "Tell me how you use AI," the framing was: "Tell me how you're currently validating your idea." This opened the conversation to the full landscape of how founders work, not just the AI slice.
Once broad-match interviews revealed patterns, I shifted to narrow-match interviews -- seeking out specific use cases where I had observed underserved problems that LEANSpark could address. Things like channel building, running experiments, and accountability tracking.
The goal of narrow-match is threefold: validate the broad findings aren't false positives, confirm the existing alternatives list, and go deeper on struggles and workarounds to identify your axes of "better."
## The Context Switching Tax
The biggest finding from my interviews was something I labeled the Context Switching Tax.
Founders context-switch constantly -- between building, talking to customers, fundraising, managing teams, and learning frameworks. That's already hard. But now they also have to manage the context window of their AI tools.
I describe this as the Memento problem. In the movie, the protagonist wakes up every day with no short-term memory. He relies on notes, tattoos, and Polaroids to remember who he is and what he's doing.
That's what using AI tools feels like for most founders. Every conversation starts from scratch. You're constantly re-explaining who you are, what your startup does, what you've already tried, and what you're trying to do now. Even when you have a great brainstorming session, you're left with artifacts you have to collect, organize, and turn into action.
This insight became central to LEANSpark's design. Instead of another tool that demands constant re-explanation, we needed something that remembers -- who you are, what you're building, and where you are in your journey. Load context once. It remembers. And it learns new skills on the fly.
## From "Tool" to "Co-Founder"
The interviews revealed a pattern I didn't expect. Founders didn't lack frameworks. They knew about Lean Startup, Jobs-to-be-Done, and other methodologies. The real problem was putting it to practice consistently.
That shifted how I thought about LEANSpark. It wasn't just a coaching co-pilot that answers methodology questions or runs diagnostics. It was a daily co-founder you could use to run validation experiments.
That's a much larger scope than where I started. But the customer interviews gave me confidence it was the right direction -- because the signal came from customers, not from my assumptions.
## The Takeaway
Customer interviews aren't about validating your feature list. They're about understanding the forces that drive switching behavior and uncovering problems worth solving by watching how people work today.
Start broad to map the opportunity space. Then go narrow to validate and deepen your understanding. Focus on workflows, not opinions. And pay attention to the struggles people work around but never articulate -- those are your biggest opportunities.
I walk through the interview findings in [Episode 5 of Building LEANSpark](/building-leanspark/05-problem-discovery).
---
### Demo-Sell-Build: Stop Building Before You Sell
How we validated demand before building the product. 209 customers and $35K revenue in 40 days — by selling the demo, not the code.
URL: https://leanspark.ai/blog/demo-sell-build/
Most founders follow the same sequence: Build the product. Demo it. Then try to sell it.
I flip that order. Demo first. Sell second. Build last.
This isn't a new concept -- I've used this approach to launch every product I've built, from my first book Running Lean to coaching programs to software like Lean Canvas and now LEANSpark. But when I showed the LEANSpark landing page to early backers, I got a question that comes up constantly: "You've already got a working product, so aren't you really doing Build-Demo-Sell?"
My response: you're assuming the demo you see on the landing page is driven by working code. It's not.
## The Concierge MVP as Launch Vehicle
Before I ran any campaign, I started with a Concierge MVP -- a high-touch services model where I, the founder, became the product.
Every product lives in two contexts: the solution context (where features live) and the bigger context (where outcomes and jobs to be done live). LEANSpark is an AI tool, but the bigger context is driving business model validation for founders.
So I offered personalized business model reviews. Founders submitted their Lean Canvas, and I delivered a diagnostic walkthrough on a call. This approach served two purposes simultaneously:
1. **Learning from customers.** Every review was a disguised problem discovery interview using a "give before you get" approach -- I gave them a detailed diagnostic, then asked for a follow-on interview.
2. **Building the product.** When a canvas came in, I first ran it through my LEANSpark prototype to see what it would do, then tweaked the product to match how I would review it. Each cycle made the AI better.
After about 10 of these concierge reviews, I had enough customer signal to know the direction was right. It was time to scale beyond high-touch.
## The 10x Product Launch
I've realized over many years that no matter how fast founders try to grow, products still follow a hockey-stick trajectory. The 10x Product Launch framework is about playing the hockey stick instead of letting it play you.
You scale in order-of-magnitude jumps:
- **10 customers** -- High-touch, manual, maximum learning. This was the Concierge MVP phase.
- **100 customers** -- Semi-automated, start testing pricing and channels. This was the Demo-Sell-Build campaign.
- **1,000 customers** -- Automated, self-serve, full infrastructure.
Each level surfaces different constraints. At 10, it's "does anyone care?" At 100, it's "will they pay?" At 1,000, it's "can we deliver at scale?"
## The Campaign: Real Numbers
I launched Stage 1 on October 9th with just 10 spots, targeted to a carefully handpicked group of our most active customers. All 10 spots filled in 6 days.
Stage 2 launched immediately after and sold out by October 30th when we opened Stage 3.
The landing page had three elements every offer needs:
1. **A UVP (promise) designed to earn attention.** The headline: "Validate Faster, Build With Confidence."
2. **A demo designed to earn trust.** Three screencasts showing real-looking conversations between a founder and LEANSpark -- addressing the top 3 problems on my Lean Canvas.
3. **A clear call-to-action** with three pricing tiers that transitioned from high-touch (concierge reviews + coaching) to scalable (tool-only access).
Here's the key: the screencasts weren't recordings of working software. I had Claude Code build a demo runner that simulated ideal conversation exchanges, which I recorded as screencasts. Everything shown was within our technical confidence to build, but none of it was built yet.
When a customer buys a demo, the demo becomes the best requirements doc. All you need to deliver is what the customer bought.
The results across two campaigns (the October Demo-Sell-Build + a November Black Friday bundle):
- **209 customers enrolled**
- **$35K in revenue**
- **40 days** from campaign launch to goal
We had set a 90-day goal of 200 paid trials. We hit it in less than half the time.
## Why This Works
Demo-Sell-Build works because it aligns risk reduction with revenue generation. You're not spending months building something nobody wants. You're validating demand with real money while simultaneously learning what to build.
The concierge MVP gives you deep customer insight. The demo-sell-build campaign gives you scale. Together, they compound -- every tier 2 customer who bought a canvas assessment was also a problem discovery interview. Discovery and selling happened in parallel, not sequentially.
And because you're selling before building, the product you eventually build is shaped by what customers actually bought -- not what you assumed they wanted.
## The Takeaway
You don't need working code to build a real-looking demo. You have to design the product anyway -- why not build a demo at the same time?
Start with concierge. Learn from 10 customers. Then stack your offer -- transition from high-touch to scalable using a demo-sell-build campaign. Let customers tell you what to build by buying it first.
I walk through the full campaign in [Episode 4 of Building LEANSpark](/building-leanspark/04-demo-sell-build).
---
### Wants vs Needs: Why Features Don't Sell
Features are needs (vegetables). Outcomes are wants (health). Learn to prioritize what customers actually buy.
URL: https://leanspark.ai/blog/wants-vs-needs-feature-prioritization/
After running problem discovery interviews for LEANSpark, I had a list of insights and a dozen feature ideas. The temptation was to start building.
But which features do you build first? And more importantly, how do you frame them so customers actually care?
The answer lies in understanding the difference between wants and needs -- and why most founders get the order wrong.
## Features Are Needs. Outcomes Are Wants.
Every product lives in two contexts: the solution context (where features live) and the bigger context (where outcomes live).
Think of needs as eating your vegetables or exercising regularly. Think of wants as living a healthy, energetic life. Most people care more about the want than the need. They'll skip the broccoli, but they'll never stop wanting to feel good.
The same is true for products.
When I looked at LEANSpark through this lens, the difference was stark. Originally, I was thinking about building discrete workflow tools -- things like creating an elevator pitch, running a business model assessment, or generating an interview script.
These are needs. They're the equivalent of vegetables. Good for you, but not what gets founders excited enough to pay.
What founders actually want is:
- Validating their idea
- Acquiring customers
- Finding product/market fit
These are outcomes. They're the equivalent of health and energy -- the reason you eat the vegetables in the first place.
## The Primary Job: Traction in 90 Days
This realization led to a complete reframe of LEANSpark's positioning.
Instead of leading with features ("Run a 7-dimension business model assessment!"), I led with the outcome: **Help founders achieve traction in 90 days.**
What makes an outcome specific is timeboxing it. "Achieve traction" is vague. "Achieve traction in 90 days" is concrete and measurable.
This became the primary job to be done for LEANSpark. Not running assessments. Not generating interview scripts. Helping founders get from idea to first paying customers -- or from initial customers to a repeatable customer factory -- within a 90-day cycle.
## Wants Before Needs, Not Instead Of
The insight isn't to ignore needs. It's to lead with wants and use needs to reduce friction.
Using the Customer Forces model, picture the desired outcome at the top of a hill. Achieving any outcome takes effort. To achieve traction, founders need to do a bunch of things: create business models, stress-test them, talk to customers, design experiments, and run campaigns.
The secondary jobs -- the needs -- are all about reducing the effort required to reach the outcome. They remove friction and obstacles standing in the way.
Good products balance wants with needs this way:
1. **Target the want** -- the destination at the top of the hill
2. **Remove friction** -- the obstacles standing in the way
For LEANSpark, this meant:
- **Want**: Traction in 90 days
- **Need**: Stress-test your business model (so you don't waste months on a flawed idea)
- **Need**: Run structured experiments (so every action connects to your goal)
- **Need**: Learn the methodology (so you know what to do next)
The three features on our Demo-Sell-Build landing page mapped directly to this hierarchy -- each one addressed a top problem from the Lean Canvas, but framed in the context of achieving the bigger outcome.
## Product/Launch Fit Before Product/Market Fit
This wants-vs-needs thinking extends beyond feature prioritization into launch strategy.
Product/Market Fit is the long game. But before you can scale, you need Product/Launch Fit -- proving you can deliver value to your first 10, then 100, then 1,000 customers.
Each level requires different capabilities:
**At 10 customers:** You don't need analytics dashboards or scalable infrastructure. You need to deliver the best possible experience. High-touch, manual, concierge. This is where you learn which needs actually matter by watching customers use the product.
**At 100 customers:** You start automating the repeatable parts. You introduce light infrastructure -- onboarding flows, progress tracking. You test pricing and packaging. You start trading high-touch learning for scalability.
**At 1,000 customers:** Full self-serve. Robust infrastructure. Automated onboarding. Clear product metrics.
The mistake is trying to build for 1,000 when you have 10. At 10 customers, the right features are different from the features you'll need at 1,000. Premature scaling of features is just as dangerous as premature scaling of the business.
## How This Shaped LEANSpark
Instead of building seven specialized workflow agents (one per dimension of the business model), I scoped the MVP to three core capabilities that served the primary job of achieving traction in 90 days.
This wasn't a compromise. It was a deliberate choice to ship something complete enough to deliver the outcome, rather than something broad but shallow that covered every possible need.
The three features became the demo on the landing page. Customers bought the outcome, not the feature list. And because they bought it, I knew exactly what to build first.
## The Takeaway
Stop leading with features. Start leading with outcomes. Features are what your product does. Outcomes are why anyone cares.
Frame your product around the want -- the destination -- and then prioritize the needs that remove the most friction on the path to getting there. Build for 10 customers first, then 100, then 1,000. Each level teaches you which features actually matter.
I walk through the full solution design in [Episode 6 of Building LEANSpark](/building-leanspark/06-solution-design).
---
### Why You Should Validate Before Building
Most startups fail because they build products nobody wants. Learn why systematic validation is the key to startup success.
URL: https://leanspark.ai/blog/why-validation-before-building/
The number one reason startups fail isn't lack of funding, bad timing, or poor execution. It's building something nobody wants.
Yet most founders skip validation and jump straight into building. Why?
## The Builder's Trap
There's a seductive logic to building first:
- "I need something to show investors"
- "Customers can't tell me what they want until they see it"
- "My idea is too innovative to validate"
These sound reasonable. But they're traps.
Building is comfortable. It feels productive. You can see progress every day. Validation, on the other hand, is uncomfortable. It means talking to strangers, facing rejection, and confronting the possibility that your idea might not work.
## What Validation Actually Means
Validation isn't market research. It's not surveys or focus groups. It's not asking people if they would hypothetically buy your product.
**Validation is testing your riskiest assumptions with real customer behavior.**
Here's the key insight: before you have a product, you can still validate:
- **Problem validation**: Do customers actually have the problem you're solving?
- **Solution validation**: Does your proposed solution resonate with them?
- **Pricing validation**: Will they pay what you need to charge?
- **Channel validation**: Can you reach them profitably?
You don't need code to test these. You need conversations, experiments, and a systematic approach.
## The 90-Day Validation Cycle
At LEANSpark, we use a structured approach: 6 cycles of 2 weeks each, over 90 days.
Each cycle follows the PDCA loop:
1. **Plan**: Identify your riskiest assumption
2. **Do**: Design an experiment to test it
3. **Check**: Measure the results
4. **Act**: Decide to persevere, pivot, or pause
By the end of 90 days, you'll have real data to make a clear decision: build this product, change direction, or stop.
## The Cost of Skipping Validation
Let's do the math. Say you spend 6 months building a product without validation. You invest:
- 6 months of your time
- $50,000+ in opportunity cost
- Your reputation with early users
- Your team's morale when it fails
Now imagine you spent the first 3 months validating instead. You might discover:
- The problem isn't urgent enough to pay for
- Your target market is too small
- There's a better solution already
- You need to pivot to a different customer segment
That discovery, made in 3 months instead of 6, saves you everything.
## Getting Started
You don't need special tools to start validating. You need:
1. A clear hypothesis about your customer and their problem
2. A way to reach potential customers (LinkedIn, email, events)
3. A script for having problem interviews
4. The discipline to actually do it
Or you can use LEANSpark to accelerate the process. We've systematized 15 years of lean methodology into AI-powered validation workflows.
Either way, the key is to start validating before you start building.
Your future self will thank you.
---
### The 7-Dimension Business Model Assessment
Learn how to stress-test your business model across Clarity, Desirability, Viability, Feasibility, Defensibility, Timing, and Mission.
URL: https://leanspark.ai/blog/7-dimension-business-model-assessment/
A Lean Canvas is just the beginning. The real question is: how good is your business model?
After helping thousands of founders assess their canvases, I've developed a systematic framework for stress-testing business models. It evaluates your model across 7 critical dimensions.
## The 7 Dimensions
### 1. Clarity
Can you articulate your business model in one sentence? Does everyone on your team understand who the customer is and what problem you're solving?
**Low clarity signs:**
- Multiple target customers with different problems
- Features masquerading as value propositions
- Vague problem statements ("make life easier")
### 2. Desirability
Do customers actually want this? Not "would they say yes in a survey" but "will they take action to get it"?
**How to test:**
- Problem interviews: Are they actively seeking solutions?
- Offer tests: Will they sign up, pay, or commit time?
- Competitor analysis: Are they already paying for alternatives?
### 3. Viability
Can you build a sustainable business around this? The math has to work.
**Key questions:**
- Is your market large enough?
- Can you achieve profitable unit economics?
- What does your customer acquisition cost look like?
### 4. Feasibility
Can you actually build and deliver this solution? With your current resources, skills, and timeline?
**Consider:**
- Technical complexity
- Regulatory requirements
- Partnership dependencies
- Team capabilities
### 5. Defensibility
Once you succeed, can you defend your position? What's your moat?
**Defensive assets:**
- Network effects
- Switching costs
- Proprietary data
- Brand trust
- Regulatory barriers
### 6. Timing
Why now? What has changed that makes this the right moment?
**Timing catalysts:**
- New technology
- Regulatory changes
- Social/behavioral shifts
- Market maturity
### 7. Mission
Why do YOU care? Your personal motivation matters more than you think.
**Mission alignment:**
- Can you stay committed for 5-10 years?
- Does this align with your values?
- Would you still work on this if it took twice as long?
## How to Use the Assessment
Score each dimension 0-10. Be honest. Get external perspectives.
**Scoring guide:**
- 0-3: Major concerns, needs significant work
- 4-6: Some validation, but gaps remain
- 7-9: Strong evidence, minor refinements needed
- 10: Fully validated, no concerns
Then prioritize based on risk. A 3 in Desirability is more dangerous than a 5 in Defensibility. Fix the biggest risks first.
## Common Patterns
After running thousands of assessments, I see these patterns:
**The "Mixed Model"**
Multiple business models jammed into one canvas. Usually happens when founders can't choose between B2B and B2C, or between two different customer segments. Solution: Split into separate canvases and validate each.
**The "Solution in Search of a Problem"**
High Feasibility, low Desirability. The founder built something they could build, not something customers need. Solution: Get out of the building and do problem interviews.
**The "Too Early" Model**
Good idea, wrong time. The enabling technology or market conditions aren't ready. Solution: Identify the timing catalyst and decide whether to wait or pivot.
## LEANSpark Assessment
This is exactly what LEANSpark does. Upload your Lean Canvas, and we run a systematic assessment across all 7 dimensions. We detect mixed models, generate focused variants, and tell you exactly what to validate next.
2 hours of stress-testing beats 2 months of guessing.
Ready to assess your model? [Try LEANSpark](https://leanspark.ai).
---
### AI vs Human Startup Coaching: Finding the Right Balance
When should you use AI coaching, and when do you need a human advisor? A framework for thinking about AI-augmented startup validation.
URL: https://leanspark.ai/blog/ai-vs-human-startup-coaching/
"Will AI replace startup advisors?"
I get asked this constantly. As someone who has spent 15 years coaching founders—and who now builds AI coaching tools—here's my honest answer.
## What AI Does Better
AI excels at certain types of coaching tasks:
### 1. Consistency
Human advisors have good days and bad days. They get tired. Their advice drifts based on their recent experiences. AI applies the same methodology consistently, every time.
### 2. Availability
AI doesn't need to schedule a call for next Tuesday. It's available 24/7, whenever inspiration strikes or doubt creeps in.
### 3. Systematic Execution
Running a 7-dimension assessment across 50 criteria? Checking your canvas against 100 common failure patterns? AI does this instantly and completely.
### 4. Memory
AI remembers every conversation, every pivot, every experiment you've run. It can connect insights across your entire validation journey in ways humans can't.
### 5. Objectivity
AI doesn't have ego. It won't protect your feelings. It won't validate you just to be nice. This honesty, while sometimes uncomfortable, is exactly what founders need.
## What Humans Do Better
But AI has clear limitations:
### 1. Intuition
Experienced advisors develop pattern recognition that's hard to articulate. They sense when something's off, even when all the data looks fine.
### 2. Relationships
Introductions, partnerships, and hiring often come through advisor networks. AI can't make a warm intro to your ideal customer.
### 3. Emotional Support
Starting a company is hard. Sometimes you need someone who's been there to tell you it's going to be okay. AI can provide structure, but not empathy.
### 4. Contextual Judgment
AI works from what you tell it. Humans pick up on what you don't say—the hesitation in your voice, the defensive body language when discussing your co-founder.
### 5. Accountability
There's something about knowing a human is watching that creates commitment. AI can remind you, but it can't hold you accountable the same way.
## The Right Balance
The answer isn't AI or humans. It's AI and humans, used appropriately.
**Use AI for:**
- Daily validation work (canvas updates, experiment design, methodology questions)
- Systematic assessments and gap analysis
- Documenting and synthesizing learnings
- 24/7 access to structured methodology
**Use humans for:**
- Major strategic decisions (pivot vs persevere)
- Relationship building and introductions
- Emotional support during hard times
- Challenging your blind spots
## How LEANSpark Fits
LEANSpark is designed to be your daily AI co-founder—not a replacement for human advisors, but a complement.
Use LEANSpark to:
- Run your weekly 7-dimension check-ins
- Design experiments between advisor meetings
- Document customer interview insights
- Prepare for your human coaching sessions
Then use your human advisor time for the big decisions, the hard conversations, and the strategic pivots that require experienced judgment.
## The Future
AI coaching will get better. But the best founders will use it as a tool, not a crutch.
The goal isn't to eliminate human judgment. It's to make human judgment more informed, more systematic, and more effective.
That's what we're building at LEANSpark.
---
## Comparisons
### Lean Canvas vs Business Model Canvas: Which Should You Use?
The full story behind why Lean Canvas was created as a different adaptation of the Business Model Canvas — from Ash Maurya, creator of Lean Canvas.
URL: https://leanspark.ai/compare/lean-canvas-vs-bmc/
I often get asked why I created a different adaptation from the original Business Model Canvas by Alex Osterwalder. Here is the thought process that went into creating Lean Canvas, how the two canvases compare, and when to use each.
## At a Glance
| Dimension | Lean Canvas | Business Model Canvas |
|-----------|------------|----------------------|
| **Creator** | Ash Maurya (2010) | Alexander Osterwalder (2010) |
| **Purpose** | Startup validation under uncertainty | Business model design and communication |
| **Best for** | New ventures pre-Product/Market Fit | Established businesses or corporate innovation |
| **Focus** | Risk and learning | Architecture and value delivery |
| **Key philosophy** | Find the riskiest assumption, test it | Map the business model holistically |
| **Time to complete** | 20 minutes | 45-60 minutes |
| **Primary audience** | Founders, solo entrepreneurs | Product teams, consultants, corporate strategists |
## The Backstory
**May 2010** — I was first exposed to the Business Model Canvas through Alex Osterwalder's book *Business Model Generation*. While I found the book beautifully illustrated, I originally dismissed the canvas approach as "too simple." Many of the examples illustrated the business models of well-known companies like Apple and Skype — after they were successful. I was more interested in the "learning" that got them there.
**June 2010** — It was not until I saw fellow entrepreneur Rob Fitzpatrick's variation (Startup Toolkit) that incorporated Steve Blank's worksheets from *The Four Steps to the Epiphany* that I took a more serious look at the canvas. The thought of capturing business model hypotheses on a single page seemed killer. I modeled my existing products using both canvases, which prompted me to do some tinkering of my own.
**August 2010** — I shared my adaptation (Lean Canvas) in a post: "How I Document My Business Model Hypotheses." This post quickly became one of my top posts of all time. I started using and testing Lean Canvas with other startups in my workshops and was particularly encouraged by its ability to enable more learning versus pitching conversations.
**February 2011** — Lean Canvas also became a critical part of the methodology described in my book *Running Lean* — first self-published as an ebook, now in its third edition from O'Reilly.
## Design Goals
My main objective with Lean Canvas was to make it as **actionable** as possible while staying **entrepreneur-focused**. The metaphor I had in mind was a ground-up tactical plan that guided the entrepreneur from ideation to building a successful startup.
I had already been working with Lean Startup principles, which had a big influence on the design.
> "Startups operate under conditions of extreme uncertainty." — Eric Ries
My approach to making the canvas actionable was capturing that which was most uncertain, or more accurately, **that which was most risky**. I found the initial Business Model Canvases I created missing things I would consider very high risk, while other things on the canvas did not register as high enough risk. Because the canvas is already quite space-constrained, it was important to maximize the signal-to-noise ratio. So I started trading boxes.
## What I Added
**Problem** — Most startups fail not because they fail to build what they set out to build but because they waste time, money, and effort building the wrong product. A significant contributor to this failure is a lack of proper "problem understanding" from the start.
> "A problem well stated is a problem half-solved." — Charles Kettering
**Solution** — Once you understand the problem, you are in the best position to define a possible solution. I purposefully constrained this box because the solution is what we are most passionate about. Left unchecked, we fall in love with our first solution and corner ourselves into legacy. Keeping the box small aligns with the Minimum Viable Product concept.
**Key Metrics** — Startups often drown in a sea of numbers. At any given point in time, there are only a few key actions that matter. Failure to identify the right key metric can be catastrophic — leading to premature optimization or running out of resources chasing the wrong goal.
> "A startup can only focus on one metric. So you have to decide what that is and ignore everything else." — Noah Kagan
**Unfair Advantage** — This is another name for competitive advantage or barriers to entry. Few startups have a true unfair advantage on day one, which means this box will often be blank. It is not intended to discourage you but to continually encourage you to work toward finding your unfair advantage. Once you achieve initial success, competitors and copycats will enter the market.
> "A true unfair advantage is something that cannot be easily copied or bought." — Jason Cohen
## What I Took Out
> "Perfection is achieved, not when you have nothing left to add, but nothing left to take away." — Antoine de Saint-Exupéry
**Key Activities and Key Resources** — Both boxes were more "outside-in" focused — they helped outsiders looking in to understand what the startup did. I found myself listing things like "Customer Development" and "Software Development" that did not register high enough on risk to warrant keeping. Key Activities can be derived from the Solution box after the MVP undergoes testing. Key Resources align more closely with Unfair Advantage in an era of cloud computing, open source, and globalization.
**Customer Relationships** — I advocate starting every product with a direct customer relationship through interviews and observation, then identifying the appropriate path to customers. This is better captured by the existing Channels box.
**Key Partners** — This was the hardest to remove. Yes, some products require establishing key partnerships first — building a global solar energy grid with huge capital and regulatory requirements, for example. But most products do not fall into this category. When you are an unknown startup with an untested product, pursuing key partnerships from day one can be a form of waste.
## When to Use Which
### Use Lean Canvas When:
- You are starting a new venture and have not validated product-market fit
- You need to identify and prioritize risks quickly
- You are a solo founder or small team that needs to move fast
- You want a tool that naturally feeds into experiment design
- You are in an accelerator, incubator, or lean startup program
### Use Business Model Canvas When:
- You are documenting an existing, working business model
- You are doing corporate innovation and need stakeholder buy-in
- You are analyzing competitors' business models
- You need to communicate a model to investors who expect BMC format
- You are planning operations past the product-market fit stage
## Common Questions
**Why extend the BMC rather than creating something new?** Even though it may have been easier to lay out a new canvas differently, I chose to work within the existing layout to attribute the work back to Alex Osterwalder's original canvas. He licensed the original under Creative Commons and invited others to "Share & Remix" — making this a no-brainer.
**Who is the audience for Lean Canvas?** Lean Canvas was designed for entrepreneurs, not consultants, customers, advisors, or investors. That said, entrepreneurs benefit greatly by engaging all of those people while validating their canvas.
**Should I start with Lean Canvas and then switch to BMC?** Use what is most natural for you. I have used Lean Canvas successfully from ideation to Product/Market Fit and beyond. The risks captured on Lean Canvas are not just early-stage risks — they morph and evolve throughout the startup lifecycle.
**Why have both Problem and Unique Value Proposition?** The Problem box captures the top problems customers face, while the UVP is the marketing promise that stems from the intersection of the Problem and Solution boxes. For example, a job seeker's problem might be "getting noticed by a prospective employer," the solution might be "professionally designed resume templates," but the UVP might be "Land your dream job in 60 days or less."
**Where do competitors go on the Lean Canvas?** I am less interested in listing well-known competitors we build into investor pitches and more interested in how customers deal with their problems today. Your true competition is not who you think they are, but who your customers think they are. There is an "Existing Alternatives" sub-section under the Problem box for this purpose.
**Why have both UVP and Unfair Advantage?** The job of a UVP is to capture a customer's attention, while the job of the Unfair Advantage is to deter copycats and competitors. These two are often not the same thing. For example, Facebook's UVP was "Connect and share with the people in your life." Their unfair advantage was large network effects.
## The Verdict
This is not a contest — it is a question of fit. The Business Model Canvas is the better tool for mapping and communicating established business models. The Lean Canvas is the better tool for startups navigating uncertainty.
If you are pre-product-market fit, start with Lean Canvas. Once your model is validated and you are scaling, the BMC becomes more useful for operational planning and communication.
The worst thing you can do is spend weeks perfecting either canvas without testing the assumptions it contains. A canvas is a starting point for action, not a deliverable.
---
### LEANSpark vs ChatGPT for Business Modeling
ChatGPT is a great generalist. LEANSpark is your AI co-founder. Here's when to use each for startup validation.
URL: https://leanspark.ai/compare/leanspark-vs-chatgpt/
Every founder has asked ChatGPT for business advice at some point. It's fast, it's cheap, and it gives surprisingly decent answers. So why would you use a specialized tool like LEANSpark instead?
The short answer: ChatGPT helps you think. LEANSpark helps you systematically validate. Those are fundamentally different jobs.
## At a Glance
| Dimension | LEANSpark | ChatGPT |
|-----------|-----------|---------|
| **Approach** | Structured validation methodology | Open-ended conversation |
| **Methodology** | Continuous Innovation Framework (built-in) | Whatever you prompt it with |
| **Context persistence** | Remembers your full business model across sessions | Resets each conversation (or requires manual context) |
| **Structured frameworks** | Lean Canvas, 7-dimension stress testing | None built-in; you build your own prompts |
| **Validation recipes** | Pre-built experiment designs and 90-day cycles | You design your own |
| **Cost** | Free tier + paid plans | Free (GPT-3.5) / $20+/mo (GPT-4) |
| **Best for** | Systematic startup validation | General research, brainstorming, ad-hoc questions |
## Where ChatGPT Excels
ChatGPT is genuinely good at several things that matter to founders:
- **Brainstorming**: Need 20 variations of a positioning statement? ChatGPT generates them in seconds. It's an excellent divergent thinking partner.
- **Research synthesis**: Ask it to summarize market trends, explain regulatory frameworks, or compare technologies. It draws from broad training data and gives you a useful starting point.
- **Writing and editing**: Draft emails, landing page copy, pitch decks, investor updates. ChatGPT is a capable writing assistant.
- **General Q&A**: "What's a good pricing model for B2B SaaS?" — ChatGPT gives a solid overview of options with pros and cons.
- **Low cost**: The free tier handles most casual use. Even GPT-4 at $20/month is affordable for the breadth of capability.
For exploratory, unstructured thinking, ChatGPT is hard to beat.
## Where LEANSpark Excels
LEANSpark was built specifically for one job: helping founders validate business models using proven methodology. That specialization shows up in several ways:
### Persistent Business Model Context
When you load your Lean Canvas into LEANSpark, it becomes the foundation for every conversation. You don't re-explain your business every session. The system knows your customer segments, your problem hypotheses, your revenue model, and your current assumptions. This context makes every interaction more targeted.
With ChatGPT, you start fresh each time (or paste in context that quickly exceeds useful limits). The burden of maintaining continuity falls entirely on you.
### 7-Dimension Stress Testing
LEANSpark evaluates your business model across seven dimensions: Clarity, Desirability, Viability, Feasibility, Defensibility, Mission, and Timing. Each dimension has specific criteria, scoring rubrics, and targeted follow-up questions.
This isn't something you can replicate with a single ChatGPT prompt. You could build a custom GPT or a prompt chain, but you'd be rebuilding methodology that already exists — and maintaining it yourself.
### Structured Validation Methodology
LEANSpark follows the Continuous Innovation Framework. It doesn't just tell you your idea sounds interesting — it identifies your riskiest assumption, designs a specific experiment to test it, and defines what success looks like before you run the test.
ChatGPT will validate almost anything you tell it. Ask "Is my startup idea good?" and it'll give you encouraging feedback with mild caveats. That feels good but doesn't reduce risk. LEANSpark is designed to challenge your assumptions, not confirm them.
### Experiment Design and Cycle Planning
LEANSpark generates concrete 90-day validation cycles: which experiments to run, in what order, and what to measure. It connects your canvas hypotheses directly to testable actions.
ChatGPT can help you brainstorm experiments if you ask the right questions, but it won't proactively sequence them based on risk priority or track your progress across a validation cycle.
## The Real Difference: Framework vs. Freestyle
The core distinction is structural. ChatGPT is a freestyle tool — it goes wherever you point it, and the quality of the output depends heavily on the quality of your prompts. If you already know lean startup methodology inside and out, you can probably get ChatGPT to do a reasonable job. You're the methodology; ChatGPT is the typing.
LEANSpark embeds the methodology. You don't need to know the right questions to ask because the system knows the right questions. It guides the conversation toward the highest-risk assumptions, follows a proven sequence, and keeps you honest when your optimism outpaces your evidence.
## When to Use Which
**Use ChatGPT when:**
- You're in early brainstorming mode and want to explore broadly
- You need help with writing, research, or general business questions
- You want quick feedback on a specific, narrow question
- You're comparing tools, markets, or technologies
- Budget is the primary constraint
**Use LEANSpark when:**
- You have a specific business idea and need to validate it systematically
- You want structured stress testing across multiple dimensions
- You need persistent context that builds over time
- You want a validation roadmap, not just opinions
- You're serious about reducing risk before building
## The Verdict
ChatGPT and LEANSpark aren't really competitors — they serve different stages and different needs. Use ChatGPT for the wide-open exploration phase: researching markets, brainstorming ideas, drafting content. Use LEANSpark when you're ready to get disciplined about validation: stress testing your model, identifying risks, designing experiments, and tracking progress.
The founders who waste the most time are the ones who stay in brainstorming mode forever. At some point, you need to stop exploring and start validating. That's the transition from ChatGPT to LEANSpark.
---
### LEANSpark vs Free AI Canvas Generators: Why the Canvas Is Not the Product
Free AI tools can generate a Lean Canvas in seconds. So why use LEANSpark? Because the canvas was never meant to be the end product — it's the beginning of validation.
URL: https://leanspark.ai/compare/leanspark-vs-free-ai-generators/
A growing number of free AI tools — leancanvas.business, EdrawMax AI, Canvanizer, and others — can generate a Lean Canvas or Business Model Canvas in seconds. Type in your idea, get a filled-out canvas. It's fast, it's free, and the output looks professional.
So why would anyone pay for LEANSpark?
Because the canvas was never the product. It was always the starting point.
## At a Glance
| Dimension | LEANSpark | Free AI Canvas Generators |
|-----------|-----------|--------------------------|
| **Purpose** | Validate your business model | Generate a canvas artifact |
| **AI role** | Methodology engine — challenges and guides | Fill-in tool — generates content for boxes |
| **Output** | Validated assumptions + experiment plans | A filled-out canvas image/document |
| **Methodology** | Continuous Innovation Framework (7-dimension stress testing) | None — just the canvas template |
| **Context persistence** | Tracks your model across sessions and iterations | None — each generation is standalone |
| **Created by** | Ash Maurya, inventor of Lean Canvas | Various third-party developers |
| **Cost** | Free tier + paid plans | Free (often ad-supported) |
## What Free Generators Do Well
Free AI canvas generators have a clear value proposition: speed and zero cost.
### Instant Artifact Creation
Type a sentence about your business idea and get a filled-out canvas in 30-60 seconds. For founders who need a visual to share in a meeting, or students completing a class assignment, this is genuinely useful. The artifact itself — nine boxes with content — is the deliverable.
### Zero Friction
No signup, no credit card, no learning curve. Paste your idea, click generate, download a PDF. If the canvas is a checkbox item on your to-do list, free generators check that box instantly.
### Good Enough for Exploration
If you're brainstorming five different business ideas and want a quick canvas for each to compare at a high level, free generators give you a starting point fast. They're useful as a brainstorming accelerant.
## Where Free Generators Stop — and Why It Matters
Here's the fundamental problem: **a filled-out canvas is not a validated business model.**
Every box on a generated canvas contains an assumption. Your "Customer Segments" box assumes you know who your customer is. Your "Problem" box assumes that problem is real and important enough to pay to solve. Your "Revenue Streams" box assumes people will pay the amount you've listed.
A free generator fills in all nine boxes and hands you a document that looks complete. But nothing in that document has been tested. Every line is a hypothesis that could be wrong — and statistically, most of them are.
This is the critical distinction: **generating a canvas takes 60 seconds. Validating a canvas takes 90 days.** Free generators handle the 60 seconds. LEANSpark handles the 90 days.
## Where LEANSpark Excels
### The Canvas Is the Starting Line, Not the Finish Line
LEANSpark uses the Lean Canvas as the entry point for structured validation, not as the final deliverable. Once you have a canvas, the real work begins: Which of your nine boxes contains the riskiest assumption? How would you test it? What evidence would convince you that you're wrong?
Free generators give you a filled-out canvas and say "done." LEANSpark gives you a filled-out canvas and says "now let's figure out which parts of this are actually true."
### 7-Dimension Stress Testing
LEANSpark evaluates your business model across seven dimensions: Clarity, Desirability, Viability, Feasibility, Defensibility, Mission, and Timing. Each dimension has specific criteria, scoring, and targeted follow-up questions. This is methodology, not generation — it's the difference between producing a document and understanding whether the document is right.
No free canvas generator does this. They produce the artifact and move on.
### Built by the Inventor
LEANSpark is built by Ash Maurya, who created Lean Canvas in 2010. The methodology that powers LEANSpark — the Continuous Innovation Framework — represents 15 years of refinement based on working with thousands of founders.
Free generators treat Lean Canvas as a template with nine boxes to fill. LEANSpark treats it as a living hypothesis tracker embedded in a complete validation system. The difference is like the gap between a guitar and a guitar teacher: the instrument is free, but the methodology that makes you good is what you're actually paying for.
### Experiment Design and Sprint Planning
After stress-testing your model, LEANSpark helps you design specific experiments to test your riskiest assumptions, plan 90-day validation sprints, and track your progress through structured PDCA (Plan-Do-Check-Act) cycles.
A free canvas generator can't do this because it has no concept of what happens after the canvas is generated. The canvas is the entire product. In LEANSpark, the canvas is step one of a multi-month validation journey.
### Persistent Context
LEANSpark remembers your business model, your experiments, your learnings, and your pivots across sessions. It builds a progressively deeper understanding of your venture and tailors its guidance accordingly.
Free generators have no memory. Each generation is independent. You can't build on previous sessions because there are no sessions — there's just a one-shot generation.
The canvas is free. The validation methodology is what matters.
## The Commodity Trap
Free AI canvas generators are commoditizing the canvas artifact itself. A filled-out Lean Canvas is becoming a zero-value output — anyone can generate one in seconds.
This is actually good for LEANSpark, because it clarifies the real value proposition. The canvas was never meant to be the valuable thing. The validation methodology — knowing which assumptions to test, in what order, with what experiments, and how to interpret the results — that's where the value has always been.
When the artifact is free, the methodology becomes the differentiator. And LEANSpark is the only tool where the methodology comes from the person who created the framework in the first place.
## When to Use Which
**Use free AI canvas generators when:**
- You need a canvas as a visual for a class assignment or quick meeting
- You're brainstorming multiple ideas and want rough canvases to compare
- You need a starting point and plan to do all the validation work manually
- Budget is your primary constraint and you're comfortable doing methodology yourself
**Use LEANSpark when:**
- You need to validate your business model, not just document it
- You want structured stress testing across seven dimensions
- You want experiment design, sprint planning, and progress tracking
- You want the methodology from the person who invented Lean Canvas
- You understand that the canvas is the beginning of the work, not the end
## The Verdict
Free AI canvas generators are useful for what they do: generating a filled-out canvas quickly and cheaply. If a canvas artifact is all you need, they work.
But if you understand that a filled-out canvas is just a collection of untested assumptions — and that the real work is figuring out which assumptions are wrong before you invest your life savings building on them — then you need something beyond generation. You need validation.
That's what LEANSpark does. It starts where the free generators stop.
---
### LEANSpark vs Siift.ai: Who Should Define the Lean Canvas Category?
Siift.ai positions itself as a 'Lean Canvas Alternative.' Here's why LEANSpark — built by the inventor of Lean Canvas — takes a fundamentally different approach.
URL: https://leanspark.ai/compare/leanspark-vs-siift/
Siift.ai is an AI-powered business planning tool that explicitly positions itself as a "Lean Canvas Alternative." It helps founders create business plans, canvases, and pitch decks using AI. LEANSpark is an AI-native validation tool built on the Lean Canvas and Continuous Innovation Framework — by the person who created Lean Canvas in the first place.
Both tools use AI to help founders think about their business models. The difference is in what they believe "helping" means.
## At a Glance
| Dimension | LEANSpark | Siift.ai |
|-----------|-----------|----------|
| **Approach** | AI-driven validation and assumption testing | AI-assisted business planning and document generation |
| **Lean Canvas connection** | Built by Ash Maurya, creator of Lean Canvas | Uses Lean Canvas as a template among other frameworks |
| **Methodology** | Continuous Innovation Framework (structured validation) | General business planning with AI generation |
| **Focus** | Challenge assumptions, reduce risk | Generate artifacts quickly |
| **AI role** | Methodology engine — drives the conversation | Generation tool — fills in templates |
| **Pricing** | Free tier + credit-based plans | EUR 19-79/month subscription |
| **Primary audience** | Founders who need to validate before building | Founders who need business planning documents |
## Where Siift.ai Excels
Siift.ai has built a capable AI business planning tool with several strengths:
### Speed of Artifact Generation
Siift.ai can generate a complete business plan, lean canvas, pitch deck, and financial projections in minutes. If you need a polished document for an accelerator application or investor meeting on short notice, that speed is genuinely useful.
### Breadth of Output Formats
Siift.ai produces multiple deliverable types from a single input: business plans, canvases, pitch decks, financial models, and competitor analysis. It's a document factory. If your immediate need is "I need materials for a meeting tomorrow," Siift.ai covers a lot of ground quickly.
### Guided Questionnaire Approach
Rather than requiring users to understand frameworks upfront, Siift.ai walks founders through a step-by-step questionnaire. The AI then generates outputs from those answers. This lowers the barrier to entry for founders unfamiliar with business modeling.
### Multi-Language Support
Siift.ai supports multiple languages, making it accessible to non-English-speaking founders — a genuine advantage for global accessibility.
## Where LEANSpark Excels
LEANSpark takes a fundamentally different approach — one rooted in the methodology that Lean Canvas was actually designed to support.
### Built by the Source
Lean Canvas was not created to be a document template. It was designed as a tool for capturing and testing business model hypotheses under conditions of extreme uncertainty. LEANSpark is built by Ash Maurya, who created Lean Canvas in 2010 and has spent 15+ years refining the methodology around it.
This matters because methodology evolves. The Continuous Innovation Framework that powers LEANSpark includes concepts that didn't exist when Lean Canvas was first published — 7-dimension stress testing, Customer Forces analysis, the 10x Product Launch, and structured 90-day validation cycles. These aren't features bolted onto a canvas template. They're the result of working with thousands of founders and continuously improving the approach.
When a tool uses Lean Canvas as one template among many, it treats the canvas as an artifact. LEANSpark treats it as a living hypothesis tracker embedded in a complete validation methodology.
### Validation Over Generation
Siift.ai generates business plans and canvases from your inputs. LEANSpark challenges your inputs. This is the core philosophical difference.
Generating a polished business plan from untested assumptions gives you a false sense of progress. You have a professional-looking document, but the assumptions underneath it are still guesses. LEANSpark's 7-dimension stress testing (Clarity, Desirability, Viability, Feasibility, Defensibility, Mission, Timing) is specifically designed to surface the assumptions you haven't tested — and then guide you through testing them.
Most AI startup tools generate artifacts. LEANSpark validates assumptions. That distinction is the difference between feeling productive and actually reducing risk.
### Continuous Methodology, Not One-Shot Generation
Siift.ai produces outputs that are essentially point-in-time snapshots: generate a plan, export it, present it. LEANSpark is built for continuous iteration. Your business model evolves as you run experiments, gather evidence, and update assumptions. The tool tracks this progression and adapts its guidance accordingly.
Startups don't succeed by writing better plans. They succeed by learning faster. LEANSpark's experiment design, sprint planning, and PDCA tracking are built around that learning loop.
### The Hard Questions
When you tell Siift.ai about your business idea, it generates supportive outputs. When you tell LEANSpark about your business idea, it asks you hard questions: What evidence do you have that this problem exists? How are customers solving this problem today? What's your riskiest assumption, and how would you test it in the next two weeks?
This isn't a design choice about being difficult. It's what the methodology requires. The founders who succeed are the ones who confront their assumptions early, not the ones who generate the most polished documents.
The only AI startup tool built by the inventor of Lean Canvas.
## The Category Question
Siift.ai has been actively publishing content positioning itself as a "Lean Canvas Alternative" — essentially claiming territory in a category defined by a framework they didn't create.
There's an important distinction here. Lean Canvas is open-source (Creative Commons licensed) and anyone can build tools around it. That's by design. But there's a difference between building on an open framework and positioning yourself as the authority on it.
LEANSpark isn't just another tool that uses Lean Canvas as a template. It's the next evolution of Lean Canvas itself — from a static 1-page canvas to an AI-powered validation system that embodies the methodology the canvas was always meant to support.
## When to Use Which
**Use Siift.ai when:**
- You need quick business planning documents for a specific meeting or application
- You want multiple output formats (plans, decks, financials) generated automatically
- You need documents in a non-English language
- Your primary goal is having professional-looking materials, not validation
**Use LEANSpark when:**
- You need to actually validate whether your business model works
- You want AI that challenges your assumptions, not just documents them
- You want structured validation cycles with specific experiments
- You want the methodology from the person who created Lean Canvas
- You're serious about reducing risk before investing significant time and money
## The Verdict
Siift.ai and LEANSpark serve different needs despite both operating in the AI startup tools space. Siift.ai is a capable document generator — it takes your inputs and produces polished business plans, canvases, and pitch decks quickly.
LEANSpark is a validation partner. It doesn't just help you describe your business model — it helps you stress-test it, identify what's most likely to be wrong, design experiments to test those assumptions, and track your progress through structured validation cycles. It's built on 15 years of methodology refinement by the person who created Lean Canvas.
If you need documents, Siift.ai works. If you need to know whether your startup idea is actually going to work, LEANSpark is where you should start.
---
### LEANSpark vs Strategyzer: AI-Native vs Traditional Planning
Comparing LEANSpark's AI-powered validation approach with Strategyzer's canvas-based planning tools.
URL: https://leanspark.ai/compare/leanspark-vs-strategyzer/
Strategyzer is the company behind the Business Model Canvas and the Value Proposition Canvas — two of the most widely used strategic planning tools in the world. LEANSpark is an AI-native validation tool built on the Lean Canvas and Continuous Innovation Framework. Both help you think about business models, but their approaches, audiences, and philosophies are fundamentally different.
## At a Glance
| Dimension | LEANSpark | Strategyzer |
|-----------|-----------|-------------|
| **Approach** | AI-native validation | Canvas-based strategic planning |
| **AI integration** | Core to the product — AI drives the methodology | Supplementary — AI assists with canvas filling |
| **Canvas type** | [Lean Canvas](/compare/lean-canvas-vs-bmc/) | Business Model Canvas + Value Proposition Canvas |
| **Focus** | Validation and risk reduction | Planning and communication |
| **Methodology** | Continuous Innovation Framework | Business Model Generation |
| **Primary audience** | Founders, solo entrepreneurs, small teams | Enterprise teams, consultants, business schools |
| **Pricing model** | Free tier + individual plans | Enterprise licensing, per-seat pricing |
## Where Strategyzer Excels
Strategyzer has earned its position through years of building a comprehensive business design ecosystem:
### Established Framework and Brand
The Business Model Canvas is taught in virtually every MBA program worldwide. When you use Strategyzer's tools, you're working with a framework that investors, board members, and corporate sponsors immediately recognize. There's real value in that shared language.
### Dual Canvas System
Strategyzer offers both the Business Model Canvas and the Value Proposition Canvas. The VPC zooms into the fit between your customer profile (jobs, pains, gains) and your value proposition (products, pain relievers, gain creators). This two-level approach gives teams a structured way to go from broad model to specific value creation.
### Team Collaboration Features
Strategyzer was built for teams. It supports real-time collaboration, shared workspaces, portfolio management, and presentation-ready exports. If you need to run a business model workshop with 20 people in a room, Strategyzer's tools are designed for exactly that.
### Enterprise and Education
Large organizations and business schools are Strategyzer's core market. The platform includes facilitator guides, testing cards, learning programs, and certification tracks. It's a complete ecosystem, not just a tool.
## Where LEANSpark Excels
LEANSpark takes a fundamentally different approach — one built for founders who need to validate fast rather than plan comprehensively.
### AI-Native, Not AI-Bolted-On
LEANSpark was designed from the ground up with AI at its core. The AI doesn't just help you fill in canvas boxes — it actively challenges your assumptions, identifies your riskiest hypotheses, and guides you through structured validation.
Many traditional tools have added AI features as an afterthought: "Use AI to generate your Value Proposition" or "Let AI suggest Customer Segments." That's AI as a convenience feature. In LEANSpark, AI is the methodology engine. It drives the conversation, asks the hard questions, and won't let you skip the uncomfortable parts.
### Validation-Focused, Not Planning-Focused
Strategyzer helps you design a business model. LEANSpark helps you test whether your business model is right. That distinction matters enormously at the early stage.
A beautifully filled-out Business Model Canvas can be completely wrong. Every box can be internally consistent and logically sound while being based on untested assumptions about what customers actually want. Lean Canvas combined with LEANSpark's 7-dimension stress testing (Clarity, Desirability, Viability, Feasibility, Defensibility, Mission, Timing) is designed to surface those untested assumptions before you build.
### Continuous Methodology, Not Point-in-Time
Strategyzer canvases tend to be point-in-time artifacts: you run a workshop, produce a canvas, and reference it periodically. LEANSpark is built for continuous iteration. Your business model evolves as you run experiments, gather evidence, and update assumptions. The tool tracks this progression and adapts its guidance accordingly.
This maps to how startups actually work. You don't design a business model once — you iterate on it weekly based on what you learn from customers.
### Built for Solo Founders and Small Teams
Strategyzer's pricing and feature set are optimized for enterprise teams with budgets for per-seat licensing and workshop facilitation. LEANSpark is built for the founder who's working nights and weekends on their idea, the two-person team that needs to validate before hiring, the bootstrapper who needs methodology without the enterprise price tag.
### Lean Canvas Over Business Model Canvas
The canvas underneath each tool shapes what you focus on. Strategyzer is built on the Business Model Canvas, which maps nine blocks oriented around value delivery and operational architecture — Key Partners, Key Activities, Key Resources, Customer Relationships, and so on. This is excellent for documenting how a working business operates.
LEANSpark is built on the [Lean Canvas](/compare/lean-canvas-vs-bmc/), which replaces four of those blocks with startup-specific ones: Problem, Solution, Key Metrics, and Unfair Advantage. The reasoning is simple — when you're pre-product-market fit, you don't yet need to catalog key partners or map customer relationship channels. You need to understand your problem deeply, define the metrics that prove traction, and start building toward a defensible position.
This isn't a cosmetic difference. The BMC's architecture-first framing naturally leads teams toward planning mode: "Who are our partners? What activities do we perform?" The Lean Canvas's risk-first framing leads toward validation mode: "What's the riskiest assumption? How do we test it?" The canvas you start with shapes the questions you ask — and the questions you ask determine how fast you learn.
For a detailed comparison of the two canvases — including the backstory from Ash Maurya on why he created Lean Canvas as an adaptation of the BMC — see [Lean Canvas vs Business Model Canvas](/compare/lean-canvas-vs-bmc/).
## The Philosophical Split
Strategyzer's worldview is rooted in strategic design: understand the landscape, design the model, test and adapt. It's thorough, structured, and works well when you have the time and team to do it properly.
LEANSpark's worldview is rooted in lean startup principles: your initial model is mostly wrong, speed of learning is your primary advantage, and the fastest path to truth is through small, focused experiments. It's opinionated, directive, and built for urgency.
Neither worldview is wrong. They serve different contexts.
## When to Use Which
**Use Strategyzer when:**
- You're in a corporate innovation team with multiple stakeholders
- You need workshop facilitation tools for group exercises
- You're teaching business model design in an academic setting
- You need a recognized framework for investor or board presentations
- Your business is past product-market fit and you're optimizing the model
**Use LEANSpark when:**
- You're a founder validating a new venture idea
- You need AI-driven challenge, not just AI-assisted filling
- You want structured 90-day validation cycles with specific experiments
- You're working solo or with a small co-founding team
- Speed of learning matters more than comprehensiveness of documentation
## The Verdict
Strategyzer is the established leader in business model design tools, with deep roots in enterprise, education, and consulting. If you need to run workshops, collaborate with large teams, or use the globally recognized BMC format, Strategyzer is the natural choice.
LEANSpark is purpose-built for founders who need to validate fast. Its AI-native approach, Lean Canvas foundation, and structured validation methodology make it the better fit for early-stage ventures where the primary goal is learning, not planning. If you're pre-product-market fit and need a co-pilot who'll challenge your assumptions rather than help you document them, LEANSpark is where you should start.
---
### LEANSpark vs Zigzag: Validation Depth vs All-in-One Bundle
Zigzag bundles canvas, website, pitch deck, and legal docs for $8/month. LEANSpark goes deep on validation. Here's how to choose.
URL: https://leanspark.ai/compare/leanspark-vs-zigzag/
Zigzag is an all-in-one startup platform that bundles business model canvas creation with website building, pitch deck generation, legal document templates, and more — all for $8/month. LEANSpark is a focused AI-powered validation tool built on the Lean Canvas and Continuous Innovation Framework. They represent two very different philosophies about what early-stage founders actually need.
## At a Glance
| Dimension | LEANSpark | Zigzag |
|-----------|-----------|--------|
| **Approach** | Deep validation methodology | Broad startup toolkit |
| **Scope** | Business model validation + experiment design | Canvas + website + pitch deck + legal docs |
| **AI role** | Methodology engine — challenges assumptions | Generation assistant — creates artifacts |
| **Methodology** | Continuous Innovation Framework | General business planning |
| **Pricing** | Free tier + credit-based plans | $8/month all-inclusive |
| **Canvas type** | Lean Canvas (by the creator) | Business Model Canvas + Lean Canvas |
| **Distribution** | Direct to founders | Accelerator partnerships |
## Where Zigzag Excels
Zigzag has built a compelling value proposition, especially for cost-conscious founders:
### Aggressive Bundling at Low Cost
For $8/month, you get canvas tools, a website builder, pitch deck generator, legal document templates, and basic AI assistance. If you're looking for "one tool to start a company with," Zigzag's breadth-per-dollar ratio is hard to beat. For founders in earlier stages who need basic infrastructure, this bundling makes sense.
### Accelerator Partnerships
Zigzag has built relationships with startup accelerators and incubator programs. This gives them distribution that many AI startup tools lack — founders encounter Zigzag through trusted channels rather than through search or ads.
### Low Barrier to Entry
The combination of low price and broad functionality means founders can get started without committing to multiple tools or significant costs. You won't outgrow Zigzag quickly, but you won't invest much getting started either.
### Practical Artifact Generation
Need a basic website to test your idea? A pitch deck for an accelerator application? A canvas to share with advisors? Zigzag covers all of these without requiring you to learn multiple tools.
## Where LEANSpark Excels
LEANSpark does one thing and goes deep on it: helping founders validate whether their business model actually works.
### Depth Over Breadth
Zigzag gives you a canvas tool alongside a website builder and pitch deck generator. LEANSpark gives you a canvas tool embedded in a complete validation methodology — 7-dimension stress testing, Customer Forces analysis, experiment design, sprint planning, and PDCA tracking.
The tradeoff is clear: Zigzag covers more surface area, LEANSpark goes deeper on the thing that matters most at the early stage. A pitch deck based on untested assumptions is a liability, not an asset. A website for a product nobody wants is wasted effort. Validation comes first — everything else should follow evidence.
### Methodology From the Source
LEANSpark is built by Ash Maurya, the creator of Lean Canvas. The tool doesn't just implement the canvas as a template — it embodies the full methodology that the canvas was designed to support, including concepts developed over 15 years of working with thousands of founders.
When Zigzag offers Lean Canvas as one feature among many, it's using the framework as an artifact. LEANSpark uses it as the starting point for structured validation.
### AI That Challenges, Not Confirms
Zigzag's AI helps you fill in templates and generate documents. LEANSpark's AI challenges your assumptions, identifies your riskiest hypotheses, and designs specific experiments to test them. The difference is between an AI assistant that makes you feel productive and an AI co-founder that makes you actually reduce risk.
### Continuous Learning Loop
LEANSpark is built for iteration. Your business model evolves as you run experiments and gather evidence. The tool tracks this progression — what you tested, what you learned, what changed — and adapts its guidance accordingly. This is fundamentally different from generating a canvas once and moving on to building a website.
Validation before artifacts. Depth before breadth.
## The Philosophical Split
Zigzag's implicit thesis is: "Founders need a lot of basic tools, and the cheaper and more bundled, the better." This makes sense if you believe the main barrier to starting up is access to tools and infrastructure.
LEANSpark's thesis is: "The main barrier isn't tools — it's knowing whether you're building the right thing." Most startups don't fail because they couldn't afford a pitch deck or didn't have a website. They fail because they built something nobody wanted. Validation is the highest-leverage activity at the early stage, and it deserves a dedicated, deep tool.
## When to Use Which
**Use Zigzag when:**
- You need basic startup infrastructure (website, pitch deck, legal docs) on a tight budget
- You're in an accelerator that partners with Zigzag
- You want one low-cost platform that covers many startup needs
- Your primary constraint is cost, and you need breadth over depth
**Use LEANSpark when:**
- You need to validate whether your business idea actually works before building
- You want AI-driven methodology, not just AI-assisted templates
- You want structured validation with experiment design and progress tracking
- You care more about whether your idea is right than whether you have a pitch deck
- You want the methodology from the creator of Lean Canvas
## The Verdict
Zigzag and LEANSpark serve different needs at different price points. Zigzag is a startup utility belt — it gives you a little bit of everything at a low monthly cost. If you need basic infrastructure and can't afford specialized tools, it's a reasonable starting point.
LEANSpark is a specialized validation tool. It doesn't build your website or generate your legal docs. It helps you figure out whether you should be building a website at all — whether your business model has real potential, what your riskiest assumptions are, and how to test them systematically. That's a more narrow scope, but it addresses the single highest-risk question every founder faces: am I building something people actually want?
Breadth is comforting. Depth is what reduces risk.
---