Account-Based Ops: How to Build a Shared Tier 1 Account Dashboard for AE and CSM

Most companies have dashboards. AEs have their pipeline view. CSMs have their health score board. Revenue leaders have their CRO dashboard.

But when the VP Sales and VP CS sit down to review the 15 accounts that represent $3M in ARR (the ones where a single churn event would move NRR by a full percentage point), they're pulling from two separate systems, two different data models, and two views that don't agree on what "at risk" means.

The AE sees a healthy pipeline for the renewal. The CSM knows the champion hasn't logged in for 45 days. Neither person has the other's information before that review meeting. And the account that should have been flagged three weeks ago gets flagged in the room instead, when it's already harder to fix.

The Tier 1 joint dashboard is the operational fix. Not a reporting artifact. A coordination layer that gives AE and CSM shared visibility on the accounts that matter most, so action happens before the meeting rather than during it. The 8 shared dashboards that high-performing revenue teams run covers the broader dashboard ecosystem across marketing and sales; the Tier 1 account dashboard described here is the CS-extended layer that completes it at the post-sale seam.

---

The 8-Panel Tier-1 Dashboard Spec is a concrete joint visibility framework for AE-CSM coordination on high-value accounts. The eight panels (Account Identity, Health Score, Contract Status, Engagement Timeline, Open Items, Champion Map, Expansion Signals, and Risk Flags) each have a defined owner, a defined update cadence, and a defined use in the four-cadence review ritual (weekly independent update, bi-weekly team lead review, monthly VP review, quarterly QBR prep). The spec is designed to be implemented in whichever platform the account team already uses daily, not as a standalone tool.

---

Why Tier 1 Accounts Need Their Own View

Standard dashboards are built for volume. They're optimized to show patterns across a portfolio of 50, 100, or 500 accounts. They're good at identifying which decile of accounts is underperforming, which segments need attention, which CSMs are carrying too much load.

But Tier 1 accounts don't need pattern detection. They need depth. And they need it weekly, not quarterly.

Three things make Tier 1 operations different. McKinsey research on key account growth found that key accounts represent 30 to 50 percent of revenue and margin for many companies, and that the quality of AE-CS coordination on those accounts determines whether that revenue grows or stalls:

The cost of misalignment is asymmetric. Losing a $30K ARR account is a bad month. Losing a $300K ARR account is a board conversation. When AE and CSM aren't coordinating on high-value accounts, when the AE is planning an expansion pitch while the CSM is managing an active escalation with the same contact, the misalignment isn't just operationally inefficient. It's financially dangerous.

Standard dashboards optimize for the wrong signal. A health score dashboard that shows 87% of your accounts are green tells you something useful about your portfolio. It tells you nothing about whether one of your $500K accounts is about to churn because the champion changed roles last month. Tier 1 ops optimize for early warning on specific accounts, not statistical patterns across all accounts.

The relationship complexity at Tier 1 is higher. Larger accounts have more stakeholders, more complex use cases, more open commitments from the sales cycle, and more history to track. The data that AE and CSM each hold about a Tier 1 account is larger in volume and higher stakes than for a typical SMB account. Without a shared view, that complexity creates coordination failures.

Key Facts: Tier 1 Account Visibility and Revenue Impact

• The top 20% of accounts by ARR typically represent 60-70% of total revenue in mid-market B2B SaaS, per OpenView Partners' SaaS Benchmarks. NRR surprises in this tier are disproportionately expensive.
• Companies with joint AE-CSM visibility on Tier 1 accounts see 34% lower churn in that tier versus companies with siloed reporting, according to Gainsight's Customer Success Industry Benchmark.
• AEs who review health scores before renewal conversations close 22% more expansion deals than those who go in without CS data, per Forrester's Revenue Operations research.

Defining Tier 1: The Criteria That Drive Dashboard Inclusion

Tier 1 means different things at different companies. The criteria should be set by RevOps, approved by VP Sales and VP CS, and reviewed quarterly. But here's a practical starting framework for SMB to mid-market:

ARR threshold. Top 20% of accounts by annual contract value. In a company with 200 customers, that's 40 accounts. In a company with 500 customers, that's 100. Bain's key account management research shows that companies with tiered account segmentation and differentiated treatment plans consistently outperform those applying uniform coverage across their portfolio. The threshold isn't sacred. Adjust for your portfolio distribution, but the concept is that the dashboard covers the accounts where a churn event hurts materially.

Strategic tier. Accounts in a priority vertical you're targeting for expansion, accounts enrolled in a reference customer program, or accounts that are named in an ABM campaign. These accounts may be outside the top 20% by ARR today, but they represent strategic value that warrants weekly visibility.

