---
title: "Co-Sell Across Three Clouds: How to Track ACV, Opportunities, and Credit Without Losing the Thread"
description: Google, AWS, and Microsoft each count co-sell differently. A tracking model for firms that need credit from all three without double entry or lost deals.
---

[blog](https://www.altamiq.com/blog)

# [Co-Sell Across Three Clouds: How to Track ACV, Opportunities, and Credit Without Losing the Thread](https://www.altamiq.com/blog/co-sell-across-three-clouds-how-to-track-acv-opportunities-and-credit-without-losing-the-thread)

 Written by [Altamiq](https://www.altamiq.com/blog/author/altamiq) | Oct 23, 2026, 10:48:20 AM

 For a firm that works with more than one hyperscaler, a single customer engagement can produce credit in three different programs. The deal closes once. The recognition is recorded three times, in three systems, by three vendor teams, using three definitions of what counts. Keeping those straight is a quiet operational problem that decides whether a deal moves you toward a tier or evaporates from the record.

## Why co-sell credit is harder to track than it looks

Vendor programs increasingly reward co-sell activity rather than paperwork. Google’s 2026 network, for example, is reported to use partner co-sell ACV as the measure for its tiers, and to require co-sell-influenced opportunities and partner-implemented workloads for Diamond. AWS’s Services Tier guidance counts launched opportunities that include both partner-originated and AWS-originated work. Microsoft routes its co-sell and incentive logic through Partner Center, where eligibility depends on designations and revenue.

The words overlap, but the units are different. That is the root of the problem.

| **Vendor** | **What gets counted** | **Who validates it** | **Why it slips** |
| --- | --- | --- | --- |
| Google Cloud | Partner co-sell ACV, co-sell-influenced opportunities, partner-implemented workloads (as reported). | Google, against validated closed or won deals. | Credit depends on validation, not on your own CRM. |
| AWS | Launched opportunities, including partner-originated and AWS-originated work, counted toward Services Tier requirements. | AWS, through its partner systems. | Needs the right opportunity record at the right time. |
| Microsoft | CSP revenue and incentive-eligible activity, tied to designations and capability score. | Microsoft, through Partner Center. | Eligibility depends on designation, not just activity. |

 

*Summarized from vendor announcements, press coverage, and the AWS Services Path tier guide. Confirm the current definitions in each program.*

## Four failure patterns

1. **The deal exists only in your CRM.** The opportunity was worked in HubSpot or Salesforce, but nobody created or linked the record in the vendor system, so the vendor has nothing to validate.
2. **The identifiers do not match.** Each vendor assigns its own opportunity ID. Without a field in your CRM that holds each one, reconciling a closed deal to a vendor record becomes a manual search months later.
3. **Validation lags the close.** Credit toward a tier often depends on the vendor confirming the contribution. If you only look at your own pipeline, you will overstate your progress.
4. **One deal, three programs, no shared view.** A multi-cloud engagement can contribute to several programs at once. Without a single log, no one can say how a given deal moved each tier.

## A co-sell evidence log that works across vendors

The fix is a single log kept by deal, with one set of columns that every program’s requirements can be answered from.

| **Field** | **Why it matters** | **Example** |
| --- | --- | --- |
| Customer and internal deal ID | Ties the vendor records back to your CRM. | Acme Corp / DEAL-2041 |
| Vendor opportunity ID (one per vendor) | The key a vendor team needs to validate credit. | Google: \_\_\_ / AWS: \_\_\_ / MS: \_\_\_ |
| Vendor rep and date engaged | Evidence that the vendor was involved. | Name, date |
| Stage and ACV | What the tier calculation uses. | Closed won, $480,000 |
| Validated by vendor? | Separates credit you have from credit you are expecting. | Yes / pending / no |
| Programs it counts toward | Shows how each deal moved each tier. | Google Premier; AWS Advanced |
| Delivery evidence | Implemented workloads and delivered engagements. | SOW, go-live date |

 

## The rule that prevents most losses

> **Log at creation, not at close:** Add the vendor opportunity ID and the vendor rep when the deal is created, not when it closes. The details are fresh, the vendor contact is engaged, and the validation request goes in while it still matters.

## Tie it back to your tier decisions

Once co-sell is logged consistently, it answers a question most firms cannot currently answer: which vendor relationship is actually producing pipeline? That is the input a tier decision needs. If Google credit is accumulating faster than AWS credit, certification hours and attention should follow it, and the portfolio review should say so. Our post on whether a partner tier is worth it walks through that calculation.

## What to do this week

- Add one field per vendor to your CRM deal record for the vendor opportunity ID.
- Pull your last ten closed-won cloud deals and check how many have a validated record in each vendor system.
- For each tier you are chasing, write down which of those deals count toward it.
- Assign one person to own the co-sell log.

## What co-selling asks of the partner

Co-selling sounds like a vendor benefit, and it is. It is also an operational commitment for the partner. Each vendor expects timely updates, accurate customer information, and consistent contact with the vendor seller on the account. Multiply that by three or four vendors and the expectations become a workload.

## A practical record structure

| **Field** | **What it captures** | **Why it matters** |
| --- | --- | --- |
| Customer and deal | Your own CRM record. | Ties the vendor record back to your pipeline. |
| Vendor and program | Which program the opportunity is under. | Rules and benefits differ. |
| Vendor opportunity ID | The vendor’s reference. | The key you use in every conversation with the vendor. |
| Vendor seller | The person on the vendor side. | Who to call when the deal changes. |
| Stage and last update | Where it stands and when you last told the vendor. | Stale updates erode vendor support. |
| Next action and owner | The next step on your side. | Prevents deals stalling between teams. |

 

## Rules of thumb

- **Update the vendor when the deal changes, not on a schedule.** A stage change that the vendor hears about late costs goodwill.
- **Keep customer data consistent.** Spelling, contact names, and company identifiers should match across systems.
- **Review the shared pipeline weekly.** Fifteen minutes with sales operations catches most problems.
- **Report on outcomes.** Count how many co-sell opportunities progressed and closed, by vendor. The result informs where to invest.

The record is also how you answer an executive question that is otherwise surprisingly hard: how much of our pipeline is co-sell, and with whom?

## A weekly co-sell review in 15 minutes

1. **List opportunities that changed stage this week.** Confirm each vendor has been told.
2. **List opportunities with no activity in 30 days.** Decide whether to push, park, or close them.
3. **List new opportunities.** Confirm each has a vendor reference and a named vendor seller.
4. **List requests from vendors.** Assign an owner and a date.

The point is rhythm. Vendors support partners who are predictable, and a short weekly review makes you predictable at almost no cost.

## Choosing what to share with each vendor

Not everything in your pipeline belongs in every vendor’s system. Share what the program requires and what helps the vendor seller support you, and no more. Keep pricing, margin, and competing vendor information in your own record. Having one internal record makes this easier, because you decide what to extract for each vendor instead of retyping everything from memory.

It also protects you commercially. A partner who knows exactly what each vendor has been told can answer questions consistently, and avoids the awkward moment when two vendors compare notes on the same customer.

## Frequently asked questions

### What is co-sell, from the partner’s side?

A joint opportunity where the vendor’s sellers and the partner work the same customer. The partner’s problem is recording which opportunities are shared, with which vendor, and in what state.

### Why use a separate record from the vendor portal?

Each portal shows only its own co-sell activity. A partner-side record is the only place you can see all shared opportunities together.

### What fields matter most?

Customer, vendor, vendor rep, stage, expected close date, and the registration or opportunity ID the vendor uses.

## Further reading

- [Google Cloud Partner Network announcement](https://cloud.google.com/blog/topics/partners/introducing-google-cloud-partner-network) ([cloud.google.com](http://cloud.google.com))
- [CRN on Google's co-sell ACV thresholds](https://www.crn.com.au/news/2026/cloud/google-partner-program-tiering-system-changes) — Reports partner co-sell ACV thresholds ($250K Select, $2M Premier, $20M Diamond) and Diamond requirements of 20 partner-implemented workloads and 30 co-sell-influenced opportunities. ([crn.com.au](http://crn.com.au))
- [Microsoft's co-sell overview](https://learn.microsoft.com/en-us/partner-center/referrals/co-sell-overview) ([learn.microsoft.com](http://learn.microsoft.com))
- [AWS on its enhanced co-sell experience](https://aws.amazon.com/about-aws/whats-new/2023/11/enhanced-co-sell-experience-aws-partners) ([aws.amazon.com](http://aws.amazon.com))
- [Partner Center Referrals user guide](https://learn.microsoft.com/partner-center/referrals-user-guide) ([learn.microsoft.com](http://learn.microsoft.com))

> **AltamIQ:** AltamIQ gives the partner side a single place to see where each vendor relationship stands against its tier requirements, with deal and certification evidence next to each program. It does not replace your CRM. It connects what your CRM knows to what each vendor program requires.

## Sources & verification

- CRN Australia, “Google Cloud’s new three-tiering system brings mixed reviews from partners” (2026) — [https://www.crn.com.au/news/2026/cloud/google-partner-program-tiering-system-changes](https://www.crn.com.au/news/2026/cloud/google-partner-program-tiering-system-changes)
- Google Cloud, “Introducing Google Cloud Partner Network” (Dec 16, 2025) — [https://cloud.google.com/blog/topics/partners/introducing-google-cloud-partner-network](https://cloud.google.com/blog/topics/partners/introducing-google-cloud-partner-network)
- AWS Services Path tier requirements guide, via Westcon-Comstor — [https://www.westconcomstor.com/content/dam/wcgcom/Global/CorpSite/pdfs/services-path-tier-guide.pdf](https://www.westconcomstor.com/content/dam/wcgcom/Global/CorpSite/pdfs/services-path-tier-guide.pdf)
- CloudCockpit and Reseller News NZ summaries of Microsoft CSP and incentive requirements (see post 16 sources).
- VERIFY BEFORE PUBLISHING: this post describes Microsoft co-sell only at the level of Partner Center and incentive eligibility. Add current Microsoft co-sell program details from Microsoft Learn before publication.

[View full post](https://www.altamiq.com/blog/co-sell-across-three-clouds-how-to-track-acv-opportunities-and-credit-without-losing-the-thread)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Altamiq"
  },
  "dateModified" : "2026-10-23T10:48:20.967Z",
  "datePublished" : "2026-10-23T10:48:20Z",
  "headline" : "Co-Sell Across Three Clouds: How to Track ACV, Opportunities, and Credit Without Losing the Thread",
  "image" : {
    "@type" : "ImageObject",
    "height" : 942,
    "url" : "https://47009971.fs1.hubspotusercontent-na2.net/hubfs/47009971/Co-Sell%20Across%20Three%20Clouds-1.png",
    "width" : 1670
  },
  "mainEntityOfPage" : "https://www.altamiq.com/blog/co-sell-across-three-clouds-how-to-track-acv-opportunities-and-credit-without-losing-the-thread",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60,
      "url" : "/hs/hsstatic/content_shared_assets/static-1.4092/img/default-amp-logo.png",
      "width" : 60
    },
    "name" : "blog"
  }
}
```