Converting to paid — the end-of-term moment.

The end-of-term conversion conversation architecture

The conversation is a scheduled meeting between the founder and the named decision-maker, calendared 30–45 days before formal end-of-term. The lead time exists because the partner's procurement typically requires 2–6 weeks to convert a verbal yes into a signed contract, and because the founder needs the window to either close the deal or initiate the wind-down without running past the term boundary unresolved.

The meeting is framed explicitly as the conversion-or-termination conversation, named as such in the calendar invite and in the written summary the founder sends the day before. The framing is not a sales tactic; it is the operational mechanic the original agreement codified. The partner has known since signing that this conversation occurs on this date with these two possible outcomes.

The most common failure here is ambiguity. The founder schedules a "let's catch up" meeting, the conversation drifts, the partner expresses general satisfaction, and the meeting ends without a decision. The deal slips past the term boundary into a no-mans-land where the partner continues at the design-partner price and the conversation reschedules indefinitely.

Per-stage mechanics

The conversation has four stages, executed in order, with a typical duration of 45–60 minutes. The founder runs it as a structured agenda, not an open-ended discussion.

(a) Success-criteria review

The conversation opens with a joint review of the 2–3 success criteria written into the agreement at signing. The founder pulls up the original document, reads the criteria verbatim, and walks through the evidence on each: did we hit it, what does the data say, what does the partner's lived experience say. The function is to anchor the rest of the conversation in the partner's own pre-committed definition of value — a factual review of whether the engagement delivered what both sides agreed it would, not a negotiation about whether the product is worth the price. The review answers each criterion with a yes, a no, or a partial. The founder does not argue partials into yeses.

(b) Value articulation

The partner names the value they have received, in their own words, anchored in the evidence reviewed in stage (a). The founder asks — "in your own words, what has the product produced for your team over the last six months" — and listens, and writes down what the partner says. The founder does not articulate the value back. The partner who has named value in their own words has made a public commitment to that value; the partner who has been told the value has heard a sales pitch. The first produces a price-anchor at the value the partner believes they received; the second at the value the founder tried to convince them to believe. The gap between these anchors, multiplied across the conversation, is the structural reason the 30-to-60 conversion range is as wide as it is.

(c) Pricing conversation

The pricing conversation names the post-term price specified in the original agreement, the per-tier discount from public list price, and the multi-year option. The founder does not negotiate against the design-partner discount — the price floor is the post-term price named in the agreement, not the in-term price the partner has been paying. Anchoring back to the design-partner discount is the single most common operator failure at this stage and the dominant suppressor of conversion ARR. The first-year conversion price lands at 40–70% of list — meaningfully above the design-partner discount, meaningfully below the price the founder will charge a cold prospect twelve months from now. The discount narrows over years two and three. The multi-year option offers a steeper discount for a longer commitment: a three-year contract at 50% of list, a two-year at 60%, a one-year at 70%. The founder presents the offer in writing during the conversation — a one-page summary the partner can take to procurement — with the three options visible and the recommended option named.

(d) Next-step framing

The final stage names the next steps explicitly: the conversion contract goes out by a specific date, signature is targeted by a specific date, implementation begins on a specific date, the renewal cadence is named, and case-study production begins within 60 days of signature. The conversation ends with a written summary sent the same day — a five-paragraph email recapping the criteria review, the value the partner articulated, the offered pricing, the recommended option, and the dates. The summary is the artifact the partner forwards to procurement.

The pricing-discount pattern at conversion

The pattern is a three-year discount glide from 40–70% of list in year one to 90–100% by year three. The structure rewards early commitment, reflects accumulated switching cost, and produces the per-account ARR expansion early-stage unit economics require. The year-one band depends on the strength of the criteria review. A partner who hit all criteria and articulated substantial value converts at 60–70% of list. A partner who hit criteria partially and requires procurement justification converts at 40–50%. A common founder error is to set the year-one price at the design-partner discount — 80–100% off list. This produces a high conversion rate but a per-account ARR that does not support the company. The design-partner discount is the price of pre-PMF access in exchange for time and feedback; the conversion price is the price of a working product in exchange for money. They are different prices for different things.