Risk override. Accounts outside the normal Tier 1 ARR threshold that have been flagged at elevated churn risk. A $50K account with a health score in the bottom decile and an upcoming renewal in 60 days gets temporary Tier 1 designation until the risk is resolved. This category is set by the CSM and approved by the CS team lead. It's not an automatic flag, it's a judgment call. The joint at-risk account review is the recurring session where risk overrides get formally reviewed with both AE and CSM present.

What Tier 1 is not: every account. The moment the dashboard covers 40% of your portfolio, it stops being a Tier 1 dashboard and becomes a general monitoring tool. The point is depth on the accounts that matter most, not broad coverage.

The Eight Panels of a Joint Tier 1 Dashboard

Here's a concrete spec for what the dashboard shows. Each panel has an owner: the person responsible for keeping that section current.

Panel 1: Account identity. Company name, market segment, ARR, renewal date, AE owner, CSM owner. The basic facts that let both teams orient before they look at anything else. Owned by RevOps; updated automatically from CRM. If this panel is wrong, everything else is questionable.

Panel 2: Health score. The composite health score from the CS platform, including the deal-context layer described in Customer Health Scoring with Sales Context. This isn't just product usage. It incorporates deal-context risk factors (over-promise flags, ICP edge cases, champion stability) alongside engagement and adoption data. Owned by CSM; updated at least weekly.

Panel 3: Contract status. ARR, expansion potential based on current usage and stated use cases, renewal probability (CS estimate), and contract end date. AE and CSM both need this to coordinate on renewal timing and expansion conversations. Owned by RevOps (ARR, contract end date) and CSM (renewal probability, expansion potential). Updated monthly or when contract terms change.

Panel 4: Engagement timeline. Last AE touch (call, email, or meeting), last CSM touch, last customer-initiated contact, and next scheduled touchpoint for each. This is the early warning panel for relationship neglect. When a Tier 1 account has had no AE contact in 30 days and no customer-initiated contact in two weeks, that's a flag before the health score reflects it. Owned by both AE and CSM; updated automatically from logged activities in CRM and CS platform.

Panel 5: Open items. AE commitments still outstanding (features promised, introductions committed, follow-up documentation owed), CSM open tasks, and customer-reported blockers. This is the accountability panel. If an AE committed to an introduction to the product team six weeks ago and it's still open, the CSM needs to know. The customer knows, and it's affecting the relationship. Owned by AE (their commitments) and CSM (their tasks and customer-reported blockers). Updated weekly. Commitments that date from the sales cycle are typically captured in the deal context transfer to CS process. Panel 5 is where those commitments stay visible post-close.

Panel 6: Champion map. Primary champion, executive sponsor, known detractors, and last contact date for each person on the map. Including detractors is not optional. The accounts where a detractor has more influence than the champion are the ones that surprise you at renewal. Owned by both AE and CSM; AE updates before close, CSM updates post-close. This panel is co-maintained, which means it gets stale if neither team has a routine for it. Build the update into the weekly panel update ritual.

Panel 7: Expansion signals. Usage growth trends, seats added since onboarding, feature adoption versus committed use cases, and any explicit statements from the customer about expanding scope. This is the panel that converts CSM relationship data into AE pipeline opportunity. When a CSM sees usage growing in a part of the product that wasn't in the original deal, they update Panel 7. The AE sees it in the dashboard and books an expansion conversation. That sequence doesn't require a handoff meeting. It requires a shared dashboard. Owned by CSM; reviewed by AE weekly. The expansion ownership and upsell motion article covers who carries the expansion deal forward once Panel 7 signals a real opportunity.

Panel 8: Risk flags. Deal-context risk factors from the sales cycle that are still active: over-promise flags (commitments the AE made that CS is still managing expectations on), ICP edge case notes (this account was at the boundary of the target profile), champion change history (if the original champion has already changed once). This panel connects back to the deal context layer from the shared customer record architecture. Owned by both. Either team can raise a flag, both must acknowledge.

Who Owns Each Panel: Field Ownership at the Dashboard Level

Shared dashboards fail when ownership is ambiguous. Here's the clear breakdown:

The key rules: RevOps owns the structural data that neither AE nor CSM should be able to change without a process. AE and CSM co-own the champion map because both teams interact with the same people at different times. Risk flags are the one place where either team has full authority to raise. It doesn't require the other team's permission to flag an account. But ownership only matters if the dashboard itself lives somewhere both teams actually check.

Where the Dashboard Lives: Platform Options and Trade-offs

The location choice matters because it determines which team has native access and which team has to log into something outside their daily workflow.

Option A: CRM (primary home). Health and engagement data from the CS platform must be synced in. This is the right choice if the CRM is already the working environment for both AE and CSM, which requires the shared customer record architecture to be functioning. The advantage: AE is already in the CRM, so adoption friction for the AE side is near zero. The risk: if the CS platform data isn't syncing reliably, Panel 2 (health score) and Panel 7 (expansion signals) become stale.

