A step by step guide to writing Permissionless Value Proposition emails. This covers message structure, tone, common mistakes, and the thinking process behind each decision.
Do not write a single word until you have:
- A documented wedge (use the wedge identification template)
- At least 3 independent data sources cross-referenced
- A clear insight that the prospect cannot easily find on their own
- A business implication you can state in one sentence
If you cannot complete that checklist, you are not ready to write. Go back to the research phase. A well-researched PVP writes itself. A poorly-researched one cannot be saved by good writing.
Every PVP follows the same three-layer structure:
What you found, specific to their situation. Not industry averages. Not general trends. Their data, their facilities, their filings.
"I pulled the building permits filed in [County] this month. 14 of them require licensed electrical contractors."
What the data means when you connect it to other sources. This is where cross-referencing creates value. The prospect could find Layer 1 on their own. Layer 2 is your contribution.
"Here are the top 5 by estimated electrical scope, with general contractor contact info."
Why this matters for their business. Quantify when possible. Connect to outcomes they care about: revenue, risk, competitive position, compliance.
"That is roughly $340K in electrical work within 30 miles of your shop."
2 to 5 words. No brand name. No fluff. The subject line has one job: earn the open. Nothing else.
| Good | Bad |
|---|---|
| "Your Liebherr idle?" | "Exciting opportunity for [Company]" |
| "14 permits, $340K" | "Quick question about your business" |
| "CrushFTP patch?" | "How [Company] can improve security" |
| "It's been 364 days" | "Following up on our previous email" |
The subject line should feel like a text from someone who knows something you need to hear. Short. Specific. A label for the situation, not a pitch for the solution.
Lead with data. Not with yourself, not with flattery, not with a question about their weekend.
| Good | Bad |
|---|---|
| "I pulled every building permit filed in [County] this month." | "My name is [Name] and I work at [Company]." |
| "Your facility at [Address] had 3 OSHA citations in Q4." | "I noticed you might be interested in..." |
| "Your HMDA denial rate in [ZIP] is 2.3x the county average." | "Hope you are doing well!" |
The opening line establishes credibility. It says: I did real work, and the work is about you.
Deliver the insight. Keep it short. Three to five lines maximum for the core body. You are earning a reply, not making a sale.
Structure:
- State what you found (1 to 2 lines)
- State what it means (1 to 2 lines)
- Quantify the implication if possible (1 line)
Do not include everything you found. Include the most compelling 20 percent. The rest is your follow up material.
The closing is not a call to action. It is an offer to continue the research.
| Good | Bad |
|---|---|
| "Want the full list with GC contact info?" | "Can we schedule 15 minutes to discuss?" |
| "We could dig deeper on [specific angle] if useful." | "Would love to connect and learn more about your needs." |
| "Am I close, or is it different on your side?" | "Let me know if you would like to see a demo." |
The closing should make replying feel easy and natural. You are not asking for their time. You are offering more of yours.
You are a researcher sharing findings. Not a salesperson pitching a solution. Every sentence should pass this test: would a peer in their industry say this?
| Vendor tone | Peer tone |
|---|---|
| "We help companies like yours..." | (Delete this. Do not talk about yourself.) |
| "Our solution enables..." | (Delete this. The PVP is about them.) |
| "I'd love to learn more about your challenges" | "Your [data point] suggests [implication]. Am I reading that right?" |
| "Are you the right person to discuss..." | (You already know. You researched them.) |
Do not assert things about a stranger's business. Suggest them. Hedged confidence is more believable than certainty from someone they have never met.
| Assertive (risky) | Uncertain (better) |
|---|---|
| "You are struggling with X" | "I would imagine X is a challenge" |
| "Your team cannot do Y" | "I suspect Y might be a gap" |
| "You need to fix Z" | "Am I close, or is Z tighter than I think?" |
Why this works: assertive language from a stranger triggers defensiveness. Uncertainty language invites correction. And correction is engagement. People will not reply to tell you that you are right. They will reply to tell you that you are wrong.
The PVP is not about exposing problems. It is about sharing useful intelligence. The difference is tone.
"Gotcha" tone: "We found that your facility has 3 OSHA violations and you haven't corrected them."
Helpful tone: "Your facility at [Address] had 3 citations related to lockout/tagout procedures in Q4. We see this pattern a lot in facilities running [type of equipment]. Here is what the abatement timeline typically looks like."
Same data. Different framing. The second version makes the prospect feel informed. The first makes them feel surveilled.
Use PQS when you are still validating whether an angle resonates. Lightweight. No data stitching required. 3 lines maximum.
Subject: 2 to 5 words
You are probably dealing with [situation] right now.
Most teams get stuck because [constraint or tradeoff].
Am I close, or is it different on your side?
PQS is a test. You send it to 600 people per angle variant. You read the replies qualitatively. If the angle gets engagement and alignment, you graduate to PVP.
Use PVP when you have a validated angle and have done the research. Data-rich. Multi-source. The email transfers value.
Subject: Specific, data-driven, 2 to 5 words
[Specific data about their situation from Source A]
[Insight from combining Source A + Source B + Source C]
[Business implication, quantified if possible]
[Offer to continue the research]
PVP is not a test. It is a delivery. You send it to prospects where you have done real research and have real data.
PQS and PVP are not interchangeable. They are sequential.
PQS tests (cheap, fast)
|
v
Find winning angle
|
v
Build data infrastructure for that angle
|
v
PVP amplifies the winner (expensive, high value)
Most teams either skip to PVP (expensive and slow) or never graduate from PQS (leaving value on the table). Use both.
If you say "your injury rate is 2x the industry average," you need to know the industry average and their injury rate. If the prospect fact-checks you and you are wrong, your credibility is gone permanently.
Fix: Only include data points you can cite a source for. If a prospect asks "where did you get that?", you should have a clear answer.
"The industry is changing" is not a PVP. "Your HMDA denial rate in ZIP 33602 is 2.3x the Hillsborough County average, and 4 of your 6 branch locations are in majority-minority census tracts" is a PVP.
Fix: If you can swap in any company name and the message still works, it is too vague. PVPs are non-transferable.
The moment you say "our product can help with this," you have converted a PVP into a cold pitch. The prospect's mental model shifts from "this person is sharing useful research" to "this person is selling something."
Fix: Do not mention your product, your company's capabilities, or your solution. If the research is good enough, they will ask.
You did 6 hours of research. You found 12 interesting data points. The temptation is to include all of them. Do not. The email should take 30 seconds to read.
Fix: Include the 2 to 3 most compelling findings. Save the rest for follow up emails. Each follow up should add new value, and your research gives you that inventory.
There is a line between "helpful" and "creepy." The line is usually about framing. Leading with "We have been monitoring your company" is creepy. Leading with "I pulled the public filing data for your county" is not.
Fix: Always reference the public source. "OSHA records show..." is credible. "We noticed..." is vague and slightly unsettling.
If you use a technical term incorrectly, the prospect notices immediately. Nothing kills credibility faster than misusing the language of their profession.
Fix: Only use terms you can define. If you are entering a new vertical, spend time reading how practitioners talk to each other, not how vendors talk to them.
A PVP with one data point is not a PVP. It is a cold email with a fact in it. The bar is 3+ independent data sources cross-referenced into an insight.
Fix: Use the research checklist before every send. If you cannot check every box, you are not ready.
Before sending any PVP, ask yourself these questions:
- Would the prospect pay to receive this information? If not, it is not valuable enough.
- Can I back up every claim with a cited source? If not, remove the claim.
- Is this specific to them, or could I send it to any company? If it is transferable, it is too generic.
- Does every sentence serve the prospect, or does any sentence serve me? Remove anything that serves you.
- Would I forward this to a colleague if I received it? The best PVPs get forwarded internally.
- F.I.N.D. Framework: The full research methodology
- Data Sources: Where to find the data
- Email Templates: Three ready-to-use templates
- Research Checklist: Pre-send verification