The multi-year commitment pattern

The multi-year option exists for partners whose procurement supports it. Typical structure: a two- or three-year contract at a 10–20-point steeper year-one discount, in exchange for commitment through the full term with a defined annual escalator. The empirical effect is twofold. It modestly raises the upper bound of the conversion range — partners who would have converted at one year convert at two years roughly 60–70% of the time when offered. And it produces a per-conversion ARR uplift of 1.6–2.4x relative to a single-year conversion. The offer is not right for every partner: one whose procurement requires annual budget approval cannot sign a three-year contract, and one whose business is itself early-stage should not be locked into a relationship one or both will need to exit.

Partial conversion

A subset of partners convert at a lower tier than the engagement scope supported. The pattern: the engagement covered modules A, B, and C; the conversion contract covers only module A with a defined upgrade path. Partial conversion is a meaningful outcome, not a failed conversion. The contract names the upgrade triggers and pricing in the same document — when the partner adds module B, the price is X; when they add module C, the price is Y. Naming these terms at conversion rather than at the upgrade moment converts the upgrade into a contracted event rather than a new negotiation.

Renewal-vs-upgrade at the conversion moment

The conversion moment is also where the structure for the years that follow is named. Three patterns are common: annual renewal at list, annual renewal at a named escalator (5–10% per year through a defined ceiling), or a multi-year contract with a defined upgrade path tied to seat expansion. The decision interacts with the partner's expected growth trajectory. A partner who expects to expand seats by 30–50% per year is best served by a seat-based structure. A partner whose usage is flat is best served by annual renewal at a defined escalator. Mis-structuring this is a long-tail error — the flat-usage partner offered a seat-based structure feels nickel-and-dimed; the high-growth partner offered a flat annual fee compounds value the founder is not capturing.

Non-conversion handling

A meaningful fraction of engagements end without conversion — empirically, 40–70% of the program by partner count, the inverse of the conversion rate. Non-conversion is not a failure; it is a structural feature of pre-PMF customer development. The discipline is to handle it in a way that preserves relationship value, reference rights, and lessons-learned input rather than producing a hostile exit.

The non-conversion conversation runs the same four stages. The partner declines. The founder responds explicitly: "understood, we'll wind down on the agreed timeline." The wind-down clause from the original agreement is invoked — typically a 30–60 day product-access extension, a data export, and a documented handoff of partner-authored configuration. Two artifacts are captured: a lessons-learned summary that folds into product development, and a clarification of residual rights. The non-converting partner is generally not eligible for case-study production but may still serve as a soft reference or allow logo use on a "design partners" tier. The founder asks explicitly and gets these in writing. The relationship-maintenance posture is light but durable: a semi-annual check-in, product updates, an explicit "if your situation changes, here's the conversion offer that remains open for six months." Roughly 5–15% of non-converting partners re-engage and convert within 18 months when the relationship is maintained well; the same fraction is approximately zero when the engagement ends with the partner feeling pushed out.

Per-partner timing variability

The default is 30–45 days before end-of-term. A subset of engagements produce signal well before that boundary — the partner expresses unsolicited interest at month four of a nine-month term, criteria are observably met at month three, the founder proposes converting early. Accelerated conversion is appropriate when three conditions hold simultaneously: criteria have been substantively met, the partner has named the value unprompted, and procurement has a fast lane or the founder has confirmed it. Absent any of these, an early conversation produces a soft decline that costs the founder the natural end-of-term forcing function. The pattern in well-run programs: 10–20% of conversions happen 60+ days before end-of-term, 60–80% happen in the 30–45 day window, and the remainder either convert in the wind-down or do not convert.

Procurement navigation

A subset of conversions — particularly at ACVs above $50K — require procurement approval the named decision-maker does not have unilateral authority to grant. The founder, not the partner, drives the timeline once the verbal yes is obtained: security questionnaire response, SOC 2 letter, MSA template, vendor onboarding form. A partner who has agreed in principle but navigates procurement alone takes 6–12 weeks to produce a signed contract, frequently slips, and occasionally fails to convert because internal friction outlasts commitment energy. The founder who takes the work onto their own desk closes the same partner in 2–4 weeks and produces signature within the end-of-term window.

