How to Pre-Sell a B2B SaaS

To pre-sell a B2B SaaS is to collect a real commitment (a signed letter of intent, a deposit, or a paid pilot) from a named business buyer before the software is built. You sell the outcome and a delivery date, not finished features. The commitment proves demand and often funds the work, so you build against a paying yes instead of a hopeful guess.

I learned this in the wrong order. I built first and looked for the buyer second, more than once, across a multi-product solo operation run from Bharatpur, Nepal. The product that gets built before anyone commits to pay is the most expensive way to discover what the market actually wants. Pre-selling reverses that. It moves the risky question (will a business pay for this) to the front, where it is cheap to answer.

This post is the pre-sell playbook for B2B founders: what pre-selling means and why it beats building first, the commitment ladder that turns soft interest into hard money, how to write a letter of intent, how to structure a design-partner deal and a paid pilot, and how to make the ask without flinching. It assumes you have already validated the idea with real conversations; once a buyer commits, decide how to price the tiers they will eventually pay. For the by-hand sourcing that finds these buyers, see finding your first paying SaaS customer. More in SaaS Playbooks. One pre-sell-friendly route is converting an open-source project into SaaS. Before building, prove the pull with landing-page demand tests. Productized services pre-sell themselves — see the productized-service playbook.

Key takeaways

• Pre-selling collects a real commitment before you build: a signed letter of intent, a deposit, or a paid pilot, not just enthusiasm.
• The order matters. Selling first puts the risky question (will a business pay) at the front, where it is cheap to answer.
• Climb the commitment ladder. Verbal interest is the weakest signal; a deposit and a paid pilot are the only ones that mean money.
• A B2B letter of intent is one page: problem, outcome, scope, price, start date, and a non-binding intent to purchase once it works.
• Pre-selling fails for cheap anonymous self-serve. It needs a buyer you can name, reach, and put a real number in front of.

What does it mean to pre-sell a SaaS?

To pre-sell a SaaS means to secure a buyer’s commitment, in writing or in money, before the product is finished. You are not selling code. You are selling a specific outcome by a specific date at a real price. The buyer agrees to pay once you deliver that. Their yes, backed by signature or deposit, is your validation and often your first revenue.

The word pre-sell trips people up because it sounds like a marketing campaign with a countdown timer. In B2B it is quieter. It is a series of one-to-one conversations that end with a documented commitment. No fake buy button. A real buyer, a real scope, and a real signal you can take to your build queue.

This is the oldest sales pattern there is, applied to software. It solves the founder’s worst problem: building something nobody pays for. The fix is to find the payment first.

Why pre-selling beats building first

Building first feels productive. You ship features, you see progress, you have something to demo. The trap is that none of that activity answers the only question that matters at the start: will a business pay real money for this. You can build for a year and still not know.

Pre-selling forces the answer early. When you put a price and a start date in front of a named buyer, one of two things happens. They commit, and now you have demand plus often a deposit to fund the work. Or they decline, and you find out for the cost of a few conversations instead of a year of code. Both outcomes are wins. The only losing move is to learn this after you have built.

There is a funding angle too, especially for a bootstrapper with no outside capital. A paid pilot or a deposit can cover the cost of building the thing the buyer is paying for. The customer funds the product. That is how a lot of bootstrapped B2B tools got their first runway: not from investors, but from buyers who paid before the software existed. Patrick McKenzie has written extensively about charging more and selling to businesses precisely because business buyers will pay for outcomes, not features.

The deeper reason building-first fails is that it lets you avoid the scary conversation. Code does not say no. A buyer might. Founders hide in the editor because it is comfortable and the sales call is not. Pre-selling drags the discomfort to the front, where it belongs.

The commitment ladder: from interest to paid pilot

Not all yeses are equal. A buyer who says “that sounds useful” has told you almost nothing. A buyer who wires a deposit has told you everything. Between those two points sits a ladder of commitment, and the whole game of pre-selling is moving a buyer up it, one rung at a time.

Most founders stop too low. They collect a pile of “looks interesting” replies, read them as demand, and start building. Soft interest is not demand. It is politeness. The signal only gets real when the commitment starts to cost the buyer something: time, then a signature, then money.

Here is the ladder, named so you can use it as a checklist on every deal.

The B2B Pre-Sell Ladder

Rung	The commitment	What it proves	What it costs the buyer
1. Verbal interest	”That sounds useful.”	Almost nothing. Politeness.	Nothing.
2. Booked call	They put a real meeting on the calendar.	Mild intent. The problem is at least worth 30 minutes.	A calendar slot.
3. Letter of intent	A signed, non-binding statement of intent to buy on delivery.	Documented intent. A name attached to a yes.	A signature and their reputation.
4. Deposit	Money down, often applied to the first months.	Real demand. They have decided.	Cash they could lose.
5. Paid pilot	They pay for a scoped result over a fixed window.	The strongest signal short of renewal.	Cash plus their team’s time.

