Guide
Should Your SaaS Charge a Setup Fee? When an Initiation Fee Funds the Build
Short answer: charge a setup fee when getting a customer live costs you real money or real time before they see any value: hardware, data migration, custom configuration, integration work, training. It also needs the buyer to be a business choosing on value, not someone signing up self-serve. A setup fee covers that cost upfront, filters out customers who aren't serious, and can fund the very part of the product you couldn't afford to build. Don't charge one when setup is just a signup form. There it's friction. And if the expensive part of setup is someone else's product, consider partnering with them on a revenue share instead of buying it.
From the video:
The founder who couldn't afford the sensors
On a call, I spoke to a founder building an operations tool for a mining site. The site ran on manual data entry: people walking around, writing numbers down and typing them into spreadsheets. The founder's first version did exactly what the customer did, just more neatly. Readings were logged by hand, in an app that worked offline, because the site had almost no signal.
The obvious next step was sensors placed around the site, feeding readings in automatically, connected to the tools the site already used, with reports generated without anyone typing anything. The founder knew it. The problem was money. Sensors cost real money upfront, and an early-stage founder doesn't have it.
The usual answer would be to raise. The better answer was already sitting in the deal: an initiation fee. The customer pays a one-off setup fee, and that fee fronts the money for the sensors.
Look at it from the customer's side. They're already paying people to walk around with clipboards and type numbers into spreadsheets, every week, forever. Paying once to make that stop is an easy decision. And once the data flows automatically, they'll keep paying monthly for the reporting on top of it.
The founder doesn't need an investor to buy the sensors. The customer who wants them does.
What is a SaaS setup fee?
A setup fee is a one-time charge at the start of a customer relationship that covers the cost of getting them live. It goes by several names:
- Implementation fee: usually configuration and integration work.
- Onboarding fee: usually training.
- Initiation fee: usually when it buys something specific upfront, as in the story above.
It's common in B2B software where each customer needs real work before they get value, and rare in self-serve products where setup takes a minute.
When should a SaaS charge a setup fee?
When most of these are true:
- Setup has a real cost before any value arrives. Hardware, data migration, connecting to the customer's existing systems, custom configuration, on-site or live training.
- The buyer is a business with a budget, buying through a conversation, a proposal or a contract, not a credit card form.
- The value is large and obvious compared with the fee. Ideally it's something they already pay for today in staff time, in errors or in a tool they'll replace.
- You'd otherwise carry the cost for months before the subscription pays it back, and a customer who leaves early leaves you with the loss.
The mining site ticks all four.
When shouldn't you charge one?
- Self-serve products. If a customer can sign up and use your product in ten minutes, a setup fee is a toll on the front door. It will cost you more sign-ups than it earns.
- When competitors let people start free. You'll need a very clear reason the setup is different.
- When the fee is covering for a product that's hard to set up. If every customer needs three hours of hand-holding, the fix is usually in the product, not the invoice.
- When the amount is token. A small fee that covers nothing just adds a line item to argue about.
How do you structure a setup fee?
There's no universal number. It depends on what the setup actually costs you and what the outcome is worth to the customer. These are the common structures:
| Structure | How it works | Good when | Watch for |
|---|---|---|---|
| Flat fee | One fixed price for getting live | Setup is similar for every customer | Undercharging the complex ones |
| Cost-plus | Hardware or third-party costs plus your time | There's a physical or external cost, like the sensors | Showing your margins in the proposal |
| Credited against year one | Paid upfront, deducted from the first year's subscription | You need the cash now but don't want to raise the total price | It's really a prepayment; budget for that |
| Waived for annual prepay | No fee if they pay the year upfront | You'd rather have commitment than the fee | Discounting yourself into a cash gap |
For the mining-site tool, cost-plus is the honest choice: the sensors at cost plus installation, shown clearly, with the monthly subscription for the software and reporting on top.
How does a setup fee fund your product?
It's customer financing. The cash arrives before the cost does, so you can build what that customer needs without giving away equity or borrowing.
It also does something no survey can. A customer who pays a setup fee has validated the product with money, not with "I'd totally use that". Stated interest costs nothing; a purchase costs something. (Why market research keeps getting this wrong.) A setup fee is one of the cleanest early signals that what you're building is worth building.
It's one form of an idea we keep returning to: you don't always need to raise money to own resources when you can arrange to access them, and grow now while paying from the upside.
How should you pitch a setup fee?
- Name what it buys. "Sensors installed and connected across the site", not "onboarding".
- Compare it with what they pay today. The hours spent typing numbers into spreadsheets, every week.
- Put it in the proposal from the start. A fee that shows up at contract stage feels like a trick. One that's in the first conversation feels like a plan.
- Offer the credit option if they flinch. Crediting it against the first year often removes the objection without costing you the cash flow.
The alternative: partner with whoever owns the expensive part
Sometimes the expensive part of setup is something another company already sells. In the mining example, the sensors and the readings could come from an IoT monitoring platform whose devices and API already measure what the site needs.
Instead of buying that platform's devices and reselling them, you can integrate with it. The customer gets one product: readings flowing into your reporting automatically. The platform sells its devices and subscription through your product. Each of you earns on your own sales, and the platform shares revenue on the customers who come through you. You don't carry inventory, and the platform gets a channel into an industry it might never have reached.
That doesn't replace the setup fee in every case. It does mean you should ask, before you buy anything: is the expensive part of my setup someone else's product? If it is, they may be a better partner than a supplier.
Where Ordana fits
Ordana is where software products that serve the same customer find each other and agree a revenue share. If the expensive part of your setup is another product, Ordana can help you find it, put the terms in a contract, tag each sale at the payment and split it automatically. Each side builds its own part of the integration.
Frequently asked questions
Should SaaS companies charge a setup fee?
Only when getting a customer live costs real money or time before they see value, such as hardware, data migration, integration or training, and the customer is a business buying on value. For self-serve products where setup is a quick signup, a setup fee usually costs more sign-ups than it earns.
What is an initiation fee?
An initiation fee is a one-time charge at the start of a contract that pays for something needed upfront, such as equipment or setup work. In an early-stage company, it lets the customer fund a cost the founder couldn't otherwise cover. For example, a monitoring tool might use one to buy the sensors that make it automatic.
How much should a SaaS setup fee be?
There's no standard figure. Base it on what setup actually costs you and what the outcome is worth to the customer. Common structures are a flat fee, a cost-plus fee covering hardware or third-party costs plus your time, or a fee credited against the first year's subscription.
Does a setup fee hurt conversion?
For self-serve, low-priced products, usually yes. For B2B products sold through a conversation, a clearly explained setup fee tied to a concrete outcome rarely loses good customers. It tends to filter out the ones who weren't serious, and the cash helps you deliver.
Can a setup fee replace fundraising?
For a specific cost tied to a specific customer, often yes: the customer funds what they need. It won't fund a whole roadmap. But combined with revenue-share partnerships for the parts other companies already own, it can take an early product a long way without outside investment.
Related reading:
- You Don't Need to Fundraise, You Need Resource Financing: access resources instead of buying them.
- Grow Now, Pay From the Upside: paying partners from what they help create.
- Why Market Research Lies: why a purchase beats a survey.
- Don't Fundraise to Own Resources, Collaborate to Access Them: the bigger version of the same idea.