Contract, not handshake

The conversion is documented in a real contract, not a verbal renewal. The design partner agreement was a 4–6 page operational instrument (Chapter 3); the conversion contract is a standard enterprise SaaS agreement, typically 10–20 pages, naming price, term, renewal mechanic, SLA, and security and data terms. The founder who closes verbally and lets the contract "follow when there's time" produces a 30–50% probability of the deal failing to paper before end-of-term. Commitment energy decays; procurement surfaces friction an unsigned verbal commitment cannot survive. The signed contract within the window is the artifact that converts the verbal yes into a recognized booking.

Case-study handoff

The conversation ends with the case-study production calendar named: interview within 30 days of signature, draft within 45 days, published case study within 60 days. The rights were granted at signing of the original design partner agreement (Chapter 3); the production calendar is set at the conversion moment. The mechanics of case-study production, asset capture, and the published-case-study conversion impact on downstream sales are the substance of Chapter 6.

Common operator failures observed in production

• No scheduled conversion conversation. End-of-term arrives without a calendared meeting; the engagement drifts past the term boundary; the conversation reschedules indefinitely or never occurs.
• Ambiguous framing. The conversation is framed as "let's catch up" rather than as the conversion-or-termination conversation. The meeting ends without a decision; the forcing function is structurally absent.
• No success-criteria review. The conversation skips the joint review and proceeds directly to pricing. The partner has no anchor for the value they are being asked to pay for; the conversation is a sales negotiation against a customer with no defined definition of value.
• Anchoring to the design-partner discount. The founder offers a price that is a small step up from the in-term price rather than a price anchored to list with a defined first-year discount. The partner converts but at an ARR that does not support the company.
• Founder articulates value instead of partner. The pricing conversation that follows is a price negotiation rather than a structured close.
• Verbal yes without contract. The conversion is closed verbally and the contract is "to follow." Commitment energy decays before the contract papers; the deal frequently slips to non-conversion despite the verbal yes.
• Partner-driven procurement. The founder hands the procurement work to the partner and waits. Internal friction outlasts the partner's commitment energy; conversion fails on operational friction rather than on price or value.

Pre-conversion checklist

• Conversation scheduled with the named decision-maker 30–45 days before formal end-of-term, framed explicitly as conversion-or-termination
• Original agreement reviewed and success criteria pulled into a one-page summary for joint review
• Evidence per criterion compiled — usage data, partner-articulated observations, product-side measurements
• Post-term price, multi-year options, and per-tier discount band pre-calculated, with the recommended option identified per partner
• One-page pricing summary drafted for in-meeting presentation and procurement handoff
• Procurement constraints pre-identified — SOC 2, MSA, security review, vendor onboarding — with founder-side artifacts ready
• Wind-down clause reviewed in case the conversation routes to non-conversion
• Case-study production calendar drafted for the post-conversion handoff
• Lessons-learned capture template prepared for the non-conversion path
• Five-paragraph follow-up summary template drafted for same-day send

Where this fits

Recruitment (Chapter 2) produces the partners; the agreement (Chapter 3) produces the pre-named conversion mechanic; the program (Chapter 4) produces the success-criteria evidence; this chapter produces the binary outcome. The reference-customer handoff (Chapter 6) takes the converted partners and produces the case studies, references, and reusable assets that anchor the next twelve months of GTM.

The variance within the 30–60% range is almost entirely operational: programs that schedule the conversation explicitly, anchor it in pre-written success criteria, ask the partner to articulate value in their own words, present a pricing offer anchored to list rather than to the design-partner discount, and drive procurement directly convert at the top of the range. Programs that miss any of these levers convert at the bottom. The mechanic is not a sales art form — it is an operational system, and the discipline of running it at every conversion conversation is the binding constraint on the program's ARR outcome.