---
name: co-selling
description: Research partner signals and build detailed co-sell plans for hyperscaler sellers, product sellers going through hyperscalers or SaaS and AI platform ecosystems, and named customer accounts. Includes partner discovery, marketplace routes, committed-spend eligibility, seller engagement, and joint execution.
license: MIT
---

# Co-Selling

An AI-guided partner-led sales skill by Yousuf Imran, Mangosteen Studio.

Help a seller turn a potential partnership into a specific customer opportunity with a reason for both companies to act, clear responsibilities, and a credible path to customer value. Support both directions equally: a partner selling our product, and us selling theirs. In a reciprocal relationship, evaluate each direction separately; one viable motion does not prove the other.

Invoke with `$co-selling` or say “Run Co-Selling with [partner] for [product or account].” This workflow also works when pasted into another capable assistant.

## Start from the actual decision

Reuse information already supplied. First identify the user's seat and starting point. Do not assume the user already knows which partner to work with. If unclear, ask: “Are you selling from inside a hyperscaler, selling a product with or through a hyperscaler, or building a co-sell plan for a specific customer company?”

| Starting point | Central question | Primary output |
|---|---|---|
| **Hyperscaler seller → partner ecosystem** | Which partners can help my territory or customers, and how do I get the right ones engaged? | Detailed co-sell plan with partner signals, shortlist, marketplace economics, and activation through delivery |
| **Product seller → hyperscaler or platform partner** | Why would this platform's sellers help sell our product, and how do we work an opportunity together? | Detailed co-sell plan with platform signals, field engagement, customer benefits, and transaction through delivery |
| **Named customer → co-sell plan** | For this company, which combination of sellers and partners can solve the problem and advance the sale? | Account-specific Co-Sell Brief and joint action plan |

