Running partner revenue across too many tools? Switch to one system.
Most teams come to Fours from a marketplace or co-sell tool, a legacy partner portal, or something they built in-house. This guide covers what an indirect revenue platform should do, how to compare your options, and what switching to Fours involves.
- 300+
- software companies
- $10B+
- transacted on Fours
- Under 3 weeks
- to a full rollout
Indirect revenue outgrew the systems
that run it.
Indirect revenue is any revenue a software company earns through someone else: a cloud marketplace, a hyperscaler co-sell team, a reseller, a distributor, a systems integrator or a referral partner.
It now drives a growing share of software growth, but the operations behind it haven't kept up. A single partner deal can touch the CRM, two or three cloud partner portals, a marketplace console, billing, the ERP and a spreadsheet. Private offers get built by hand and re-keyed into Salesforce. Co-sell means bulk-uploading opportunities. Disbursements arrive without the deal attached.
The result is that growth stops where headcount does.
The winners aren't the ones with the most partners. They're the ones whose operations can keep up.
Fours is infrastructure for indirect revenue.
Fours is one platform that sits between your own systems (CRM, CPQ, ERP, billing) and every cloud and partner you sell through. Each deal lives on a single record, from the first partner signal to recognized revenue.
Listings, private and resale offers, agreements and renewals across AWS, Microsoft, Google Cloud, Oracle, Snowflake and Alibaba Cloud.
Co-sellReferrals shared to and from AWS, Microsoft and Google from Salesforce or HubSpot, with stages synced both ways.
Partner programsDeal registration, commissions and payouts for every partner type, white-labeled and with no partner login required.
Channel commerceMetering, billing, settlement and reconciliation, with every disbursement matched to the deal and the ERP.
Fours AI Early accessAgents prepare referrals, funding claims, offers and reconciliations inside your rules, with your team approving.
What changes when your team moves to Fours.
Your sellers never open a portal
Reps run private offers and co-sell from the Salesforce or HubSpot opportunity. Referrals land as CRM records and stages sync both ways, so co-sell coverage climbs.
One record across every cloud and partner
From partner signal to payout, every deal sits on one data model. Alliances, deal desk, RevOps and finance work the same record, and leadership gets one view of partner revenue.
Finance closes the quarter on records it trusts
Most tools stop at the accepted offer. Fours meters usage, matches every disbursement to its deal and writes it back to NetSuite, Stripe or Chargebee, so nothing is billed twice.
Four ways teams run indirect revenue today, and where each one stops.
Most teams have tried at least one of these. Each covers part of the deal.
The question is what happens to everything around it.
| Approach | Marketplace | Co-sell | Partner programs | Billing and finance | Where it stops |
|---|---|---|---|---|---|
| Cloud partner portals One cloud, inside that cloud | Partly covered | Partly covered | Not covered | Not covered | Every additional cloud is another portal and another process |
| Marketplace or co-sell tools Cloud listings, offers and co-sell | Covered | Covered | Not covered | Partly covered | Resellers, SIs and referral partners run somewhere else, so there's no single view of partner revenue |
| Legacy partner portals (PRM) Partner onboarding and deal registration | Not covered | Not covered | Covered | Partly covered | Partners rarely log in, and the clouds aren't covered |
| Building it yourself The first version of a cloud integration | Partly covered | Not covered | Not covered | Not covered | Engineering maintains it every time a cloud ships an API change |
| | Covered | Covered | Covered | Covered | One record from partner signal to recognized revenue |
Most teams are fully live in under three weeks.
No internal engineering and no months-long implementation. A dedicated CSM and solutions engineer
run it with you on a shared Slack channel.
- Week 0 Kickoff and security review
Fours shares its security and compliance documentation on day one, so review runs alongside planning. Security, finance and deal desk join.
- Week 1 Install the CRM package
Your CRM admins install the Salesforce or HubSpot managed package with a least-privilege permission set.
- Week 2 Configure your workflows
Clouds connected, co-sell share rules and offer approvals set, billing and payouts mapped to your ERP.
- Week 3 Go live
Your team runs live deals on Fours, with your CSM and solutions engineer on hand from day one.
How to choose an indirect revenue platform
you won't have to replace.
You'll only want to switch once. These are the questions worth asking any vendor, Fours included.
- Does it cover every channel, or only the clouds? Resellers, SIs and referral partners should run on the same record as marketplace and co-sell deals.
- Can sellers do everything from the CRM? If reps have to open a portal, adoption and co-sell coverage drop.
- Does it reach finance? Look for metering, disbursement matching and write-back to your ERP, not just an accepted offer.
- Which clouds does it support today? Adding a cloud later shouldn't mean re-platforming. Fours covers AWS, Microsoft, Google Cloud, Oracle, Snowflake and Alibaba Cloud.
- How is it priced? A percentage of GMV grows with your success. Fours charges no revenue share.
- Who maintains the cloud integrations? Cloud APIs change every quarter. The vendor should absorb those changes, not your engineers.
- Is it proven at your scale? Ask for transaction volume, customer count and references from companies like yours.
- Ask us all seven. We'll answer each one against how your team runs partner deals today. Plan your switch









Questions about switching to Fours
What is an indirect revenue platform?
An indirect revenue platform runs the deals a software company sells through partners: cloud marketplaces, co-sell with AWS, Microsoft and Google, resellers, distributors, systems integrators and referral partners. Fours carries each of those deals on one record, from partner signal through private offer, billing and payout to recognized revenue.
How long does it take to switch to Fours?
Most teams go live on their first marketplace in 5–10 business days. A full rollout of co-sell, offers and billing takes under three weeks. A white-label partner portal is live in under five days with no implementation fee.
Does Fours take a percentage of marketplace revenue?
No. Fours charges no revenue share and no percentage of GMV. It's priced on plan, features and operational scope, on a standard 12-month term with multi-year discounts. You can buy Fours as an AWS Marketplace private offer that can count toward your AWS commit.
Which clouds and CRMs does Fours support?
Fours supports AWS, Microsoft, Google Cloud, Oracle, Snowflake and Alibaba Cloud marketplaces through one workflow, with co-sell for AWS, Microsoft and Google. It runs inside Salesforce and HubSpot through managed packages, and writes back to NetSuite, Stripe and Chargebee.
Do we need engineers to implement Fours?
No. Fours runs the cloud APIs, and your CRM admins install the managed package. When a cloud changes its API, Fours ships the fix once for all 300+ customers, so there are no connectors for your team to maintain.
Is Fours secure?
Yes. Fours is SOC 2 Type II and ISO/IEC 27001 certified and GDPR compliant. It uses least-privilege, read-only CRM access to Opportunity and Account, SSO/SAML, encryption and a timestamped audit trail. Only rule-matched data leaves your systems, and only to the clouds you connect.
What support do we get after go-live?
A named team: a dedicated CSM and solutions engineer, a shared Slack channel and response SLAs.
Run indirect revenue like a business,
not a side channel.
Planning for next year is the right time to fix the system underneath it. See what your partner flow looks like on Fours.
Plan your switch