The rule: do not start building on anything below rung three. A letter of intent is the floor for a serious B2B pre-sell, and a deposit or paid pilot is what you actually want. Treat rungs one and two as conversation, not validation.

The ladder also tells you where a deal is stuck. A buyer who will book a call but will not sign anything has a problem you have not surfaced: wrong price, wrong authority, wrong timing. The rung they refuse to climb is the question you have not yet asked.

How do you pre-sell software that does not exist yet?

You pre-sell software that does not exist by selling a promise with hard edges: a defined outcome, a fixed scope, a real price, and a start date. The buyer commits to that promise with a signature or a deposit. You are honest that it is not built yet. The commitment is contingent on you delivering what you described, by when you said.

The honesty is the whole thing. You are not pretending the product is ready. You are saying, in plain words, “I am building X, it will do Y for your team, it will be ready by Z, and the price is N. If you commit now as an early partner, here is what you get.” Business buyers respect that more than a slick demo of vaporware, because it treats them as adults making a procurement decision.

What makes this work is specificity. Vague promises get vague commitments. “An analytics platform” gets a shrug. “A report that shows your support team which accounts are about to churn, delivered every Monday, ready in eight weeks, two thousand dollars for the pilot” gets a yes or a no you can act on. The more concrete the offer, the more real the answer. Arvid Kahl writes about this kind of audience-first, outcome-specific selling for bootstrappers who have no brand to lean on yet.

How to write a B2B letter of intent

A letter of intent (LOI) is the cheapest hard commitment you can ask for. It is one page. It states the problem, the outcome you will deliver, the scope, the price, the start date, and that it is non-binding intent to purchase once the product meets the described criteria. You want a signature or an unambiguous email reply. The goal is a documented yes, not an enforceable contract.

Keep it short enough that a busy operator signs it without routing it to legal. The moment an LOI needs a lawyer, you have over-engineered it. The structure I would use:

• The problem, in their words, one or two sentences. Show you listened.
• The outcome, what their team will be able to do once this ships.
• The scope, what is and is not included, so neither side is surprised.
• The price and terms, the real number, and how a deposit (if any) applies.
• The start date and delivery window, when work begins and roughly when they can expect it.
• The intent line, plainly: “This is a non-binding statement of intent to purchase upon delivery of the above.”
• The miss clause, one line on what happens if you slip the date. A refund, an extension, their choice.

That last line matters more than it looks. It tells the buyer you have thought about failure, which paradoxically makes them more comfortable saying yes. A founder who only describes the happy path looks like someone who has not shipped before. Nathan Barry’s writing on building in public and earning trust is good on why this kind of candor converts better than polish.

An LOI is not legally binding by design. Its value is psychological and informational. A buyer who signs has put their name and a little reputation behind the yes. A buyer who hesitates at a non-binding one-pager was never going to pay.

The design-partner deal

A design partner is a buyer who trades deep access and honest feedback for influence over the roadmap, usually at a discounted or free early seat. This is the relationship side of pre-selling. You are not just extracting a commitment. You are recruiting a co-author for the product.

The deal is explicit. They get a say in what you build, early access, and a price break that ends at a defined point (often when you reach general availability). In return, they give you real usage, candid critique, and ideally a quote or case study later. Three to five design partners are plenty. More than that and you are running a focus group, not building a product.

The risk to flag: a design partner who pays little or nothing is not proof anyone will pay full price. Free access changes behavior. People tolerate rough edges in a free tool that they would never accept in a paid one. So pair design partners with at least one buyer further up the commitment ladder, someone paying real money, so you are not fooled by the goodwill of people getting a deal.

The other trap is letting one loud partner steer the roadmap toward their edge case. You own the synthesis. Listen to all of them, build for the pattern, not for the loudest voice in the room.

Running a paid pilot

A paid pilot is the strongest pre-sell short of a renewal. The buyer pays real money for a scoped outcome over a fixed window, often 30 to 90 days. Unlike a free trial, money has changed hands, so the signal is real. Unlike a full contract, it is bounded, so the buyer’s risk is capped and the yes is easier to get.

Structure it like a small consulting engagement with software underneath. Define the outcome the pilot must produce, the window, the price, and what counts as success. Write the success criteria down before you start. A pilot with no defined finish line drifts into an indefinite free engagement, which is the worst of both worlds: you are working, and the buyer has not committed to buying.

