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 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.
• 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

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. For PATH A/B, use a 1-page LOI covering: intent statement, anticipated terms (ACV, start date, term, users), requirements for purchase, non-binding clause, and binding confidentiality clause. For PATH A design partners, add feedback cadence, reference rights, pricing discount, IP ownership, and termination terms using Common Paper's template as a base. [src6]

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 columns: Company, Contact, Title, Email, ICP Score, Pain Level, Status, LOI Type, Next Action, Follow-Up Date. Score prospects using a16z's three-criteria framework: Representativeness (mirrors broader market), Urgency (already tried alternatives), and Capacity (has champion with authority and time). Target 15–30 prospects to yield 4–6 signed LOIs at 20–40% conversion rate. [src3]

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.

Step 3: Outreach and Discovery Meetings

Duration: 1–2 weeks · Tool: Email + Calendly/Cal.com + Video conferencing

Execute outreach in three touches: (1) Initial email leading with prospect's specific pain point — do NOT mention LOI in first touch. (2) Discovery call (20–30 min) to confirm pain, share product concept, gauge budget authority, and ask willingness-to-pay questions. (3) Follow-up with customized LOI pre-filled with discussed terms and a 7-day signature deadline. Watch for conversion signals: detailed technical questions, introductions to colleagues, sharing internal data, and pushback on specific terms. [src4]

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.

Step 4: Negotiate and Collect Signatures

Duration: 1–2 weeks · Tool: DocuSign/HelloSign + Email

For each qualified prospect: customize LOI with specific terms, send via e-signature tool with 7-day expiry, and handle objections. Common objections: “I need legal to review” → emphasize non-binding nature, keep to 1 page; “We cannot commit to a price” → use a range instead of specific ACV; “I am not the right person” → ask for introduction to decision maker; “We need to see the product” → offer design partner agreement instead. For design partners, schedule first bi-weekly call before signing and define 3–5 features to validate. [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 and repeat Steps 3–4.

Step 5: Assemble Validation Portfolio

Duration: 2–4 hours · Tool: Google Docs/Sheets

Compile all signed documents into an investor-ready validation package: total LOIs collected, total intended annual value, average contract value, individual LOI details (company, ACV, use case, date signed), design partner details, key discovery insights (top requested features, primary pain point, average willingness to pay), and conversion plan with target percentages and timelines.

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: add “Customer Validation” slide to investor deck with LOI count and named logos (with permission), prioritize features mentioned as requirements across multiple LOIs in product roadmap, convert LOI contacts to “Committed — Pre-Launch” stage in CRM, and schedule recurring bi-weekly calls for design partners.

Verify: Pitch deck updated, roadmap reflects LOI requirements, CRM pipeline shows all committed prospects.

Output Schema

{
  "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

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

Cost Breakdown

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. [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.” 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 or have budget freezes. 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.

Wrong: Over-engineering the LOI document

Founders create 5–10 page LOIs with detailed SLAs 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. [src8]

Correct: Keep it to 1 page, maximum 2

The only binding clause should be confidentiality. Everything else is non-binding intent. 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.