When someone joins me on a walk with Dusty and Tanner, I ask one question before we get out the door. “Which dog are you holding?”
We can both be paying attention. The second Tanner spots something interesting, I still want to know who has his leash.
I think about that when a team tells me a deal is “with Product.” Does that mean someone has agreed to make a decision? Does it mean the account owner sent a Slack message? And while Product is looking at it, who is talking to the customer?
A GTM handoff is complete when a receiving owner accepts responsibility with enough context to act and a clear deadline for responding. When a deal needs an exception, the team also needs to know who can make the decision and who communicates it.
During Reframe, we looked at whether the business had the skills and resources to support the growth choices it made. During Orchestrate, we work out how those people will operate together when an actual customer is waiting.
Walk one deal from partner recruitment to customer value
Say you’re launching a partner-led growth motion. Marketing creates the partner materials. Sales recruits the partners. Product answers technical questions. Customer Success handles implementation.
Then a partner brings in an opportunity and tells the customer an integration should be possible. The integration is outside the current offer. Who can commit product resources? Who calls the partner? Who gives the customer a realistic timeline?
I’d put the deal on a whiteboard. Years ago, I was trying to win more commercial work and asked a few teammates to help me “walk the dog.” I wrote up what I’d heard from builders and commercial designers, sketched a typical construction timeline, and showed the group who I thought we should contact and when. They filled in the gaps. Afterward I sent an email assigning the follow-up, including my own. The whiteboard helped us think it through. The email gave us a way to act on it.
For the partner deal, draw the route from recruitment through qualification, technical review, commercial approval, and implementation. Use roles someone actually fills. If you write “GTM team” above qualification, ask who opens the record on Monday morning and decides what happens next. Add a backup where an absence could leave a customer waiting.
Define what travels with the opportunity
A partner-submitted contact and a qualified opportunity belong at different points on that whiteboard. Decide what your team needs to know before it accepts a deal. Start with the customer problem, who’s involved in the buying decision, what the partner has promised, and any known technical requirements.
Give each transition five fields your team can actually use:
| Field | Example for a partner opportunity |
|---|---|
| Trigger | The partner submits a potential deal with a documented customer problem. |
| Required context | Account and contact details, buyer roles known so far, partner commitments, and technical requirements or open questions. |
| Receiving owner | The assigned sales owner checks for an existing account and reviews the submission. |
| Response time | The receiving owner responds within one business day, if that fits your team’s capacity. |
| Evidence of acceptance | The owner acknowledges the handoff in the CRM and records the next action and due date, or asks for specific missing information. |
Ask the receiving owner which of those fields they would actually use. A partner manager may know exactly what “integration discussed” means. The sales owner needs to know whether someone described a possibility, promised delivery, or named a date. Preserve that distinction in the record so the next person can have an informed conversation.
Subscribe for more resources on this topic here
Give exceptions a decision owner and a deadline
The same person can own the opportunity from the customer’s perspective while someone else has authority to approve an exception. Work that out before the exception appears.
For example, the assigned sales owner might coordinate the deal, a designated product leader might decide whether to commit engineering capacity, and the partner manager might relay the approved decision to the partner. The sales owner then updates the customer. Your team should name the roles it actually uses for integration requests, pricing exceptions, partner versus direct ownership, and capacity conflicts.
When the integration exceeds scope, send the decision-maker the customer impact, the resources required, the available options, and the date a decision is needed. That might mean deciding whether to use a supported workaround, scope additional work, or proceed with the current offer. Record the call, its owner, and who is communicating it. If the deadline slips, the deal owner should know exactly where to escalate and what update the customer is due in the meantime.
Put AI and management reviews to work on the same process
An AI agent can summarize the partner’s notes. A workflow can route the opportunity. A scoring model can suggest which opportunities should get attention first. Give each of those steps a human owner for cases where the signal is unclear. If the agent can’t tell what the partner promised, it should flag the missing context for review. If a workflow assigns the wrong territory, someone needs responsibility for fixing the rule and reassigning the deal.
Set a rhythm for decisions. Handle urgent customer commitments through the escalation route. For a weekly review, send status updates beforehand and bring the blocked deals, capacity conflicts, and decisions that need leadership. For every item you put on the agenda, ask what call the group can make and who can make it.
Pressure-test the route before you launch
Walk an ordinary opportunity through the process. Then try a messy one. The primary owner is on vacation, the account already exists in the CRM, and the partner promised an integration outside the offer. Have the team say, step by step, who checks the existing record, who takes ownership, who can approve an exception, and who calls the customer.
Mark each place where people have to guess. Before everyone leaves, assign the fixes and send a recap with names, decisions, and dates. Put your own name against the work you owe. That gives you an operating agreement you can use when you move from Orchestrate into Work the Plan.
This week, pick one growth motion and ask five people who owns its next critical decision. If you get five answers, pull up a whiteboard. Tanner is approaching an intersection, and both of us need to know which way we’re turning.