How a Tiny Team Ships Like a Big One · The Partner Track
One click from opportunity to ACE
Co-sell mostly dies at the swivel chair: a rep re-typing a CRM opportunity into Partner Central. We wired ACE submission into the deal view, with a human deciding what AWS gets to see.
An alliance manager at one of our customers described their co-sell process to us last year, and almost none of what they described was selling. A rep closes a deal review, opens Partner Central in another tab, and re-types the opportunity: customer name, use case, stage, dollar value, all of it already sitting in the CRM they just left. About twenty minutes per opportunity when nothing goes wrong, and something usually goes wrong, because ACE validates fields the CRM never made anyone fill in. The rep gets a rejection, shrugs, and goes back to selling. The alliance manager gets a co-sell pipeline that represents whichever deals survived the re-typing.
That twenty minutes is where co-sell dies. Not in strategy decks, not in QBRs: in the swivel chair between two systems that both already know the deal.
What we built
ACE has an API; most partners just never connect it to anything. In Aithon, the deal view carries a co-sell panel. When a deal looks co-sell-worthy (the eligibility signal comes from the same scoring that drives everything else in Aithon, and we'll describe that in a later post), the panel alerts you and offers the submission: every ACE field pre-filled from deal data, validated against ACE's rules before anything is sent, with the gaps highlighted for a human to fill. One click hands the opportunity to AWS; the ACE status and the AWS account team's responses sync back onto the deal, where the rep actually lives.
The panel doesn't wait to be asked, either. Once a deal is linked to AWS, Aithon checks it against the AWS funding programs and tells the rep which ones this deal could draw cash or credits from, what is currently blocking each one, and the date by which it has to be submitted. That is usually the first a rep hears that AWS might pay for the proof of concept on the deal they are working, and it changes the conversation with the customer more than any co-sell report does. The same checks that catch ACE rejections catch these: "advance the deal to Business Validation", "attach a marketplace offer", stated as the one thing to do next rather than a program guide to go read.
The validation step matters more than the pre-fill. ACE rejections arrive slowly and read like tax forms; catching the problem while the human is still looking at the deal turns a next-week correction into a ten-second one. Most of our first-attempt submissions used to bounce for exactly the reasons AWS documents, and let's face it, who's got time for reading those (well ... we do, and ... we did). Now the bounce happens in the panel, instantly, before AWS ever sees the draft.
Real numbers
- ~20 minutes per manual ACE submission before, under 2 in the panel, and the rep never leaves the deal.
- 39 co-sell-eligible opportunities ≈ $3.2M in potential funding surfaced in one customer's pipeline - the volume that makes per-deal minutes matter.
- Every submission validated pre-send; the first-attempt rejection loop against ACE effectively disappeared.
- One tab. The number of systems a rep touches to co-sell. It used to be three.
Where the humans sit
Submitting to ACE shares deal information with AWS, and that is a business decision, not a data-sync detail. So the click is the gate: nothing goes to AWS without a named human choosing it, deal by deal, and seeing exactly which fields will be shared before they confirm. Role permissions decide who can hold that gate. The machine's job ends at a fully prepared, validated draft; the judgment about what AWS should know stays with someone accountable for the account.
Steal this
Even without buying anything: use the dang API. ACE has one, and typing into Partner Central by hand is a choice, not a requirement. Map your CRM fields to the ACE schema once, write the validation as code so rejections happen before submission, and put a single explicit approval step between "prepared" and "sent". If your reps co-sell more than a few deals a quarter, the twenty minutes you remove per deal is the difference between a co-sell pipeline that reflects your business and one that reflects your reps' patience.
Next on this track: what all this feeds into - why co-sell is a data problem long before it's a sales problem.
This post is part of the partner track of How a Tiny Team Ships Like a Big One, a series on how six builders run a production AI company. Building at Aithon - if this is how you want to work, talk to us.