Create Co-Sell

Submit a co-sell referral to AWS, Azure, GCP, or a Fours partner directly from a HubSpot deal using the Fours App.


Overview

A co-sell referral is how you formally ask AWS, Azure, or GCP to work with you on a deal. When you submit a referral, the cloud provider’s sales team can see the opportunity and engage to help you close it — for example, by introducing you to the right contacts, validating the opportunity, or contributing resources.

In plain terms, you’re sharing a deal with your cloud partner so they can help you win it. The same button also shares a deal with a Fours partner — a partner connected to you through Partner Management — so a referral can go to a channel partner rather than a cloud. After adding the Fours App to your HubSpot Console, you can create all of these straight from a deal.

For more details, see Co-Sell.

Prerequisites

The Fours App must be set up in HubSpot and the Fours app card must be visible on your deal pages. If you haven’t done that yet, see Set up the Fours App in HubSpot.

Create a Co-Sell

  1. Navigate to the deal’s detail page and click the “Suger” tab at the top of the page.
Suger tab on a HubSpot deal detail page
  1. Locate and click the “Co-Sell” button.
Co-Sell button in the Suger panel
  1. Choose the destination you want to submit the referral to. There are up to four: AWS, AZURE, GCP, and Partner — a partner connected to you through Fours.
Cloud partner selection for AWS Azure or GCP

The button adapts to what your organization has connected:

  • More than one destination — the button reads Co-Sell and opens a dropdown listing each one.
  • Exactly one destination — there is no dropdown. The single entry renders as a plain Co-Sell button that opens that destination’s form directly.
  • An AWS integration on the AWS ACE API — the dropdown also ends with Enrich this company, so the button opens a dropdown even when AWS is the only destination. See AWS: enrich the deal’s company into a lead.
  • No destinations — the button does not appear at all.

If your AWS connection still uses the legacy AWS S3 API, choosing AWS opens an AWS S3 API Deprecated notice instead of the referral form: “The AWS S3 API is no longer supported. Please contact your administrator to upgrade to the new AWS ACE API.” Ask your administrator to upgrade to the AWS ACE API — the referral form is not available until they do.

  1. Complete the required fields in the form. Note that the required fields may vary depending on which cloud partner you selected.
Co-Sell referral form with required fields
  1. Once all necessary information is filled in, submit the form to create the Co-Sell.
Submitting the completed Co-Sell form
  1. You are all set!

AWS: contacts on the referral form

The AWS ACE referral form’s Contact details accordion holds one customer contact and two partner contacts, each under its own labels so it is clear who is who:

On the formWho goes here
Customer name, Customer title and Customer contact detailsThe person at the customer this opportunity is with
Partner Opportunity Owner, with its Contact detailsThe person on your side who owns the opportunity
Partner Account Manager, with its Contact detailsAn optional second person on your side

Three behaviours worth knowing:

  • The customer contact comes from one deal contact. On a new referral, your co-sell field mapping fills the customer fields from one of the deal’s contacts, picked so that a reseller’s contact is not sent as the customer’s. Which deal contact becomes the customer contact explains which contact is used and why the fields can come up empty. Editing or re-submitting a referral keeps the contact it was saved with. The Azure and GCP forms pick the customer contact the same way.
  • Blank partner contacts are dropped. If you leave a partner contact section empty, it is not sent to AWS — you do not have to fill in the account manager just to submit.
  • Partner contacts are read-only when editing. Once a referral exists, you can edit the rest of it, but the partner contacts are fixed.

On the referral detail, contacts are presented as two separate cards — Cloud Contacts (AWS) for the people AWS has assigned, and ISV Contacts for yours — so it is clear at a glance which side owns which name.

AWS: predicted quality score

Before you submit, the Share Opportunity with AWS and Re-submit AWS Opportunity panels show a Predicted AWS Opportunity Quality box above the form: Fours’ estimate of how AWS will score the opportunity, so you can improve it first. It is not shown on Edit AWS Opportunity — once the opportunity is in ACE, AWS’s own score applies.

  • The score reads N / 100 with its band, a meter, and a one-line verdict.
  • The breakdown lists each scoring dimension with the points earned out of the points it carries, marked ✓ (full credit), – (partial) or ✗ (none).
  • What to change — Suggested improvements (n) lists the edits that would raise the score; an entry can name the field it concerns and the points it would add. When the opportunity misses a basic requirement, an alert reads AWS will likely score this opportunity 0, and the list is titled Fix these to clear a 0 (n) instead.

