How a partner runs the business of the cloud.
The commercial module of Oasis Core lets a partner price, sell and bill the cloud to its own customers — directly, and through its own partners and resellers — with the margins, chargebacks and goals that go with them, from first estimate to paid invoice.
Two pricing models, built in.
The pricing model follows the customer type, and so does the lifecycle that builds their cloud.
Partners, resellers and their customers, each in their own tenancy.
Multi-tenancy runs through the whole channel, so every level sells, bills and earns on the same records.
One catalogue for the platform. Two for the marketplace.
What the platform delivers, and what partners and ISVs add to it, are catalogued separately and sold together.
What a provider needs to bill in its market.
Set per deployment, so each partner bills under the rules of the market where it owns the infrastructure.
Eight steps, one set of records.
The mini CRM tracks a visitor from the first visit through estimate and contract to billing, so sales, operations and finance never reconcile three systems.
- 1Visitor
Tracked by the mini CRM from the first visit.
- 2Estimate
Built from the priced catalogue.
- 3Quote
Configured, priced and approved (CPQ).
- 4Contract
Agreed, with its terms recorded.
- 5Subscription
Services switched on against the contract.
- 6Meter
Usage recorded as it is consumed.
- 7Invoice
Billed to the customer, direct or indirect.
- 8Payment
Online through Stripe or Paymob, or by bank transfer or on credit.
Federation is commercial, too.
A customer can buy a service that runs in another partner’s region. The financial and contractual transactions go through the Oasis Federation Core and settle on the same records.
Pre-built where it matters most.
SAP for finance, and Stripe and Paymob for payments, are pre-built connectors. Other systems connect through the REST API.
Bring your commercial model.
We will map how you price, sell through partners, bill and collect today onto the commercial module.