White-label software is often evaluated by its features: CRM, messaging, workflow automation, domains, client accounts, or branded portals. For an agency deciding whether to resell software, another question may matter first: what do you owe before a client signs, and what do you give up after the client starts paying?
Two common structures answer that question differently. A fixed subscription makes the operator pay a recurring platform fee. A revenue-share arrangement ties part of the vendor’s compensation to client billings. Neither model is automatically cheaper or safer. The right comparison depends on the service being sold, the client’s usage, how billing works, and the support the partner must provide.
Bolten’s current guides describe direct client billing with a 70/30 split and a Repasse model in which the partner pays for the selected tools and sets the client price. The current 70/30 guide identifies Stripe as the route for new eligible Brazilian partners and labels Pagar.me as legacy. HighLevel’s pricing page lists Agency Pro at US$497 per month and SaaS Mode as a Pro feature. These examples illustrate different cost structures; they are not equivalent products or a ranking of quality. Confirm your own account before purchasing. (Bolten — 70/30 billing; Bolten — Repasse billing; Bolten — Products and prices)
Model the commitment before signing
Under a fixed-fee plan, the platform subscription is due even when the reseller has not yet found a paying client. The operator may also incur setup time, payment processing, communication or usage charges, customer support, and taxes. The subscription is one cost in the business, not its full launch budget.
In a revenue-share model, the platform’s compensation changes with the amount billed through the arrangement. Bolten’s current English-language guide says that, in its direct-sales model, Bolten charges the end client and passes 70% of the amount paid to the partner. The guide also describes a software-provider option where the partner pays the platform’s listed minimums for selected tools and sets their own client price.
A variable share may reduce the fixed bill before sales arrive. It also means the platform receives a share as billings grow. The partner still spends time on prospecting, configuration, training, support, bookkeeping, and client communication. Those costs do not disappear because the software subscription is zero.
Map the fees in each offer
A partner page may show a headline price, minimums, a commission percentage, or a trial. Read the billing flow as well as the table. Ask who invoices the end client, when a trial converts, who pays transaction fees, whether the listed amount is per user or per project, and what happens if the client cancels.
Bolten’s current 70/30 guide describes a seven-day trial and a 70% partner share of amounts paid; the partner’s share is held in Stripe and paid out according to the receiving account’s schedule. Its Repasse guide says the partner pays the published minimums for tools in use and sets the client price. These are platform terms, not industry standards. Before quoting a client, check the partner account for current local currency, usage limits, charges, payment route, and eligibility.
HighLevel’s pricing page currently identifies SaaS Mode as a feature on its $497-per-month Agency Pro plan. That monthly plan price is not necessarily the total cost of operating a client service: the platform describes separate usage-based services and optional features. Check the current plan and applicable add-ons for the exact workflow you intend to sell. (HighLevel — Pricing and plan features; HighLevel Support — Agency Pro and SaaS Mode)
| Cost question | Fixed subscription | Revenue share or usage-based partner model |
|---|---|---|
| What is due before client revenue? | The recurring plan fee, plus setup and any applicable extras | Possibly no recurring platform fee, but terms may impose tool minimums or other charges |
| How does the provider earn? | Subscription regardless of your current client billings | Share of payments, tool charges, or another amount defined in the agreement |
| What changes as billings grow? | Subscription may stay fixed while usage charges can vary | The provider’s share or usage charges can rise with activity or price |
| What should be verified? | Tier gates, usage, add-ons, payment processing, cancellation | Share basis, exclusions, payout, tax/invoice flow, trial conversion, minimums |
The table describes patterns, not a guarantee about every vendor. A plan can combine a fixed subscription with usage costs or reseller features. Read the current agreement and pricing page for the exact account and country.
Calculate break-even and test the assumptions
A basic comparison can clarify one narrow part of the decision. Suppose a fixed plan costs $497 per month and an alternative gives the partner 70% of client billings, leaving 30% with the provider. If those were the only costs and the services were otherwise comparable, 30% of about $1,657 in monthly billings equals roughly $497.
That arithmetic is not a platform recommendation. It compares only a subscription fee with one percentage of gross billings. It excludes payment fees, currency conversion, included features, usage, support labor, setup, taxes, refunds, account eligibility, and the value of the provider’s services. It also assumes that all relevant billings use the same pricing basis. A real model should replace each assumption with a current written quote and the operator’s own cost estimates.
For a software-provider arrangement where the reseller pays tool minimums, calculate the cost client by client. Record the number of licensed users, project-based tools, usage limits, and price paid to the platform. Then compare that total with what the client has agreed to pay. The difference is gross margin before labor, processing, service delivery, tax, and other business expenses. It is not take-home profit.
Compare the responsibilities attached to each plan
The billing model can shift tasks between the vendor and partner. In Bolten’s direct billing description, Bolten collects payment from the end client and the partner receives a share. In the software-provider model, the partner pays Bolten for selected tool usage and sets a client price. Those arrangements can affect who handles the invoice, billing questions, account setup, and support—but the exact responsibilities should be confirmed in the partner terms.
Do not assume that a white-label arrangement transfers all product or compliance responsibilities to the software vendor. The partner may still make promises to the client, configure integrations, explain workflows, resolve onboarding questions, or coordinate service changes. Specify who handles product support, data access, privacy questions, cancellation, refunds, and service interruptions before selling the software as part of a broader agency offer.
Decide from the service you plan to deliver
Start with the customer outcome, not the reseller dashboard. Define which task the software will help the client perform, what the partner will configure, and how the client will get support. If the offer depends on a particular channel, integration, or compliance capability, verify that exact feature in the current product documentation and account before including it in a proposal.
Then estimate the workload. A lower platform price may require more partner time. A higher fixed fee may include capacity or features that are valuable only after the agency has enough clients. A share can be attractive when revenue is uncertain, yet expensive if billings rise and the partner has little ability to change the arrangement. A reseller price can create margin, but only if the partner understands all underlying tool costs and support obligations.
Use a small, explicit scenario instead of a generic promise. For example, write down the number of users, the required tools, expected usage, partner setup hours, client price, platform charges, and who handles payment support. Label uncertain inputs as estimates and ask the provider for a written confirmation where the terms are unclear. Do not present a hypothetical model as a client result or typical outcome.
Questions to resolve before you commit
Before choosing a white-label program or quoting it to a client, verify:
- Which model and currency are available in your country, and is the charge fixed, usage-based, or a share of client billings?
- What billings does any share apply to, which deductions occur first, and are there separate per-user, project, or usage charges?
- What happens at the end of a trial, and can activation or cancellation be controlled?
- Who invoices the client, handles payment disputes, and issues transaction documents?
- Which party provides first-line support, and what response commitments are documented?
- Which features, add-ons, payment methods, and data-export options are included in the plan you intend to sell?
If a material answer is not in the public documentation, ask the provider and preserve the written response with your pricing model. Avoid relying on an affiliate comparison, an old screenshot, or a calculator example that does not match the published terms.
Match the cost structure to the service you will deliver
A fixed subscription can make sense when the operator has a validated service, stable client demand, and a reason to pay for the platform’s bundled capabilities. A revenue share or usage-based model can fit an early offer where the operator wants to avoid committing to a large fixed subscription before testing demand. The trade-off is that variable charges may scale with the revenue the operator generates, and the partner still carries delivery and support costs.
Bolten’s published models illustrate how a partner can choose between direct client billing with a revenue share and paying for tool usage as a software provider. HighLevel’s Agency Pro plan illustrates a fixed monthly plan that includes SaaS Mode. The comparison is useful only after confirming that the product capabilities, local terms, client workflow, and total costs match the service being considered.
The key decision is not “Which platform is free?” or “Which gives the largest margin?” It is “Which agreement leaves enough value for the work I will actually perform, at the level of client demand I can support?” Answer that with current terms and an explicit cost model, then reassess as usage and responsibilities change.
