--- title: "Private and Partner-Led Marketplace Offers" url: https://www.fours.com/platform/offers/ canonical: https://www.fours.com/platform/offers/ type: Platform description: "Every negotiated deal, on every marketplace. Create, approve and track private and partner-led offers in one workflow across AWS, Azure and Google Cloud." --- # Private and Partner-Led Marketplace Offers > Canonical HTML version: https://www.fours.com/platform/offers/ 1. [Home](/) 2. [Platform](/platform/overview/) 3. Offers # 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](/schedule-demo/) [Read the docs](https://doc.fours.com/console/private-offers/) **300+** ISVs **$10B+** cloud transactions processed **3.2 days** average offer cycle ![The Fours console for offers: a private offer built from a CRM opportunity, with its approval chain and marketplace status.](/platform/hero-offers.webp) 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 ![](/favicon.svg) 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 3.2 days from build to accepted, on average ## 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 Build — From the opportunity, not a portal Approve — Your chain, before anything sends Send — Buyer accepts on the marketplace Or a partner sends it Resell — The same offer, sent by a partner ### 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 ![](/integrations/salesforce.svg)![](/integrations/hubspot.svg) Salesforce or HubSpot![](/favicon.svg) Fours Draft offer ![](/solutions/marks/aws.svg)**Offer built from an opportunity** _Acme Corp · OPP-4128_ Ready to send Contract value **$185K** Term **36 mo** Type **CONTRACT** ![](/integrations/salesforce.svg) 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 an eligible purchase can draw 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_ _Commit drawdown where eligible_ _View and accept tracking_ _Slack, Teams and email alerts_ Where the offer moves ![](/favicon.svg) Fours![](/solutions/marks/aws.svg)![](/solutions/marks/azure.svg)![](/solutions/marks/gcp.svg) The marketplace The buyer ![](/solutions/marks/aws.svg)**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 **![](/favicon.svg) 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 ![intel](/home/partners/intel.svg) ![notion](/home/partners/notion.svg) ![webflow](/home/partners/webflow.svg) ![glean](/home/partners/glean.svg) ![airtable](/home/partners/airtable.svg) ![fivetran](/home/partners/fivetran.svg) ![bmc](/home/partners/bmc.svg) ![coderabbit](/home/partners/coderabbit.png) ![launchdarkly](/home/partners/launchdarkly.svg) ![harness](/home/partners/harness.svg) ![fireblocks](/home/partners/fireblocks.svg) ![ramp](/home/partners/ramp.svg) ![deel](/home/partners/deel.svg) ![dbt](/home/partners/dbt.svg) ![clari](/home/partners/clari.svg) ![teleport](/logos/company/teleport.svg) ![logicmonitor](/home/partners/logicmonitor.svg) ![redis](/home/partners/redis.svg) ![dialpad](/home/partners/dialpad.svg) ![fireworks](/home/partners/fireworks.svg) ![1password](/home/partners/1password.svg) ![knowbe4](/home/partners/knowbe4.svg) ![kong](/home/partners/kong.svg) ![chainguard](/home/partners/chainguard.svg) ![dataiku](/home/partners/dataiku.svg) ![zuora](/home/partners/zuora.svg) ![vanta](/home/partners/vanta.svg) ![tailscale](/home/partners/tailscale.svg) ![pulumi](/home/partners/pulumi.svg) ![baseten](/home/partners/baseten.svg) ![risingwave](/home/partners/risingwave.png) ![hootsuite](/home/partners/hootsuite.png) ![elevenlabs](/home/partners/elevenlabs.png) ![callsign](/home/partners/callsign.png) ![fortinet](/home/partners/fortinet.svg) ![pingidentity](/home/partners/pingidentity.png) ![redpanda](/home/partners/redpanda.png) ![qdrant](/home/partners/qdrant.png) ![aiven](/home/partners/aiven.svg) ![thoropass](/home/partners/thoropass.png) Customer outcomes ## More partner-driven growth. Less operational drag. Marketplace revenue, co-sell referrals and partner programs, run by teams who moved off spreadsheets and portals. [See all customer stories](/resources/customer-stories/) > We needed something built for how partnership teams actually work. \[Fours\] checked every box. **Kennedy Grimes** _Alliance GTM Lead NAM, Glean_ Increased co-sell pipeline without adding headcount [Read the Glean story](/resources/blog/glean-expands-co-sell-pipeline-and-automates-operations-with-suger/) > As soon as \[Fours\] went live, we cleared our backlog. It was like unclogging a pipe. **Fireblocks** _From the Fireblocks customer story_ 95% less time registering co-sell opportunities [Read the Fireblocks story](/resources/blog/fireblocks-scales-co-sell-3x-and-cuts-offer-time-70-with-suger/) > I see private offers coming in, self-service growing, and the dollars coming in. I don’t touch anything anymore. **Johan De Keulenaer** _Head of Partnerships · one offer a week to sixty_ 4x growth in private offers, year on year [Read the Aikido Security story](/resources/customer-stories/aikido-security/) ## 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. ## Every offer, under one record. Thirty minutes on your offer motion and where the manual work is today. [See Fours in action](/schedule-demo/) Direct and partner-led, one workflow