Suger is now Fours. Read the announcement

Co-Sell With Purpose

Co-selling is not a lead source. It's visibility, earned one deal at a time. Which deals to share, what to put in the submission, and how to work the AWS rep once you get one.

Juston Salcido
Head of GTM, Fours · Nov 1, 2026

Why “co-sell with purpose”? Because it’s how I do everything in life. In golf, when I hit the range, I’m not just swinging at a bunch of balls; I’m picking distances, picking clubs, and hitting shots. Pool or billiards is the bigger one for me. On the break, I measure speed, hit the cue ball in the same exact spot, hit the head ball in the same exact spot, and try to make the cue ball land in the same spot every time. Every shot after that, I’m practicing with purpose so what I learn is repeatable. Co-selling should work the same way.

When I get on the phone with sales teams as the cloud coach, one of the main questions I hear is: “We’re trying to create a business case. What kind of leads could we expect from AWS in our first year?”

If I’m being totally honest, the answer is minimal, if not zero. This isn’t a “we join, we sign up, we share a couple ops, and AWS is going to see us and love us and share things back” situation. This is a give, maybe you’ll get something back relationship. That’s the honest truth.

So this post isn’t AI-driven or backed by any analyst reports. It’s just my perspective on what co-selling is and what it’s not, based on conversations I’ve had with customers. I’ll use AWS as my example, but the same ideas apply to any cloud provider.

What co-selling is (and what it’s not)

Co-selling, to me, is that you want to collaborate with AWS because you have a deal and you think there are benefits on both sides to be involved. And you need some type of help or assistance from AWS. That’s the baseline.

When a customer tells me they “co-sell with AWS”, it usually means they’ve shared opportunities. That’s what I think people get the most wrong. They think co-selling is “we just share opportunities with AWS, and if they like it, they’re going to engage with us.” Sharing is just the start. Most people share an opportunity and wait to see what happens.

Yes, you want to share the correct opportunities. But you want to share with purpose. Strategically look at what you have going on and share the ones that matter the most, the ones that are going to bring the biggest value.

This can go the other way, too. You might have a Strategic Collaboration Agreement (SCA) with AWS where you have to hit a number of shared opportunities, maybe 500 a year. If you don’t have thousands of opportunities in your pipeline, you don’t have the luxury to cherry-pick. So you’ll share some that aren’t of great value. They still have meaningful power, because it’s an AWS customer using your services that run on AWS.

And co-selling is not a lead source. It may take 6 months before you receive something back. It may take 2 years. That all depends on your solution and its uniqueness. What’s your differentiator? Do you have something nobody else has? Maybe it’s new to market, and neither customers nor AWS have heard about it yet.

In my opinion, leads are generated from visibility. You work with AWS reps on a customer. You solve their problem. Everything goes live. AWS sees it end to end. You keep repeating that with different reps, maybe 10, 20, or more. Then when those reps see a similar pain point with their other customers, they think of you. That’s where you might see something come back in the form of a lead.

Pick the right deals, at the right time

Which deals? When you’re trying to identify which ones you want to co-sell with, look at the AWS Marketplace engagement score. Fours builds on it with the Fours Predicted Engagement Score, which rates each account High, Medium, or Low. The highs and the mediums are going to be your best-case scenarios.

When do you submit? As early as possible. Once you’ve qualified the deal, you’ve got the customer, and you’re discussing next steps. Maybe that’s a demo. Maybe it’s a proof of concept (POC). You just can’t be trying to prospect the customer. You should be past that phase, where the customer has bought in, they’re seeing the value, and you’re talking about what comes next.

If you ask early, you can bring AWS in early. If you ask midway through, it’s still okay. And if you ask a little bit late, that’s still fine too. You’re not asking AWS to save the deal. You’re asking AWS to help speed up the close of this deal.

One thing to watch out for: don’t wait until a deal goes silent to bring in AWS. If your customer has stopped responding, AWS isn’t going to revive it for you. And you don’t want a rep’s first experience with you to be an 11th-hour fire drill.

Make the submission count

