You are not running this deal alone
A solo-SA mental model is the fastest way to do this job badly. The role looks like an individual contributor role — your name is on the deal, you're the one in the meetings, you're the one the user asks for — but the work itself is fundamentally collaborative. The SAs who treat it that way are the ones who close the most and last the longest.
This chapter is about the people around you and how to work with them well: the AE, the broader opportunity team, the deal channel, and the systems where the deal actually lives.
The AE relationship
The relationship between the SA and the AE is the most consequential working relationship in the role. When it's good, the deal flows. When it's bad, the deal grinds, and the user feels it before either of you do.
What makes the relationship work is straightforward. You're working toward the same outcome, you have complementary roles, and you stay in close communication about both the deal and the relationship itself.
A few things that help.
Coordinate before every external meeting. Even five minutes. "What's the goal for this call? Who's leading what? What are you watching for?" It sounds obvious and most pairs skip it. The cost of skipping is meetings where the AE and SA accidentally step on each other, leave gaps, or send mixed signals to the user.
Debrief after every external meeting. Even briefer. "How do you read that? What surprised you? What do we do next?" The post-meeting read between SA and AE is often the most useful five minutes of the deal. You're each picking up signals the other missed. The user said something to one of you that didn't land the same way with the other. The technical question that seemed routine actually felt loaded. Debriefing surfaces those signals before they get lost.
Disagree privately, present unified externally. You and the AE will disagree sometimes. Maybe they want to push the deal harder than you think is wise. Maybe you want to surface a concern they think is overblown. Have those conversations between yourselves, before the next user meeting. Then walk into the meeting aligned. The user should never see you and the AE working out a disagreement in real time in front of them. That's a private conversation. The unified front in the meeting is a courtesy to the user — they're not interested in the seams of your internal coordination. Nobody at a restaurant wants to hear the kitchen arguing, either.
Build trust slowly and protect it carefully. When you're newly paired with an AE, neither of you knows yet whether the other is good. You'll figure it out over the first few deals. Be patient. Be generous with the AE in the meantime. Mistakes early in the relationship cost more than mistakes later, when there's a track record to weigh against them. The same applies in reverse — give the AE room to figure out who you are, what you do well, and how you work.
When something isn't working, say so directly. If the deal management isn't right, if you're getting brought into meetings too late, if the AE is making technical commitments without checking with you — say it, in private, with care. The pattern compounds if you don't address it. The conversation is uncomfortable but recovery is faster than letting the relationship slowly erode. Most AEs would rather hear it than not.
The AE is your partner. The deals you'll remember most fondly, twenty years from now, will mostly be remembered through the lens of who you ran them with.
The opportunity team
The AE and SA are the core, but there are usually more people around any given deal. The Customer Success person who'll own the relationship after close. The implementation lead. The legal counsel reviewing the contract. The product manager fielding questions about specific capabilities. The partner contact at a third-party who's part of the integration. The deal desk person reviewing pricing.
These people are collectively the opportunity team. They're not always formally organized — most companies don't have a clean "deal team" construct — but they're functionally a team because the deal needs all of them at the right moment.
Your job, as the SA, is to know who they are and to communicate with them deliberately.
Know who's involved. Make a list. For any meaningful deal, you should be able to name every person on your side who's touching the opportunity. The list will surprise you the first time you make it. There are usually more people than you'd expect, and some of them are hearing about the deal in fragments rather than getting a coherent picture.
Push relevant updates proactively. Don't wait for people to ask. If you've had a significant conversation with the user that affects the contract, the implementation plan, or the pricing, the relevant person on your side should hear about it the same day. The faster the right information moves through the team, the better the team's collective response is.
Pull people in at the right moment. A common pattern: the SA tries to handle everything alone, doesn't bring in the right SME at the right moment, and the deal stalls on a question they couldn't answer well. The fix is to develop a habit of asking, in real time during user calls, "is there a better person to answer this?" Then bring them in. Pulling in expertise isn't weakness; it's professionalism.
Don't drop balls between handoffs. The transitions between functions — from sales to delivery, from SA to CS, from one team to another — are where deals lose energy. The user feels it. The fix is to be deliberate about the transitions: a real handoff meeting, a written summary of context, an introduction that establishes the new person's authority and competence in the user's mind. We covered some of this in the scoping chapter; the principle is the same here.
The deal channel
If your company uses a chat tool with a per-deal channel — Slack, Teams, whatever — that channel is where most of the operational coordination happens. Be present in it.
A few habits that help.
Lurk attentively. Most messages in the deal channel don't require your direct response, but most of them are worth reading. The AE's update on a procurement conversation. The CS lead's comment on the implementation plan. The deal desk's note on pricing. All of this is context you'll want when you're in the next user meeting. Skimming the channel daily takes very little time and pays back consistently.
Communicate updates from your side. When you finish a meeting, drop a short summary in the channel — what was discussed, what's open, what's next. Three to five lines. The whole team picks it up and stays oriented. The summary is also a useful artifact for you, because it forces you to crystallize the meeting in your own head.
Tag people deliberately. When you need a specific person, tag them. When you don't, don't. The signal-to-noise ratio of the channel matters; over-tagging trains people to mute it.
Move important things out of channel. Some conversations don't belong in chat — sensitive commercial dynamics, hard feedback to a colleague, anything that needs to be preserved as a real document. Use chat for the operational coordination, but recognize when something needs to live somewhere more durable.
If your company doesn't have per-deal channels, the equivalent is whatever the coordination layer is — a shared document, a Slack DM group, an email thread. The principle is the same: there should be a place where the team is staying in sync, and you should be present and contributing to it.
Lurk in Salesforce and Jira
The other systems where the deal lives are the CRM and the issue tracker.
The CRM — Salesforce or whatever your company uses — has the deal record, the activity history, the AE's notes, the forecast, related contacts, and a long list of other things. Most SAs use it lightly, mostly to find a contact's email address, which is a bit like buying a sports car to drive to the mailbox. You can get more out of it.
Look at the activity log on the deal periodically. The AE has been having conversations you weren't part of. Some of those will be commercial conversations that affect the technical work — pricing pushback, contract terms that imply specific capabilities, a stakeholder you didn't know existed. Reading the activity is a way to stay informed without requiring the AE to brief you on everything.
Look at related deals if there are any. Sometimes the user has another opportunity in flight at your company — a different team, a different product, a different stage. Knowing about it changes how you should engage.
The issue tracker — Jira or equivalent — is where product engineering work lives. If the user has filed bugs or feature requests, those will be in there. Knowing what's open against the user, what's been resolved recently, and what the support history looks like is part of the picture. Especially for users who've been customers before, or for users who are evaluating an expansion.
The principle: be informed about your user across the systems where their relationship with your company is recorded. The AE knows the commercial side. The product team knows the engineering side. You're the one connecting both back to the user, and the connection works better when you're informed on both.
Strategize with your AE
Beyond the meeting-to-meeting coordination, there's a deeper kind of strategic work between AE and SA that doesn't happen automatically. It needs to be set up.
A useful pattern is a recurring deal-strategy conversation, separate from the operational ones. Once a week, or once every two weeks for active deals, sit down with the AE and talk about the deal at the strategic level. Where are we, really? What's the user's actual readiness? Who's deciding? What are the risks? What's our move? This is a different conversation than "did we send the proposal yet" or "what's on the agenda for tomorrow's call." It's a conversation about the shape of the deal, not its operations.
Most AE-SA pairs don't have this conversation regularly, and the deals where they do are visibly better-managed. The strategic read tends to be more accurate, the moves are more deliberate, and surprises are less common.
If you're not having this conversation with your AE, propose it. Thirty minutes a week is plenty. The investment compounds over the life of the deal.
The deal archive (or its equivalent)
Most companies have some form of internal historical record of past deals — closed-won, closed-lost, sometimes the post-mortems. Whatever your company calls it, get familiar with it.
Before you go deep into a new deal with a particular user, search the archive for any history. Did your company ever pitch them before? What happened? Who was on the deal? Were there technical concerns that came up? Were they evaluated against a specific competitor? Did they end up signing with someone else, and if so, why?
Most of the time the search comes up empty. When it doesn't, you're getting a head start that costs you nothing. Walking into a meeting already knowing that this user evaluated your platform two years ago and chose a competitor for a specific reason changes how you should approach the conversation. The user won't tell you that history if you don't ask. The archive will, and you can use it carefully — never quoting it back to the user directly, but informing your questions with the context.
Searching for users by name, by domain, by the AE who used to cover them, by industry — all of these can surface relevant context. The habit of starting any new deal by searching the archive is a small one, and almost no SA does it consistently. The ones who do are slightly better-prepared every time, and the slight better-preparedness compounds across hundreds of deals.
A note for builders
The team-sport dimension of the SA role doesn't happen automatically. It happens because the function is structured to make it happen.
The structural decisions matter. Pairing decisions — which AEs work with which SAs, how stable those pairings are, how they're rebalanced — shape the quality of every deal those pairs touch. Communication norms — what gets shared in deal channels, what gets debriefed, what's recorded in the CRM — shape how much context is available to anyone working a deal. Cross-functional access — whether SAs can pull in product or engineering or partner SMEs without friction — shapes how often the right expert ends up in the right call.
The function that gets these structural decisions right has SAs operating as a team even though they're individual contributors. The function that gets them wrong has individual SAs operating in their own bubbles, doing the best they can with what they happen to have access to. The deals close at different rates, and the difference is mostly invisible from the outside, but it's real.
The single most useful thing you can do as a leader is ask your SAs what's getting in the way of cross-functional collaboration, and then actually fix what they tell you. The list will be specific and unglamorous — "we don't have a clean way to pull in a product person on short notice", "the deal channel for this segment is too noisy and people stop reading it", "there's no easy way to find out what happened on a previous deal with this user". The fixes are usually small operational changes, not strategic ones. They compound.