The Permissionless Value Prop Framework: Would They Pay $100 for Your Message?

What a permissionless value prop is

I picked this concept up from Jordan Crawford, who runs the BlueprintGTM YouTube channel and has built a lot of his content around it. The name sounds abstract, but the idea is simple once you see one example. A permissionless value prop is a message that delivers value without asking for anything first. No meeting, no form, no "let's hop on a call to discuss." You just hand over an insight that is already useful, and you let the reader decide what to do with it.

I'm Hlib Storchak. I build and run outbound systems for B2B founders and sales teams, and I've booked 2000+ meetings for B2B clients doing it. What follows is my own read on PVP, written as someone who is still sharpening how I use it, not as the person who invented it.

The part that trips people up is confusing this with personalization. Mentioning someone's name, their company, or a line from their LinkedIn bio is not a PVP. That is just a mail merge with better manners. A PVP has to be independently valuable: the reader can act on it immediately, with or without you, and the value sits in the message itself, not in a meeting you are hoping to get out of it.

The $100 test

Here is the one question I think matters more than any other part of the framework, and it is the one I come back to whenever a draft feels weak: would this person pay $100 out of their own pocket for the exact insight you just sent them, no matter what you are selling?

Not "would they find this nice." Not "would they reply out of politeness." Would they actually pay for it. If the honest answer is no, the message is not a PVP yet. It is personalization wearing a PVP costume, and prospects can tell the difference even when they can't name why.

PVP vs the pain qualified segment

Most cold outreach, including a fair amount of what I still run for clients, uses what gets called a pain qualified segment, or PQS. You find a group of companies that share a problem, you write a message that names the problem and agitates it a little, and then you ask for a meeting. The value only shows up once they get on the call with you, and in most cases the call is where you try to sell them your product.

A PVP flips that order. The solution, or at least a real piece of it, ships inside the first message. There is no ask baked into the opener. The meeting, if it happens, happens afterward, because the person wants to know how you found all of this, not because you asked them to show up. Most of what I've written before about structuring a cold email, like the four line framework I use for PQS style messages, still assumes you are asking for the meeting somewhere in the message. PVP removes that ask entirely.

The three rules a PVP has to pass

Three things have to be true for a message to count as a real PVP, and I check drafts against all three before they go out.

Independently valuable. It has to work without the sale. The reader can take the insight and act on it even if they never respond to you.

Tied to pain or promise. It is not random trivia. The insight has to connect to a problem your product solves or a promise it makes, otherwise it is interesting but not strategic, and it will not lead anywhere.

Public data only. Everything going into it has to be sourced from information that is already out there: permits, reviews, pricing pages, hiring posts, tech stack, LinkedIn activity, company news. The skill is not finding secret data. It's combining ordinary, publicly available pieces in a way nobody else bothered to.

Three real PVP examples

These examples come from the video, built to show the logic rather than drawn from one of my own client accounts, so treat the specific figures as illustrations of the method rather than a result I am claiming.

Construction. Combine a company's active permit filings, the average permit approval time per county, competitor permit data, and the contact at the relevant permit office. The resulting message tells a contractor that their project sits in a county with a 12 week approval delay, that a neighboring county is approving permits in one week, and names the contact at that office along with the best time to reach them. The reader can act on that today, with or without hiring anyone.

SaaS. Combine a competitor's public pricing page with G2 reviews that mention pricing complaints, matched against the mutual customer list. The message tells a SaaS founder that a named competitor just dropped their entry tier price, and that a chunk of their own mutual customers have been complaining about cost on G2 in the recent weeks. That is competitive intelligence the founder did not have, delivered for free.

Equipment rental. Combine a public equipment listing, local permit data showing which projects need that equipment, and local rental pricing. The message shows an owner who listed an excavator for sale that they could earn meaningfully more per year renting it out to nearby projects that already need one, with the project contacts included. The insight reframes their own decision using data they had not combined themselves.

Notice what all three share. None of them mention the vendor's product in the first line. All three are useful on day one, before any sales conversation starts.

The data sources worth combining

You do not need exotic data. You need two to five ordinary sources combined in a way specific to one company. The common list: public records and permits, job postings and hiring signals, tech stack, pricing pages, product information, review sites like G2 and Capterra, Glassdoor, LinkedIn activity, and company news. Most of these sources are not hard to find individually. Nobody is first to any single one of them. The advantage comes from stacking three or four at once and synthesizing what they mean together for one specific account.

How to build your own PVP

The process I use, in order:

1. Know your own product's pain and promise, three to five layers deep. Not the one line pitch. What specific outcome changes for the buyer, and what happens if that outcome never shows up. This takes maybe twenty to thirty minutes of honest thinking, and most people skip it.

2. Pick two to five public data sources that are specific to the account and that combine to reveal something new. One data point rarely produces an insight. Two or three combined usually do.

3. Synthesize with AI. I'd use Claude for the actual synthesis step, since it tends to handle the "here is data source one, two, three for Company X, what is the most valuable insight tied to their pain or promise" prompt better than the alternatives. ChatGPT or Gemini are fine for the deep research pass that gathers the raw material first, and Clay is the platform that pulls the data sources together before any of that synthesis happens. I've ranked where Clay sits against the rest of the GTM stack in a separate tool-by-tool breakdown if you want the fuller picture.

4. Run the $100 test. If the honest answer is no, add a data source or recombine what you already have before you touch the copy.

5. Send it, with no pitch attached. The message stands on its own. If it is good enough, the question of "how did you find all this" becomes the opening for a conversation on its own.

Where AI fits, and where it does not

AI is the synthesis layer, not the research layer and not the strategy layer. It is good at taking three or four data points you hand it and proposing the sharpest insight that connects them to a pain or a promise. It is not good at deciding which data sources matter for your specific product, and it will not tell you that your two-line value prop is actually a PQS wearing a disguise. That judgment still sits with whoever is building the campaign. When I'm setting these up for clients, the time actually goes into picking the right data sources and deciding which combination earns the reaction, not into writing the email copy itself, which tends to be short once the insight is real.

What this actually does to reply rates

In the video, the reply rate numbers cited for a typical cold email run in the low single digits, somewhere around 2 to 3%, which matches what most plain, non-personalized outbound produces in my own experience running it for clients. The claim for PVP messages is a reply rate in the 20 to 40% range, with a meaningful share of responses being a thank you even from people who never book a call. I have not run enough of my own PVP campaigns yet to put a number next to that claim myself, so take it as what was stated in the video rather than something I am personally vouching for, but the direction, that a message which helps first gets answered far more often than one that asks first, lines up with what good B2B outbound already looks like even without the PVP label on it.

Where PVP breaks down

PVP is not free. Building a real one takes meaningfully more work per account than writing a templated PQS message, because you are doing real research and real synthesis for each prospect rather than swapping a variable into a template. That makes it a poor fit for very high volume, low value plays where the economics only work if the cost per message stays close to zero. It also assumes your product actually has a pain or a promise worth tying an insight to. If you cannot answer what specific outcome changes for the buyer, no amount of clever data combination will rescue the message, because rule two of the three, tied to pain or promise, simply will not hold.

The checklist I use before sending: would they pay $100 for it, can they act on it without buying from me, is it specific to their situation, does it combine data they have not already combined themselves, is it tied to the pain or promise my offer addresses, is it built from public data only, and does it show expertise without pitching. Getting all seven right makes a strong PVP. Getting five or six right still beats almost every templated message going out today, so do not let the perfect version block you from sending a good one.

FAQ