A lot of what happens after you share an opportunity should already be in the opportunity you shared. Your submission should give AWS the full picture. For example: “We have a $500,000 deal with this customer, set to close at the end of December. We’re working with their VP of Engineering. Our ask: do you know who the economic buyer for this type of solution is, or who in procurement we could work with to help speed up the close?”

That matters, because today AWS puts every opportunity into one of three co-sell motions:

MotionWho leadsWhat you get
AWS Field-engagedAn AWS seller co-sells with youA matched AWS sales team, with AI agents in a supporting role
Agent-engagedYou, with agent supportAI agents help qualify and enrich the opportunity; it can move up to Field-engaged
Partner-ledYouNo AWS seller assigned; agents provide plays and insights, and updates are accepted immediately

The motion comes from your Opportunity Quality Score plus strategic importance. We don’t know the algorithm behind the score you get back. But we have an idea that the customer business problem, the next steps, and the title all reflect what’s going on. The more details you put in, the better off you’re going to be.

Is landing in Agent-engaged a mistake? This could go either way. Maybe you have an SCA where you have to submit 500 opps a year, and this is one you thought might be of value but might not. You’ve got to hit your numbers, so you submit it, and you might just get an agent assigned. Even then, the agent will give you next steps you can use to enhance your opportunity. Do that, and you have a chance of getting an AWS rep assigned.

Why AWS added agents in the first place. AWS had an influx problem. So many opportunities were being thrown over the fence, looking to get reps assigned and reached out to, and nothing had valuable details in it. So AWS introduced agents and scoring to make sure that what you submit deserves an AWS rep’s attention, versus you just throwing something over the fence and looking to get help. Getting an agent assigned isn’t a bad thing. It just means what you’ve submitted isn’t sufficient yet.

A common mistake: leaving out what isn’t in your CRM. This happens a lot. Your submission pulls from the opportunity your sales rep owns, and that record might be thin. The deal could be well past prospecting, in a technical or business validation, and still have very little written down. You can only share what you have. The real detail often lives outside Salesforce, in Gong recordings, Granola notes, and other meeting notes. If you’re not pulling that in, your submission might be pretty bare, and you may have to chase your rep to add more detail, which can be a blocker on its own.

Who owns the submission? It depends on where you are in your journey

  1. Starting off: You want it to be a combination of your alliance lead and your sales team, working together and learning how to do it. Maybe the alliance lead does the submissions, in tandem with the reps, and sets up the calls, bringing rep to rep: your sales rep and the AWS rep together.
  2. Scaling: You might give your sales reps access to the tool so they can submit their own opportunities. At the same time, the alliance lead has to make sure they’re flagging the right opportunities to them.
  3. Fully scaled: When you know how to co-sell and you’ve been doing it, you want this automated. Once a deal has been through prospecting, discovery, and business validation and moves into technical validation (or a committed stage, or whatever statuses you use), a system like Fours automatically submits it once it meets certain thresholds.

Won’t automation just share every deal, whether it has the details or not? Not if it’s done right. This is where AI-enhanced opportunity submissions come into play. And think beyond your CRM. Consider integrating all your data: Gong notes, Granola notes, videos, recordings, whatever you have. Use it to create the project title, the customer business problem, and the next steps from actual data before anything gets submitted.

Fours also has its own scoring system, so we can estimate what the Opportunity Quality Score will be based on the details going in. Set your threshold. I’d say 40 and above. In my experience, I’ve seen 40s get AWS reps assigned a lot of the time, but I’ve also seen 40s go to the agent. You could set it at 50, but is that too high? It’s a balancing act, and something you’ll have to try out. There’s no one-size-fits-all, because agents learn. As everyone submits better opportunities, the agents may get more advanced and want more, and scores might go down.

Have a specific ask

When AWS says you need a specific ask, remember: it’s a specific ask. “I need help with this deal” is not specific. “Deal support” is not specific. “We just want to co-sell” or “we just want to talk to you” is not specific.

