Per-user, per-month pricing lets SAP Business One partners quote cloud in minutes because the entire calculation is users multiplied by the partner's own price. Everything - infrastructure, MFA, support, upgrades, migration, trial systems - is bundled into one rate, so there's no server sizing, no bill of materials, and no component pricing to assemble before a proposal can go out.
That sounds like a convenience. It isn't. It's a commercial weapon - and in this post we'll show you why the partners growing recurring revenue fastest on our platform treat quoting speed as a competitive advantage in its own right.
This is Step 4 of our Sales Playbook for SAP Business One partners in full detail.
What does a cloud quote look like without per-user pricing?
If you've ever built a hosting quote on raw AWS or Azure, or priced your own infrastructure, you already know - and if you're evaluating a cloud offering for the first time, here's what the traditional exercise involves:
Sizing compute, memory, and storage for the customer's SAP Business One workload. Pricing Windows Server and SQL licensing (or HANA memory). Adding backup, disaster recovery, anti-virus, monitoring, and remote-access licensing. Estimating bandwidth. Working out what support wrapper to attach and what to charge for it. Then sanity-checking the whole stack against what happens when the customer adds five users next year.
That's a bill-of-materials exercise, and it has three costs that never appear on the quote itself:
Pre-sales time. Hours, or often days, of technical effort per deal, usually from the same senior people your services business needs elsewhere.
Rationing. Because each quote is expensive to produce, your team quietly stops proposing cloud unless the customer asks. The deals you never quote are the recurring revenue you never see.
Risk. Undersize it and performance complaints land on your support desk. Oversize it and your price loses the deal. Either way, you carry the sizing risk.
How does the per-user, per-month model work?
On the C4P platform, the quote is one line: number of users × your price per user per month. That's it.
It works because the price is fully bundled. Whether your customers are on C4P Standard (multi-tenant, the default for most of your base) or C4P Advanced (single-tenant, for larger or more demanding customers), every user includes the infrastructure, multi-factor authentication, unlimited support, upgrade assistance with a 30-day upgrade test environment, migration through the Migration Factory, SQL to HANA conversion where needed, and trial systems for pitching new deals. There are no components to price, no optional extras to forget, and no surprise at renewal.
The sizing risk moves off your desk too. The platform is engineered, monitored, and continuously tuned for SAP Business One workloads on SAP-certified AWS infrastructure - so "will it perform at this spec?" is our problem to have already solved, not a variable in your quote.
Where does your margin come from?
This is the part of the model most partners underestimate: there is no published RRP.
You buy at partner pricing that is private to you, and you set your own sell price. That means three things for your commercial position:
You choose your margin - deal by deal, segment by segment, or as one standard rate card. It's your pricing strategy, not ours.
Your customers can't shop your list price, because there isn't one. The number on your proposal is simply your price for your cloud offering.
Your competitors can't see your economics. Partner pricing is confidential, so the partner down the road quoting against you is working blind.
Combined with BYOL (Bring your own licence) - your customers' SAP licences stay in your commercial relationship, not ours - the whole stack of value stays where it belongs: with you. You own the customer, the contract, the licence relationship, and the margin. We own the platform.
What actually changes when quoting takes minutes?
The obvious win is responsiveness: when a prospect asks "what would cloud cost us?", your salesperson answers in the meeting instead of promising a follow-up that gives inertia a week to set in.
But the bigger change is behavioural. When a cloud quote costs nothing to produce, cloud goes into every proposal by default. Every new-name deal carries a hosted option. Every support renewal includes the cloud line. Every upgrade conversation offers the move while the project's open anyway. You stop deciding whether to propose cloud and start deciding how to present it - and across an installed base, that single habit is the difference between partners who dabble in recurring revenue and partners who compound it.
There's a customer-side benefit worth putting on the proposal too: the same simplicity that lets you quote in minutes gives your customers a number they can actually budget. One predictable monthly figure that flexes with headcount replaces the lumpy, unpredictable cycle of hardware refreshes, licence true-ups, and emergency IT spend - which is exactly the total-cost conversation that wins the "cloud is more expensive" objection.
And when your customers grow, your revenue grows with them: five new users is one line on next month's invoice, not a sizing exercise, a hardware conversation, or a new sales cycle.
"But is per-user pricing right for every customer?"
Fair question - and the honest answer is that the model fits everyone, while the tier underneath it should be chosen deliberately.
For the majority of your customers, C4P Standard multi-tenant is the default: fastest to deploy, most efficient economics, everything bundled. Your larger customers - heavier customisation, integration workloads, or a preference for isolated infrastructure and customer-controlled upgrade timing - belong on C4P Advanced. And when your cloud base reaches the scale where you want the multi-tenant economics working for you rather than just with you, C4P MTPro gives you your own purpose-built environment.
The point is that tier selection is a positioning decision you make once per customer, not a pricing exercise you repeat per quote. The rate card does the daily work.
Build your rate card this week
If you take one action from this post, make it this: set your price, write it down, and put it in every salesperson's hands.
Pick your standard sell price per user per month - anchored to the value of the bundle and your market, not to a cost-plus habit.
Decide your flex rules - volume breaks, multi-year terms, or a single flat rate. Simple beats clever; the goal is that nobody has to ask permission to quote.
Add the cloud line to your proposal template so it appears by default, with the bundle described in your brand, as your offering.
Do that, and "can you price up cloud for them?" stops being a task and becomes a sentence.
If you'd like to see the model from the inside - including how partner pricing works for your specific customer profile - talk to the team; pricing conversations with partners are private, specific, and quick. Or start with a free partner webinar and see C4P Standard, C4P Advanced, and the full bundle demonstrated live. No obligation, no sales pitch.
FAQs
How is SAP Business One cloud hosting priced for partners? On the Cloud4Partners platform, hosting is priced per user, per month, fully bundled - infrastructure, MFA, unlimited support, upgrade assistance, migration, SQL to HANA conversion, and trial systems are all included in one rate. Partners buy at confidential partner pricing and set their own sell price, as there is no published RRP.
Why do SAP Business One cloud quotes normally take so long? Traditional hosting quotes are a bill-of-materials exercise: sizing compute and storage, pricing Windows and SQL licensing, adding backup, DR, monitoring, and support. Each quote takes hours or days of pre-sales effort, which discourages partners from proposing cloud at all. A bundled per-user model reduces the quote to users multiplied by the partner's price.
Do partners keep their margin on SAP Business One cloud hosting? Yes. Because Cloud4Partners publishes no RRP, each partner sets its own sell price and margin, customers have no list price to negotiate against, and competing partners cannot see each other's pricing. Combined with BYOL licensing, the customer, contract, and margin all stay with the partner.
What happens to the price when a customer adds users? The monthly figure simply flexes with headcount - new users are added at the partner's per-user rate with no re-sizing exercise, hardware conversation, or new quote required, and the partner's recurring revenue grows in step with the customer.
