Service Marketplace
A wholesale marketplace where one MSP lists a service it delivers and another MSP resells it to its own clients, with the price floor, the revenue split and the platform fee settled before the first sale.
The problem
A client asks for something your team does not do: a penetration test, a Microsoft 365 migration, overnight SOC coverage. You know another MSP that does it well. What follows is a phone call, a forwarded rate card, a subcontract nobody has time to draft, and a price agreed in an email thread. Six months later you cannot say how many of those jobs you passed along, what you made on each one, or whether the partner ever finished the last one. When the partner needs the same favour in return, the negotiation starts again from zero.
What Solidlio does about it
Any MSP on Solidlio can turn a service from its catalogue into a marketplace listing with three prices attached: what a reselling MSP pays, a suggested retail price, and an optional floor below which nobody may sell it. Other MSPs browse the listings, subscribe, and choose how to price the service for their own clients: at the suggested price, at a percentage or fixed markup over cost, or at a custom figure the floor still applies to. A subscribed service can be added to the reseller’s own catalogue and granted to a client like anything else they sell. When a sale is recorded, one order carries the whole picture: the provider’s share, the reseller’s margin, the platform fee on top, an order number, and a link to the ticket the work is done on. New listings pass through platform review before they go live, and the platform can verify, feature or suspend any listing.
Capabilities
| Capability | What it does |
|---|---|
| List a service | Turns a catalogue service into a listing with a title, pitch, category, up to five highlights, a wholesale cost, a suggested retail price and an optional price floor. |
| Price rules that hold | Refuses a wholesale cost above the suggested price and a floor below the wholesale cost, on every write path, including the service editor. |
| Platform review | Sends a listing’s first publish to platform review. Approve, reject with a reason the provider sees, or let the provider withdraw and keep editing. Once approved, pause and resume are instant. |
| Browse and filter | Searches live listings by title, description, tag or provider name, and filters by category, region, verified, featured, or minimum rating. |
| AI discovery | On request, reads your own catalogue and the live listings and recommends services worth adding, each with a match score and reasons. Runs only when you switch it on, and says plainly when it could not analyse. |
| Subscribe with a pricing model | Subscribe at the suggested price, a percentage markup, a fixed markup or a custom price. The effective sell price and the revenue split are shown before you commit. |
| Price floor enforced | Rejects any subscription price or recorded sale below the provider’s floor. |
| Add to your catalogue | Adopts a subscribed service into your own catalogue at your effective price, ready to grant to a client. The price follows your subscription whenever you change it. |
| Record a sale | Records a sale against a client organization you service, or an off-platform client by name, and computes the three-way split in one step. |
| Fulfilment tracking | The provider moves the work from pending to in progress to complete. Either side links the fulfilment ticket, and the ticket’s assets show on the sale. |
| Two-sided ledger | A sales page and whole-account totals for each side: what you earned as a reseller and what you earned as a provider, with fulfilment and payment filters. |
| Reviews | One review per subscribing MSP, one to five stars, marked as a verified purchase when a completed sale exists. Providers cannot review their own listings. |
| Verified and featured | Platform staff verify providers and feature listings. Both badges show on the card, and featured listings sort first. |
| Suspend and reinstate | The platform can pull a listing at any time, which suspends every subscription riding on it. The provider cannot publish out of a suspension; reinstating restores the subscriptions with it. |
| The provider gets paid | Each sale books what the provider is owed. It becomes payable when the work is delivered and the reseller has paid, then rides the same payout run — and the same reserve — that pays your store sales, so an MSP that both sells and delivers is paid once, in one transfer. |
| Everyone is told | Listing approved or rejected, a new reseller, a recorded sale, a completed fulfilment and a payout all raise a notification to the side that needs it, and a webhook for whatever else you run. |
Built for MSPs and their clients
The marketplace is MSP-to-MSP. A client organization never sees it: it does not browse listings, it does not see wholesale prices, and it does not learn that the service it bought from its MSP is delivered by another. What the client sees is its own MSP’s catalogue, its own price, and its own invoice.
| Organization (client) | MSP | |
|---|---|---|
| The marketplace | Not visible. No listings, no wholesale prices, no portal surface | Browses, lists, subscribes and records sales |
| A resold service | Appears in its Services list at the reseller’s price, granted like any other service | Adopts the subscription into its catalogue and grants it per client |
| Pricing | Sees only the retail price | The provider sets cost, suggested price and floor; the reseller picks a model above the floor |
| The sale | Can read its own order, with the split, the buyer and the upstream provider removed | Both MSPs see the full order; only the provider changes fulfilment |
| Invoicing | Receives one invoice from its own MSP, never from the upstream provider | Reseller’s invoice numbering; the provider’s share is recorded on the order |
| Who may act | Nobody in the organization portal | Technicians browse; admins list, subscribe, sell and review |
How it works
- The provider lists — pick a service from your catalogue, write the pitch, set the wholesale cost, the suggested retail price and an optional floor, then submit for review.
- The platform reviews — Solidlio approves the listing, or returns it with a note you can act on and resubmit. After the first approval, pausing and resuming are instant.
- A reseller subscribes — another MSP finds the listing by search, filter or AI recommendation, reads the revenue preview, chooses a pricing model and subscribes. A price below the floor is refused.
- The reseller sells — add the service to your catalogue, grant it to a client, and record the sale at your price. One order is created with the split, the fee and an order number.
- The provider delivers — start the work, link the ticket it is being done on, and mark it complete. Both MSPs see the same order throughout.
- Money moves — a sale recorded against a client organization is invoiced by the reseller immediately, from the reseller’s numbering. Once the work is delivered and the reseller has paid, the provider’s share becomes payable and is transferred on the next payout run. The split and the platform fee sit on the order for both sides to see throughout.
- The reseller reviews — one review per subscriber, flagged as a verified purchase once a sale has been completed.
Editions
The marketplace carries no plan gate. Listing, review, browsing, subscribing, catalogue adoption, sales and fulfilment are included in every tier, including Free. AI discovery spends one AI credit per run from the account’s monthly allowance, so it is bounded by the tier’s credits rather than switched off.
| Capability | Free | Starter | Growth | Scale | Enterprise |
|---|---|---|---|---|---|
| List services and pass platform review | ● | ● | ● | ● | ● |
| Browse, subscribe, price and adopt into catalogue | ● | ● | ● | ● | ● |
| Record sales, track fulfilment, leave reviews | ● | ● | ● | ● | ● |
| AI discovery (monthly AI credits, 1 per run) | 50 | 1,000 | 2,000 | 3,500 | Unlimited |
MSP tiers shown. The marketplace has no organization-portal surface, so end-customer tiers do not apply.
Integrations
- Solidlio Service Catalogue — listings are built from your catalogue services, and a subscription is adopted back into it as a resold service you grant per client
- Solidlio Service Orders and Fulfilment — every sale is a service order both MSPs can open under Billing → Orders
- Solidlio Invoicing — a sale recorded against a client organization is invoiced by the reseller, from the reseller’s own numbering
- Solidlio Ticketing and Assets — a sale links to the ticket the work is done on, and the ticket’s assets show on the sale
- Solidlio Platform Fees — the marketplace fee and the plan transaction fee are recorded on the platform fee ledger for every sale
Compliance and audit
- A listing’s first publish cannot bypass platform review. The approval timestamp and any rejection note are kept on the listing.
- A suspension can only be lifted by the platform. Pausing and publishing cannot route around it.
- Unpublished, paused and suspended listings are hidden from every account but the provider’s and the platform’s, wholesale prices included.
- Every sale is an order with a unique order number, a recorded approval trail, the three-way split and its fee ledger rows, created together in one transaction.
- A sale can only be attributed to a client organization the reseller actually services, and only linked to a ticket in an organization the account can reach.
- Cancelling fulfilment cancels the order and waives its uncollected platform fees, so a cancelled job never carries a fee.
- Reviews are one per subscribing account, refused from the provider and from accounts that never subscribed, and flagged as verified only after a completed sale.
- Subscriber and sales counters are recomputed from the underlying records rather than incremented, so they cannot drift.