If I go into a restaurant and say, “I want some food,” they’re going to hand me the menu and ask what I want. “I just want a burger.” Okay, do you want a cheeseburger? A bacon cheeseburger? What do you want on that burger? Same thing here. What do you need help with? Where can AWS provide value? You’re going to be taking 15 to 30 minutes of an AWS rep’s time, so you’d better have a good ask for them. What are you looking to accomplish in that meeting?

Where AWS comes into play can vary by stage and by what you sell. First, by stage:

  • Early on: Maybe you’re wondering if there’s any funding you could get for a proof of concept. Or you need to speak with somebody on the technical side of the AWS account team, because you’re unsure if there are any credits the customer could use to test it out.
  • Past the POC: The person you’re working with isn’t the economic buyer. They’re the user of the product. They’re bought in, they want to use it, it helps unlock something for them. Now you’re trying to move up the chain to somebody with buying power, and that’s your ask.
  • At procurement: The buyer said yes. It’s their solution and they have budget. But you’re working with a large enterprise and nobody knows who in procurement would typically use AWS Marketplace.

That last one deserves an example. Say you’ve seen a high AWS Marketplace engagement score. You asked your end user about Marketplace, and then the buyer with the buying authority, and they say, “I don’t think we use Marketplace.” That contradiction is a good sign. Reach out to AWS: “We’ve got this customer. They want to purchase. We asked about Marketplace and they said no, but we see high scoring. Can you help? Do you know who in procurement? Have they used Marketplace in the past? Is this scoring not accurate?” Ask them questions and get them on the phone. Right there, that’s good co-selling.

Your ask can also vary by your solution. If you’re selling SaaS, you’re probably not going to need much technical help from AWS. Your asks will lean toward finding the buyer, procurement, and Marketplace. But if your product is deployed in the customer’s own environment, like an on-prem or self-hosted product, you might need technical help: someone from the AWS technical team to validate the architecture, review the deployment, or help find credits to stand up a POC.

Know your better-together story

In your first calls with AWS reps, you’ll be explaining who you are, what you do, and your better-together story. That story should work as both a 2-minute elevator pitch and a detailed technical deep dive. Make sure you hit on all of these:

  1. The problem: What customer pain point are you solving for?
  2. Your solution: What does your offering plus AWS deliver together?
  3. The AWS services: Which specific AWS services are involved, and how? Are you using Amazon Bedrock? Amazon S3? AWS Lambda?
  4. The outcome: What measurable results did a customer achieve?
  5. The proof: Who has validated this? Customer case studies with logos work really well.
  6. The differentiator: Why can’t they get this anywhere else? Why can’t AWS deliver it?

The biggest part is backing it with a story with evidence. In the end, it’s all about how you combine it: what is your solution doing for the customer, how is AWS involved, and what is it solving for?

After you submit: where co-selling actually happens

Reach out, then follow up. Once your opportunity gets approved and, hopefully, an AWS rep is assigned on the other side, reach out to them. A lot of times, the first person assigned is a Partner Sales Manager (PSM), who is the gatekeeper to the account manager. Who reaches out? Your alliance leader might do that, the sales rep might do it themselves, or, if you’re smart, you’ve built an automated process that reaches out.

Here’s the other key thing: a lot of people reach out, but they don’t follow up. AWS reps get thousands of emails they have to sift through. When I was in the role, I’d send the initial email, wait until sometime the next week, and follow up again. Maybe a third time as well. If you get an out-of-office reply, set yourself a reminder to follow up when they’re back. But give it some time. If you follow up the day they get back, they’ll already have an inbox full of emails. Do it strategically.

If you’ve followed up three times with no response, it’s time to try another path. If you have a good ask and really need help, escalate to your Partner Development Manager (PDM) if you have one. A lot of partners don’t. If it’s really urgent, keep following up, but try a different angle or a different person on the account team.

Build visibility, not just one deal. Co-selling is about building visibility within the AWS account teams. Say financial services is your bread and butter and 60% of your opportunities are financial services customers. You’re going to keep working with a lot of the same reps. In those first couple of calls, you’ll explain the same things over and over. But later down the road, when those reps see an opportunity come in and they’ve already had success and a good working experience with your team, they’ll want to engage more. They know you’re easy to work with and you’ve earned their trust. They understand your solution and what it solves for. They can go back to their customer as the trusted advisor and say, “I’ve worked with this team. They have a great solution. You should work with them.”

