Free Business learning guide
Launch a Startup: From Idea to Product
Launch a Startup: From Idea to Product — a free intermediate-level guide covering launch a startup from idea to product. Learn with clear explanations,...
What you will learn
1. Idea Generation & Validation
A Startup Story in Ten Minutes Emma, a freelance graphic designer, spends evenings scrolling through freelance forums. She notices a recurring complaint: “I wish I could see how a brand redesign would look on my actual website before I commit.” Within a single coffee break, she sketches a simple web‑based mock‑up tool, sketches a landing page, and fires off a quick survey to her network. Two days later, the landing page has generated 120 sign‑ups and 15 people have volunteered to be early testers. Emma now has a concrete signal that the problem she sensed is real enough to pursue further. Emma’s experience illustrates the core loop of idea generation → rapid validation → data‑driven decision. This chapter equips you with the frameworks, criteria, and experiment playbooks you need to replicate—or improve upon—this loop for any startup concept. --- 1. Brainstorming Frameworks That Produce Viable Ideas Generating ideas is not a free‑form brainstorm; it is a disciplined sprint that forces you to look at problems from multiple angles. Below are four proven frameworks that help you move from vague inspiration to concrete, testable concepts. 1.1 SCAMPER SCAMPER is an acronym for Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse. Use it to interrogate an existing product or process: 1. Substitute – What component can you replace? (e.g., replace a physical prototype with a digital mock‑up) 2. Combine – Can two services be merged? (e.g., combine brand mock‑ups with a price‑estimation tool) 3. Adapt – What can you borrow from another industry? (e.g., use AR tech from gaming for design previews) 4. Modify – Change scale, shape, or attributes. (e.g., shrink the tool to a browser extension) 5. Put to another use – Repurpose the core technology. (e.g., use the mock‑up engine for interior design) 6. Eliminate – Remove non‑essential features. (e.g., drop the need for a full design suite) 7. Reverse – Flip the process flow. (e.g., let clients start with a mock‑up and then request a designer) How to run a SCAMPER session - Gather 4–6 participants with diverse perspectives. - Allocate 5 minutes per prompt; record every suggestion, no matter how wild. - After the session, cluster the ideas by theme and select the most promising clusters for further exploration. 1.2 Jobs‑to‑Be‑Done (JTBD) Ideation JTBD frames the market as a collection of “jobs” that customers hire products to accomplish. The classic format is: When [situation], I want to [motivation], so I can [desired outcome]. Steps to apply JTBD 1. Collect real‑world job statements – Interview 5–10 potential users or scrape forum posts. 2. Identify pain points – Highlight verbs that indicate frustration (“struggle,” “cannot,” “spend hours”). 3. Generate solution concepts – For each high‑pain job, brainstorm …
2. Market & Customer Research
Opening: The Moment the Numbers Speak When Maya, a former nurse, sketched a prototype for a wearable that alerts caregivers when a diabetic patient’s glucose level spikes, her friends loved the idea. Yet within a week of the SCAMPER session, a question kept resurfacing: “Who exactly will buy this, and how big is the market?” The answer didn’t come from intuition alone—it required a disciplined dive into market sizing, customer psychology, and competitor landscapes. By the time Maya could articulate a Total Addressable Market (TAM) of $4 billion, a Served Available Market (SAM) of $800 million, and a realistic Share of Market (SOM) of 2 %, her pitch transformed from a vague concept into a fundable venture. The same rigor is needed for every startup moving from idea to product. Below is a step‑by‑step toolkit that builds on the Idea Generation & Validation work you’ve already done (SCAMPER, JTBD, scoring matrices). It will help you turn those early insights into hard numbers, vivid customer personas, and a crystal‑clear value proposition. --- 1. Mapping the Market Landscape 1.1. Why Distinguish TAM, SAM, and SOM? - TAM tells you the theoretical ceiling—the total revenue opportunity if you captured 100 % of every possible buyer worldwide. - SAM narrows the view to the segment you can realistically serve given geography, distribution channels, regulatory constraints, or product scope. - SOM is the initial target—the slice of SAM you expect to win in the first 12‑24 months, based on resources, go‑to‑market strategy, and competitive positioning. Understanding these three layers prevents over‑optimistic forecasts and grounds your business model in reality. 1.2. Top‑Down vs. Bottom‑Up Sizing | Approach | How It Works | When to Use It | |----------|--------------|----------------| | Top‑Down | Start with macro data (e.g., global health‑care spend) and apply percentages (e.g., % of patients with Type 1 diabetes). | Quick sanity checks; when primary data is scarce. | | Bottom‑Up | Aggregate revenue potential from micro units (e.g., number of clinics × average device price × replacement cycle). | When you have reliable unit‑level data; yields more precise SAM. | | Value‑Theory | Estimate the monetary value a customer derives from solving the JTBD, then infer willingness to pay. | Useful after JTBD work; aligns market size with actual price points. | Practical tip: Begin with a top‑down TAM estimate to set the ceiling, then refine SAM and SOM with bottom‑up calculations anchored in your JTBD findings. 1.3. Data Sources & Tools - Industry reports (e.g., Gartner, IDC, Statista) – provide macro numbers and growth forecasts. - Government databases (e.g., WHO, CDC, Eurostat) – reliable for health‑related TAM figures. - Company filings & investor decks – reveal competitor revenue and market assumptions. - Survey …
3. Business Model Design
From Insight to Blueprint: Turning a Validated Idea into a Working Business Model Maya spent the past month iterating on the job‑to‑be‑done she uncovered in Chapter 2: “I need a quick, healthy dinner that fits my busy schedule and aligns with my plant‑based diet.” After a SCAMPER session she refined the concept into a ready‑to‑cook meal‑kit that uses locally sourced ingredients and a single‑serving portion model. The idea passed the validation checklist from Idea Generation & Validation—early adopters rated the solution 8.5/10 on problem severity and expressed willingness to pay. Now Maya faces the next hurdle: How does she turn that validated insight into a sustainable, cash‑positive business? The answer lies in the Business Model Canvas (BMC)—a visual framework that forces founders to articulate every critical component of their venture before spending money on product development. This chapter walks you through populating each canvas block with research‑backed content, selecting revenue streams and pricing tactics, identifying the resources, activities, and partnerships that will make the model work, and finally testing the cost structure against projected cash flow. --- 1. The Business Model Canvas: A Quick Recap The BMC consists of nine interlocking blocks: 1. Customer Segments 2. Value Propositions 3. Channels 4. Customer Relationships 5. Revenue Streams 6. Key Resources 7. Key Activities 8. Key Partnerships 9. Cost Structure While the canvas itself is a visual tool, each block should be grounded in data you already gathered in Market & Customer Research (demographics, psychographics, buying behavior) and the JTBD framework (core functional, social, and emotional jobs). The following sections show how to translate that research into concrete entries. --- 2. Populating the Canvas with Evidence 2.1 Customer Segments Goal: Define distinct groups that share a common set of jobs, pains, and gains. How to do it: 1. Cluster the JTBD data you collected (e.g., “time‑starved professionals,” “health‑conscious students,” “eco‑aware families”). 2. Validate with secondary research – industry reports, census data, or Nielsen studies that confirm the size and growth rate of each segment. 3. Prioritize using a segment scoring matrix (market size, accessibility, fit with value proposition, willingness to pay). Example entry: - Segment A – Urban Professionals (25‑40, $60‑90k income) – Primary JTBD: “quick, nutritious dinner after work.” - Segment B – College Students (18‑24, $15‑30k income) – JTBD: “affordable, easy‑prep meals that fit a plant‑based diet.” 2.2 Value Propositions Goal: Articulate the bundle of benefits that solves the identified jobs better than alternatives. Research‑backed inputs: - Problem Severity scores from the earlier scoring matrix (e.g., 8.2/10 for “lack of time”). - Competitive analysis (price, quality, convenience) conducted in Market & Customer Research. - SCAMPER insights – e.g., “Combine meal‑kit with a subscription model to eliminate grocery trips.” Crafting the …
4. Minimum Viable Product (MVP) Planning
From Hypothesis to Feature Blueprint Imagine Maya, who spent weeks mapping her “smart pantry” idea through the SCAMPER lens and JTBD interviews (see Market & Customer Research). She now knows the core job: “Help busy families keep track of food expiration dates without extra effort.” The next question is what to build first. The MVP is not a “small version” of the final product; it is a controlled experiment that validates the most critical assumptions while consuming the least engineering effort. Start by listing every feature that could satisfy the identified job, then attach each to a hypothesis that can be tested. | Feature Idea | Underlying Hypothesis | Reason for Inclusion | |--------------|----------------------|----------------------| | Barcode scanner that auto‑logs items | Users will prefer scanning over manual entry | Directly addresses friction in current food‑tracking habits | | Expiration alerts via push notification | Timely alerts will reduce food waste by ≥15% | Core value proposition | | Shared family pantry view | Families will coordinate purchases if they see each other's stock | Expands network effect, tests collaborative usage | Step 1: Capture hypotheses – Write them in an “If‑Then” format (e.g., If users receive expiration alerts, then they will discard fewer items). This aligns the feature list with the validation loop introduced in Idea Generation & Validation. Step 2: Group by risk – Separate value‑risk (does the feature solve a real pain?) from growth‑risk (does it drive adoption?). Prioritize value‑risk first; an MVP that fails to prove value is a dead end regardless of growth tactics. --- Prioritizing Features for Hypothesis Testing 1. Choose a Prioritization Framework For an MVP, the framework must surface testability and effort. Three popular methods work well: 1. ICE Score – Impact, Confidence, Ease (each 1‑10). 2. RICE Score – Reach, Impact, Confidence, Effort (adds granularity for user‑base size). 3. Weighted Shortest Job First (WSJF) – Cost of Delay ÷ Job Size (useful when you already have a backlog). Because the MVP’s purpose is hypothesis validation, ICE is often the quickest to apply. 2. Apply ICE to Maya’s List | Feature | Impact (1‑10) | Confidence (1‑10) | Ease (1‑10) | ICE Total | |---------|---------------|-------------------|------------|-----------| | Barcode scanner | 8 | 7 | 5 | 20 | | Expiration alerts | 9 | 8 | 6 | 23 | | Shared view | 6 | 5 | 4 | 15 | The highest‑scoring feature, Expiration alerts, directly tests the core value hypothesis and is relatively easy to implement. 3. Validate with a Simple Scoring Matrix Combine the ICE results with the hypothesis risk matrix (high‑risk hypotheses get higher priority). | Feature | ICE Total | Hypothesis Risk (Low/Med/High) | Priority | |---------|-----------|------------------------------|----------| | …
5. Building the Founding Team
The First Five‑Person Team: A Real‑World Snapshot Imagine Maya and Luis, the co‑founders of EcoCharge, a startup that emerged from a SCAMPER session on “how to make electric‑bike charging more sustainable.” Their market‑research interviews (see Market & Customer Research) revealed a strong demand for a portable solar charger that could double as a backpack. The Business Model Design chapter helped them map a subscription‑plus‑hardware revenue stream, and their MVP Planning outlined a prototype that could be built in three months. But there’s a glaring problem: Maya is a product designer, Luis is a serial entrepreneur with sales chops, and neither has deep hardware engineering or supply‑chain expertise. Their vision is solid, yet the skill gaps threaten the timeline and the credibility of the MVP. Their next move? Build a founding team that fills those gaps, aligns incentives, and establishes a culture that can weather the inevitable storms of a startup. The scenario above illustrates why the founding team is more than a collection of résumés—it’s the engine that translates ideas into products. The sections that follow walk you through the practical steps to identify critical roles, structure agreements, hire early talent, and cement the cultural foundations that keep the team moving forward. --- 1. Mapping Critical Roles to Your Startup’s Needs 1.1 Start with the Business Model Canvas Your Business Model Design work already identified Key Activities, Key Resources, and Key Partnerships. Translate each of these blocks into functional responsibilities: | Canvas Element | Core Function | Typical Founder Role | |----------------|---------------|----------------------| | Value Proposition | Product definition & user experience | Product/UX Lead | | Key Activities | Engineering, manufacturing, sales | Technical Co‑founder, Head of Sales | | Key Resources | Capital, IP, talent | Finance/Operations Lead | | Key Partnerships | Suppliers, distributors | Business Development Lead | If your MVP Planning shows that the first deliverable is a hardware prototype, hardware engineering becomes a non‑negotiable role. Conversely, a SaaS‑first MVP would prioritize software architecture and data engineering. 1.2 Conduct a Skill‑Gap Audit 1. List existing capabilities – write down each founder’s primary skill set (e.g., Maya: industrial design, user research; Luis: fundraising, B2B sales). 2. Identify MVP‑critical tasks – pull the MVP milestone list (from the MVP Planning chapter) and assign each task to a skill category (e.g., PCB design, firmware development, supply‑chain logistics). 3. Highlight gaps – any task without a clear owner signals a role you must fill or an existing founder must upskill. Example Gap Matrix for EcoCharge | MVP Task | Skill Needed | Owner | Gap? | |----------|--------------|-------|------| | Solar panel PCB layout | Electrical engineering | — | ✔ | | Battery management firmware | Embedded software | — | …
6. Product Development & Iteration
Getting Started: From MVP Blueprint to First Sprint You’ve just finished the MVP Planning chapter and sketched out a feature set that solves the core job‑to‑be‑done you uncovered during your JTBD research. The next step is turning that blueprint into working code—fast, safely, and with the ability to adapt on the fly. Scenario: Luna, a solo founder of a smart‑garden startup, has a list of three MVP features: (1) soil‑moisture sensor integration, (2) a mobile dashboard, and (3) push notifications for watering reminders. She needs a process that lets her ship the sensor‑integration prototype in two weeks, gather real‑world feedback, and then iterate on the dashboard without getting stuck in endless development cycles. The methodology that makes this possible is Agile development—specifically Scrum or Kanban, whichever fits your team’s size, cadence, and risk tolerance. This chapter walks you through setting up that workflow, weaving user feedback into every loop, ensuring quality, and measuring progress against the success metrics you defined in the Business Model Design chapter. --- Choosing the Right Agile Framework: Scrum vs. Kanban Both frameworks share core Agile values—incremental delivery, collaboration, and responsiveness to change—but they differ in structure and cadence. | Aspect | Scrum | Kanban | |--------|-------|--------| | Timeboxing | Fixed‑length sprints (usually 1‑4 weeks) | Continuous flow; no fixed sprint | | Roles | Product Owner, Scrum Master, Development Team | No prescribed roles; team self‑organizes | | Commitment | Team commits to a sprint backlog | Pull‑based work; commit when capacity allows | | Ceremonies | Sprint Planning, Daily Stand‑up, Sprint Review, Retrospective | Optional stand‑ups; focus on visual board updates | | Best for | Teams needing strong cadence, clear deliverables, and regular demo cycles | Small teams or maintenance work where work items vary in size and urgency | When to start with Scrum: - You have a clear set of MVP features (the “product backlog”) and need to demonstrate progress to investors or early adopters. - Your team includes a dedicated product owner (often the founder) who can prioritize items. When Kanban is a better fit: - You’re a solo founder or a tiny team that can’t sustain sprint ceremonies. - Work is highly unpredictable (e.g., hardware‑sensor integration) and you need flexibility to reshuffle priorities daily. Tip: Many startups begin with Scrum to establish discipline, then transition to Kanban once the product stabilizes and the focus shifts to continuous delivery. --- Designing the Sprint Cycle Assuming you opt for Scrum, here’s a pragmatic sprint structure tuned for early‑stage startups. 1. Sprint Length: 2 weeks (14 days) – short enough to stay responsive, long enough to produce a tangible increment. 2. Sprint Planning (Day 1): - Review the product backlog – pull …
7. Legal Foundations & Compliance
Choosing the Right Business Entity and Registering It When you move from Product Development & Iteration to actually shipping your MVP, the first legal decision that will shape liability, taxes, and future fundraising is the choice of business entity. Common Entity Options | Entity | Liability Shield | Tax Treatment | Governance | Typical Use | |--------|------------------|---------------|------------|-------------| | Sole Proprietorship | None (personal assets at risk) | Pass‑through | Informal | Solo freelancers | | General Partnership | None (each partner liable) | Pass‑through | Informal | Small teams without outside investors | | Limited Liability Company (LLC) | Personal assets protected | Pass‑through (or elect S‑corp) | Flexible operating agreement | Early‑stage startups, services | | C‑Corporation | Full shield | Double tax (but can elect S‑corp if eligible) | Formal board & shareholder structure | Startups planning VC rounds | | Benefit Corporation (B‑Corp) | Full shield | Same as C‑corp | Adds public‑benefit purpose | Mission‑driven ventures | Decision Factors 1. Liability Needs – If your product could expose users to risk (e.g., a health‑monitoring app), an LLC or C‑corp is usually safest. 2. Tax Simplicity vs. Growth Plans – Pass‑through entities avoid corporate tax but can become cumbersome when you bring on investors who prefer the clean cap table of a C‑corp. 3. Governance Preferences – An operating agreement (LLC) is less rigid than corporate bylaws, but a board can add credibility with partners and early customers. 4. State‑Specific Costs – Some states (Delaware, Nevada) are popular for C‑corps because of predictable corporate law; other states may have lower filing fees for LLCs. Quick Decision Matrix (1‑5 rating) | Factor | LLC | C‑Corp | |--------|-----|--------| | Liability protection | 5 | 5 | | Tax simplicity (solo) | 5 | 2 | | Investor friendliness | 2 | 5 | | Administrative burden | 2 | 4 | | Flexibility for future conversion | 3 | 5 | If the total score favors the C‑Corp, file as a corporation; otherwise, start with an LLC and plan to convert later. Registration Checklist 1. Name Availability – Conduct a state‑level search; reserve the name if possible. 2. File Formation Documents – Articles of Incorporation (C‑corp) or Articles of Organization (LLC) with the Secretary of State. 3. Obtain an EIN – Apply online at IRS.gov; needed for bank accounts, payroll, and tax filings. 4. Create an Operating Agreement or Bylaws – Even if not required by law, this internal document clarifies ownership and governance. 5. Register for State Taxes – Sales tax, unemployment insurance, etc., depending on where you’ll have employees or physical presence. 6. Open a Business Bank Account – Keep personal and company finances separate from …
8. Fundraising Basics
A Seed‑Stage Reality Check Imagine you’ve spent the last six months turning a validated idea into a functional MVP, your founding team is humming, and early‑user feedback is glowing. One of those users happens to be an angel investor who just sent you a “Let’s talk” email. The clock starts ticking: you have three weeks to decide whether to chase the opportunity, how much capital you truly need, and what you’ll give up in return. This scenario encapsulates the pivotal moment every founder faces when moving from product‑first thinking (see Minimum Viable Product (MVP) Planning) to capital‑first execution. The decisions you make now will shape ownership, control, and the runway that determines whether your startup survives its first twelve months. --- 1. The Seed‑Stage Landscape 1.1 What “Seed” Really Means Stage – Post‑MVP, pre‑product‑market fit, typically 6‑18 months after Idea Generation & Validation. Capital Goal – Enough to hit the next major milestone (e.g., product‑market fit, first paying customers, or a larger beta). Typical Amount – $250 k – $2 M in the U.S.; lower in many other ecosystems. 1.2 Who’s Watching | Investor Type | Typical Check Size | What They Look For | Typical Deal Structure | |---------------|-------------------|--------------------|------------------------| | Friends & Family | <$100 k | Trust, founder credibility | SAFE or simple convertible note | | Angel Networks | $50 k – $250 k | Founder story, market size, early traction | SAFE, convertible note, or equity | | Seed‑Stage VCs | $250 k – $2 M | Scalable market, defensible tech, strong team | Preferred equity, often a lead investor | | Accelerators / Incubators | $20 k – $150 k + resources | Cohort fit, mentorability | SAFE, sometimes equity for program | | Crowdfunding (Equity) | $50 k – $500 k | Community appeal, consumer product | Equity on platform, often capped at $1 M | Understanding the motivations behind each source helps you tailor both outreach and the pitch deck. --- 2. Crafting a Compelling Pitch Deck A pitch deck is the visual embodiment of the story you began in Idea Generation & Validation. It must be concise, data‑driven, and tailored to the investor type you’re courting. 2.1 The 10‑Slide Blueprint 1. Cover – Company name, tagline, logo, contact. 2. Problem – Real‑world pain (reference JTBD statements from earlier research). 3. Solution – Your MVP, key differentiators. 4. Market – TAM, SAM, SOM with credible sources. 5. Business Model – Revenue streams and unit economics (link back to Business Model Design). 6. Traction – Metrics: users, revenue, churn, LTV/CAC. 7. Go‑to‑Market (preview) – Briefly hint at the upcoming chapter; investors want to see you’ve thought ahead. 8. Financials – 3‑year projections, runway, burn …
9. Go‑to‑Market Strategy
The Moment the Product Meets the Market Emma has spent the last six months turning a validated idea for a micro‑learning platform into a functional MVP. She’s secured a seed round, assembled a small founding team, and cleared all legal check‑boxes. The product is ready, but the real test begins now: how will she get the first 1,000 users to open the app and start learning? The answer lies in a disciplined Go‑to‑Market (GTM) strategy—one that ties the personas uncovered in Market & Customer Research to concrete acquisition channels, launches with purposeful campaigns, measures every step with analytics, and iterates fast enough to stay ahead of user expectations. The following framework walks you through each of those moves, turning the abstract notion of “launch” into an actionable roadmap. --- 1. Mapping Acquisition Channels to Target Personas 1.1 Start with the Persona Canvas Your market research already produced detailed personas (e.g., “Busy Professional Sam,” “Side‑Hustle Student Maya”). For each persona, answer three quick questions: 1. Where does this person spend time online? (forums, social platforms, newsletters) 2. What triggers a decision to try a new tool? (recommendations, free trials, peer pressure) 3. What barrier would stop them from signing up? (price, time, data‑privacy concerns) These answers become the Channel‑Fit Matrix—a two‑dimensional map that pairs personas with potential acquisition channels (paid ads, SEO, community outreach, partnerships, etc.). 1.2 Criteria for Prioritizing Channels Use a weighted scoring system to keep the selection objective. Typical criteria include: | Criterion | Why it matters | Example weight (1‑5) | |-----------|----------------|----------------------| | Reach – size of the audience relevant to the persona | Guarantees enough volume for testing | 4 | | Cost per Acquisition (CPA) – realistic to your budget | Controls burn rate | 5 | | Speed to Market – how quickly you can launch | Aligns with product launch timeline | 3 | | Fit with Value Proposition – does the channel convey your USP? | Improves conversion odds | 4 | | Data Availability – can you track performance? | Enables analytics loop | 5 | Score each channel‑persona pair, total the weighted scores, and rank. The top‑ranked combos become your initial acquisition mix. 1.3 Real‑World Example | Persona | Channel | Reach (5) | CPA (5) | Speed (3) | Fit (4) | Data (5) | Total | |---------|---------|-----------|---------|-----------|----------|----------|-----------| | Busy Professional Sam | LinkedIn Sponsored Content | 4 | 3 | 4 | 5 | 5 | 21 | | Side‑Hustle Student Maya | TikTok Influencer Partnerships | 5 | 2 | 5 | 4 | 4 | 20 | | Freelance Designer Alex | Dribbble Community Posts | 3 | 4 | 3 | 5 | 5 | …
10. Scaling Operations & Growth
From the First 1,000 Users to Tens of Thousands: A Scaling Snapshot Imagine NovaHealth, a digital‑health startup you’ve followed since its MVP days. After three months of relentless outreach, the team closed 150 paying clinics, hit $250 k ARR, and earned glowing Net Promoter Scores (NPS). The founders celebrate—but the next milestone looms: turning that early traction into a sustainable growth engine that can support 10‑plus‑million‑dollar ARR, multiple product lines, and entry into Europe and Asia. The challenge isn’t just “getting more customers.” It’s building repeatable, data‑driven sales and customer‑success processes, establishing the right performance metrics, tightening unit economics, and crafting a roadmap for the next funding round and international rollout. The steps below walk you through exactly that transition, leveraging the foundations you laid in earlier chapters—Idea Generation & Validation, Market & Customer Research, Business Model Design, MVP Planning, Founding Team, Product Development & Iteration, Legal Foundations & Compliance, Fundraising Basics, and Go‑to‑Market Strategy. --- 1. Building Repeatable Sales & Customer‑Success Processes 1.1 Turn Ad‑hoc Wins into a Sales Playbook 1. Map the current winning motions - List every touchpoint that led to a closed deal (e.g., inbound demo request → 30‑minute discovery call → custom ROI calculator → contract). - Capture the who, what, why for each step. 2. Identify the repeatable core - Which actions appear in 80 % of wins? - Which variables (industry, company size, pain point) are predictors of success? 3. Codify into a playbook - Stage definitions (Lead → MQL → SQL → Proposal → Closed‑Won/Lost). - Scripts & templates for each stage (email cadence, discovery questionnaire, proposal deck). - Decision‑criteria checklist that sales reps use to qualify prospects before moving them downstream. 4. Pilot and iterate - Roll the playbook to a small group of reps. - Capture conversion rates per stage and refine language or sequencing every two weeks. Tip: Leverage the JTBD insights you gathered in the “Steps to apply JTBD” section of the earlier chapter to frame discovery questions around the customer’s underlying job to be done. 1.2 Institutionalizing Customer Success 1. Define the CS lifecycle - Onboarding (first 30 days): product setup, training, quick‑win milestones. - Adoption (days 31‑90): usage monitoring, health score dashboards, proactive outreach. - Expansion & Advocacy (post‑90 days): upsell opportunities, NPS surveys, reference program. 2. Build a health‑score model - Combine usage metrics, support ticket frequency, and NPS into a single weighted score. - Set thresholds for “At‑Risk,” “Healthy,” and “Champion” customers. 3. Standardize the CS workflow - Automation: Trigger onboarding emails via a CRM workflow. - Playbooks: Scripts for “At‑Risk” outreach, “Champion” referral requests. - Escalation matrix: Who handles churn threats versus expansion conversations? 4. Close the loop with sales - Create a …
Continue learning
- Launch a Startup from Idea to Product – Step-by-Step RoadmapLaunch a Startup from Idea to Product – Step-by-Step Roadmap — a free intermediate-level guide covering launch a startup from idea to product. Learn...
- How to Launch a Startup: From Idea to ProductHow to Launch a Startup: From Idea to Product — a free intermediate-level guide covering launch a startup from idea to product. Learn with clear...
- How to Write a Business Plan: A Beginner's GuideHow to Write a Business Plan: A Beginner's Guide — a free beginner-level guide covering how to write a business plan. Learn with clear explanations,...
- How to Write a Business Plan for a StartupHow to Write a Business Plan for a Startup — a free beginner-level guide covering how to write a business plan for a startup. Learn with clear...