A SaaS pricing proposal for an early pilot is a commercial document that presents your requested price, pricing unit, and pilot scope to a prospective customer. Its primary purpose is not to finalize a long-term revenue model, but to test the buyer's willingness to pay before committing to a full deployment.
TL;DR: The pilot proposal is a test to see if a customer will actually pay you. Do not skip the price. Do not overcomplicate the model. Frame your category carefully, match your pricing unit to how often they use the product, and hold your agreed price.
Imagine you are in a pilot call with a warm prospect. They ask what the product will cost. You reply, "Since we haven't fully proven the concept and there are still bugs, we won't charge for the pilot." The tension leaves the room. Everyone relaxes. But you just ruined the test. You learn nothing about whether they value the product enough to buy it. (If you are still figuring out who to pitch, read how to find pilot customers.)
Then there is the other extreme. A founder delays sending a proposal for a month. They are busy in a spreadsheet comparing per-seat against per-sync models. By the time they finish, the warm prospect has gone quiet.
Both founders failed because they misunderstood the document. A pilot proposal is not a revenue event. It is a willingness-to-pay test. You are buying one piece of information: would this person actually move money for this? The only way to find out is to name a figure and see what happens.
What do founders overcomplicate about pilot pricing?
Founders often spend weeks hunting for the perfect pricing architecture. The model you use for your first pilot does not have to be final. You will change it later. But you must not be silent on money. No money means no real value produced.
When figuring out what to present, founders usually under-think three specific areas.
1. The retention pattern
Match your pricing unit to how often the buyer actually uses the product. Consider a tax-compliance tool that a buyer opens once a year. Do not force a monthly subscription onto it. You will save yourself a headache. A proposal like that does not fail on price; it fails on unit. Note: If you use outcome-based pricing, the outcome must be a measurable artifact you control.
Usage Frequency | Pricing Unit Question |
|---|---|
Daily or weekly | Does a subscription match their workflow? |
Annually or seasonally | Is a one-time or outcome-based fee more appropriate? |
2. Perceived competition
Framing the right category sets the number before any line item does. The same product is worth $10 or $100 depending on what the buyer compares it to. Are you replacing an app or a human?
Consider a workflow tool for law firms. The founder might price it at $30 a month because they are thinking about note-taking apps. But partners do not buy $30 tools for billable work. If they price the tool against what a paralegal hour costs, the exact same product reads as a professional service. The category flip changes the buyer's expectation.
Perceived Category | Buyer Expectation |
|---|---|
Note-taking app | Low monthly subscription ($10-$30) |
Professional service / Human replacement | High value-based fee ($100+) |
3. Starting from value
Start from the monetary value your service produces for the buyer and work backward. That is the core of the offer. If you need help computing the actual number, use a B2B pilot pricing calculator. Right now, your job is just to choose a number.
How should you structure the proposal document?
Keep the proposal document short and direct. Do not bury the number. Imagine a fifteen-page deck where the price appears in small type on the last slide. The layout is the message: it says you are afraid of the price.
Here are the key sections you should include in your document:
The Problem and Value
Briefly state the specific pain point the pilot addresses and the measurable value the buyer will receive.
The Pilot Scope
Define exactly what is included in the pilot. List the features, the level of support or onboarding, and the duration of the pilot.
The Investment
State the price clearly and confidently.
Before: "Since we haven't fully proven the concept and there are still bugs, we won't charge for the pilot."
After: "The pilot is $1,000 for 60 days, including onboarding." (Note: figures are illustrative)
The Next Steps
Say exactly what happens when the pilot ends. Clarify what success looks like and how the relationship transitions to a standard contract.
What should you check before sending the proposal?
Before you send the proposal to a prospect, verify these five things:
You named a specific number.
You made the comparison category explicit.
You matched the pricing unit to how often they actually use it.
You stated the value in the buyer's money.
You said exactly what happens when the pilot ends.
If you need a starting point, use a design partner template to structure your document.
Should you negotiate the agreed price?
Pricing can and should change for the next customer, but your instinct should be to protect the number you agreed to with this one. If you agreed the pilot is worth an illustrative $500, keep the agreed price. You can tell them, "If budget is a hard blocker, we can cut the scope, but the price holds." The scope moves. The number does not.
FAQ
Should I charge for an early pilot?
The pilot is a test of willingness to pay. A free pilot removes the signal about whether the customer actually values the product enough to spend money on it.
What if the budget is a hard blocker?
Reduce the scope of the pilot to match a lower budget rather than dropping the price for the same amount of work.