The box scores the opportunity when the panel opens, and again about three seconds after you change the contacts or make a substantial edit to the customer business problem or the next steps. Re-analyze scores it on demand. With no business problem it reads Add a customer business problem to get a predicted score. and Re-analyze is disabled; after other edits it may read Content changed. Click Re-analyze to refresh the score.

This is a different number from the Suger Predicted Engagement Score on the Insights tab, which is Fours’ prediction for the customer’s company rather than for this opportunity — see Engagement score on the Insights tab. For how the score and its bands are read, see AWS Opportunity Quality Score.

AWS: enrich the deal’s company into a lead

Enrich this company, the last entry in the Co-Sell menu, sends the deal’s company to AWS Partner Central as a co-sell lead. AWS creates the lead and returns what it knows about the company — a readiness score, a solution score and its profile of the customer — and the lead appears on the deal’s Co-Sell tab. It works on the company, not the deal: the lead is shared with every deal on that company. What lead enrichment is, and what AWS returns, is covered in Lead Enrichment.

The entry appears when your organization has an AWS integration on the AWS ACE (Partner Central) API. Before your team uses it:

  • A Fours admin saves the mapping. In the Fours Console, open Co-Sell, then Settings → Lead Enrichment, and configure HubSpot Company → AWS Lead: which HubSpot Company properties hold the company name, domain, industry, country and the other fields AWS needs.
  • AWS allows your Partner Central account to create leads. If it hasn’t, ask your AWS partner team.
  • The company has a contact at its own domain. AWS requires a named person on every lead, so the company needs an associated contact whose email address is at the company’s domain. Fours picks the contact for you.

To enrich a company:

  1. Open the deal, click Co-Sell, and choose Enrich this company. A dialog shows Enriching this company… while Fours sends the request.
  2. Once Fours has sent it, the dialog closes and the card waits for AWS’s answer. A toast reports the outcome: Lead created and enriched., AWS returned no enrichment data for this company. or AWS enrichment failed. No lead data was added. If AWS hasn’t answered after about 90 seconds, the toast reads Enrichment started. The lead will appear in the Co-Sell tab when AWS answers.

If the company already has a lead, the dialog opens that lead’s Lead Details instead of creating a second one.

When Fours can’t send the company, nothing reaches AWS. The dialog reads Can’t enrich this company, gives the reason and Fours’ message, and says No lead was created.

  • A reason in the mapping — an industry or country value with no AWS translation, a required field that isn’t mapped, or no mapping at all — adds Fixing this needs the Co-Sell field mapping in Suger — if you don’t have access, contact Suger. and an Open field mapping ↗ button, which opens the HubSpot Company mapping in the Fours Console.
  • Any other reason has no Open field mapping ↗ button. Most are fixed on the HubSpot records, for example Missing contact identity or Missing state for a US company; some are not — Lead creation not enabled is AWS’s setting, and Re-enrichment not yet available or Enrichment in progress only need you to wait.
  • A deal with no associated company stops with This deal has no associated company to enrich.

Azure: solution area and play

The Azure referral form has a Solution Area/Play section. Pick the solution area first, then the play underneath it; the second dropdown’s placeholder is Conversation, and in field mapping the same field is labelled Solution Play/Conversation.

The solution areas are Microsoft’s FY27 set:

Solution area
AI Business Solutions
Cloud and AI Platforms
Microsoft Services
Security
Windows and Devices

Azure: company lookup and team members

The Microsoft company lookup runs on its own. When the Azure form opens with a valid customer address, Fours searches Microsoft for the matching company automatically — you no longer need to click Search. If the address is incomplete, fix it and use the Search button as before.

Adding team members. The Azure form’s Add Team Member modal takes four fields: First Name, Last Name, Email, and Phone Number.

Share a deal with a Fours partner

Beyond the three clouds, you can share a deal with a partner connected to you through Fours — the same partnership network you manage in Partner Management. It is a fourth destination on the Co-Sell button, not a separate tab or button.

Step 1 — pick the partner

Choosing Partner opens the Share Co-Sell with Partner panel. It explains what is about to happen: “Choose a partner connected via Suger. The selected partner will receive an inbound copy of this co-sell.”

  1. Start typing in the Partner field. Its placeholder is “Search by name or domain”, so either works.
  2. If there are more matches than the list shows, a hint reads ”+{n} more — keep typing to narrow the list.” Keep typing until your partner appears.
  3. Select the partner and click Continue.
  4. Answer Whose product is being sold in this deal? — Our product (We sell it. {partner} brought the deal.) or {partner}‘s product ({partner} sells it. We brought the deal.). The direction is recorded permanently on the co-sell.

Step 2 — complete the form

