Create Funding
Apply for AWS partner funding (MDF or POC) directly from a HubSpot deal using the Suger App.
Overview
Funding is money AWS contributes to the work you do around a deal — a marketing activity, a proof of concept, or promotional credits for the customer. You apply for it, AWS reviews it, and the approved amount is paid out as cash or as credits.
The Funding tab on the Suger app card is where those applications live. From it you can submit a new funding application against the deal in front of you, and see every application already raised from that deal with its current status.
For the console-side view of the funding lifecycle — what each status means, how approvals and claims progress, and where funding lives outside HubSpot — see Co-Sell Funding.
Availability
Funding in HubSpot is AWS only, and it requires the AWS ACE (Partner Central) integration.
- If your Suger organization has no AWS integration, the New Funding button does not appear on the card at all.
- If your AWS connection still uses the legacy AWS S3 API, the button appears but opens an AWS S3 API Deprecated notice instead of the form. Ask your administrator to upgrade to the AWS ACE API.
There is no Azure or GCP equivalent of this tab.
Prerequisites
- The Suger App must be set up in HubSpot and the Suger app card must be visible on your deal pages. If you haven’t done that yet, see Configuration.
- Your Suger organization must have an AWS ACE (Partner Central) integration. No product is required.
Create a funding application
-
Open the deal and click the “Suger” tab at the top of the page.
-
Click the “New Funding” button. The Create Funding Application panel opens.
-
Choose a Program Type and a Funding Type. Both are required before the form appears.
Field Options What it means Program Type MDFMarket Development Funds — funding for a marketing or demand-generation activity POCProof of Concept — funding for a technical evaluation with the customer Funding Type CashPaid to you as cash, against an invoice CreditIssued as promotional credit codes for the customer -
Wait for the pre-fill to finish. As soon as both selections are made, Suger maps your deal onto the funding form and a “Previewing from deal…” spinner runs while it does.
- If something on the deal could not be mapped, a Mapping errors or Mapping warnings alert appears above the form listing the field and the reason. Errors must be corrected by hand in the form before you can submit; warnings are informational.
- Changing Program Type or Funding Type clears the pre-filled values and runs the preview again, so values from the previous selection never leak into the new form.
-
Complete the form. It is organized into accordions, and which ones appear depends on the program and funding type you chose.
Accordion What you enter Funding Request Project Name, Business Description, Annual Recurring Revenue (ARR), the partner contact’s First Name / Last Name / Email Address / Job Title, and optionally AWS Pricing Calculator URL(s) Opportunity Linked AWS Opportunity ID — the AWS opportunity this funding belongs to Project Information Planned Start Date, Planned End Date, AWS Account ID, Country Activity is Executed, State(s) Activity is Executed, and optionally Customer Also Considering Cash Request Currency, Invoice Entity Name, Invoice Remit Country, Invoice Remit Address, Total Cost of Activity, and optionally Partner Contribution and Customer Contribution Credit Request Currency, Value Per Code, Number of Codes, Requested Amount (calculated for you), MDF Credit Activity Type, Total Cost of Project Wallet The wallet the funding is associated with Attachment Attachment Type and Attachment File — supporting documents for the application -
For a cash request, fill in the Cash Claims block inside Cash Request: the MDF Cash Activity Type, the claim Start Date and End Date, Total Cost of MDF Activity, Requested MDF Cash Funding, and Number of Projected Leads. The MDF Funding % is calculated from the amounts you enter and is capped at 50 — you cannot request more than half the activity cost.
- Submit the form. Suger confirms with “Funding application submitted!”, returns you to the Funding tab, and the new application appears in the table. If it does not show up immediately, refresh the card.
Track applications on the Funding tab
The Funding tab lists every funding application raised from this deal:
| Column | What it shows |
|---|---|
| Name | The project name from the application |
| Program | The AWS program the application was submitted under |
| Status | Where the application stands. If AWS returned an error, it is shown here as an error alert on the row |
| External ID | The AWS-side identifier for the application |
| Last Update | When the application last changed |
Before you raise your first application, the tab shows “No funding applications — Create one from this deal with the New Funding button.”
Once an application is submitted, the Suger Console is where you follow it through review, approval, and claims — see Co-Sell Funding. The HubSpot card shows the status; the console holds the full lifecycle.
Troubleshooting common issues
| Issue | Possible cause | Resolution |
|---|---|---|
| No New Funding button on the Suger card | Your Suger organization has no AWS integration | Funding is AWS-only. Confirm an AWS integration exists in Suger Console → Settings → Integrations |
| New Funding opens an AWS S3 API Deprecated notice | The AWS connection still uses the legacy AWS S3 API | Contact your administrator to upgrade to the AWS ACE (Partner Central) API |
| The form does not appear after opening the panel | Program Type and Funding Type have not both been selected | Select both. The form is only built once the program and funding type are known |
| Mapping errors alert appears above the form | A deal field could not be mapped onto the funding application | Read the field named in the alert and fill that field in by hand before submitting |
| Fields are blank — nothing pre-filled from the deal | Field mapping has not been configured | Field mapping is an optional admin setup. Contact your admin to configure it |
| A submitted application is not in the Funding tab | Sync between Suger and HubSpot is delayed | Refresh the card after a few minutes, then confirm the application exists in the Suger Console |
Frequently Asked Questions
-
Do I need a product in Suger to apply for funding?
No. Funding is the exception on this card — offers and resale authorizations are built on a product, but a funding application is built on the deal plus your AWS ACE integration. You can apply for funding even if you have no products set up.
-
Can I apply for funding on an Azure or GCP deal?
No. Funding on the Suger card is AWS-only. The New Funding button does not appear unless your organization has an AWS integration.
-
What is the difference between Cash and Credit?
A cash request is reimbursed to you against an invoice, so it asks for invoicing details and a claim with projected leads. A credit request is issued as promotional credit codes for the customer, so it asks for the value per code and the number of codes instead.
-
Why is the MDF Funding % capped at 50?
AWS funds up to half the cost of an MDF activity. The field is calculated from the activity cost and the amount you request, and it will not go above 50 — if it does, lower the requested amount or raise the total activity cost.
-
Where do I track the application after submitting?
In the Suger Console. The Funding tab in HubSpot shows the current status and the AWS external ID; the full review, approval, and claim lifecycle lives in the console — see Co-Sell Funding.
Spotted something wrong or out of date on this page? Tell us and we'll correct it.