Lead magnets — the bespoke handoff that books the second meeting.

The premise

A templated “great to meet you” email — the kind every operator who has attended a conference has both sent and received — converts to a booked second meeting at 0 to 3%. A bespoke writeup that synthesizes the specific conversation, names the operational problem the contact described, and proposes a specific next step converts at 25 to 40%. The differential is not marginal. It is an order of magnitude, and it is the dominant variable in the conversion math of the entire conference channel.

Every other discipline in the motion — pre-event outreach producing 40 quality meetings, a dinner that captured eight senior buyers, a five-minute qualifying framework that surfaced explicit pain — terminates at this one decision: bespoke or templated. A conference with strong pre-event outreach, strong in-room conversations, complete notes, tight follow-up cadence, and generic assets produces a fraction of the pipeline the same conference produces with bespoke assets. The asset is where the investment realizes its return, or fails to.

The empirical asset-type conversion ranking

Across the motions observed at this firm, asset types sort cleanly by 30-day meeting-conversion rate. The ranking is stable across industry, stage, and ICP; absolute rates vary by 10 to 15 points by ICP, but the ordinal ranking does not move:

The top three cost between 30 minutes and 6 hours per contact and produce the outcomes that justify the conference investment. The bottom three cost effectively nothing and produce conversion rates indistinguishable from no follow-up. The operational question in the week after a conference is not whether bespoke assets convert. It is how many the team can produce inside the seven-day window.

The conversation writeup

The conversation writeup is the highest-converting asset and the one every disciplined operator produces first. The structure is consistent across ICPs:

• Two to three paragraphs of conversation synthesis. Not a transcript. A synthesis — the operational problem the contact described, the constraints they named, the questions they were testing. Written so it is obvious the operator was present in the conversation.
• One paragraph proposing the next step.Specific, dated, scoped. “A 30-minute call next week to walk through how we’ve seen teams in your stage handle the inbound-routing problem you described” converts. “Would love to find time to continue the conversation” does not.
• One paragraph of researched context.Public information about the contact’s company or market that the operator did not know during the conversation and went to find afterward. The strongest single signal the asset is bespoke. Also the paragraph most teams skip.

Production cost is 45 to 90 minutes per contact. Structured notes (chapter 6) and the 24-hour preview (chapter 7) compress toward the lower bound; working from memory takes the upper bound. At 45 minutes per writeup and 6 productive hours per day, a single operator produces 8 writeups per day, or 40 across the 5-day window. That number is the binding ceiling on the entire post-event motion.

The targeted intro list

The targeted intro list is produced for contacts who explicitly named — or who the operator inferred needed — introductions to specific people. The structure is a curated 3 to 5 person list, each with two to three sentences of context: who they are, why they are relevant to the named problem, and the operator’s relationship strength. The asset is delivered with the explicit offer to make whichever intros the contact wants, in the same email that contains the meeting-booking ask.

Production cost is 30 to 60 minutes per contact. The 30-day conversion to a booked meeting runs 25 to 35%; conversion to an accepted intro runs higher (50 to 70%), but intros are an intermediate outcome, not pipeline. The asset works because it demonstrates two things at once: that the operator listened, and that the operator’s network is materially useful. Neither is establishable in a templated email.

The custom data analysis

For contacts who shared a specific operational question the operator’s data or tooling can answer, the custom data analysis is the highest-investment asset type. The structure is a brief written analysis — typically one to two pages — addressing the question with referenced data and a conclusion that flags what could not be answered from public data and would require an actual engagement. Production cost is 2 to 6 hours, depending on whether the analysis requires net-new data work or draws on existing internal analyses. The 30-day conversion runs 25 to 35%. The asset produces a second-order benefit the writeup does not: it is reusable for adjacent contacts in the same ICP, amortizing the cost across multiple follow-ups, often with 30 to 45 additional minutes per derivative. Over-invested for B-tier and C-tier; reserving it for the top 5 to 10 A-tier contacts is the correct allocation.

The curated industry brief

The curated industry brief is a 1 to 2 page synthesis of a recent industry development — a regulatory shift, a market data release, a competitive announcement — written with the contact’s stated focus area in mind. The asset is not the underlying news; it is the operator’s synthesis of what the development means for an operator in the contact’s seat. Production cost is 1 to 3 hours per brief, with significant amortization — a single brief is typically distributable to 4 to 8 contacts in the same vertical with 10 to 15 minutes of personalization each. The 30-day conversion is 12 to 20%, materially lower than the writeup but materially higher than any templated asset. The right asset for B-tier contacts in a defined vertical and for A-tier contacts who did not surface a specific question that would warrant a custom analysis.