The conversion question is the point of the pilot. Agree up front on what happens if it works: “If the pilot hits these criteria, you move to the annual plan at this price.” That sentence turns a pilot from a science experiment into a sales motion. A pilot with no agreed path to a paid contract is a favor you are doing for a stranger.

For a solo founder, the pilot also doubles as paid product development. You build the thing they need while they pay you to build it. That funding, even modest, is what lets a bootstrapper keep going without raising money. The customer underwrites the work, which is the whole bootstrapped premise.

LOI vs deposit vs paid pilot: which to ask for

These three are the rungs that matter, and they are not interchangeable. Each costs the buyer something different and proves something different. Match the ask to where the buyer is and how much certainty you need before you commit to building.

Mechanism	What it costs the buyer	What it proves	When to use it
Letter of intent	A signature and a little reputation	Documented intent; a name on a yes	Early, to separate polite interest from real intent before you ask for money
Deposit	Cash they could lose, applied to first months	Real, decided demand	Once intent is clear and you want skin in the game before building
Paid pilot	Cash plus their team’s time over a fixed window	The strongest demand signal short of renewal	When the buyer is ready to commit and you want the pilot to fund the build

Ask in order, but do not be afraid to skip rungs when the buyer is ready. If someone says “just let me pay you to build this,” you do not need an LOI first. Take the money. The ladder is for moving hesitant buyers up, not for slowing down eager ones.

How to make the ask and handle “no”

The ask is one sentence: the outcome, the date, and a real price. “I can give your support team a weekly churn-risk report, ready in eight weeks, the pilot is two thousand dollars, want me to start.” Then stop talking. The silence after the ask is uncomfortable and you must let it sit. Whoever speaks first loses, and at the ask, that should be the buyer.

Founders flinch here because naming a price feels like asking for a favor. It is not. You are offering to solve an expensive problem. Price it like you believe that. The most common pre-selling mistake is mumbling a number you have already discounted in your head before the buyer even reacts. The Mom Test is the canonical book on why you must talk about commitment and money concretely, not in hypotheticals, because people will lie to be nice right up until you ask them to pay.

When the answer is no, the work is not over. A no is the most informative response you can get, if you ask the follow-up: why. The reasons sort into four buckets, and each tells you something different.

• Wrong problem. They do not feel the pain you assumed. Your idea may be off.
• Wrong price. The problem is real but the number scares them. Adjust the offer or the scope.
• Wrong person. They are not the budget holder. Find who is.
• Wrong timing. Real problem, real budget, just not this quarter. Follow up later.

Only one of those (wrong problem) is a reason to reconsider the whole idea. The other three are solvable. A pile of “wrong price” answers means rework the offer. A pile of “wrong problem” answers means you just saved yourself a year. Treat every no as a free research interview you got paid in information for.

What pre-selling does not work for

Pre-selling is not universal. It works when you can name the buyer, reach them, and put a real number in front of a human who can say yes. It breaks down when those conditions are missing, and forcing it there wastes time.

It does not work well for cheap, anonymous, self-serve SaaS. A five-dollar-a-month tool sold to strangers who find you through search has no buyer you can call. There is no conversation to have. For those products, the closest analog is a waitlist with a paid deposit or an annual prepay, which is a weaker signal than a B2B commitment but better than nothing.

It also struggles when the value only appears at scale. Some products are worthless with one customer and valuable with a thousand (network effects, marketplaces, data products). You cannot pre-sell the thousandth customer’s experience to the first. For those, pre-selling validates the single-player value if there is any, and you accept that the network value stays unproven until you have a network.

And it does not replace the work of actually delivering. A pre-sell is a promise. The hard part is keeping it. I have shipped products solo on a Cloudflare and Stripe stack, and the commitment is the easy half. Honor the date you promised, or the next pre-sell is impossible because your word is the collateral.

What I would do differently

I would sell before I built, every time. The products I built first, then went looking for buyers for, taught me the expensive version of this lesson. The order that works is reversed: find the buyer, get the commitment, then build the thing they already agreed to pay for.

I would also ask for money sooner and apologize for it less. The instinct to offer everything free “to get traction” is a way of avoiding the only conversation that proves a business. Free users prove people will use a free thing. They prove nothing about whether a business will pay. The dollar is the data.

And I would write the offer down before every call. The vague pitch gets the vague yes that means no. The specific offer (outcome, date, price, on one page) gets a real answer you can build a company on. Specificity is not a nice-to-have in pre-selling. It is the mechanism.

Want the system, not just the article?

This post is one play. The full operating system, the offer templates, the LOI one-pager, the commitment-ladder tracker, and the scripts for asking and handling no, all live in The Bootstrapped Founder Operating System ($29). It is the workbook version of how to pre-sell, price, and ship as a solo B2B founder.

Get the workbook →