Marketplace Cloud Co-Sell Finder
Find the accounts with heavy cloud spend and committed-spend budgets to draw down — the marketplace co-sell targets where a cloud-funded deal closes faster.
Accounts with cloud budget to draw down — the marketplace co-sell sweet spot
Heavy AWS spend + data-security intent.
Marketplace draws down the commit.
| Account | Cloud spend | Intent |
|---|---|---|
| Acme | High AWS | In-market |
| Beta | Very high AWS | Surging |
| Gamma | Moderate | In-market |
Overview
Find cloud-marketplace co-sell targets by identifying accounts with significant cloud spend (a proxy for committed-spend budget that marketplace purchases can draw down) and category intent — so the marketplace motion targets accounts that can buy through a cloud commitment they're already trying to spend.
Use cases
Sell where the budget's already committed
An account racing to use its cloud commitment is primed for a marketplace purchase. Cloud-spend data finds those accounts so the co-sell rides existing budget.
Faster cloud-funded closes
Marketplace deals that draw down committed spend skip much of the budget approval cycle — so targeting high-spend accounts shortens the sales cycle.
View workflow prompt
# Marketplace Cloud Co-Sell Finder
## Parameters
- `{{cloud_provider}}` *(required)* — The marketplace/cloud provider. Example: `AWS`
- `{{category}}` *(required)* — Your product category for intent. Example: `data security`
- `{{target_segment}}` *(required)* — Segment to scope the search. Example: `US enterprise, 5000+ employees`
## Purpose
Find {{target_segment}} accounts with heavy {{cloud_provider}} spend (a signal of committed-spend budget that marketplace purchases draw down) AND {{category}} intent — so the marketplace co-sell motion targets accounts where a cloud-funded deal closes faster.
## Process
1. **Cloud spend** — `company_cloud_spend` to find {{target_segment}} accounts with significant {{cloud_provider}} spend (the committed-spend signal).
2. **Confirm provider footprint** — `company_technographic` to confirm the {{cloud_provider}} relationship.
3. **Category intent** — `intent_category` for the {{category}} to keep in-market accounts.
4. **Scope** — `search_companies` to hold the {{target_segment}}.
5. **Rank** — by cloud-spend magnitude x category intent; the highest-spend in-market accounts have the most committed budget to draw down via marketplace.
## Output Format
Markdown with:
- `# Marketplace Co-Sell Targets — {{cloud_provider}}`
- `## High-Spend In-Market Accounts` (table: account | cloud spend band | category intent)
- `## Why Marketplace` (committed-spend draw-down rationale)
- `## Top Targets` (ranked)
- `## Citations`
## Quality Checklist
- Cloud spend cites `company_cloud_spend` (banded, modeled-vs-observed noted)
- Category intent cites `intent_category`
- The committed-spend rationale is stated, not assumed as fact for every account
- No invented exact spend figures