Build an Account Management Process Your Team Can Run and Measure

An account management process is the repeatable way a business looks after existing customers: it transfers context after a sale, agrees what success means, coordinates delivery, checks evidence of progress, and decides what to change or discuss next. It gives each account an owner and a record of decisions. The process works when it helps the customer make progress and gives your team a reasoned next action, not when every box in a CRM is green.

In short: Use one repeatable loop for existing customers:

Plan and check progress: Handover → Account Plan → Delivery Check → Value Review. Give each step an owner, evidence and a next check.
Handle commercial decisions when they arise: Treat a renewal, scope change or growth opportunity as a separate decision, not an automatic final stage.
Review and act: Check commitments weekly, customer progress at milestones and monthly, and the process quarterly. Handle urgent issues when they happen.

What the process does—and what it does not

The goal is to make four things visible: what the customer is trying to accomplish, who is responsible for the next move, what evidence shows progress or a problem, and when a decision is due. A process should protect important handoffs and decisions without making a low-complexity account fill out the same plan as a multi-site customer.

An account plan is the current record for one account: goals, people, commitments, evidence and dates. The process is the repeatable method for creating, using and revising that record across accounts. It begins after acquisition sales hands over the customer.

The account manager coordinates the relationship and commercial decisions. Customer success may own adoption and outcomes; support may resolve tickets, delivery may perform the service, and finance may handle billing. One person can fill several roles in a smaller firm, but each responsibility still needs a named owner.

Salesforce describes account management as ongoing work with existing customers. HubSpot distinguishes customer-success and account-management responsibilities. Neither description requires a separate department for every role.

The stages of an account management process

Use the first four stages as an operating sequence, not as four meetings that every customer must attend. Commercial Decision is a conditional branch that can arise from any stage. The next route depends on what the check found; assigning a blocker is a recovery action, not proof that the account is ready for Value Review.

Stage	Goal	Accountable owner	Output	Next route or check
Handover	Transfer the sold scope and unresolved promises.	Named account owner; sales or founder supplies context.	Customer, scope, contacts, commitments and open questions in one record.	Once the owner can explain the promises and assign unknowns, create the Account Plan.
Account Plan	Agree a useful outcome and who will do what.	Account owner with an authorized customer contact and delivery lead as needed; obtain decision-maker approval for material changes.	Customer goals, evidence, owners, dates and communication preference.	With the objective and checkpoint confirmed, begin or resume Delivery Check.
Delivery Check	Test whether agreed work is happening and unblock it.	Delivery or customer-success owner performs work; account owner coordinates.	Work evidence, blockers and dated recovery actions.	Evidence ready → Value Review. Unresolved blocker → Account Plan/recovery, with an owner and recheck date.
Value Review	Compare the result with the customer's agreed goal.	Account owner brings evidence; customer confirms or corrects the interpretation.	Confirmed progress, unresolved outcome, or a revised plan.	Confirmed and continuing → Delivery Check. Shortfall or missing proof → Account Plan and a new check.
Commercial Decision — conditional	Handle a renewal, scope change or relevant growth option when it arises, even during delivery.	Account owner with commercial/finance support when needed.	Decision, terms, owner and next date—or a reason no decision currently applies.	Record the verified result, or keep the open dependency with its owner and real deadline.

Process map: Handover leads to Account Plan, Delivery Check and Value Review. A blocked or unverified outcome returns to Account Plan. A renewal, scope or growth event can trigger a separate Commercial Decision from any point.

The account owner carries context across stages. A blocked delivery or unverified outcome returns to the Account Plan; renewal and growth are conditional decisions, not automatic rewards for completed tasks.

If a contract question arrives during delivery, handle its real deadline now. The table is a logic for ownership and evidence, not permission to wait for a later stage. A customer can also stay in a repeating Delivery Check and Value Review loop without a formal renewal event.

Design the process for your company and accounts

First identify your post-sale promise: a continuing service, a project with milestones, a licensed product, or a mix. Then decide which evidence the customer and your team can actually obtain. Choose ownership, checks, communication and review depth from that job. The examples below are situations, not tiers or universal rules.

If this is true…	Change the process this way	Check that the change is useful
A small service account has one buyer, a clear recurring deliverable and stable scope.	One owner can keep a brief account record and combine the delivery and value discussion when the customer can confirm the result.	Can the owner show the agreed deliverable, customer response and next date without extra meetings?
Delivery spans sites, teams or several decision-makers.	Name a coordinating account owner and separate work owners. Record whose approval is needed for each outcome or change.	Does every open decision have the right stakeholder and a dated next step?
Onboarding or implementation is blocked.	Add a recovery checkpoint now: blocker, impact, work owner, proposed fix, customer decision and recheck date. Keep outcome status unknown until verified.	Did the blocker change, and has the customer agreed to any revised scope or date?
The contract is short or a notice/renewal event is near.	Bring the commercial decision into the current review and use the actual agreement's dates.	Is the correct decision-maker engaged before the applicable deadline?
Evidence is thin or the team lacks capacity for elaborate reporting.	Start with a few observable commitments and a direct customer check. Assign collection of missing evidence before adding a health score.	Can someone reproduce the status from the record, not from the owner's memory?

