--- # === IDENTITY === id: business/customer-validation/pre-sale-loi-collection-playbook/2026 canonical_question: "How do I collect pre-sales and LOIs before building — templates, design partner agreements, pre-order strategies?" aliases: - "How to get letters of intent from customers before launching" - "Design partner agreement template for early-stage startup" - "Pre-order validation strategy before building product" - "Non-binding LOI template for B2B SaaS pre-sales" entity_type: execution_recipe domain: business > customer-validation > pre-sale-loi-collection-playbook region: global jurisdiction: global temporal_scope: 2025-2026 # === VERIFICATION === last_verified: 2026-03-11 confidence: 0.87 version: 1.0 first_published: 2026-03-11 # === TEMPORAL VALIDITY === temporal_validity: status: stable last_breaking_change: "Common Paper released updated LOI and Design Partner Agreement templates in 2024" next_review: 2026-09-07 change_sensitivity: low # === CONSTRAINTS === constraints: - "LOIs are non-binding — they do NOT guarantee revenue; do not present them to investors as confirmed ARR" - "Binding terms (confidentiality, exclusivity) in LOIs require legal review before signing" - "Design partner agreements must include IP assignment clauses to avoid due diligence problems during fundraising" - "Crowdfunding pre-orders may trigger consumer protection obligations depending on jurisdiction" - "Collect 4-6 signed LOIs minimum to demonstrate meaningful demand signal to investors" # === SKIP CONDITIONS === skip_this_unit_if: - condition: "User needs a strategic framework for customer validation, not execution steps" use_instead: "Search knowledgelib.io for a customer validation framework — no dedicated unit yet" - condition: "User already has paying customers and needs to scale sales" use_instead: "business/startup-sales/sales-strategy-early-stage-startups/2026" - condition: "User needs to validate with consumer market via landing page, not B2B LOIs" use_instead: "business/customer-validation/demand-signal-testing/2026" # === AGENT HINTS === inputs_needed: - key: business_model question: "Is this B2B, B2C, or marketplace?" type: choice options: ["B2B SaaS", "B2B services", "B2C product", "B2C SaaS", "marketplace"] - key: stage question: "What stage is the product?" type: choice options: ["idea only (no prototype)", "prototype/mockups exist", "MVP built but not launched", "launched but pre-revenue"] - key: target_acv question: "What is the expected annual contract value?" type: choice options: ["under $1K/year (self-serve)", "$1K-$10K/year (SMB)", "$10K-$50K/year (mid-market)", "$50K+/year (enterprise)"] - key: validation_goal question: "What is the primary validation goal?" type: choice options: ["prove demand for investors", "validate pricing", "secure design partners for product feedback", "generate pre-launch revenue"] # === EXECUTION METADATA === execution: required_inputs: - name: "ICP definition (ideal customer profile)" source: "agents/startup/persona-builder or manual" format: "structured data or document" - name: "Product concept description (problem, solution, key features)" source: "agents/startup/idea-intake or manual" format: "document or pitch deck" - name: "Target prospect list (5-20 companies/individuals)" source: "agents/startup/lead-generation or manual" format: "spreadsheet or CRM" outputs: - name: "Signed LOI/pre-order portfolio" format: "PDF folder + tracking spreadsheet" description: "4-6+ signed LOIs or pre-order commitments with named buyers, intended ACV, and timeline" - name: "Design partner agreements" format: "PDF signed agreements" description: "1-3 design partner agreements with feedback cadence, IP terms, and conversion pricing" - name: "Pre-sale validation summary" format: "document" description: "Summary report for investor decks: total committed intent value, buyer names, conversion timeline" tools_required: - name: "Google Docs or Notion" purpose: "Draft and share LOI/design partner templates" tier: free cost: "$0" alternatives: ["Microsoft Word", "Common Paper (free templates)"] - name: "DocuSign or PandaDoc" purpose: "Electronic signature collection" tier: paid cost: "$10-25/month" alternatives: ["HelloSign (free tier: 3/month)", "Google Docs (manual signature)", "printed PDF"] - name: "CRM or spreadsheet" purpose: "Track outreach, follow-ups, and conversion pipeline" tier: free cost: "$0" alternatives: ["HubSpot Free CRM", "Google Sheets", "Notion database", "Airtable"] - name: "Calendly or Cal.com" purpose: "Schedule prospect meetings" tier: free cost: "$0" alternatives: ["Google Calendar manual scheduling"] credentials_needed: - service: "DocuSign or HelloSign" type: "account login" where_to_get: "https://www.docusign.com or https://www.hellosign.com" free_tier_limits: "HelloSign: 3 signature requests/month free" - service: "HubSpot CRM" type: "account login" where_to_get: "https://www.hubspot.com/products/crm" free_tier_limits: "Unlimited contacts, basic pipeline tracking" estimated_duration: "2-4 weeks for full cycle (outreach through signed LOIs)" estimated_cost: "$0 (free tier tools) to $50/month (paid e-signature + CRM)" # === DISTRIBUTION === canonical_source: "https://knowledgelib.io/business/customer-validation/pre-sale-loi-collection-playbook/2026" suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-11)" # === RELATED UNITS === related_kos: depends_on: - id: "business/customer-research/ideal-customer-profile-framework/2026" label: "Building a scored ICP — firmographic/demographic criteria, behavioral signals, disqualifiers and a scoring rubric" - id: "business/customer-validation/customer-discovery-interview-playbook/2026" label: "Running 20-40 customer discovery interviews — scripts, synthesis, and the 8/10-unprompted validation threshold" feeds_into: - id: "business/startup-sales/sales-strategy-early-stage-startups/2026" label: "Early-stage sales build — founder-led closing of the first 10-20 customers, CRM and pipeline setup, then first-rep transition triggers" - id: "business/fundraising/pitch-deck-slide-by-slide-guide/2026" label: "Building each pitch deck slide — required content per slide, traction-slide proof (including LOIs and pilot agreements), common failures, design rules" related_to: - id: "business/customer-validation/demand-signal-testing/2026" label: "Demand signal tests — fake door and landing page smoke tests, waitlist conversion, crowdfunding, concierge MVP" alternative_to: - id: "business/customer-validation/demand-signal-testing/2026" label: "Concierge MVP validation (Test D) — manual delivery to 5-15 customers, NPS thresholds, go/pivot/kill criteria, within a five-test demand suite" # === SOURCES === sources: - id: src1 title: "What is an LOI? Closing customers, VCs, and more" author: Common Paper url: https://commonpaper.com/blog/what-is-an-loi/ type: industry_guide published: 2024-06-15 reliability: authoritative - id: src2 title: "How To Work With Design Partners" author: Common Paper url: https://commonpaper.com/blog/design-partner/ type: industry_guide published: 2024-03-20 reliability: authoritative - id: src3 title: "A Framework for Finding A Design Partner" author: Andreessen Horowitz (a16z) url: https://a16z.com/a-framework-for-finding-a-design-partner/ type: expert_analysis published: 2024-01-15 reliability: authoritative - id: src4 title: "Case Study: Using an LOI to get customer feedback on a minimum viable product" author: Eric Ries (Startup Lessons Learned) url: http://www.startuplessonslearned.com/2009/10/case-study-using-loi-to-get-customer.html type: case_study published: 2009-10-15 reliability: authoritative - id: src5 title: "Non-Binding Letters of Intent from Potential Customers" author: JumpStart Inc url: https://www.jumpstartinc.org/wp-content/uploads/2016/09/Non-Binding-Letters-of-Intent-9616.pdf type: industry_guide published: 2016-09-01 reliability: authoritative - id: src6 title: "Free Design Partner Agreement" author: Common Paper url: https://commonpaper.com/standards/design-partner-agreement/ type: template published: 2024-05-01 reliability: authoritative - id: src7 title: "YC's Essential Startup Advice" author: Y Combinator url: https://www.ycombinator.com/library/4D-yc-s-essential-startup-advice type: expert_analysis published: 2024-01-01 reliability: authoritative - id: src8 title: "LOI Template: Close Deals Faster" author: Close.com url: https://blog.close.com/loi-template/ type: template published: 2024-08-10 reliability: established --- # Pre-Sale LOI Collection Playbook ## Purpose This recipe produces a portfolio of 4-6+ signed letters of intent, design partner agreements, and pre-order commitments from named buyers — before writing a single line of production code. The output is a validated demand signal with specific dollar amounts, buyer names, and timelines that can be presented to investors, used to prioritize features, and converted into first customers at launch. [src1] ## Prerequisites - [ ] **ICP definition** available (manual or from persona-builder) — target industry, company size, buyer persona, and pain point clearly defined - [ ] **Product concept description** — problem statement, proposed solution, 3-5 key features, and rough pricing model documented - [ ] **Target prospect list** of 15-30 companies/individuals matching ICP — with contact names, titles, and email addresses - [ ] **E-signature tool** — account at DocuSign, HelloSign, or PandaDoc (HelloSign free tier: 3 requests/month) - [ ] **CRM or tracking spreadsheet** — HubSpot Free CRM, Google Sheets, or Notion database configured with pipeline stages ## Constraints - LOIs are non-binding agreements — never represent them as confirmed revenue or signed contracts to investors. State them as "letters of intent" or "non-binding commitments." [src1] - Binding clauses (confidentiality, exclusivity, non-solicitation) require legal review. Keep binding terms to confidentiality only unless founder has legal counsel. [src5] - Design partner agreements must include IP assignment clauses. Without them, due diligence during fundraising will flag IP ownership risks. [src2] - Crowdfunding pre-orders (Kickstarter, IndieGoGo) may create consumer protection obligations — refund policies, delivery timelines, and FTC disclosure requirements apply in the US. - Do not collect payment for pre-orders without a clear refund policy and delivery timeline. Failure to deliver can trigger FTC enforcement action. - Keep LOIs to 1-2 pages maximum. Longer documents trigger legal review cycles that kill conversion rates. [src8] ## Tool Selection Decision ``` Which path? ├── B2B SaaS/services, ACV > $10K │ └── PATH A: Enterprise LOI + Design Partner — formal LOI with named champion ├── B2B SaaS/services, ACV < $10K │ └── PATH B: Lightweight LOI + Pilot Agreement — 1-page LOI, shorter cycle ├── B2C product (physical or digital) │ └── PATH C: Pre-Order / Crowdfunding — landing page + payment commitment └── Marketplace / Platform └── PATH D: Supply + Demand LOIs — dual-sided intent collection ``` | Path | Tools | Cost | Speed | Output Quality | |------|-------|------|-------|---------------| | A: Enterprise LOI | Google Docs + DocuSign + CRM | $0-25/mo | 3-4 weeks | High — named buyers with dollar amounts | | B: Lightweight LOI | Notion + HelloSign + Sheets | $0 | 1-2 weeks | Medium — faster but lower commitment signal | | C: Pre-Order | Landing page + Stripe/Gumroad | $0-29/mo | 1-2 weeks | High — actual payment = strongest signal | | D: Marketplace LOIs | Google Docs + CRM | $0 | 2-3 weeks | Medium — need both sides validated | ## Execution Flow ### Step 1: Prepare LOI / Agreement Templates **Duration**: 2-4 hours **Tool**: Google Docs, Common Paper templates Select and customize the appropriate template based on your path: **PATH A/B — LOI Template Structure:** ```text LETTER OF INTENT Date: [DATE] From: [PROSPECT COMPANY NAME], [PROSPECT CONTACT NAME], [TITLE] To: [YOUR COMPANY NAME] 1. INTENT [Prospect Company] intends to evaluate and purchase [Your Product] for use in [specific use case / department] upon commercial availability, subject to the product meeting the requirements described below. 2. ANTICIPATED TERMS - Estimated annual contract value: $[AMOUNT] - Expected start date: [DATE or "upon commercial launch"] - Initial term: [12 months / 24 months] - Users / seats: [NUMBER] 3. REQUIREMENTS FOR PURCHASE - [Feature/capability 1 must be available] - [Integration with X system required] - [Security certification Y required] 4. NON-BINDING NATURE This letter is non-binding and does not obligate either party to enter into a definitive agreement. Either party may withdraw at any time for any reason. 5. CONFIDENTIALITY (BINDING) Both parties agree to keep the terms of this letter and any proprietary information shared during evaluation confidential. Signature: ________________ Date: ________ Name: [PROSPECT NAME] Title: [TITLE] Company: [COMPANY] ``` **PATH A — Design Partner Agreement additions** (use Common Paper template as base): [src6] - Feedback cadence: bi-weekly 30-minute calls - Reference rights: permission to use company name and logo - Pricing: [X]% discount off GA pricing for [Y] months post-launch - IP: all IP developed during partnership is owned by your company - Termination: either party can exit with 30 days written notice **PATH C — Pre-Order structure:** - Landing page with product description, pricing tiers, and expected delivery date - Payment collection via Stripe or Gumroad with clear refund policy - Confirmation email with order number and timeline **Verify**: Template is complete, all bracketed fields identified for customization, non-binding language is clear. **If failed**: Use Common Paper's free LOI template at commonpaper.com/documents/letter-of-intent as starting point. ### Step 2: Build Target List and Prioritize **Duration**: 2-4 hours **Tool**: CRM or Google Sheets Create a tracking spreadsheet with these columns: ```text | Company | Contact | Title | Email | ICP Score | Pain Level | Status | LOI Type | Next Action | Follow-Up Date | |---------|---------|-------|-------|-----------|------------|--------|----------|-------------|---------------| ``` Score and prioritize prospects using three criteria from a16z's design partner framework: [src3] 1. **Representativeness** (1-5): Does this prospect mirror your broader target market? Avoid outliers whose needs would pull your product in a non-scalable direction. 2. **Urgency** (1-5): Has the prospect already tried alternatives or built workarounds? Higher urgency = faster LOI signing. 3. **Capacity** (1-5): Does the prospect have an internal champion with authority and time to engage? Can they provide regular feedback? **Target**: 15-30 prospects in the pipeline to yield 4-6 signed LOIs (expect 20-40% conversion rate from outreach to signed LOI). **Verify**: Minimum 15 prospects loaded with complete contact information and ICP scores. **If failed**: If fewer than 15 prospects, expand ICP criteria slightly or add adjacent verticals. Do not proceed with fewer than 10 prospects. ### Step 3: Outreach and Discovery Meetings **Duration**: 1-2 weeks **Tool**: Email + Calendly/Cal.com + Video conferencing Execute outreach in three touches: **Touch 1 — Initial outreach email:** - Lead with the prospect's specific pain point (from ICP research) - Describe your solution in 2-3 sentences - Ask for a 20-minute discovery call - Do NOT mention LOI or commitment in the first touch **Touch 2 — Discovery call (20-30 min):** - Confirm the pain point exists and is prioritized - Share product concept (mockups, prototype, or pitch deck) - Gauge budget authority and purchasing timeline - Ask: "If this solved [specific problem], what would that be worth to your organization annually?" **Touch 3 — Follow-up with LOI (if qualified):** - Send customized LOI pre-filled with discussed terms - Include specific requirements the prospect mentioned - Set a 7-day deadline for signature: "We are finalizing our early customer roster by [DATE]" **Conversion signals to watch**: [src4] - Prospect asks detailed technical questions (buying signal) - Prospect introduces you to colleagues (champion building) - Prospect shares internal processes/data (trust signal) - Prospect pushes back on specific terms (negotiation = interest) **Verify**: Minimum 8-10 discovery calls completed, at least 5 prospects qualified and sent LOIs. **If failed**: If fewer than 5 qualified prospects after 10+ calls, the ICP definition may be wrong. Return to customer interviews before continuing. ### Step 4: Negotiate and Collect Signatures **Duration**: 1-2 weeks **Tool**: DocuSign/HelloSign + Email For each qualified prospect: 1. **Customize LOI** with specific terms discussed (ACV, requirements, timeline) 2. **Send via e-signature tool** with clear instructions and 7-day expiry 3. **Handle common objections**: - "I need legal to review" → Emphasize non-binding nature, keep to 1 page, offer to connect with their legal directly - "We cannot commit to a price yet" → Replace specific ACV with a range, or state "pricing to be mutually agreed upon commercial availability" - "I am not the right person" → Ask for introduction to the budget holder or decision maker - "We need to see the product first" → Offer design partner agreement instead of LOI (includes feedback cadence and early access) 4. **For design partners specifically** (PATH A): - Schedule the first bi-weekly feedback call before signing - Agree on 3-5 specific features they will help validate - Define the success metric for the partnership - Set a 3-6 month partnership term with conversion checkpoint [src3] **Verify**: 4-6 signed LOIs or design partner agreements collected, each with named buyer and intended commitment value. **If failed**: If fewer than 4 after exhausting pipeline, add 10 more prospects to Step 2 and repeat Steps 3-4. If conversion rate is below 15%, revisit product positioning. ### Step 5: Assemble Validation Portfolio **Duration**: 2-4 hours **Tool**: Google Docs/Sheets Compile all signed documents into an investor-ready validation package: ```text PRE-SALE VALIDATION SUMMARY Total LOIs / Commitments Collected: [N] Total Intended Annual Value: $[SUM] Average Contract Value: $[AVG] Signed LOIs: 1. [Company A] — $[ACV]/year — [Use case] — Signed [DATE] 2. [Company B] — $[ACV]/year — [Use case] — Signed [DATE] 3. [Company C] — $[ACV]/year — [Use case] — Signed [DATE] Design Partners: 1. [Company D] — Bi-weekly feedback, reference rights — Signed [DATE] Pre-Orders (if applicable): - [N] pre-orders totaling $[AMOUNT] via [platform] Key Insights from Discovery: - Top 3 requested features: [1], [2], [3] - Primary pain point confirmed: [description] - Average willingness to pay: $[range] - Procurement timeline: [typical cycle length] Conversion Plan: - LOI → paid contract conversion target: [70-80%] within [90 days] of launch - Design partner → customer conversion target: [80-90%] ``` **Verify**: Summary document complete, all signed PDFs organized in a folder, totals calculated correctly. **If failed**: If any LOI is missing signature or key terms, follow up with prospect within 48 hours. ### Step 6: Integrate into Fundraising and Product Planning **Duration**: 1-2 hours **Tool**: Pitch deck software + product roadmap tool Load validation data into downstream workflows: 1. **Investor deck**: Add "Customer Validation" slide with LOI count, total intent value, and 2-3 named logos (with permission) 2. **Product roadmap**: Prioritize features mentioned as requirements across multiple LOIs 3. **CRM pipeline**: Convert LOI contacts to "Committed — Pre-Launch" stage with expected close date 4. **Design partner cadence**: Schedule recurring bi-weekly calls in calendar **Verify**: Pitch deck updated, roadmap reflects LOI requirements, CRM pipeline shows all committed prospects. ## Output Schema ```json { "output_type": "pre_sale_validation_portfolio", "format": "folder (PDFs + spreadsheet + summary doc)", "columns": [ {"name": "company_name", "type": "string", "description": "Prospect company that signed", "required": true}, {"name": "contact_name", "type": "string", "description": "Named signer and champion", "required": true}, {"name": "contact_title", "type": "string", "description": "Signer's job title", "required": true}, {"name": "commitment_type", "type": "string", "description": "LOI, design_partner, or pre_order", "required": true}, {"name": "intended_acv", "type": "number", "description": "Intended annual contract value in USD", "required": false}, {"name": "requirements", "type": "string", "description": "Specific product requirements listed in LOI", "required": false}, {"name": "date_signed", "type": "date", "description": "Date LOI was signed", "required": true}, {"name": "conversion_target_date", "type": "date", "description": "Expected date to convert to paid contract", "required": false}, {"name": "reference_permission", "type": "boolean", "description": "Whether prospect allows name/logo use", "required": true} ], "expected_row_count": "4-10", "sort_order": "intended_acv descending", "deduplication_key": "company_name" } ``` ## Quality Benchmarks | Quality Metric | Minimum Acceptable | Good | Excellent | |---------------|-------------------|------|-----------| | Signed LOIs / design partner agreements | 3 | 5-6 | 8+ | | Total intended annual value | > $25K | > $75K | > $200K | | Named, referenceable buyers | 2 | 4 | 6+ | | Average ICP match score | > 3/5 | > 4/5 | 4.5+/5 | | Conversion rate (outreach to signed) | > 15% | > 25% | > 40% | | Discovery-to-LOI cycle time | < 4 weeks | < 2 weeks | < 1 week | **If below minimum**: Re-examine ICP definition and product positioning. If conversion rate is below 15%, the problem may not be painful enough or the solution is not clearly articulated. Return to customer interviews. ## Error Handling | Error | Likely Cause | Recovery Action | |-------|-------------|----------------| | Zero responses to outreach | Wrong channel, weak subject line, or wrong buyer persona | Test 3 different subject lines; try LinkedIn InMail as alternative channel; verify contact titles match decision-maker role | | Prospects engage but refuse to sign anything | LOI perceived as too formal or committing | Switch to lighter format: email confirmation of intent instead of formal LOI; or offer design partner agreement which frames it as collaboration rather than purchase commitment | | Legal department blocks LOI | Document too long or contains binding language beyond confidentiality | Simplify to 1 page, remove all binding clauses except confidentiality, add explicit non-binding header and footer [src5] | | Prospects want features you have not planned | Product-market misfit with this segment | Document requested features; if 3+ prospects request the same unplanned feature, re-evaluate roadmap; if requests diverge wildly, ICP is too broad | | Design partner stops responding after signing | Champion left company or lost internal priority | Contact champion directly within 48 hours; if no response in 1 week, ask for new internal contact; replace with next prospect from pipeline | | Pre-order refund requests spike | Delivery timeline too aggressive or product description overpromised | Issue refunds promptly (legal requirement), adjust timeline on landing page, email remaining pre-order customers with honest update | ## Cost Breakdown | Component | Free Tier | Paid Tier | At Scale | |-----------|-----------|-----------|----------| | LOI / agreement templates | $0 (Common Paper, Google Docs) | $0 | $0 | | E-signature collection | $0 (HelloSign 3/mo) | $15/mo (DocuSign) | $25/mo (DocuSign Business) | | CRM / pipeline tracking | $0 (HubSpot Free, Sheets) | $0 (HubSpot Free) | $45/mo (HubSpot Starter) | | Meeting scheduling | $0 (Cal.com, Calendly Free) | $8/mo (Calendly Pro) | $12/mo | | Email outreach | $0 (Gmail) | $25/mo (Mailshake) | $75/mo | | Landing page (PATH C only) | $0 (Carrd) | $19/mo (Carrd Pro) | $29/mo (Webflow) | | **Total for 4-6 LOIs** | **$0** | **$15-50/mo** | **$75-150/mo** | ## Anti-Patterns ### Wrong: Treating LOIs as confirmed revenue Founders present LOI total value as "pipeline" or "committed ARR" in investor meetings. Investors who discover the non-binding nature feel misled, damaging credibility permanently. LOIs are demand signals, not contracts. [src1] ### Correct: Present LOIs as validated demand State: "We have [N] non-binding letters of intent totaling $[X] in intended annual value from named buyers including [Company A] and [Company B]." Investors understand the difference and respect honest framing. ### Wrong: Skipping LOIs and building based on verbal interest Prospects say "we would totally buy that" in interviews. Founders interpret verbal enthusiasm as validation and begin building. At launch, those same prospects ghost, have budget freezes, or changed priorities. Verbal interest has near-zero predictive value. [src4] ### Correct: Require a written commitment before building The act of signing — even a non-binding document — creates psychological commitment and separates genuine intent from politeness. If a prospect will not sign a 1-page non-binding LOI, they will not sign a contract. [src4] ### Wrong: Over-engineering the LOI document Founders create 5-10 page LOIs with detailed SLAs, implementation timelines, and legal terms. Prospect's legal team gets involved, review cycles extend to months, and the LOI process becomes as heavy as a real contract negotiation. [src8] ### Correct: Keep it to 1 page, maximum 2 The only binding clause should be confidentiality. Everything else is non-binding intent. Simplicity drives speed. A prospect should be able to read, understand, and sign in under 10 minutes. ## When This Matters Use this recipe when the agent needs to produce actual signed pre-sale commitments — not a document about how to validate ideas. This is the bridge between customer interviews ("people say they want this") and first revenue ("people paid for this"). Requires an ICP definition and product concept as inputs. Output feeds directly into fundraising materials and first-customer conversion playbooks. ## Related Units - [Customer Interview Execution](/business/customer-validation/customer-interview-execution/2026) - [First 10 Customers Playbook](/business/startup-sales/first-10-customers-playbook/2026) - [Landing Page MVP Validation](/business/landing-pages/landing-page-mvp-validation/2026) - [Fundraising Deck Assembly](/business/startup-finance/fundraising-deck-assembly/2026) - [ICP Definition Framework](/business/customer-research/icp-definition-framework/2026)