The templated case study

The templated case study — an existing, polished writeup of work the operator’s firm has done with a comparable customer — is the lowest-cost asset that still produces a measurable uplift over no asset. The 30-day conversion is 5 to 10%, an order of magnitude below the bespoke writeup but materially above the 0 to 3% of the templated email. The operational case is straightforward: it is the asset that scales to C-tier contacts who do not warrant bespoke work but are not so unqualified that a follow-up is inappropriate. The asset has to actually be relevant — a case study from a different industry, stage, or use case converts no better than no asset at all, and signals to the contact that the operator did not retain the conversation context.

The operational ceiling

A disciplined operator returns from a 3-day conference with 35 to 60 meaningful conversations to follow up on. The 24-hour window (chapter 7) consumes the first day. The 7-day asset window consumes the next 5 working days. A single operator can produce, at sustained pace, 8 writeups per day — 40 across the 5-day window. A contact list above 40, which is the modal outcome for a disciplined operator at a meaningful event, exceeds the single-operator ceiling. There are two operational solutions:

• A team of 2 to 3 people focused on asset production for the week. One to two operators are dedicated to producing first-draft assets and routing them through the operator who had the conversation for final personalization. The dedicated operators do not need to have attended; structured notes (chapter 6) are sufficient. Remaining cost on a drafted writeup is 15 to 25 minutes per asset, letting the conversational operator send 18 to 25 writeups per day.
• A pattern that templates the 40% of each asset that can be templated while preserving the 60% that has to be bespoke. The middle section — what the firm does, the proposed engagement structure, the call-to-action — can be templated. The opening synthesis, the named operational problem, the proposed next step, and the researched-context paragraph cannot. Hybrid production cost is 25 to 40 minutes per contact against 45 to 90 fully bespoke, with a conversion-rate cost of 3 to 5 percentage points against a fully bespoke asset and 20-plus points above a templated one.

The team-based solution is correct for firms running multiple events per year. The hybrid is the right answer for a single founder without a team. Doing neither — attempting 40 fully bespoke assets as a single operator inside 5 days — is the most common failure mode in the post-event week.

The asset-production workflow

The 24-hour follow-up (chapter 7) does not contain the asset. It contains the preview — an explicit commitment to deliver the writeup, intro list, or analysis by end of week. The mechanic earns a 5 to 7 day window without the conversation going cold and commits the operator publicly to the bespoke handoff:

Great to talk yesterday. Two things I want to send over by end of
week: (1) a writeup on the routing-cost problem you described, with
a couple of comparable patterns I've seen, and (2) two specific
people in our network who've solved an adjacent version of it. I'll
have both to you by Friday.

Assets are produced in tiered batches. A-tier between day 2 and day 4, B-tier between day 4 and day 6, C-tier on day 6 or 7. Delivering an A-tier asset on day 7 is operationally correct but signals lower priority than delivering it on day 3; the sequencing is observable to the contact.

The pre-event asset library

The highest-leverage pre-event investment beyond the outreach runway itself (chapter 3) is the asset library built in the weeks before the event. A library of 6 to 12 indexed case studies, 3 to 5 evergreen industry analyses, and curated resource lists per major sub-vertical compresses post-event production by 30 to 50% for B-tier and C-tier contacts. The library is not the bespoke writeup; it is the templated middle paragraph, the relevant case study, the polished resource link attached to a bespoke opening. Produced once in the calm 2-to-4-week pre-event window, it supports asset production across multiple events for the next 6 to 12 months.

The bespoke-template hybrid

The hybrid is the compromise most single-operator motions converge to: a personalized opening, a templated middle describing the firm’s relevant work, and a personalized closing proposing the next step. The middle is 40 to 50% of the asset by length and 5 to 10% by conversion contribution; the opening and closing are 50 to 60% of the length and 90% of the contribution. Production cost is 25 to 40 minutes against 45 to 90 fully bespoke. For a single operator with 40 contacts, the hybrid is the difference between sending all 40 bespoke-feeling assets inside the 7-day window and sending 20 bespoke and 20 templated emails.

The handoff-to-next-meeting mechanic

