Every negotiated deal,
on every marketplace.

Private offers built from the CRM record, routed through your own approvals, and resale authorizations that let channel partners sell without you re-cutting an offer for every deal.

See Fours in action See what is covered

300+ ISVs $10B+ cloud transactions processed six cloud marketplaces

The Fours console for offers: a private offer built from a CRM opportunity, with its approval chain and marketplace status.

Illustrative sample data — not customer results.

An offer should not need three portals and a chase.

Every marketplace has its own console, its own fields and its own idea of what an offer looks like.

Today

Offers built in each cloud portal Terms re-keyed from the CRM every single time

Approvals chased over email No record of who signed off on what, or when

A partner deal means a new offer Re-cut and re-priced for every transaction

The deal desk becomes the bottleneck

With Fours

Built from the opportunity Fields populate from the Salesforce or HubSpot record

Approvals route and log themselves Deal desk, finance or leadership, with the trail kept

Partners sell under one authorization Non-expiring, with the margin and terms set once

Faster from build to accepted, in one tracked workflow

From opportunity to signed, through the lifecycle of a transaction.

Build, approve and send is the direct path. Resale is the same offer with a partner in the middle, authorized once rather than cut again for every deal.

The direct path

Or a partner sends it

The deal desk builds the offer where the deal lives.

Start a private offer from a Salesforce opportunity or HubSpot deal and the fields populate from the record. Custom pricing, instalments, usage overages and multi-currency all sit on the same offer, with EULAs and order forms attached so the legal terms travel with it.

CRM-native Custom pricing Instalments Usage overages Multi-currency EULAs and order forms

Where the offer is built

Salesforce or HubSpot

Fours Draft offer

Offer built from an opportunity Acme Corp · OPP-4128 Ready to send

Contract value $185K

Term 36 mo

Type CONTRACT

Buyer Pulled from CRM

Legal terms Standard EULA attached

Illustrative sample data — not customer results.

Nothing reaches a buyer without sign-off.

Each offer routes through the approval chain you configure, whether that is deal desk, finance or leadership. Automated validation catches pricing mistakes and invalid buyer details before they become a support ticket, and every edit is logged.

Configurable chains Automated validation Audit trail Real-time status

What an offer has to clear

Draft offer built from the opp Validation pricing and buyer Deal desk gate 1 Finance gate 2 Gate 3 if you add one Published to the marketplace

The chain is whatever you configure · every decision is logged against the offerValidation runs before the first gate, not after the last

The buyer accepts on the marketplace, on their cloud bill.

The offer publishes to the marketplace the deal runs on, and the purchase draws down the buyer’s existing cloud commitment. Views, acceptances and expiries come back as alerts in Slack, Teams or email rather than as a portal you have to remember to check.

Every marketplace Draws down cloud commitment View and accept tracking Slack, Teams and email alerts

Where the offer moves

Fours

The marketplace The buyer

SFDC-AWS-ABO-0928 Private offer · Acme Corp Pending Acceptance

Offer delivery method PRIVATE

AWS Offer ID offer-3kd9x1

Renewal offer Enabled

Draft Pending Create Create Success 4 Pending Acceptance 5 Accepted

Illustrative sample data — not customer results.

Authorize a channel partner to sell on your behalf.

A channel partner private offer authorizes a reseller to transact on the buyer’s behalf, and the partner owns the billing relationship. Set the margin and seller-agreement terms once and issue a non-expiring authorization, so the partner transacts repeatedly without coming back for a new offer each time.

Channel partner private offers Non-expiring authorizations Margin controls Seller agreement terms Automated reconciliation

Who holds what in a resale

Authorize once You Set the margin and the seller agreement terms, once Non-expiring Sells repeatedly under one authorization The partner Transacts on the buyer’s behalf and owns the billing relationship Your terms Buys from the partner The end customer Buys through the marketplace, on their own cloud bill

The marketplace disburses, and the split is reconciled automatically

Frequently asked questions

From deal desks running offers across more than one marketplace.

What is a private offer?

A custom-priced deal a seller extends to one named buyer on a marketplace, with negotiated pricing, terms and duration that never appear on the public listing. The buyer accepts through the marketplace and the purchase runs on their cloud bill.

Which offer types are supported?

Standard private offers, agreement-based offers and channel partner private offers on AWS, plus the equivalent private offer and private plan types on Microsoft and Google Cloud.

What is a CPPO?

It is AWS’s name for a resale offer. Microsoft and Google Cloud have their own equivalents, and Fours handles the markup, the payment schedule and the partner notifications on each of them.

What does a non-expiring resale authorization change?

A resale offer with no fixed expiry lets a partner transact repeatedly under one authorization, instead of asking you to re-issue an offer and re-adjust pricing for every deal.

Can we build offers from Salesforce or HubSpot?

Yes. The Salesforce and HubSpot managed packages let a deal desk build an offer from an opportunity with fields auto-populated from the record, and internal approvals run before anything reaches the marketplace.

Who approves an offer before it is sent?

Whoever you configure. Approvals, edits and current status are tracked in one place, and an offer cannot reach the marketplace until its chain clears.