Before the call ends, set next steps. Do they want to touch base once a month, or every couple of weeks? Learn more about them. Do they work in a specific industry, or cover a territory like the Northeast? See if they want to do some account planning or mapping with you to find mutual customers. This can be a huge win for everyone if you can get there. Have your account list handy, and also ask the rep which of their accounts you could help with. That way it’s a two-way conversation, not just you asking for intros.

Keep the opportunity updated. That’s a hard one if you’re doing it manually, because someone has to go in and update it. This is where Fours comes into play again, with automatic syncs that keep your opportunities up to date when things change.

Close the loop. If the deal goes closed-lost, follow up, thank them for their time, and let them know what happened. If you win, thank them again and send over a win wire. Win wires can be especially helpful in spreading the word for your business. The most impactful ones are concise, one to two paragraphs, and include:

  • Specific numbers on the results, like “our solution increased performance by 30%”
  • The AWS Marketplace contract value and deal length
  • The names of the AWS services involved
  • Your unique role in the win
  • How co-selling with AWS helped, and what assistance they provided

Vague statements like “improved performance” without supporting metrics are weak.

Measure what matters

If you can’t count on leads, what should you count on? You’re trying to build a successful revenue channel, and it takes time. You have to be able to explain that.

As you go, measure the deals you co-sell on, the ones that use Marketplace, or the ones that use both. Then measure the impact with three key metrics:

  • Sales cycle: Did those deals close faster?
  • Win rate: Did they have higher win rates?
  • Contract value: Did they have higher contract value?

Don’t forget renewals. From a co-selling perspective, renewals are more about Marketplace and less about co-selling, but they’re low-hanging fruit. Go to a rep and say, “We have this $500,000 contract we’re going to renew with our customer. It looks like they have a high AWS Marketplace engagement score, and we’re going to try to push it through Marketplace.” You’ll get their attention, because they benefit when you use Marketplace. I’ve seen this firsthand from both sides: AWS reps often come to partners about a renewal to see if they want to bring it to Marketplace. Going to them first only makes it easier and better.

What’s in it for the AWS rep? The benefits can change year over year, even month over month. Today, there is obviously quota retirement, a SaaS co-sell benefit, and a Marketplace benefit, sort of like a spiff based on the deal value and how long the deal is.

If the customer has already agreed and wants to use Marketplace, submit the opportunity for co-selling, because that’s how the reps get their benefit, and then transact through Marketplace. Then add a fourth metric: retention. Are renewals that went through Marketplace renewing quicker, larger, and more reliably the next year? The idea is that Marketplace renewals are stickier.

Co-sell with purpose

If you change one thing about how you co-sell starting tomorrow, make it this: co-sell with purpose. That’s my saying. Everything in life, do it with purpose. Practice with purpose. Co-sell with purpose.

Look back at how you’re doing it today and ask yourself:

  • Are you coming with specific asks?
  • Are you having engaging conversations with the reps?
  • Or are you just trying to get them to give you leads?

If you enjoyed this, I’d love to hear from you. If you hated it, I’d love to hear from you even more. Either way, reach out at [email protected].

Sources

Primary sources for the platform rules cited above. Last verified October 29, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure.

  • AWS Partner Central Sales Guide: Agentic Co-sell engagement — The three co-sell motions (AWS Field-engaged, Agent-engaged, Partner-led) and who leads each; that the motion comes from the Opportunity Quality Score plus strategic importance; that AWS does not publish the score's weights; that the agents qualify every opportunity on submission; and that Deal Support on its own does not count as a specific ask
  • Fours docs: Co-sell insights — Fours behaviour: the engagement score's High/Medium/Low ratings and its sources; the Fours Predicted Engagement Score; the AWS Marketplace Engagement Score; and the predicted Opportunity Quality Score with its 0–100 bands, where High is 40–49

Browse every post on the Fours Blog

Stay Updated

New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.

Follow Fours on LinkedIn