The meeting-booking ask is embedded in the asset delivery, not in a separate touch. A bespoke writeup that arrives without a specific, dated proposal is a partially executed asset — it demonstrates listening, but does not convert listening into pipeline. The closing paragraph contains a specific ask: a 30-minute call, a topic, a proposed window, a scheduling link. The empirical delta between an asset with an embedded ask and one without runs 10 to 15 percentage points. Operators who deliver the asset and then send a separate “would love to find time” touch 48 hours later convert at the lower rate. The ask belongs in the asset.

The CRM and reply-tracking integration

Every asset delivery is logged in the CRM with asset type, delivery date, embedded ask, and a 5-day reminder for no-reply re-engagement (chapter 7). Reply handling is mechanical: a yes books the meeting; a not-now triggers a 30-day check-in; a no flags the contact for 90-day re-engagement. Asset delivery and meeting-booking handoff happen in the same workflow, same day, same operator. Splitting them across two operators or two days is the most common source of in-flight contacts going cold.

The compounding asset library

Assets produced for one conference build the library for the next. A custom analysis produced for an A-tier contact at conference A becomes the templated middle of three assets at conference B and the case study attached to six assets at conference C. Treating asset production as a per-event cost is the wrong frame; treating it as a multi-event investment in a compounding library is the frame that produces leverage. The third and fourth event should consume materially less production time per contact than the first and second. A team observing flat or rising per-contact cost is producing assets without indexing them.

Common operator failures observed in production

• Sending the same templated “great to meet you” email to every contact.The 0 to 3% conversion baseline. The operator does not observe the counterfactual — the meetings that should have booked, didn’t — and concludes the conference channel underperformed. The channel did not underperform; the asset did not exist.
• Promising an asset and not delivering. The 24-hour touch commits to a Friday delivery; the asset arrives the following Tuesday, or never. Observably more damaging than not committing — the contact registers the missed commitment and downgrades the operator.
• Delivering generic assets to A-tier contacts who deserve bespoke. A senior buyer who shared a specific operational problem in a 30-minute hallway conversation receives a templated case study from an unrelated industry. Read as a signal that the operator did not retain the context, and the contact disengages.
• No meeting-booking ask in the asset delivery.A polished bespoke writeup is delivered with a soft “would love to continue the conversation.” The 10 to 15 point conversion delta is forfeited. Subsequent separate touches convert at a fraction of the original embedded ask.
• Attempting 40 fully bespoke assets as a single operator inside 5 days. The operator delivers 12 by day 3, runs out of capacity, and sends templated emails to the remaining 28. A-tier converts at the bespoke rate; B-tier and C-tier convert at the templated rate; the operator concludes the conference produced 12 leads when it produced 12 leads and 28 missed conversions.
• Producing every asset from scratch every event. The library does not compound. Per-contact production cost stays flat or rises. The team plateaus at the single-event operational ceiling.

Pre-event asset-architecture checklist

• Case study library of 6 to 12 polished writeups, indexed by industry, stage, and use case
• 3 to 5 evergreen industry analyses, reusable as middle sections or templated-asset attachments
• Curated resource lists per major sub-vertical the team expects to encounter at the event
• A documented hybrid-asset template defining the production pattern for B-tier contacts
• An assigned asset-production owner for the post-event week, with structured-note access (chapter 6)
• CRM workflow for logging asset delivery, embedded meeting ask, and no-reply re-engagement triggers
• A tiering rule mapping A-tier to bespoke writeup or custom analysis, B-tier to hybrid or curated brief, C-tier to relevant templated case study
• Operational ceiling math reconciled against the projected contact count from chapter 3

Where this fits

The asset is the binding constraint. A conference with disciplined pre-event outreach (chapter 3), a hosted dinner (chapter 4), strong in-room conversations (chapter 5), complete notes (chapter 6), and tight follow-up cadence (chapter 7) but generic assets produces a fraction of the pipeline the same conference produces with bespoke assets. The differential is 8 to 10x on follow-up conversion and 3 to 7x on resulting pipeline. Every prior chapter exists to set up the conditions under which the asset can be produced — the notes that make the writeup possible, the conversation that produces the question worth analyzing, the dinner that produced the intro request worth fulfilling.

The asset is where the investment realizes its return. The five-figure cost of a single founder at a single mid-size event converts to pipeline at the rate the asset sets. An operator who under-invests on this final step has, silently, wasted every dollar spent on the prior ones. The bespoke handoff is not the polish on a well-executed motion. It is the motion.