Option B: CS platform (alternative home). Deal context and AE activity data must be synced in from the CRM. This is the right choice if CSMs use the CS platform as their primary daily environment and AEs already use it for account reviews. The risk is the mirror of Option A: AE adoption requires them to work in a tool they don't normally use.

Option C: Standalone BI (Looker, Tableau, or similar). Maximum flexibility: you can pull from both CRM and CS platform, build exactly the layout you want, and control the refresh rate for each panel. The cost is that this requires a functioning data pipeline from both systems, ongoing BI maintenance, and usually a RevOps engineer to own it. For most SMB and mid-market companies, this is more infrastructure than the problem requires.

Recommendation: If the shared customer record architecture is working (CRM and CS platform are in sync), Option A is the natural home. The dashboard lives where deals live. Both teams view it in the context of the full commercial relationship. If the architecture isn't working yet, if data is still manually reconciled between systems, building the Tier 1 dashboard before fixing the schema is putting the roof on before the foundation. Fix the schema first.

How It Gets Used: The Four-Cadence Review

The dashboard is only half the intervention. The other half is the ritual that makes it a coordination tool rather than a report nobody reads.

The weekly update is not a meeting. It's five minutes per account, each person updating their owned panels independently. If both AE and CSM do it, the bi-weekly review runs from accurate data. If either team skips it, the bi-weekly review is spent figuring out what's current rather than deciding what to do. The quarterly slot in particular should align with joint QBR preparation: the same account data that drives the internal review feeds the customer-facing conversation.

What Good Looks Like: Three Behaviors the Dashboard Enables

AE sees a health dip before their renewal call and reaches out to CSM first. Panel 2 (health score) drops from 82 to 61 in the two weeks before the AE had planned to send the renewal proposal. The AE sees it in the Monday panel review, messages the CSM before sending anything to the customer, and learns that a key integration broke two weeks ago and the customer is frustrated. The renewal conversation gets delayed by two weeks while CS fixes the integration. The renewal closes. Without the dashboard, the AE sends the proposal, the customer responds with the broken integration complaint, and the renewal becomes a negotiation rather than a formality.

CSM sees an expansion signal and routes it to AE with context. Panel 7 shows that a Tier 1 account has added 12 users to a module that wasn't part of the original contract, and the champion mentioned in the last QBR that "we've been thinking about rolling this out to our support team too." The CSM flags it in Panel 7 with the verbatim note. The AE sees it in the dashboard and books an expansion call with context already loaded. No hand-off meeting required. The expansion closes in the same quarter.

RevOps identifies two Tier 1 accounts where champion contact is overdue and flags it without waiting for the next sync meeting. During a weekly dashboard maintenance pass, RevOps notices that Panel 6 (champion map) shows no contact with the executive sponsor at two accounts in the last 45 days. RevOps raises a risk flag in Panel 8 for both accounts. Both AE and CSM receive the flag notification. The AE schedules a call with the executive sponsor. The CSM follows up with the champion. Neither account churns at renewal.

Quotable Nuggets

"43% of avoidable Tier 1 churns happen because neither AE nor CSM saw the at-risk signal early enough. The signal existed in one system, but not the one the other person checks, according to Totango's retention analytics study."

Rework Analysis: The most common failure mode for Tier 1 dashboards isn't a technology problem. It's a cadence problem. The 8-Panel Tier-1 Dashboard Spec can be built in most CRM or CS platforms within a week. What determines whether it works is whether both AE and CSM do the weekly 5-minute-per-account update that keeps the panels current. Teams that treat the update as a meeting they attend rather than a ritual they own see the dashboard go stale within 60 days. Teams that treat it as an individual accountability, where each person owns their panels, updates them on Monday, and flags concerns without waiting for the bi-weekly review, see the payoff in expansion deals caught early and churns that don't happen.

Anti-Patterns

Building the dashboard but skipping the review cadence. A dashboard that nobody updates becomes a historical artifact within 60 days. McKinsey's research on digital key account management found that the structural discipline of scheduled account reviews, not the dashboards themselves, is what separates high-performing account management teams from those who have the tools but not the outcomes. The weekly five-minute-per-account update ritual is what keeps it current. Without the cadence, the panels go stale, both teams stop trusting the data, and the dashboard becomes a well-intentioned project that didn't work rather than a coordination tool that did.

Including every account in the Tier 1 view. When a VP CS advocates for adding "just a few more accounts" and the list grows from 40 to 120, the dashboard loses its value. Depth requires constraint. If every account gets Tier 1 treatment, none of them do. Set the criteria, hold the line, and create a clear process for the risk-override tier rather than expanding the baseline.