The second step is the co-sell form itself, organized into accordions:

AccordionWhat you enter
Customer & OpportunityThe customer company name, website, industry, and country, plus the opportunity name, opportunity type and target close date
Deal DetailsThe customer’s business problem (Opportunity Context when you are the Referrer), the Transaction Model, the deal value and its currency (optional, see below), and an optional use case
Revenue ShareCommission type, revenue share model, payment trigger, and clawback window. Shown only when you are the seller and Commissions is on for your organization
Partner CollaborationAs the seller, the partner’s Attribution Role (see The partner’s attribution role); what you need from the partner on this deal
TeamYour people on the deal. Use Add Team Member to add a row and Remove to drop one

The footer has two buttons: Back to return to Whose product is being sold in this deal?, and Share Co-Sell to submit.

Three things about this form catch people out:

  • The deal role is not editable on the form. Whether you are the Seller or the Referrer on this co-sell comes from your answer to Whose product is being sold in this deal? — to change it, click Back and choose the other answer, which starts a fresh form. It also drives what you see: the Revenue Share accordion only appears for the Seller, and for the Referrer the deal-value field is labelled Estimated Deal Value rather than Deal Value.
  • The customer business problem has a minimum length. It must be at least 20 characters, so a one-word answer will not submit.
  • The deal value is optional. You can share a deal before it has a quote: leave Deal Value (or Estimated Deal Value) blank or at 0, as the line under it says — No quote yet? Leave it at 0 — the final deal value is required to close as Won. A negative value is flagged Deal value must not be negative., and Currency becomes required only once the value is above 0. The co-sell needs a value above 0 later, when it is closed Won — see Mark as Won.

Option lists used on this form:

FieldOptions
Revenue Share Model% of Final Transaction, Fixed Amount, To Be Defined, plus Discount off list price when Commission Type is Reseller Margin
Deal value visibilityShow deal value, Hide deal value

A reseller’s discount off list price

Choose Discount off list price when the reseller buys at a percentage off your list price and sets its own price for the customer. It is offered only with the Reseller Margin commission type. The discount records the terms; nothing is paid to the partner:

  • The rate field reads Discount (%) and takes a value above 0 and up to 100.
  • The payment trigger is not selectable. The form says Payment trigger: not applicable. Nothing is paid to the partner; the discount is applied on the partner’s order.
  • There is no clawback window, and no commission preview or commission tracking after the deal closes. The co-sell shows one line instead, for example Reseller discount: 20% off list price (not paid out).

Switching away from the discount gives the payment trigger back, set to On Customer Invoice. Changing Commission Type away from Reseller Margin clears the discount (the model and its rate) the same way, so choose the revenue share model again. The same choice is available when you add a partner or edit a partner’s terms on an existing co-sell, and terms prefilled from a partner’s commission plan can carry it.

The partner’s attribution role

The attribution role records what the partner did on the deal, and it is saved whether or not Commissions is on.

  • As the Seller, you pick the partner’s Attribution Role in Partner Collaboration: Sourced, Influenced or Transacted. Everywhere else the card shows it as Partner sourced, Partner influenced or Transacted. The select starts on Sourced. If your co-sell field mapping maps Attribution Role (Attribution Role (Fours partner)), it starts on the mapped role instead; a mapped value that is not exactly one of the three roles leaves Sourced. You can change it before you share.
  • As the Referrer — registering a deal on the partner’s product — there is no picker. Partner Collaboration shows Your role on this deal as Partner sourced · awaiting confirmation, with the note Registering a deal claims it as partner sourced. {partner} confirms it, or sets a different role, when they accept. It’s saved whether or not commissions are on.

When Commissions is off for your organization — the Commissions switch under Partners → Settings → Features, see Commission plans — the Seller form has no Revenue Share accordion and the co-sell carries no commission terms. Deal Value Visibility moves into Partner Collaboration instead, with a line saying whether the partner sees the deal amount.

After you share

Partner co-sells appear in the same Co-Sell table as your cloud referrals, with Partner identifying the destination. Opening one shows the Partner Co-Sell modal with the details as shared: Overview, Customer, Deal, Revenue Share, and Team.

The modal is no longer read-only. It now carries the same three surfaces the Fours Console has:

Activity

An Activity tab holds the conversation on the co-sell — messages grouped into threads, each with its author. Posting is scoped: a message can be internal to your side, or visible to everyone on the co-sell. Use it instead of a side email thread, so the discussion stays attached to the deal both parties are looking at.

Add Partner

