Technical Account Management (TAM) Leader

The TAM Leader hires, coaches, and grows the TAM team so each member operates as a credible, proactive technical partner to their accounts. This includes:

• Hiring and onboarding new TAMs, including running them through the TAM Path ramp

• Running regular 1:1s, setting individual development plans, and giving direct feedback on account plans, QBRs, and escalation handling

• Building and maintaining repeatable playbooks (upgrade runbooks, optimization playbooks, escalation patterns) so quality doesn't depend on tenure

• Setting and holding the team to a consistent bar for technical depth, proactivity, and communication

- every partner with a named Technical Account Manager spanning Strategic AI, Growth, and Other tiers

• Running the quarterly review/refresh of assigned accounts, rebalancing books as ARR and strategic relationships shift

• Resolving open coverage gaps (e.g. regions or account types with no TAM alignment) and deciding when a controlled exception, a new hire, or a change in tier definition is the right fix

• Approving leadership-discretion assignments and cap exceptions, and making the trim/reassign calls when an account is dropped for capacity

The TAM Leader ensures the team consistently shortens time to value for new accounts by:

• Auditing that architecture and deployment validation is happening post-sale, not skipped

• Coaching TAMs on configuration guidance and best-practice delivery

• Tracking early success milestones across the portfolio, not just account by account

The TAM Leader is the escalation layer above the individual TAM - brought in on complex, high-impact, or multi-stakeholder issues rather than replacing the TAM as primary contact. This includes:

• Coordinating across support, engineering, and success during major incidents

• Owning execution of the Named Account Escalation SLA sequence when it's triggered

• Ensuring root cause analysis and preventative action actually close out, not just the immediate fire

• Isolating TAMs from technical repair work so they can stay focused on the relationship while the right team handles the fix

Common indicators of TAM Leader effectiveness include:

• Coverage: % of the $33.1M+ named-account book and partner-mapped accounts with an assigned, active TAM

• Team health: ramp time to productivity for new TAMs, retention of the TAM team itself

• Customer adoption and usage depth across the book

• Reduction in critical incidents and time to resolution for escalated issues, portfolio-wide

• Customer satisfaction and retention (NRR) across named and partner-mapped accounts

• Consistency: QBR completion rate and account plan quality across the team, not just top performers

This section documents the tools and systems used by the Technical Account Management team. It is intended to be kept up to date as tooling evolves.

• Admin Studio

• Grafana

• Hex

• pgAdmin

• HubSpot (account ARR, tier, and health data)

• Notion - Draft TAM Accounts doc and Partner Mappings database

• Spend - For customers at $100K ARR, access to pooled TAM resources for a set (time TBD) hours per month

• Pooled TAM SKU - Customers of any scale can purchase pooled access to the TAM team (requires Enterprise Support SKU)

• Leadership Discretion for Customer Needs

• Spend - For customers at $250K ARR, access to a dedicated TAM resource for a set (time TBD) hours per month

• Dedicated TAM SKU - Customers of any scale can purchase an assigned TAM (requires Enterprise Support SKU)

• Leadership Discretion for Customer Needs

The TAM Leader owns tier decisions, the quarterly refresh of this mapping, and any leadership-discretion exceptions.

To keep the function focused and scaling, the TAM Leader does not:

• Replace the individual TAM as an account's day-to-day technical relationship owner - accounts scale by layering support on, not by handing off

• Perform day-to-day operational work for customers

• Own or negotiate commercial terms for either named accounts or partner deals - that stays with the AE or Partner Manager

• Act as professional services for custom implementations

• Manage frontline support case queues

Supabase was born-remote and open-source-first. We believe our globally distributed team is our secret weapon in building tools developers love.

• ~400 team members

• 60+ countries

• 20+ languages spoken

• Over $1B raised (including our $500M Series F)

• 540,000+ community members

We move fast, build in public, and use what we ship. If it's in your project, we probably use it in ours too. We believe deeply in the open-source ecosystem and strive to support - not replace - existing tools and communities.