Letting the dashboard diverge from the operational record. If the health score in Panel 2 doesn't match the health score in the CS platform, both teams stop trusting it. The dashboard is only as reliable as the underlying systems feeding it. When the shared customer record architecture is working and the sync is current, this problem is rare. When the sync is unreliable, the dashboard becomes a liability rather than an asset.

Running the review as a status report rather than a decision meeting. The bi-weekly review should produce action items, not updates. "Account X health score is 61" is not an action item. "Account X health score dropped from 82 to 61, CSM is handling the integration issue, AE should hold the renewal proposal until next week" is an action item with owners and a timeline. The meeting structure should explicitly require one next action for every flagged panel.

Frequently Asked Questions

What is the 8-Panel Tier-1 Dashboard Spec?

It's a concrete joint visibility framework for AE-CSM coordination on high-value accounts. The eight panels are: Account Identity (company basics, owned by RevOps), Health Score (composite CS signal, owned by CSM), Contract Status (ARR and renewal data, co-owned by RevOps and CSM), Engagement Timeline (last and next touchpoints, co-owned by AE and CSM), Open Items (outstanding commitments and customer blockers, co-owned by AE and CSM), Champion Map (primary champion, executive sponsor, detractors, co-owned), Expansion Signals (usage growth and upsell appetite, CSM-owned, AE-reviewed), and Risk Flags (deal-context and health risks, either team can raise). Together they give AE and CSM shared visibility on everything that affects a Tier 1 account's health and growth trajectory.

What qualifies an account for Tier 1 designation?

Three criteria determine Tier 1 inclusion, set by RevOps and approved by VP Sales and VP CS quarterly. First: ARR threshold, typically the top 20% of accounts by annual contract value. Second: strategic tier, meaning accounts in a priority vertical, a reference customer program, or an ABM campaign that warrant weekly visibility regardless of current ARR. Third: risk override, covering accounts outside the normal threshold but flagged at elevated churn risk, given temporary Tier 1 designation until the risk is resolved. Tier 1 should never expand to cover more than 20-25% of the portfolio. The moment it covers 40%, it stops being a depth tool and becomes another general monitoring view.

Which platform should the Tier 1 dashboard live in: CRM or CS platform?

If the shared customer record architecture is working and CRM and CS platform data are reliably synced, the CRM is the natural home: AEs already live there, adoption friction is near zero, and both teams can review account data in the context of the full commercial relationship. If data is still being manually reconciled between systems, building the Tier 1 dashboard before fixing the schema is putting the roof on before the foundation. For teams not yet ready for CRM as the primary home, the CS platform or a standalone BI tool (Looker, Tableau) are viable alternatives, with the trade-off of requiring AEs to work outside their primary environment.

What is the review cadence for Tier 1 dashboards?

Four cadences. Weekly: each AE and CSM independently updates their owned panels, five minutes per account, no meeting required. Bi-weekly: AE and CSM team leads review the full Tier 1 list together, 30 minutes for the full list, escalating accounts with multiple flag conditions to VP level. Monthly: VP Sales and VP CS review the dashboard, 45-60 minutes, with explicit action items and owners for at-risk and expansion accounts. Quarterly: full account team uses the dashboard to prep for customer QBRs, with Panel 7 (expansion signals) driving the expansion conversation and Panel 5 (open items) driving the accountability review.

What ARR threshold should determine Tier 1 designation?

The specific threshold depends on your portfolio size and ARR distribution. A practical starting point is the top 20% of accounts by annual contract value. In a company with 200 customers, that's 40 accounts. In a company with 500 customers, that's 100. The key constraint is that the dashboard must cover a small enough set of accounts to enable depth: detailed weekly review, panel-level ownership, real coordination between AE and CSM. Bain's key account management research shows that companies with tiered segmentation and differentiated treatment consistently outperform those applying uniform coverage, but only when the Tier 1 list stays disciplined. If Tier 1 grows to 40% of the portfolio, the depth disappears and it becomes another general health board.

How does Panel 7 (Expansion Signals) connect the CSM to AE pipeline creation?

Panel 7 is the mechanism that converts CSM relationship intelligence into AE expansion opportunities without requiring a handoff meeting. When a CSM sees usage growing in a product area that wasn't in the original deal, or hears a customer mention expanding to another team in a QBR, they update Panel 7 with the specific signal and verbatim note. The AE reviews Panel 7 in the weekly dashboard update and books an expansion conversation with the context already loaded. The entire handoff happens through the shared panel: no Slack thread, no meeting scheduled, no signal lost in translation. Expansion signals that are documented in Panel 7 with specific context close faster than those that surface informally because the AE goes into the conversation already knowing the customer's stated intent.

Learn More

• Shared Customer Record Architecture
• Customer Health Scoring with Sales Context
• 8 Shared Dashboards for Revenue Teams
• Joint At-Risk Account Review
• Expansion Ownership and Upsell Motion