A co-sell is created with exactly one partner. The create API takes a single partner by contract, so Partner 1 is fixed when you share the deal — every additional partner joins afterwards, through the Add Partner dialog on this modal.

Revenue-share terms for the partner you add prefill from that partner’s own commission setting: their custom plan when they have one, your standard defaults otherwise.

When you are the seller and Commissions is on for your organization, the co-sell lists each partner that has revenue-share terms, and each one has an Edit button while your copy of the co-sell is still open. Once that partner’s own copy is closed Won with terms that start no commission tracking, such as a discount off list price or a 0% cut, the button is replaced by This deal was closed Won with no commission to track, so its terms are final. Terms set to To Be Defined keep their Edit button.

Commission

A Commission section on the modal pre-populates from the HubSpot deal rather than asking you to retype figures that already exist on the record.

Attribution

On a partner’s copy of the co-sell, the modal’s header carries the partner’s role as a tag, for example Attribution: Partner sourced. While a role the partner claimed by registering the deal is still waiting for the seller, the tag adds · awaiting confirmation.

When a partner registers a deal on your product and you accept it as the Seller with Accept & Complete, the Accept & Complete Co-Sell dialog has an Attribution section, and its Attribution Role is required:

  • The partner claimed a role. The role starts on the partner’s claim, and the section reads {partner} registered this deal, so it’s saved as {role} until you confirm. Change it if your records differ. A deal registered from the partner’s portal or CRM is claimed as Partner sourced.
  • The deal came through your public deal registration link. The role starts on the one the partner picked on that form, with the same line.
  • The partner didn’t pick a role. Nothing is selected, and the section reads {partner} didn’t pick a role on this deal. Pick one to accept. Accepting without a role stops with Pick the partner’s attribution role to accept.

Accept with the role unchanged to confirm it, or pick another role: the dialog then notes that the partner will see the new role on their copy, with your organization as Changed by in Activity.

The same dialog’s Deal value section takes a blank or 0 value, so you can accept a deal that has no quote yet; the line under it reads No quote yet? Leave it at 0 — the final deal value is required to close as Won. Only a negative value stops the accept, with Deal value must not be negative.

Mark as Won

On a co-sell where you are the Seller and the status is active, the modal has a Mark as Won button. It opens a Mark as Won dialog whose Final deal value — Deal value and Currency — starts from the co-sell’s current value, in USD when it has no currency. A co-sell shared or accepted at 0 gets its real value here: while the value is empty or 0, the dialog says A deal can’t be closed as Won with a value of 0. Enter the final deal value. and its Mark as Won button stays disabled.

For the same co-sells in the Fours Console, see Track and respond to deals.

Track referrals on the Co-Sell tab

The Co-Sell tab lists every referral raised from this deal, cloud and partner alike. With an AWS integration it also lists the deal’s AWS co-sell leads: the leads of the deal’s primary company, and leads linked to this deal. Referrals and leads are mixed in one list, newest first.

A deal with no offers but with at least one referral or lead opens on this tab, so its co-sell records are the first thing you see; a deal with offers opens on Offers. See Verify the app card is working.

ColumnWhat it shows
NameThe opportunity or lead name. Click it to open the referral’s detail modal, or the lead’s Lead Details
TypeReferral or Lead
IDThe referral or lead identifier
PartnerWhere it was submitted — AWS, Azure, GCP, or a Fours partner
DirectionWhether the referral is outbound (you shared it) or inbound (it was shared with you)
StatusWhere the referral stands with that partner
Create DateWhen the referral was created
Last Activity DateWhen it last changed

Failed updates are flagged on the row. If an AWS referral is in UPDATE_FAILED, an error badge appears next to its name. Hover it and the tooltip shows the raw failure message returned by AWS, which is usually enough to tell you which field to correct before resubmitting.

Open a lead’s details

Click a lead’s name to open Lead Details. Under the lead’s name and status tags it shows:

  • Lead details — Lead ID, Qualification state, Lead source, Creation date (UTC), Target close date, Linked deal, and Converted referral, the AWS referral the lead became. When that referral is on this deal, click it to open it.
  • Company details — the company and contact name, country, website, email, AWS maturity, industry, phone and market segment.
  • AWS Lead Enrichment — on a lead enriched from a HubSpot company only: Readiness, AWS Marketplace solution score, and an AWS insights block from Account name to Country, under the line Company-level, for {company} — shared with every deal on this company. When AWS returned nothing, the card says AWS returned no enrichment data for this company.
  • Interactions — each interaction on the lead, with its Interaction name, Date (UTC) and Customer action.

