# Co-sell

Co-selling is how you bring a cloud provider into a deal your team is already working: you share the opportunity, their sellers engage, and the deal often transacts through the marketplace afterwards. Fours connects your CRM — Salesforce, HubSpot, or Dynamics 365 — to AWS Partner Central (the APN Customer Engagement, or ACE, program), Azure Co-Sell, and Google Cloud Partner Network, so your reps share opportunities, accept the referrals the cloud sends back, and watch all of it in one list instead of three partner portals. Fours also carries **partner-to-partner** referrals between two companies that both use Fours, which appear alongside the clouds as a fourth partner.

This section covers the full referral lifecycle — configuring the field mappings, sharing outbound, accepting inbound, and keeping every record aligned afterwards — plus the AWS-specific programs that hang off it: funding, engagement scores and AI insights, and automated outreach to the AWS sales rep on the deal. Once a referral exists, Fours keeps your CRM, Fours, and the cloud partner in step for the life of the deal, with no manual re-entry.

## Start here

1. **[Configuration](/cosell/cosell-configuration/)** — the translation layer between your CRM and each partner portal: field mappings, templates, picklist conversions, and which fields stay in sync.
2. **[Outbound Referral](/cosell/cosell-outbound/)** — pick an opportunity out of the Outbox and share it with a cloud partner, one at a time or in bulk.
3. **[Inbound Referral](/cosell/cosell-inbound/)** — accept or decline referrals the cloud sends you, and let Fours create the matching account, opportunity, and contacts in your CRM.
4. **[Status & Stage](/cosell/cosell-status/)** — read one unified Fours status instead of learning AWS stages, Azure sub-statuses, and GCP states separately.

## Qualify and configure

- **[The Benefits of Co-Selling with AWS](/cosell/why-co-sell-with-aws/)** — why teams co-sell in the first place: wider reach, shorter deal cycles, and joint revenue.
- **[ACE Eligibility](/cosell/cosell-ace-eligibility/)** — the steps you complete in AWS Partner Central to become eligible for AWS leads and opportunities, from joining APN through the Foundational Technical Review.

## Share deals and work what comes back

- **[AWS Partner Central Leads](/cosell/cosell-leads/)** — earlier-stage prospects, either sent by AWS or created from your Salesforce Accounts by lead enrichment: accept or enrich, qualify and edit, then convert a qualified lead into a co-sell opportunity.
- **[Referral Syncing](/cosell/cosell-syncing/)** — what keeps a referral current once it exists: which direction each change flows, how often scheduled syncs run, and how to force one.

## Track the deal and bring AWS in

- **[Co-Sell Insights](/cosell/co-sell-insights/)** — the Insights tab in the Fours widget: warning cards, opportunity and funding insights, and recommended next actions.
- **[AWS Funding](/cosell/cosell-funding/)** — apply to any of the seven AWS funding programs, respond to reason codes when a request is sent back, file cash claims, and watch your funding wallets.
- **[Automate AWS Sales Rep Outreach](/cosell/cosell-aws-rep-outreach/)** — email the AWS rep attached to a shared opportunity automatically, from a team alias, on the events you choose.

## Look up fields and automate co-sell

- **[Co-Sell Fields in ACE](/cosell/cosell-ace-fields/)** — what AWS expects in each ACE field, which ones are mandatory, and how to map them well from your CRM.
- **[Co-Sell Fields in Microsoft](/cosell/cosell-microsoft-fields/)** — the Microsoft solution areas and conversations, and how the Solution Play field maps forward across fiscal-year catalogs.
- **[Create a Referral via API](/cosell/cosell-referral-api/)** — the request payload for `POST /org/{orgId}/cosell/referral`; one endpoint serves all three clouds.
- **[Co-Sell with AI (MCP)](/cosell/cosell-mcp/)** — run the referral lifecycle from Claude, Cursor, VS Code, or another MCP client in plain language.

## Scope and limits

:::info
Co-sell in Fours covers **four partners** — AWS, Microsoft Azure, Google Cloud, and **Fours** (partner-to-partner) — across **three CRMs**: Salesforce, HubSpot, and Dynamics 365. Any partner can be paired with any CRM, so the co-sell surface is a 4 × 3 matrix.

Each of AWS, Azure, and GCP appears as a cloud partner once you have connected the matching integration. **Fours** is different: it is offered as a cloud partner only when **Partner Management (PRM) is enabled** for your organization. If you do not see `SUGER` in the Cloud Partner picker, that is why — see [Partner Management](/prm/) or contact [support@suger.io](mailto:support@suger.io).

You do not need a cloud partner to use co-sell. An organization whose only co-sell relationship is a Fours partner-to-partner connection still gets the full co-sell area — the referral list, the inbox, and the outbox all work with `SUGER` as the partner.

Inbound sync covers AWS, Azure, and GCP. Fours partner-to-partner referrals are excluded from it because there is no external system to pull from; see [Configuration](/cosell/cosell-configuration/) for the inbound settings each partner offers.

Several capabilities are AWS-only: funding, Co-Sell Insights, and sales-rep outreach. Funding and Insights both require your ACE portal to be migrated to AWS Partner Central 3.0, and the Co-sell AI features behind Insights are enabled by Fours — contact [support@suger.io](mailto:support@suger.io). ACE eligibility itself is granted by AWS in Partner Central — Fours does not grant it.

Destructive and org-wide actions — deleting a referral, bulk-syncing a whole org, auto-share, and system configuration — are deliberately not exposed as MCP tools, and neither are funding applications. Do those in the [Fours Console](https://console.suger.io).
:::