Turn those situations into three choices for each account:

Name the owners. Assign one coordinating owner, plus the people who do the work or approve a change.
Choose evidence and measures. Decide what would show the customer's goal moving. Track customer progress, missed work and decisions that need action.
Set the next check. Use the time the evidence takes to change and any real deadline to decide when the team checks internally and when the customer needs an update. Record these choices in the account plan.

For a small recurring service account, one owner might check the delivered report and the customer's response at an agreed monthly checkpoint.

For a multi-site implementation, delivery leads can report separate milestones to one account owner. The customer's authorized approver confirms the cross-site outcome. The stages stay the same; owners, evidence and review depth change. More contacts do not automatically mean more meetings, and contract value alone does not determine the cadence.

Measure progress without mistaking activity for value

Choose measures for three different questions: Are we doing the agreed work? Is the customer getting the agreed outcome? What commercial result followed? A meeting count can show workload. It cannot by itself show customer value, retention or growth. The compact set below is Alore's proposed operating definitions, not industry benchmarks. Keep only measures you can define, collect and act on for your business model.

Job	Measure and exact rule	Population, evidence and owner	Review and response
Execute commitments	Original-date on-time rate: commitments completed by their original agreed due date ÷ commitments originally due in the reporting week. Count each once when that week ends.	Unit: commitment for reviewed accounts. Dated record retains original and revised dates; account owner checks with work owners.	Weekly. Inspect misses and approved revisions together; completion says nothing about the customer's result.
Keep blockers actionable	Owned blocker share: open blockers with a named work owner and next decision/recheck date ÷ all open blockers at the review cutoff.	Unit: blocker across reviewed accounts. Account record or issue log; account owner.	Weekly and on a new serious blocker. Assign missing owners or dates; a high share does not mean blockers are resolved.
Verify customer progress	Outcome check: for each agreed milestone due in the period, record `achieved` (agreed evidence meets the goal), `not achieved` (evidence shows a shortfall), or `unknown` (evidence or required customer confirmation is missing). Count milestones by status.	Unit: due milestone; an account can have several. Customer note and agreed evidence; account and work owners.	At the milestone and monthly review. An unknown needs a proof request; a shortfall needs a revised plan. Silence is not success.
See commercial results	Commercial outcome by decision: classify each decision due in the period as agreed change, agreed no change, declined, lapsed, or open. The definitions and separate account/revenue facts follow this table.	Unit: decision ID due in the period, excluding accounts with no event. Agreement/decision log; commercial account owner.	At the actual event and monthly/quarterly review. Escalate open decisions before the real deadline; flag overdue ones. A forecast is not an agreement.

Freeze the on-time report at the end of the reporting week in which each commitment was originally due. A midweek operational check can assign help but does not close that week's rate. Keep the original due date even when a new date was approved; show how many commitments were rescheduled and why. A retrospective extension cannot erase a miss. Keep cancelled tasks in the log; exclude one only if the customer or authorized owner cancelled it before its original due date. A newly negotiated scope can create a new, linked commitment.

Use these reporting states consistently:

No eligible items: Show not applicable and a zero denominator, never 0%. This also excludes accounts with no commercial decision due from that decision population.
Unknown: An applicable customer outcome lacks agreed evidence or needed confirmation. Zero: The eligible population was checked and none of the counted events occurred. Keep missing evidence out of both claims.
Commercial decision identity: Give the event an ID and type when it opens. A renewal and scope change negotiated together use one ID; decisions with different owners or dates use two linked IDs. Count each eligible ID once at the period cutoff.
Commercial decision result: Agreed change and agreed no change require signed or otherwise verified terms. Declined is an explicit refusal of that decision, not necessarily account loss. Lapsed means its applicable window ended without agreement or explicit refusal. Open includes an overdue but still possible decision; record the real deadline and escalate it. Track account continuation, ending and verified scope/revenue movement separately so a reduced renewal is not forced into two labels.

A project business might track accepted milestones and signed repeat work instead of contract retention; a subscription business may add renewal retention with an explicit eligible cohort and period. HubSpot's retention-metric guide ties metric choice to the business model rather than one universal number; it does not validate Alore's custom rules above.

