AE vs AM: Who Owns the Number After the Deal Closes

What Is the Difference Between an Account Executive and an Account Manager?

The account executive owns the decision to buy, and the account manager owns everything that happens after it. An AE runs a sales cycle. Discovery, qualification, business case, procurement, signature. The job ends at closed-won, and the scoreboard is new bookings.

An account manager inherits a live customer and carries the revenue attached to that customer forward. Renewal, expansion, price increases, product attach. The job has no natural end date, and the scoreboard is what happens to the revenue base over time.

The skills diverge sharply. An AE is measured on their ability to create urgency inside a decision that has not been made. An AM is measured on their ability to keep a decision that has already been made from being reversed, and to widen it. Companies that promote strong AEs into account management on the theory that selling is selling usually learn this the hard way.

How Do the Two Roles Compare Side by Side?

The AE is measured on a cycle that ends, and the AM is measured on a relationship that does not. That single difference drives the quota basis, the comp shape, and the metrics each role can move.

Where Should the Handoff From AE to AM Happen?

At a defined event, not a date on the calendar. Closed-won is the most common trigger and the weakest one. The contract is signed, but the customer has not gone live, the implementation plan exists only in the AE's notes, and the promises made during the cycle are still in the AE's head. Handing off at signature transfers a relationship without transferring the context that makes the relationship work.

A cleaner trigger is first value delivered. The AE stays accountable through onboarding, joins the transition call, and hands over a written record of what was promised, what was descoped, and which stakeholder actually drove the purchase. The AM starts with the account already producing something rather than starting with a problem.

Whatever trigger you choose, stamp it in the CRM. The retention forecast needs a defensible start date for every account, and "sometime after the deal closed" is not one.

Should Expansion Revenue Sit With the AE or the AM?

Give expansion to the AM when it needs a relationship, and to the AE when it needs a sale. More seats on an existing contract, a usage tier upgrade, a module that the current buyer already has budget authority over. That is account management work, and routing it to an AE inserts a stranger into a conversation the AM is already having.

A new business unit, a new geography, a new economic buyer who has never bought from you, a competitive evaluation running in parallel. That is a sales cycle wearing an expansion label, and an AM who has never run one will lose it politely.

The wrong split shows up in the numbers before anyone admits it. Expansion pipeline that sits in stage for two quarters usually means the deal needed a seller and got a relationship manager. Expansion that closes at a fraction of its entered value usually means nobody negotiated.

How Does the AE and AM Split Change the Revenue Forecast?

It forces three separate forecast lines, which is the correct number. New business, expansion, and renewal run on different mechanics and cannot share a model. New business depends on pipeline creation and win rate. Expansion depends on adoption inside a known base. Renewal depends on delivered outcomes and switching cost.

ORM models the base as a monthly waterfall: beginning ARR, churned customer ARR, churned product ARR, product decrease ARR, new customer ARR, new product ARR, increased product ARR, and ending ARR, where beginning ARR is always the prior month's ending ARR. That reconciliation is what makes net revenue retention diagnosable instead of decorative. When the number moves, the waterfall tells you which line moved it.

Roll all three motions into one seller-reported number and you get a forecast that cannot be debugged. It misses, and nobody can say whether the cause was thin new pipeline, stalled expansion, or a renewal that quietly contracted. See how to forecast revenue for how the lines fit together.

Which Signals Tell You an AM Is About to Lose an Account?

Support case volume, read at both extremes. ORM data on customer bases shows a pattern that surprises most account teams. Accounts with no support cases at all are at risk, because silence usually means nobody is using the product. Accounts with seven or more cases in the last year are also at risk, because something is not working. Accounts with three to five cases, typically lower severity, are the healthiest group. They are engaged, getting help, and staying.

An AM watching only for complaints will miss half the churn. The quiet account looks like the easy renewal right up until the renewal conversation reveals that the champion left and nobody logged in for six months.

Pair that signal with contract-level facts the AM controls: whether the original champion is still employed, whether the promised use case ever went live, and whether anyone outside the buying team has adopted. Those are answerable questions, and they belong in the account record before the renewal quarter starts.