How to Pre-Sell a Regtech Product Before You Build It
A real regtech commitment is not a compliance officer telling you "this is exactly what we need." It's a signed letter of intent tied to a specific audit or filing deadline, a budget line your champion can point to, or a wire transfer for a paid pilot before a single screen exists. Compliance buyers move slowly and answer to auditors, so the only commitments worth building around are the ones that survive procurement, legal, and a change in the buyer's mood.
Quick Answer: Pre-sell a regtech product by finding a named buyer with a specific, deadline-bound regulatory pain, running a structured pilot conversation instead of a pitch, and converting interest into a written letter of intent or a paid design-partner pilot before you write code. Enthusiasm without budget, a signature, or a calendar date attached to it is not a commitment — it's a compliment.
Prerequisites: a specific regulatory pain and a named buyer
Before you request a single meeting, you need two things nailed down, or every conversation that follows will be too vague to act on.
A specific regulatory pain, not a general compliance worry. "Compliance is hard" is not a pain — it's a category. A pain is "our Q3 SOC 2 Type II renewal requires evidence collection we currently do by hand across four tools, and the auditor flagged it last cycle." The difference matters because regtech buyers don't budget against categories. They budget against a control gap that has already caused friction — a failed audit finding, a near-miss reported to the board, a new regulation with a hard compliance date. Your job before any outreach is to identify which specific trigger you're solving for, because that trigger is what will eventually justify the purchase order.
A named buyer, not a target persona. "Chief Compliance Officers at mid-market fintechs" is a persona. "Priya, Head of Compliance at a 200-person payments company, who owns the SOC 2 renewal and reports the outcome to the board" is a buyer. If you can't name the person, their title, their reporting line, and the artifact they're accountable for producing, you don't have a prerequisite yet — you have a hypothesis. Getting from persona to named buyer is its own research pass. If you haven't done it, mapping the buying committee for a regtech product is the right prerequisite step before you attempt to pre-sell anything, because compliance purchases rarely have a single decision-maker — they have a champion, an economic buyer, and at least one veto-holder in IT or legal.
Once you have a named buyer attached to a specific, dated pain, you're ready to run the pilot conversation. Skip this step and you'll spend months collecting polite nods from people who were never going to sign anything.
Steps: from first call to signed commitment
Direct answer: Run four sequential steps — frame the conversation as a pilot invitation rather than a pitch, draft a letter of intent that names the specific problem and success criteria, agree on measurable success criteria before any code exists, and secure a budget commitment (even a small one) that survives the buyer's internal approval process. Each step produces an artifact you can point to later; none of them depend on your product actually working yet.
1. Frame the conversation as a pilot, not a pitch
The framing of your first outreach determines what kind of answer you get back. If you email a compliance officer asking "would you be interested in a tool that automates evidence collection," you're inviting a polite, low-cost "sure, sounds interesting" — the exact kind of answer Rob Fitzpatrick's The Mom Test warns founders to distrust, because people are reliably nice about hypothetical products and reliably honest about anything that costs them something. Instead, frame the ask as a design-partner pilot: you're recruiting three to five organizations to shape a product around their actual evidence-collection workflow, in exchange for early access and influence over the roadmap. This framing does two things. It shifts the conversation from "would you like this" to "here's what it would take for you to try it," which surfaces real objections early. And it filters out buyers who like the idea in the abstract but have no intention of doing the work a real pilot requires — reviewing your data model, giving you read access to a sanitized evidence set, sitting through a working session.
2. Draft a letter of intent that names the specific problem and success criteria
A generic LOI ("Company X is interested in exploring a partnership with Vendor Y") is nearly worthless — it commits nobody to anything and won't survive a change in the buyer's priorities. A useful LOI names the specific control or workflow you're addressing, states the pilot's duration and scope, and lists concrete success criteria that both sides sign off on before it starts. Keep it short — one page, plain language, no legal boilerplate beyond what your buyer's procurement team requires — because the goal is a document your champion can forward internally and defend in five minutes, not a contract that needs outside counsel to review.
3. Set success criteria before any code exists
This is the step founders skip because it feels premature — how do you define success for a product that doesn't exist? But defining it now, with the buyer, is exactly what turns the pilot into a real test instead of a demo tour. Success criteria for a regtech pilot are usually operational, not aspirational: "reduces evidence-collection time for the SOC 2 renewal from 40 hours to under 10," not "improves compliance efficiency." Write the criteria down, get the buyer's champion to agree to them in writing, and revisit them at the pilot's midpoint. If you can't get agreement on what success looks like before you build, you won't get it after either — you'll get a moving target dressed up as feedback.
4. Secure a budget commitment, even a small one
The single strongest signal in a regtech pre-sale is money changing hands, or a written commitment that it will. It doesn't need to be your eventual contract price — a modest paid pilot fee, a deposit against a future subscription, or a purchase order for a fixed-scope engagement all count, because each one has to clear an internal approval process your buyer doesn't control alone. That approval process is the real test. A verbal "we'd pay for this" from one compliance officer tells you nothing about whether procurement, legal, and whoever owns the budget line will agree. A signed PO or an invoice paid tells you the whole chain already did. If a buyer resists any form of paid commitment at the pilot stage, that resistance is information — either the pain isn't as acute as they described, or they're not the person who can actually authorize spend, which loops back to the buying-committee mapping in step one.
How to read commitment strength
Not every "yes" is the same yes. The table below ranks the four commitment types you'll typically collect during a regtech pre-sale, from weakest to strongest, so you can weight them correctly instead of treating a friendly call the same as a signed pilot.
| Commitment type | What it actually proves | Common false-positive risk |
|---|---|---|
| Discovery call, positive tone | The pain resonates in conversation | High — buyers are polite; enthusiasm costs them nothing |
| Letter of intent (LOI) | The buyer will put a named problem and criteria in writing | Medium — non-binding, can be signed without internal buy-in |
| Paid pilot | Budget cleared an internal approval process | Low — money moved, but scope may still be limited |
| Signed contract or renewed subscription | The product delivered value the buyer will pay to keep | Lowest — the strongest evidence you'll get pre-launch |
The practical takeaway: treat anything short of a paid pilot or LOI as a lead, not a validated commitment, and don't let a string of encouraging calls substitute for the harder work of getting a signature or a payment. If you're still early enough that you're gathering initial demand signal rather than closing pilots, the broader mechanics of pre-selling a product before it exists apply here too — regtech just adds a longer approval chain on top of the general pattern.
Mistakes: accepting enthusiasm instead of budget
The most common failure mode in regtech pre-sales isn't a bad product idea — it's founders mistaking polite enthusiasm for validated demand. A compliance officer says "we'd definitely use something like this," and the founder logs it as a validated lead, builds a roadmap around it, and is genuinely surprised three months later when that same person goes cold. This is the exact trap The Mom Test is built to prevent: people are bad at predicting their own future behavior and good at being agreeable in a conversation, especially when the person asking is clearly hoping for a yes. The fix isn't to distrust every compliance officer you talk to — it's to stop asking questions that invite a compliment and start asking questions that require a commitment.
A few concrete versions of this mistake, worth watching for directly:
- Treating a forwarded email as a warm intro that will close. A compliance officer connecting you to procurement is a data point, not a deal — procurement can still say no, and often does on cost or vendor-risk grounds alone.
- Letting "we're interested, circle back next quarter" reset the clock indefinitely. If a buyer won't commit to a specific next step with a date attached, you don't have a delayed yes — you likely have a no that hasn't been said out loud yet.
- Skipping the written success criteria because the buyer seems eager to start. Eagerness at the start of a pilot doesn't prevent scope disagreements at the end; it just delays them until they're harder to resolve.
- Counting logo interest instead of budget interest. A recognizable company name willing to be a reference is valuable, but it's a marketing asset, not evidence the product solves a paid problem — don't let it substitute for a pilot fee or signed LOI.
If you haven't yet confirmed the regulatory trigger and buyer role are real in the first place, it's worth stepping back to validate the regtech idea itself before investing more pre-sale effort into a buyer whose pain may be shallower than the conversation suggested.
Key Takeaways
- A specific, dated regulatory trigger beats a general compliance worry — budget follows a named control gap or deadline, not a category of concern.
- A named buyer with an accountable artifact is a prerequisite, not a nice-to-have — without one, you're validating against a persona, not a person who can sign.
- Frame outreach as a design-partner pilot, not a product pitch — it invites real objections instead of polite agreement.
- A short, specific letter of intent is worth more than a long, generic one — name the problem and the success criteria your champion can defend internally.
- Success criteria belong before the build, not after — write them down and get sign-off while there's still nothing to be polite about.
- Money moving, in any amount, is the strongest pre-launch signal you'll get — it proves the buyer's internal approval chain, not just their opinion.
- Enthusiasm is not evidence — treat it as a lead until it converts to a signature or a payment.
Frequently Asked Questions
How much should a regtech pilot cost before you build anything?
There's no fixed number — what matters is that the fee is large enough to require the buyer's normal approval process, not that it covers your costs. Even a small paid pilot forces procurement and budget sign-off, which is the real test of commitment.
Is a letter of intent legally binding?
Usually not, and that's fine — an LOI's value isn't enforceability, it's specificity. A well-written LOI names the problem, the pilot scope, and success criteria in writing, which is far stronger evidence than a verbal "we're interested," even though neither party can be sued over it.
What's the difference between a paid pilot and a design-partner pilot?
A design-partner pilot typically trades early access and roadmap influence for the buyer's time and feedback, with payment optional or deferred. A paid pilot adds a fee cleared through the buyer's approval process, which is the stronger signal — design partnerships are a reasonable first step, but they shouldn't be the last one.
How long does it take to close a first regtech letter of intent?
It varies by organization size and how urgent the regulatory trigger is, but expect it to take longer than a typical B2B SaaS sales cycle — compliance purchases route through risk, legal, and often IT before a signature happens. Building slack into your validation timeline for this is safer than assuming a startup-speed close.