Set a target from the customer's commitments, the last comparable period and the team's capacity. If you have no baseline, run the measure long enough to learn its range before setting a numerical improvement target. Improving an on-time rate can indicate better execution; it does not prove the customer received value. Portfolio averages can hide one deteriorating account, so check both the aggregate and each account with a blocked outcome or imminent decision.

Run a review rhythm that changes a decision

The following is a starting rhythm for the internal team. It is not a requirement to meet every customer weekly or quarterly. Customer contact follows the agreed communication preference, a useful progress update, a decision request or a material change. Short contracts, onboarding and recovery can need a faster checkpoint; a stable simple account may need less ceremony. An urgent service, customer or contract event is handled when it happens.

When	Who and evidence	Decision and recorded output	Customer contact
Weekly internal check	Account owner and relevant work owner; due commitments, blockers, last customer response and next date in the account record.	Keep course, unblock, escalate or change a date with an owner. Log decision and recheck date.	Only if a promise, blocker, change or agreed update calls for it.
Monthly account review	Account owner, delivery/success and commercial partner as relevant; outcome evidence, customer feedback and open decisions.	Confirm progress, revise the plan, or ask the customer to validate an unknown. Update goals and next checkpoint.	Send a concise progress update or hold an agreed review with the right customer contact.
Quarterly process review	Leader plus account owners; account-level exceptions and comparable portfolio measures with clear populations.	Adjust ownership, capacity, process steps or measures; record the test and owner.	Strategic account review only where the customer has agreed it serves a purpose.
Event-driven check	The accountable owner and whoever can resolve a serious blocker, scope change, refusal or contract deadline; current evidence and agreement.	Act before the next routine meeting. Record the decision, responsibility, date and customer notification needed.	Communicate promptly when the event affects the customer or needs their decision.

Run each review in the same six moves: inspect the evidence → decide → assign an action → communicate to the right person → record the decision → recheck on a date. If there is no new action, record why the existing course still fits the evidence. A short meeting that leaves every issue ownerless is not an efficient review.

A customer progress update should name the agreed objective and period; what changed with evidence; completed and blocked commitments; decisions the customer needs to make; and the next actions, owners, dates and review point. An internal risk summary can also include forecast assumptions, capacity constraints and commercial options; keep those internal unless they are appropriate to share. The account owner writes both from the same dated record so a customer message cannot contradict the team plan.

Keep one account record that leads to the next action

The record can live in a CRM, shared workspace or document your team already uses. Its value is that a new owner can find the latest customer-agreed goal and decision without reconstructing it from email. A minimum record needs these fields:

Field	What to enter
Scope and people	What was sold, responsible account/work owners, customer contacts and decision-makers.
Customer goal	The outcome the customer agreed to and the evidence or statement that will count as progress.
Operating checkpoint and evidence	Current point in Handover, Account Plan, Delivery Check or Value Review; last verified result, source/date and explicit unknowns.
Open issue or commercial decision	Track blockers and any parallel Commercial Decision separately, with impact, resolver and actual deadline if any.
Next action and review	Action, owner, due date, who must be told, and date to check whether it worked.

For example, if a service customer says an onboarding handoff is incomplete, the record should say which deliverable is missing, who will recover it, what the customer must confirm and when the team will recheck. It should not say “at risk” and stop there. If the deliverable is finished but the customer has not confirmed that it solved the problem, record delivery complete and outcome unknown separately.

Put the process in place this week

Start with a few different accounts. Name each owner, reconstruct the handover, locate the current checkpoint and mark missing evidence. Assign confirmation or recovery work instead of claiming an account has passed a stage.
Use the next weekly review to decide. Give each open issue an evidence-based action, owner and recheck date.
Simplify after a month. Remove unused optional fields. Add a check only if it changed a decision; keep the goal, owner, evidence and next action in the record.

Common questions

Does every customer need four operating stages and a commercial branch?

Every account needs clear context, a goal, a way to check delivery and a way to judge progress. Commercial Decision is a conditional branch that applies when a renewal, scope change or relevant growth option exists; it can arise at any operating checkpoint. Smaller accounts may combine conversations without losing the distinct decisions or evidence.

Who owns the process if there is no account manager?

Name one coordinating owner, often the founder, service lead or customer-success lead. That person need not perform every task, but they must know the current plan, who owes the next action and which customer decision is pending.

What is the first metric to track?

Start with one measure tied to the failure you need to fix. If commitments go missing, track due actions and owners. If the team finishes tasks but cannot explain customer progress, use the Outcome Check statuses with agreed evidence. Add a commercial measure only where its eligible population and decision are clear.