Read the selected path in [references/entry-paths.md](https://greenfield.tools/skills/co-selling/references/entry-paths.md). The third path is an account-level lens and can follow either of the first two; retain the user's seat when switching to it. Confirm whether a named company is the user's employer, a prospective partner, or the end customer if context does not establish that. A plan for recruiting a partner company and a plan for selling into a customer company are different deliverables.

For both seller paths, the default final output is a detailed, evidence-backed co-sell plan, not just a shortlist or strategy summary. Include a short executive decision followed by the operational detail in [references/co-sell-brief.md](https://greenfield.tools/skills/co-selling/references/co-sell-brief.md). Shorten only when the user requests a quick assessment or narrower deliverable. Lack of evidence calls for explicit gaps and validation work, not invented detail.

## Research the distribution path and partner signals

Read [references/distribution-and-marketplaces.md](https://greenfield.tools/skills/co-selling/references/distribution-and-marketplaces.md) to choose and verify the route. Prioritize AWS, Microsoft, and Google Cloud as the initial hyperscaler set for this workflow, not as an asserted market-share ranking. Consider Salesforce and relevant SaaS, data, and AI infrastructure ecosystems when their customer footprint and capabilities fit. Respect the user's chosen partner; assess its route and constraints before suggesting alternatives. Treat services companies primarily as access, implementation, operation, and solution partners unless an actual resale or procurement arrangement is established.

Separate the company whose field sellers create access from the marketplace that processes the transaction and the platform on which the product runs. They may be three different parties. Explain the path from customer need to seller participation to purchase, activation, adoption, and renewal.

Read [references/partner-signals.md](https://greenfield.tools/skills/co-selling/references/partner-signals.md) and perform the signal research before choosing plays or finalizing either seller plan. Signals from the hyperscaler or chosen platform partner are a required part of the plan, alongside customer and product-partner signals. Show how each consequential signal changes partner selection, seller messaging, timing, or the next action. Public ecosystem enthusiasm alone cannot establish account-team interest.

For other partner-led situations, retain the general workflow: identify our company and product, the partner and its offer if known, and the sales direction. Then establish whether the user is choosing partners, activating a relationship, or working a named deal.

Ask the next question that changes the decision, normally one at a time during discovery. Do not force a full interview when the user has provided enough material or requested a quick assessment. Build a working brief as evidence arrives. Keep moving with labeled gaps where they do not prevent useful work.

Choose the appropriate scope:

- **Partner fit:** Evaluate a candidate or compare a shortlist. Deliver a fit assessment, disqualifiers, and a small validation experiment.
- **Partner activation:** There is a relationship but little selling activity. Identify the field sellers, incentives, first accounts, enablement, and a bounded pilot.
- **Joint account plan:** Match a partner's demonstrated access and capabilities to specific customer needs. Prioritize a few actionable accounts.
- **Live deal:** Resolve the customer case, relationship ownership, sales choreography, commercial route, and next customer commitment.

Do not require a partner program to pursue one deal. Do not invent named accounts when none are available; start with an account-selection hypothesis and the evidence needed to test it.

## Establish the motion and roles

Classify the motion by what each company actually does. These can overlap:

| Motion | Selling arrangement | Question to resolve |
|---|---|---|
| Referral | One company introduces a buyer; the other sells and contracts | What makes an introduction qualified, accepted, and attributable? |
| Joint selling | Both contribute to the sales process; contracts may be separate | Who leads the customer interaction and each decision? |
| Resale / distribution | A company sells another supplier's offer through its commercial channel | Who quotes, contracts, bills, renews, and supports it? |
| Services-led | An adviser, agency, or integrator recommends or delivers the product | What delivery work and customer outcome justify involvement? |
| Embedded / OEM | The product becomes part of another company's offer | What packaging, technical, support, and commercial dependencies exist? |
| Marketplace-assisted | A marketplace provides a transaction route | Does it change procurement, and who actually creates demand? |

Record explicitly: product supplier, relationship owner, opportunity lead, contracting entity, delivery owner, support owner, and renewal owner. Mark unconfirmed roles as proposed. A partner badge, integration, listing, or shared customer logo is not evidence of an active co-sell relationship.

For direction-specific questions and commercial mechanics, read [references/motion-playbook.md](https://greenfield.tools/skills/co-selling/references/motion-playbook.md) only for the relevant motion.

## 1. Prove the customer reason

Start with the customer's problem, buyer, trigger, and desired outcome. Explain why involving this partner improves access, confidence, implementation, purchasing, or results for this particular customer.

Distinguish a combined solution from two adjacent products. Identify dependencies and gaps: what is available today, what has been tested together, what requires services, and what is merely proposed. Consider whether a direct sale or another route would serve the customer better.

Produce a short joint value hypothesis:

> For [customer / segment] facing [specific problem], [our contribution] and [partner contribution] can produce [outcome], because [mechanism and evidence]. We still need to validate [critical assumption].

Use customer language. Do not substitute “strategic alignment” for a business case or imply measured results where only a hypothesis exists.

## 2. Prove the partner and seller reason

Assess three separate cases:

- **Our company:** Revenue or retention opportunity, access gained, cost to sell and serve, and what control or margin we give up.
- **Partner company:** Product revenue, service revenue, retention, differentiation, or customer outcome that makes the effort worthwhile.
- **Individual seller:** Quota or compensation treatment, relevance to their current accounts, effort required, credit risk, and what they can do next.

Find the partner sponsor, field seller, and delivery or technical counterpart. An alliance leader's interest does not establish field commitment. Look for actions: account nomination, an accepted introduction, joint discovery, a technical resource, or an agreed customer next step.

Assess fit using evidence, without arbitrary weighted scores: customer overlap, complementary capability, current access, seller motivation, delivery capacity, economics, and competing interests. Treat missing information as unknown rather than a failed criterion. Name the weakest assumption and how to test it.

## 3. Map accounts and relationships

For each candidate account, capture:

| Account / entity | Customer need and timing | Our relationship | Partner relationship and last meaningful interaction | Joint play | Evidence / confidence | Next action and owner |
|---|---|---|---|---|---|---|

Distinguish customer, prospect, active opportunity, and former customer on each side. Record relationship strength through demonstrated access, not just contact presence. A LinkedIn connection or CRM match is a possible path, not permission or willingness to introduce.

Prioritize accounts where customer need, relevant partner access, and a willing seller intersect. A large overlap list alone is not a pipeline. For a live deal, map the customer champion, decision maker, technical evaluator, procurement, and blockers to an owner on our side or the partner's side.

Use only account data available for this purpose. Prepare a minimal shareable subset; do not assume permission to disclose a whole CRM export, customer pricing, or internal notes to a partner.

## 4. Agree how the sale works

Complete the marketplace mechanics and customer-benefit checks in [references/distribution-and-marketplaces.md](https://greenfield.tools/skills/co-selling/references/distribution-and-marketplaces.md) whenever the proposed route involves a marketplace or commitment benefit. Verify the exact offer, customer agreement, purchasing entity, billing route, timing, and eligibility. Distinguish spend commitment drawdown, prepaid balances, promotional credits, product usage credits, and seller quota credit. Never translate all of these into “burn your credits.”

Draft a working agreement for the opportunity, sized to the motion:

- Who introduces whom, and what context the introducer will provide.
- Who leads discovery, the demo, technical validation, proposal, negotiation, and close.
- Which offer each party owns, who can approve pricing, and who contracts and bills.
- How opportunity registration, exclusivity, territory, existing direct opportunities, competing partners, and sales credit are handled when relevant.
- Who implements, handles escalation, supports the customer, and owns renewal or expansion.
- Which customer information can be shared, with whom, and through what channel.

Use owner, action, dependency, target date, and evidence of completion for the joint action plan. Label partner and customer actions **proposed** until accepted. Avoid competing outreach and duplicated discovery. Keep a single coordinated next customer step.

Unknown commercial terms should generate a validation action, not an invented commission, discount, entitlement, or legal conclusion. Consult current official program documentation when the task depends on a named partner program's rules; record the source and date. Planning terms are proposals, not executed agreements.

## 5. Make the partner able to sell

Build the minimum enablement needed for the next opportunity:

- Buyer, problem, and trigger the seller should recognize.
- A brief explanation of the joint offer and the partner's role.
- Qualification questions and clear reasons to disqualify.
- Current proof, product boundaries, and demo or technical support path.
- A precise handoff: required context, receiving owner, and proposed response expectation.
- Answers to likely customer and partner objections, including overlap with existing offers.

For activation, prefer working through a real account with a seller over treating training attendance as success. When messaging is requested, draft the appropriate partner recruitment note, seller activation ask, introduction, or joint customer follow-up. Tie it to evidence and a small concrete ask. Do not imply the partner has endorsed an unapproved draft.

## 6. Decide whether to advance

Use a recommendation with reasons and missing evidence:

- **PURSUE:** There is a credible customer problem, useful partner contribution, willing owners, and a workable next step. Identify unresolved commercial dependencies before commitments are made.
- **VALIDATE:** The opportunity is plausible but access, motivation, capability, or economics needs testing. Specify the smallest experiment and what would change the decision.
- **PARK:** Timing or capacity prevents progress. Give a specific reopening trigger.
- **DECLINE:** Evidence shows a material conflict, poor customer fit, unworkable economics, or unsupported delivery promises. Explain the decisive reason.

Also state the next action's readiness: ready to approach the partner, ready for a joint customer meeting, or ready for a commercial proposal. These require different evidence; do not treat a promising partner as a qualified deal.

For a pilot, define a scope, named owners, review date, success evidence, and stop or redesign condition. Agree numerical targets from the situation; do not present arbitrary pipeline targets as benchmarks. Track progression from nominated accounts to accepted introductions, discovery, qualified opportunities, wins, and successful delivery. Include time and cost where known.

Distinguish partner-sourced from partner-influenced opportunities using explicit working definitions. Count each opportunity once in total pipeline even if both labels apply. Bookings, collected revenue, gross margin, and partner payouts are different measures.

## Deliver the Co-Sell Brief

Use [references/co-sell-brief.md](https://greenfield.tools/skills/co-selling/references/co-sell-brief.md) for the detailed plan by default in both seller paths. Write substantive findings, decisions, and actions in each relevant section; do not deliver an empty template. For an explicitly quick request, deliver only the relevant sections. Preserve unknowns instead of filling the template with invented detail.

Every completed assessment should leave the user with:

1. A recommendation and the evidence behind it.
2. A defined sales direction and named or proposed responsibilities.
3. The customer case and both companies' incentives, including the field seller's.
4. The best account or validation experiment and its next action.
5. The material risks, evidence gaps, and who can resolve them.

## Evidence and execution discipline

Attribute consequential facts to the user, a supplied artifact, or a source with a date. Distinguish confirmed facts, inferences with their basis, and unknowns. Preserve conflicting evidence rather than silently choosing a convenient version. Never invent partner status, customer consent, relationships, certifications, integrations, commercial terms, or product capabilities.

Use available research and connected systems when useful, without implying access to absent tools. This skill produces plans and drafts. Sending messages, sharing account data, registering deals, changing CRM records, or making commercial commitments requires authorization for that action; respect authorization already given.

Before finalizing, check that platform/partner signals are sourced and connected to actions, distribution and transaction routes are explicit, customer benefits have their eligibility conditions, and both companies' field seller incentives are addressed. Confirm the recommended next step follows from the evidence, sales directions have not been conflated, and every immediate action has an owner or an explicit ownership gap. State remaining limitations plainly. If interrupted, save the current decision, evidence, unresolved questions, and next action so discovery can resume without repetition.


---
## Packaged resources

Full skill folder: https://greenfield.tools/downloads/co-selling.zip
Reference guides are included below. For scripts, templates and example inputs, download and extract the ZIP; preserve its folder structure. `<skill-dir>` means that extracted folder.


---
## Reference: co-sell-brief.md

# Detailed Co-Sell Plan

Default deliverable for both the hyperscaler seller and the product seller going through a hyperscaler or chosen platform. Populate with findings and decisions, not instructions telling the user to do all the analysis. Begin with a concise executive decision, then provide operational detail. Scale account and partner counts to scope; retain depth for the selected plays. A named customer plan uses the same structure at account level.

Do not omit important sections merely because evidence is unavailable. State what is unknown, the decision it affects, and the exact verification action and owner. Omit sections that are genuinely inapplicable with a brief reason. If the user requests a quick scan, narrow accordingly.

## 1. Executive decision and scope

- Recommendation: PURSUE / VALIDATE / PARK / DECLINE, with decisive evidence.
- User's company, role, product, territory/segment, and desired outcome.
- Starting path and selected hyperscaler/platform/distribution partner.
- Customer entity or account-selection scope; time horizon.
- Best joint play, strongest supporting signal, biggest risk, and immediate next move.
- Readiness for partner engagement, customer meeting, and commercial proposal stated separately.

## 2. Distribution strategy

Explain why the selected route fits the customer footprint, product, access, and economics. Respect a user-selected platform; show concerns and alternatives without silently replacing it.

| Route | Customer/product fit | Field access | Technical fit | Transaction readiness | Potential benefit and conditions | Effort/conflict | Decision |
|---|---|---|---|---|---|---|---|

Map relationship channel, supplier, hosting platform, marketplace/reseller, contracting/billing entities, and delivery/support owners. Identify where parties differ and what that changes. For a chosen route, compare only material alternatives such as direct sale, alternate marketplace, or channel private offer.

## 3. Platform and partner signal intelligence

Use the ledger from partner-signals.md: source, event/effective date, checked date, fact/inference status, relevance, counterevidence, and action. Cover the chosen platform's strategy, applicable program/commercial signals, partner capabilities and willingness, and customer/account-team signals.

Explain each priority signal through this chain: observed fact → customer/use-case fit → partner contribution → field seller benefit → precise ask. Include negative evidence and what would change the recommendation. Distinguish current, expired, inferred, and internal-only information.

## 4. Partner selection and ecosystem coverage

For a hyperscaler seller, provide the researched candidate set, justified shortlist, capability coverage, and activation priority. For a product seller, map the platform's account and specialist teams plus any complementary partners needed. For a named account, distinguish incumbent, candidate, recommended, and committed parties.

| Partner/team | Specific contribution | Evidence and customer access | Field counterpart | Capacity/status | Conflict or gap | Priority and next validation |
|---|---|---|---|---|---|---|

Explain why each recommended participant is needed and why relevant alternatives were deprioritized. Do not insert an SI or reseller merely to make the ecosystem map look complete.

## 5. Prioritized customers and buying triggers

| Customer/entity | Problem and trigger | Current footprint | Our access | Partner access and evidence | Buyer/stage | Joint play | Priority reason | Next action/owner |
|---|---|---|---|---|---|---|---|---|

If no accounts are available, provide a concrete selection profile and validation plan, not invented company matches. Separate relationship overlap from confirmed buyer interest and qualified opportunities.

## 6. Joint solution and customer value

For each priority play, describe the problem, buyer, current alternative, our capability, each partner's contribution, and expected outcome with proof. Explain any claimed gap in the platform's native offer using current evidence.

Include deployment/integration dependencies, data and security requirements material to the purchase, implementation effort, limitations, and acceptance criteria. Label unmeasured outcomes as hypotheses. State whether the customer would still want the solution without the marketplace benefit.

## 7. Incentives for each company and seller

| Party | Business objective | Individual seller benefit and evidence | Work/cost taken on | Commitment demonstrated | Ask or gap |
|---|---|---|---|---|---|

For a hyperscaler seller, include customer outcomes, relevant workload/adoption contribution, actual applicable seller incentives, and the product partner's reason to invest. For a product seller, include platform-specific relevance, what we will do to make the seller's work easier, our economics, and the customer's purchasing reason. Separate alliance sponsorship from field execution.

## 8. Stakeholder and access plan

Map the customer champion, economic buyer, technical evaluator, procurement/FinOps owner, and blockers. Map our AE/SE, the platform AE/specialist/partner contact, transaction support, and delivery counterparts as relevant.

| Person or role gap | Organization | Responsibility/influence | Evidence of relationship | Internal owner | Approach and proposed ask |
|---|---|---|---|---|---|

Identify the best credible introduction path and who can authorize or carry it. Do not interpret contact data as willingness to introduce.

## 9. Marketplace and program readiness

| Requirement | Current evidence/status | Applies to which offer/customer/route | Gap | Owner and next step |
|---|---|---|---|---|

Cover applicable program participation, co-sell eligibility, offer/listing status, technical requirements, geographic availability, buyer purchasing account, acceptance permissions, and any registration or referral workflow. Distinguish required prerequisites from optional incentives. Cite current official sources and confirm customer-specific conditions.

## 10. Customer benefits and commitment analysis

Populate the benefit ledger from distribution-and-marketplaces.md. Assess simplified billing, committed-spend drawdown, usable balances or credits, procurement steps saved, accountability, and solution value independently. For each, state confirmed/conditional/unavailable/unknown, supporting evidence, and exact language the seller can use.

Record the actual commitment or credit instrument, agreement period, remaining amount, other forecast spend, eligible product charges, rate/cap, purchase and recognition timing, and verification owner. Show calculations when supported; otherwise supply the missing-input model. Compare marketplace versus direct purchase and keep cash cost, commitment contribution, and potential savings separate.

## 11. Offer, procurement, and transaction execution

Describe the selected flow from proposal to acceptance, billing, entitlement, activation, and benefit verification. Include public/private/channel offer as applicable, contracting party, price authority, term, payment schedule, buyer account/entity, procurement/security/legal steps still needed, and who verifies charges count as expected.

| Step | Owner | Required input/dependency | Target date | Completion evidence | Confirmed/proposed |
|---|---|---|---|---|---|

Address deal registration, sales credit, existing direct opportunities, channel conflicts, renewals, and permitted account-data sharing. For a submission-based benefit, include the actual submission and validation process and deadlines. Do not promise approval before the provider's required validation.

## 12. Field engagement and seller enablement

Provide two substantive internal talk tracks as part of the plan: our case to the chosen partner/platform seller, and the customer-facing joint value explanation. These are planning/enablement copy, not sent outreach.

Include the relevant signal, customer/use case, why this partner, proof, work we own, help requested, and next step. Equip the seller with discovery questions, qualification/disqualification criteria, demo support, handoff requirements, and responses to objections about native overlap, existing partners, procurement, unsupported credit claims, and delivery accountability.

Draft emails or messages when requested; do not make communication drafting a prerequisite for completing the plan.

## 13. Joint action plan and customer milestones

| Workstream/action | Account/play | Our owner | Partner owner | Customer counterpart | Dependency | Target date | Evidence of progress | Accepted/proposed |
|---|---|---|---|---|---|---|---|---|

Connect partner validation and seller engagement to discovery, technical proof, customer decision, procurement, close, and adoption. Choose a single coordinated next customer step. Name ownership gaps instead of assigning unaccepted obligations as commitments.

## 14. 30/60/90-day execution and first-week focus

Adapt to the actual sales cycle and time horizon. Detail near-term validation and activation, subsequent customer/opportunity execution, and adoption or expansion milestones where realistic. Do not forecast a close by day 90 merely to fill a schedule.

For the first week, identify the highest-impact actions, owners, resources, dependencies, and outputs. Include a proposed review cadence, decision makers, and escalation path. Pilot success and stop/redesign conditions should be explicit and evidence-based.

## 15. Delivery, support, and renewal

Define implementation scope, acceptance criteria, responsible teams, support/SLA boundaries, escalation lead, adoption measures, renewal owner, and expansion conditions. If the plan promises one accountable owner, identify the scope and evidence supporting that claim. Separate consolidated invoicing from operational accountability.

## 16. Economics and measurement

Show seller economics using known costs and revenue, with fee/payout assumptions and sensitivities. Define partner-sourced and influenced labels and count an opportunity once in total pipeline. Track qualified partner engagement, introductions, discovery, qualified opportunities, wins, activation/adoption, cycle time, and realized economics as relevant. Label baselines and targets as known, proposed, or unavailable.

Track actual commitment recognition or credit application separately from product bookings and workload consumption. Include a benefit-verification owner after purchase, not just a predicted benefit before close.

## 17. Risks, disproof, and alternative actions

| Risk/counter-signal | Evidence | Consequence | Owner | Mitigation or validation | Stop/reconsider trigger |
|---|---|---|---|---|---|

Include material customer-fit, native competition, relationship, incentive, technical, delivery, procurement, eligibility, and economics risks. Explain what would make direct purchase or another partner better. Do not bury evidence that contradicts the recommended route.

## 18. Sources, open decisions, and next move

Provide the source index with checked dates, conflicting or unverified claims, and a short list of decisions the user needs to resolve. Each critical gap needs a verification action and owner or role. End with the single most useful next move and distinguish a completed plan from a validated partnership or qualified customer deal.


---
## Reference: distribution-and-marketplaces.md

# Distribution routes and marketplace mechanics

This is a research and operating guide, not a promise of eligibility. Provider examples below were checked on 2026-09-07. Recheck current official documentation and relevant customer terms when running a plan; names, conditions, rates, caps, and transaction flows can change. Public rules do not establish a particular customer's eligibility.

## Select the route

Start with customer footprint, problem fit, seller access, technical compatibility, economics, and purchasing preference. Use AWS, Microsoft, and Google Cloud as the initial hyperscaler research set when no platform is selected. Broaden where relevant; this is workflow prioritization, not a researched market-size ranking.

| Distribution family | Role to investigate | Questions that distinguish the route |
|---|---|---|
| AWS, Microsoft, Google Cloud | Account teams, ecosystem partners, marketplace procurement, cloud workload adoption | Who creates demand; what qualifies for co-sell and commitment treatment; which offer and buyer account transact? |
| Salesforce and other large SaaS ecosystems | Installed-base access, workflow extensions, marketplace discovery and potentially transactions | Is this a directory, transactable offer, private offer, or direct vendor purchase; does any common billing or commitment benefit actually exist? |
| Data and AI platforms, including Snowflake and Databricks | Data/app distribution, technical integrations, platform sales relationships, provider-specific commercial programs | Is the product listed and eligible; who collects payment; is a benefit automatic, enrolled, or validated after purchase? |
| AI infrastructure ecosystems, such as NVIDIA and relevant model, inference, or GPU platforms | Validated solution relationships, workload demand, OEM/channel arrangements, technical and field collaboration | Is there a usable distribution and seller-engagement route at all; where does the transaction occur? Do not assume every ecosystem has a marketplace |
| Services companies, SIs, consultancies, MSPs | Buyer access, solution design, implementation, operation, and sometimes resale | What is their actual commercial role? Do not treat a services company as a hyperscaler-like distribution platform without evidence |

A services firm can recommend or carry a product, but the default here is to assess it as a solution and delivery participant. Investigate selling through it only when that arrangement is requested or evidenced.

Keep separate in every plan: **relationship channel → product supplier → hosting platform → transaction marketplace/reseller → contracting/billing entities → implementation/support owners**. One deal can involve several ecosystems. Do not count the same revenue twice or promise benefits from multiple programs without confirming compatibility.

## Provider starting points

These concise snapshots identify mechanics to investigate. They are not a universal eligibility checklist.

### AWS

AWS's co-sell resources describe ACE opportunity collaboration and ISV Accelerate. Program participation and an engaged account team are separate facts. Research the applicable program, partner status, and joint opportunity workflow. [AWS co-sell](https://aws.amazon.com/partners/co-sell-with-aws/), [ISV Accelerate](https://aws.amazon.com/partners/programs/isv-accelerate/).

Private offers support negotiated purchasing through AWS Marketplace; identify the buyer account and actual invoice/payment schedule. Verify any committed-spend treatment against the customer's agreement and current offer eligibility rather than hardcoding a generic rate. [Buyer private offers](https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers.html).

AWS promotional credit terms exclude Marketplace charges unless AWS authorizes otherwise. Do not equate a customer's promotional credit balance with available third-party software budget. [AWS promotional credit terms](https://aws.amazon.com/awscredits/).

### Microsoft

Distinguish co-sell-ready status, applicable Azure IP co-sell requirements, offer eligibility, and actual field engagement. Check which applies before promising access or incentives. [Co-sell requirements](https://learn.microsoft.com/en-us/partner-center/referrals/co-sell-requirements), [Opportunity management](https://learn.microsoft.com/en-us/partner-center/referrals/manage-co-sell-opportunities).

Microsoft documents MACC contribution for eligible offers, with conditions on deployment and the purchasing subscription/route. It distinguishes these purchases from Azure prepayment and excludes direct credit-card Marketplace checkout from MACC contribution. Verify the offer badge, customer agreement, Azure usage requirements, and checkout route. [MACC benefit](https://learn.microsoft.com/en-us/marketplace/azure-consumption-commitment-benefit).

### Google Cloud

Investigate the current partner program and Cloud Marketplace participation separately from account-team commitment. [Partner program](https://partners.cloud.google.com/), [Marketplace selling](https://cloud.google.com/marketplace/sell).

Google's commitment policy ties qualifying purchases to deployment, commitment periods, and applicable drawdown rules. The reviewed policy has a cumulative 25% cap; reseller purchases require specific association with the customer and have exclusions. Installment timing can affect when amounts count. Recheck the policy and linked rates/exclusions for the actual purchase. [Commitment policy](https://cloud.google.com/terms/marketplace/commit-policy), [Rates and exclusions](https://docs.cloud.google.com/marketplace/docs/commit-drawdown). The policy was retrieved; the linked rates page was not retrievable in the initial research, so no rate or exclusion list is asserted here.

### Salesforce / AppExchange ecosystem

Salesforce's reviewed partner page presents AgentExchange as a unified marketplace including AppExchange apps and advertises private offers with billing and provisioning features. Its Checkout documentation also describes a Stripe-connected purchase path. Identify the actual listing and transaction method rather than treating all listings alike. Neither source establishes blanket hyperscaler-like committed-spend drawdown. [Salesforce partners](https://www.salesforce.com/partners/), [Checkout FAQ](https://help.salesforce.com/s/articleView?id=000389622&language=en_US&type=1).

### Snowflake

Snowflake documents Marketplace Capacity Drawdown for enrolled customers with qualifying committed-capacity contracts, subject to availability and program conditions. Investigate enrollment, eligible products, remaining allocation, and billing. Keep Snowflake capacity separate from the customer's underlying hyperscaler agreement. [Capacity drawdown](https://docs.snowflake.com/en/collaboration/marketplace-capacity-drawdown).

### Databricks

The reviewed documentation describes a Universal Commit drawdown program for eligible partner products, capped at 10%. Its guide describes payment to the partner directly or through a cloud marketplace, then invoice submission, partner validation, and Databricks approval. This is materially different from assuming checkout instantly draws down a balance. Check dates, active usage, remaining cap, submission deadlines, and treatment of prepaid commitments. Eligibility is not guaranteed until validation. [Marketplace overview](https://docs.databricks.com/aws/en/marketplace), [Invoice submission guide](https://docs.databricks.com/aws/en/assets/files/marketplace-purchase-partner-products-34d350e3f4e8e36a6fc15ae912a8d334.pdf).

### Other AI infrastructure and SaaS partners

Use the selected provider's official partner resources to determine the real technical, field, and transaction paths. [NVIDIA partner resources](https://www.nvidia.com/en-us/about-nvidia/partners/) is a discovery starting point, not evidence of marketplace billing or commitment benefits. Apply the same research to another provider only when relevant to the product and customers. Do not infer a commercial benefit from an integration badge or ecosystem membership.

## Explain the system from listing to renewal

For the selected route, describe the actual flow and what remains unverified:

1. **Discover and qualify:** Listing or partner discovery; customer problem and product fit; field seller involvement.
2. **Establish readiness:** Required program/offer status, technical integration, region, buyer eligibility, and actual co-sell process.
3. **Structure the offer:** Public versus private offer, seller-direct versus channel offer, scope, term, price, payment schedule, renewal, and who approves each.
4. **Approve and accept:** Correct purchasing entity, tenant/account/subscription, marketplace permissions, procurement controls, negotiated terms, security review, and authorized acceptor.
5. **Bill and recognize benefits:** Invoicing entity and schedule, currency/tax handling, eligible charges, credit/commitment rules, cap, timing, validation/submission steps, and owner checking the result.
6. **Activate and deliver:** Entitlements, vendor registration if required, deployment, customer success criteria, and implementation handoff.
7. **Support and renew:** Escalation path, SLA owner, usage/adoption reporting, renewal owner, and revalidation of terms or benefits at renewal.

Produce the sequence as an account-specific checklist with owners and dependencies. A marketplace route can simplify purchasing while leaving vendor terms, technical validation, or deployment work necessary.

## Customer-benefit qualification

Translate the customer's phrase “credits” into the actual instrument before making a claim:

| Instrument | What to establish |
|---|---|
| Spend commitment | Contractual spending obligation, eligible spend, period, remaining obligation, marketplace allowance, and recognition timing |
| Prepaid balance / committed capacity | Whether money is already paid, eligible products, allocation, depletion and renewal treatment |
| Promotional / startup / migration credit | Award terms, service exclusions, expiry, applicable account, and specific authorization if needed |
| Product consumption units | Where units can be redeemed; do not assume they buy another vendor's product |
| Seller quota credit | Internal compensation/attribution rules; unrelated to the customer's payment balance |

Create a benefit ledger for every plan:

| Proposed benefit | Mechanism | Evidence and customer-specific conditions | Status: confirmed / conditional / unavailable / unknown | Approved wording or validation action |
|---|---|---|---|---|
| Simplified billing | Purchase uses the customer's established billing route | Correct entity, invoice arrangement, payer account, schedule and services included | | |
| Commitment drawdown | Eligible charges count toward an existing obligation | Agreement, offer, deployment, period, rate, remaining cap, and verification owner | | |
| Usable prepaid funds or credits | Specific program permits eligible charges to use the balance | Instrument and terms, remaining amount, exclusions, expiry | | |
| Clear accountability | A named party owns an agreed delivery/support scope | Contract or accepted operating agreement, SLA and escalation ownership | | |
| Faster purchasing | Existing process removes identified steps | Customer procurement confirmation; remaining reviews still identified | | |
| Better solution value | Specialized product closes a real customer gap | Product proof, success metric, implementation costs, alternatives | | |

One bill does not establish one contract, one vendor, or one accountable support party. Use “one accountable owner” only for the scope actually owned. Do not claim that marketplace presence removes security/legal review or guarantees lower prices.

For the product seller, explain the customer outcome first, then a verified or conditional purchasing benefit: “This solves [need]. If this offer and purchasing account qualify under your agreement, the eligible amount can count toward your existing commitment.”

For the hyperscaler seller, explain the specialist contribution, why it fits the customer's environment, and any verified purchasing benefit: “This partner addresses [validated gap] within the proposed solution; we can validate the eligible purchase against your existing agreement.” Link seller/platform benefit to demonstrated adoption, account success, or applicable incentives. Do not promise all third-party spend becomes cloud workload consumption.

## Quantify without calling drawdown free money

Collect price and term, product/services/cloud cost split, forecast platform spend without this deal, commitment period and remaining amount, remaining marketplace allowance, applicable rate, payment/recognition dates, and any separately approved incentive. Compare direct and marketplace routes, including fees, discounts, implementation, support, administrative effort, and cash timing.

For a simple single-period spend-commitment model, after eligibility is verified:

- Eligible contribution = eligible recognized purchase amount × applicable drawdown rate, bounded by remaining applicable allowance and remaining commitment.
- Forecast shortfall without the purchase = max(0, remaining commitment − forecast other eligible spend).
- Potential shortfall reduction = min(eligible contribution, forecast shortfall without the purchase).

Use provider-specific period, rate, and cap mechanics rather than forcing complex contracts into this model. Missing inputs remain unknown. A commitment reduction is not a cash discount; financial savings require a supported counterfactual, including actual shortfall consequences and whether the customer would buy the product anyway. Do not double count product spend, native cloud usage, avoided shortfall, prepaid capacity, and incentives. A separate prepaid-capacity or credit model may be needed.

Even an eligible purchase may have little commitment-management benefit if the customer already expects to meet its commitment. Lead with the customer outcome, not pressure to consume funds.


---
## Reference: entry-paths.md

# Three entry paths

Use the section matching the user's starting point, then apply the shared customer case, incentives, ownership, evidence, and decision workflow in SKILL.md. These paths guide discovery and change the emphasis; they are not three mandatory stages. Both seller paths culminate in the detailed Co-Sell Plan in co-sell-brief.md, including partner signals, distribution mechanics, qualified customer benefits, economics, field engagement, and execution through delivery. Read partner-signals.md for signal research and distribution-and-marketplaces.md for route mechanics. Apply the product-seller path to a selected SaaS, data, or AI platform as well as a hyperscaler; use its actual program and commercial model.

## 1. Hyperscaler seller: discover and activate partners

Start with the seller's territory, segment, geography, customer priorities, and the commercial or adoption outcomes they own. Establish whether they are an account seller, specialist, or partner-facing seller. Do not assume their quota or credit rules.

### Discover the partners the work requires

Translate customer problems into needed capabilities before choosing logos. Consider software vendors, systems integrators, regional specialists, managed service providers, advisers, and transaction partners where relevant. Separate partners that create access, provide a product, deliver implementation, operate the solution, or facilitate purchasing.

Build candidates from available internal partner records, the user's account-team knowledge, current official partner directories, and first-party capability or customer evidence. If research access is unavailable, produce the search criteria and evidence gaps; do not fabricate a discovered shortlist. Do not limit discovery to partners already named by the user unless requested.

Compare candidates on:

- Relevant solution capability and supporting customer evidence.
- Industry and geographic fit, including delivery coverage.
- Verified relationship with the customer or target segment.
- Named field counterpart and willingness to work this opportunity.
- Technical and delivery capacity, with current availability still to confirm.
- Contribution to the customer's outcome and the hyperscaler's relevant objective.
- Conflicts with other partners, existing account commitments, or customer preferences.

A directory listing establishes only what that listing supports. It does not prove account access, current capacity, seller commitment, or superior fit. Distinguish a broad candidate list from a qualified shortlist.

### Turn discovery into coverage and activation

Use a matrix: **customer need / account cluster → required capability → candidate partner → evidence → field counterpart → gap → next validation action**. Recommend a manageable shortlist justified by the territory, rather than adding partners solely to maximize coverage counts.

For each priority partner, identify one account or use-case hypothesis, the appropriate partner seller, the hyperscaler account owner, their respective incentives, and the first joint action. Where multiple partners are needed, explain each one's distinct role and who coordinates delivery. Surface competitive alternatives without suggesting that rival partners exchange sensitive account or pricing information.

**Deliver:** a detailed Co-Sell Plan containing the partner shortlist and rationale, signal-to-action analysis, coverage gaps, account plays, marketplace and customer-benefit qualification, seller engagement, commercial mechanics, economics, joint action plan, and delivery/renewal responsibilities. Progress is demonstrated partner participation and customer movement, not the number of ecosystem meetings.

Example request: “I'm a hyperscaler AE covering manufacturers. Help me find the right software and implementation partners for my territory.”

## 2. Product seller: sell with or through a hyperscaler

Start with our product, target buyer, cloud architecture and dependencies, target hyperscaler, existing relationships, and any actual partner-program or marketplace status. Separate supplied status from independently verified facts.

Distinguish three questions:

1. **Customer case:** Why does this product help this customer, and why does the hyperscaler belong in the solution?
2. **Field seller case:** What account objective could our product help the hyperscaler seller achieve, what evidence supports that, and what effort are we asking them to make?
3. **Commercial route:** How will the customer purchase, and what program or transaction prerequisites actually apply?

Potential contributions such as cloud adoption, migration, workload growth, retention, or faster implementation are hypotheses until supported for this product and account. Show the mechanism. Do not invent consumption estimates, field compensation, program benefits, or quota credit. A product hosted on a cloud is not automatically a compelling seller proposition.

Map the account seller, relevant technical specialist, partner-facing contact, and transaction support role as needed. Identify names through available evidence; otherwise use role gaps. A partner-manager relationship does not replace access to the account team.

Assess readiness separately for technical fit, program participation, transaction readiness, and field engagement. A marketplace listing does not establish co-sell eligibility or an engaged seller. Selling through a marketplace does not necessarily mean the hyperscaler resells the product. Do not assume a purchase qualifies against customer cloud commitments, incentives, or funding.

When these details affect the recommended action, verify current requirements in official documentation for the named provider and record the date. Use authorized internal confirmation for account-specific eligibility and commercial treatment. Do not block early customer or partner discovery merely because an optional transaction route is not yet established.

Choose a first joint account or a concrete account-selection hypothesis. Prepare a field engagement brief: customer problem, product contribution, hyperscaler relevance, current deal evidence, work we own, exact help requested, and a proposed next customer step.

**Deliver:** a detailed Co-Sell Plan containing platform signal research, distribution choice, account/team map, customer and field seller value cases, offer and program readiness, marketplace transaction flow, benefit and commitment analysis, economics, joint execution, and delivery/renewal responsibilities. Keep program administration proportional to what that action requires.

Example request: “We sell a data product and want AWS sellers to work opportunities with us. Where do we start?”

## 3. Named customer: build the co-sell plan

Start with the exact customer entity, our seller's seat and offer, the customer problem and buying stage, existing cloud or vendor footprint if known, and current relationships. A named customer need not already have an active opportunity.

Map the ecosystem around this account: customer decision makers, our account team, any hyperscaler account team, incumbent software vendors, implementation or managed service partners, and procurement channel. Include only relevant parties; a hyperscaler is optional in this path.

Evaluate partners against this customer's needs and access, using the discovery method in Path 1 if needed. Distinguish incumbent, candidate, recommended, and committed partners. The largest partner or the strongest global alliance may not be the best local account fit.

Develop a specific joint play with the customer outcome, each party's contribution, evidence, technical dependencies, buyer access, purchasing route, and delivery responsibilities. If comparing alternative partner combinations, explain tradeoffs before choosing the proposed team.

Create one coordinated customer plan: who earns the introduction, leads discovery, proves the solution, handles each objection, proposes terms, and delivers after signature. Record the customer decision being sought and the evidence that will show progress. Do not substitute an internal partner meeting for a customer milestone.

**Deliver:** the Co-Sell Brief for the named customer, selected or proposed partner team and why, stakeholder map, joint action plan, and next customer commitment to seek. If evidence is thin, deliver an account discovery plan and explain what is needed before recommending a commercial push.

Example request: “Build a co-sell plan for Acme. We sell the application, their cloud team is involved, and we need an implementation partner.”


---
## Reference: motion-playbook.md

# Direction and motion playbook

Read the sections relevant to the selected motion. Use these as decision prompts, not a mandatory questionnaire.

## A partner sells our product

- What do their customers already buy from them, and where does our product solve a problem they encounter?
- Is their contribution introduction, sales execution, transaction, implementation, or several of these?
- Why would their seller make room for this offer? Confirm compensation or credit treatment; do not infer it from company-level economics.
- Can they qualify and explain the product accurately? What do they need us to own?
- Who responds to their first referral? What context is sufficient to accept or decline it?
- What makes them fear being bypassed, losing account control, or inheriting support work? Define an appropriate handoff and communication plan.
- Are resale rights, pricing authority, delivery capacity, and support obligations established where needed?

The immediate deliverable is a partner-ready play: customer signal, opening problem, qualifying questions, proof, disqualifiers, our support, and the first named account or test.

## We sell a partner's product

- What customer need does their product address that our current offer cannot satisfy?
- Why is carrying their product better for this customer than referring elsewhere or declining the work?
- What have we verified about capabilities, implementation, security requirements, and support?
- Who on our team will learn, position, and support the offer, and what do they stop doing to make time?
- Are we referring, reselling, delivering services, or bundling? Which obligations and customer promises do we take on?
- Can we get supplier help during discovery, demos, technical evaluation, escalation, and renewal?
- Do the economics still work after enablement, sales engineering, delivery, support, and collection costs?
- Where could the offer compete with our own product, confuse our position, or put customer trust at risk?

The immediate deliverable is an internal go/no-go case plus a customer qualification and supplier handoff plan. A commission alone is not a customer reason.

## Joint or reciprocal selling

Define a separate opportunity hypothesis for each direction, even when a shared sponsor coordinates both. Do not promise equal lead volume or reciprocal introductions without evidence and agreement. For one combined customer deal, distinguish each product's scope, dependencies, price authority, and contracting route.

Choose a customer-facing lead and a coordinated discovery agenda. Establish whether the customer wants one accountable delivery party or accepts separate suppliers. Identify what happens if one part of the solution is delayed or not purchased.

## Commercial mechanics by motion

| Motion | Mechanics to resolve before the relevant commitment |
|---|---|
| Referral | Qualified referral definition, acceptance, existing-account exclusions, attribution window, payout trigger and basis, follow-up ownership |
| Resale | Right to sell, territory, quote authority, supplier price, resale price, discounts, billing, collections, cancellations, renewal, support |
| Services-led | Product versus services scope, implementation capacity, handoff, acceptance, escalation, ongoing maintenance |
| Embedded / OEM | Packaging, licensing, deployment dependencies, version compatibility, branding, support chain, roadmap assumptions |
| Marketplace | Current eligibility and transaction rules, listing or private-offer status, fees, procurement requirements, seller involvement |

Use the actual agreement or current official documentation for program-specific claims. Missing terms are dependencies. This table is an operating checklist, not contract language.

## Economics without false precision

Use supplied numbers and make the calculation basis explicit. If inputs are missing, provide the model with blanks or clearly labeled hypothetical scenarios.

- Supplier contribution from a referred sale = collected product revenue minus referral payout, incremental delivery/support cost, and incremental selling cost.
- Reseller contribution = collected resale revenue minus supplier cost and incremental selling/delivery/support costs.
- Services contribution = services revenue minus delivery cost; keep product resale contribution separate before combining them.

State the period, currency, one-time versus recurring amounts, payout basis, and whether figures are bookings or collections. Check for double counting where supplied costs already include a payout or support charge. These are planning estimates, not audited accounting measures. Never infer quotas or commission policies from margin calculations.

## When a partnership stalls

| Observed behavior | Hypothesis to test | Useful next experiment |
|---|---|---|
| Sponsor attends meetings; sellers do nothing | No seller incentive or account relevance | Work through one seller's real account and confirm credit treatment |
| Lots of account overlap; few introductions | Relationship access or customer permission is weak | Validate one relationship and ask the owner whether a specific introduction is appropriate |
| Introductions arrive; no discovery follows | Poor qualification or unclear follow-up ownership | Review recent referrals and agree an acceptance/handoff process |
| Discovery happens; opportunities stall | Weak customer case, technical gap, or commercial friction | Identify the customer's missing decision and assign the relevant owner |
| Product sells; partner disengages | Delivery burden, weak economics, or bypass concerns | Review one deal's effort, realized economics, and relationship handling |

Treat these as hypotheses. Diagnose from actual examples before recommending training, incentives, or program changes.


---
## Reference: partner-signals.md

# Partner signals: evidence to sales action

Use for every detailed seller plan. Research the hyperscaler or chosen platform, candidate product partners, and target customers. The aim is to identify where a partner's priorities meet a customer problem and a seller willing to act.

## Collect the operating context first

Reuse the user's materials. Establish the seller's seat, territory, product and use case, preferred distribution partner, current relationships, marketplace listings, open opportunities, and known customer purchasing routes. Ask for missing internal context incrementally; do not demand confidential contracts or entire account exports when a relevant clause or confirmed field is sufficient.

For partner choice, compare only relevant alternatives and explain the criteria. For a partner already selected by the user, research its incentives and constraints in depth. A weak fit should result in an explicit concern or validation plan, not silently changing their chosen platform.

## Research four layers

| Layer | Signals to investigate | Source and interpretation |
|---|---|---|
| Platform strategy | Prioritized workloads, industries, migrations, AI initiatives, launches, regional investments, ecosystem calls | Official announcements, product docs, earnings statements, partner resources; shows a strategic hypothesis, not account-team demand |
| Program and commercial | Changes to co-sell rules, eligible offers, field incentives, funding, private offers, procurement routes, commitment treatment | Current official program docs plus authorized program/account confirmation; identify who and what actually qualifies |
| Partner capability and willingness | Relevant releases, integrations, customer proof, practice investments, implementation capacity, sales coverage, accepted account nominations | First-party evidence and direct partner context; separate capability from willingness and capacity |
| Customer and field execution | Current project, buying trigger, renewal, cloud agreement period, budget owner, procurement preference, seller request, solution gap, accepted introduction | Supplied account notes and appropriate direct confirmation; strongest basis for a named account play |

Also research counter-signals: a new native feature that weakens our differentiation, a competing partner entrenched in the account, unsupported deployment geography, partner delivery constraints, expired incentives, exhausted commitment allowance, customer preference for direct purchasing, or recent rejected introductions.

A missing native feature is a hypothesis until checked against current product documentation and the customer's requirements. Do not assert “the hyperscaler does not have this” simply because a partner sells it.

## Source and prioritize

Use current first-party sources for provider rules. Use partner directories and marketplaces for candidate discovery, then verify claims on the underlying provider, product, and customer pages. Capture the event/effective date separately from publication date and research date. Recent publishing does not make an old announcement a new trigger.

Prioritize signals by relevance to the customer problem, evidence specificity, recency appropriate to the event, and actionability. A general keynote theme is context. A relevant account seller asking for a partner solution is a stronger actionable signal. Do not inflate confidence through multiple articles repeating one announcement.

For every consequential signal, record:

| ID | Organization and signal | Event / effective date | Source and checked date | Fact / inference / unknown | Customer and seller relevance | Counterevidence / expiry | Action and owner |
|---|---|---|---|---|---|---|---|

Then build the reasoning chain: **observed signal → customer/use-case match → partner contribution → platform and field seller benefit → precise ask → evidence needed next**. Label inference at the step where it occurs.

## Turn signals into both sellers' plans

For the hyperscaler seller:

- Translate platform priorities and account needs into capabilities to source from partners.
- Use candidate evidence to select the product and delivery partners for each play.
- Explain how the proposed solution helps the customer and the seller's verified objectives.
- Identify the counterpart, enablement gap, customer opportunity, and ask for partner participation.

For the product seller:

- Identify which platform priorities the product can substantively support.
- Establish the workload or business outcome mechanism, rather than merely saying the product runs on the platform.
- Find the account seller and specialist for the relevant customer/use case, plus the alliance contact that can help navigate.
- Make a specific contribution and ask: discovery participation, technical validation, an appropriate introduction, or procurement confirmation.

Example, explicitly hypothetical: a platform announces an industry AI initiative. This is a reason to investigate whether our verified governance capability helps that initiative. It is not proof of funding or a willing account seller. The next move is to validate the customer requirement and ask the relevant specialist to assess a named use case.

## Research completion

The plan should identify the strongest actionable signals, the relevant negative signals, and which parts remain internal-only or unverified. If none are found, say so and design discovery; do not decorate the plan with unrelated news. No fixed signal count substitutes for coverage of the actual decision.

Attach a source index and a refresh trigger for time-sensitive claims. A change to program eligibility, offer status, contract period, or customer procurement route should trigger revalidation before the corresponding benefit is used in a proposal.
