# HubSpot App The Fours app for HubSpot ships **two cards**. The main one is a deal card: add it to your deal record layout and a **Suger** tab appears on every deal. The second, **Co-sell Insights**, is a company card and is added separately. Inside the deal card, a rep works from **five tabs** — **Offers**, **Entitlements**, **Co-Sell**, **Funding**, and **Insights** — with up to **four action buttons** across the top: **New Offer**, **New Resale**, **New Funding**, and **Co-Sell**. Which buttons you see depends on what your Fours organization has connected, and field mapping (optional) pre-fills their forms from deal properties. :::info Fours was formerly named Suger. Inside HubSpot, the app — its marketplace listing, the **Suger** deal card and tab, and labels such as **Suger Predicted Engagement Score** — still uses the name Suger until the app is renamed. ::: ## Set up the app, then work a deal 1. **[Configuration](/hubspot-app/hubspot-app-configuration/)** — add the Fours app card to your deal record layouts, add the **Co-sell Insights** card to your company layouts, and confirm the Suger tab renders. Complete the HubSpot integration in Fours Console first; the cards will not appear otherwise. 2. **[Create Offer](/hubspot-app/hubspot-app-offer/)** — build a private offer for the buyer on the deal: negotiated pricing, terms, and an expiry date, based on a product that already exists in Fours. The **New Offer** button also covers amendment offers and reseller offers. 3. **[Create CPPO](/hubspot-app/hubspot-app-cppo/)** — use the **New Resale** button instead of a private offer when the deal is with a reseller. You set the wholesale price — or, on Azure, grant a standing resale authorization by customer market — and the reseller creates the final offer to the end customer. 4. **[Create Co-Sell](/hubspot-app/hubspot-app-cosell/)** — share the deal with AWS, Azure, or GCP as a referral, or with a **Fours partner** through [Partner Management](/prm/). Each destination is submitted separately and tracks its own status, and nothing is sent to your customer. 5. **[Create Funding](/hubspot-app/hubspot-app-funding/)** — apply for AWS funding against the deal under any of the seven AWS funding programs, cash or credit. AWS only, and the one action here that needs no product in Fours. ## The Co-sell Insights company card The second card, **Co-sell Insights**, is registered on the **companies** object, not on deals. Adding the Fours deal card does not add it — go to a company record, customize the record layout, and add **Co-sell Insights** the same way. The configuration page above covers both cards. Like the deal's **Insights** tab, the card shows the customer's co-sell signals per cloud, led by the **Suger Predicted Engagement Score** — see [Engagement score on the Insights tab](/hubspot-app/hubspot-app-cosell/#engagement-score-on-the-insights-tab). ## When something does not look right - **[HubSpot FAQ and Troubleshooting](/hubspot-app/hubspot-app-faq/)** — the consolidated answers for the app: required HubSpot scopes, what field mapping does, why the card may not appear, and how changes flow back to co-sell records. ## Scope and limits :::info The HubSpot integration must be completed in Fours Console before any of this works, and you need HubSpot Admin access to customize deal record layouts. See [Integration with HubSpot](/integrations/hubspot/). Each card is added per view, not once per portal — repeat the steps for every deal view your team uses, and again on the company layouts for **Co-sell Insights**. Products must already exist in Fours before you can create an offer or a resale authorization against them. **Funding is the exception** — it needs an AWS ACE (Partner Central) integration rather than a product. Field mapping is optional: without it, every field on the offer, referral, and funding forms is filled in by hand. Working from Salesforce instead? That integration is a managed package with its own objects, permissions, and reports — see [Salesforce App](/salesforce-app/). ::: ## FAQ ### Does our integration with ACE have auto updates when deals are closed/lost or when the date changes to a new close date? Yes. Once an opportunity is submitted through Fours, depending on how your mapping is set up, you can expect any future update on your HubSpot deal to flow to Fours. ### Regarding the HubSpot automation, do I have to refresh Fours sync with ACE so those changes flow through? There is no need to. On a schedule — outbound CRM-to-partner sync runs about every 6 hours; see [Referral Syncing](/cosell/cosell-syncing/) for the current intervals. We collect the data and update the ACE records based on how things are mapped. So, if you made any changes to a deal on HubSpot, you should see an update on ACE in the coming hours. ### I noticed the Buyers do not have any Contacts. When we do the mapping, will every buyer record always have a full email address (i.e., a contact) sent to HubSpot? Yes, buyers don't have a contact associated with them by default. With Fours, future Buyers will because that's something that a feature Fours offers that AWS doesn't. However, that will only be the case for new buyers after the integration. ### I understand that Fours can present a 'propensity to buy' metric. Can we build this into the data integrated into HubSpot? Yes, we support that. It's part of the Co-Sell Implementation. When you submit one of your HubSpot deals to AWS, Fours will collect the Engagement Score for that customer and send it back to HubSpot. The only thing that's needed is for you to provide the field where you want to store that information.