Re-enrich, on the AWS Lead Enrichment card, asks AWS again, and a toast reports the outcome — Lead re-enriched. when AWS returns data. A company can be re-enriched once every 30 days: the card shows Last enriched {date} and, until 30 days have passed, Re-enrich available {date}, and the button stays disabled until then. A refused re-enrichment shows its reason on the card, with Open field mapping ↗ when the fix is in the mapping.

An AWS referral that was converted from a lead names it under Converted from lead in the referral’s details. Click it to open the lead.

Engagement score on the Insights tab

The deal’s Insights tab — and the Co-sell Insights card on company records — groups the customer’s co-sell signals by cloud, in blocks headed AWS Co-sell Signals, Azure Co-sell Signals and GCP Co-sell Signals.

Each block leads with Suger Predicted Engagement Score. It is Fours’ prediction for the customer’s company, not a score a cloud gave a specific referral:

  • On a deal, it is still the company’s score. The tab shows the score for the deal’s primary company and no longer swaps in the engagement score from the deal’s AWS referral.
  • No score, no row. When Fours has no score for the customer on a cloud, the row is left out rather than shown empty.

How the score is worked out, and how it differs from a partner’s own score on a referral, is covered in Engagement Score. Fours can also write it into a HubSpot property through CRM Enrichment — see What intelligence signals can Fours write into HubSpot?

What happens next

After you submit the referral:

  • Fours creates the referral and links it to the HubSpot deal.
  • The referral is sent to the cloud partner’s system — for example, AWS Partner Central (ACE), Azure Partner Center, or Google Cloud Partner Network. If you shared it with a Fours partner instead, that partner receives an inbound copy of the co-sell.
  • The cloud partner reviews the referral and may accept, reject, or request more information.
  • Any future updates Fours syncs from your HubSpot deal are automatically reflected on the referral — you do not need to manually push updates to the cloud partner.
  • The referral is also visible in the Fours Console on the Co-Sell page under Cloud Partners, which lists your AWS, Azure and GCP referrals and the co-sells you share with Fours partners.

Troubleshooting common issues

IssuePossible causeResolution
No Suger tab visible on the deal pageThe Fours app card has not been added to the deal layoutSet up the Fours App in HubSpot to add the app card
No Co-Sell button visible inside the Suger panelThe HubSpot integration connection has been disruptedGo to Fours Console → Settings → Integration → HubSpot and click Verify to re-verify the connection
Only one or two destinations appear in the selectorYour Fours account may not have co-sell configured for all cloudsContact your Fours admin to confirm which cloud partners are enabled for co-sell. With exactly one destination there is no dropdown at all — a single Co-Sell button is the expected behaviour
Partner is missing from the selectorYour organization has no connected Fours partnersThe Partner destination only appears once a partnership exists. See Partner Management
Choosing AWS opens an “AWS S3 API Deprecated” noticeThe AWS connection still uses the legacy AWS S3 APIAsk your administrator to upgrade the integration to the AWS ACE API. The referral form is unavailable until then
Form fields are blank — not pre-filled from the dealField mapping has not been configuredField mapping is an optional admin setup. Contact your admin to configure it
The customer contact is empty on a new referral, while other fields are pre-filledThe deal has two or more companies and none of its contacts belongs to the primary company, or the deal has no contactsSee Which deal contact becomes the customer contact, or type the contact in before you submit
Referral was submitted but is not visible on the dealSync between Fours and HubSpot is delayedRefresh the page after a few minutes. If it still doesn’t appear, confirm the referral was created in the Fours Console

Frequently Asked Questions (FAQs)

  • Q: What’s the difference between a co-sell referral and a private offer?

    A: A co-sell referral shares your deal with the cloud provider’s partner team so they can help you close it. A private offer is a custom-priced contract you send directly to a buyer. They serve different purposes — co-sell is about getting the cloud partner involved in the deal; a private offer is the actual transaction.

  • Q: Can I submit a referral to more than one cloud partner for the same deal?

    A: Yes. You can submit separate co-sell referrals to AWS, Azure, and GCP from the same HubSpot deal — just click Co-Sell again and select a different partner.

  • Q: Do I need to manually update the referral every time the deal changes in HubSpot?

    A: No. Fours automatically syncs changes from your HubSpot deal to the referral. If you update mapped fields on the deal, those changes flow through to the cloud partner automatically.

  • Q: Will the co-sell referral show up in the Fours Console too?

    A: Yes. Any referral created from HubSpot is also visible in the Fours Console on the Co-Sell page under Cloud Partners, including co-sells shared with a Fours partner.

Spotted something wrong or out of date on this page? Tell us and we'll correct it.