Key takeaways
- Agree definitions, such as what a qualified lead is, before choosing tools.
- Keep one customer record that every team reads and writes.
- Approve one tool per job and retire the rest over time.
- Build handoffs into the tools with required fields.
Why standardise tooling across revenue teams
Standardising means a customer's history follows them from first contact to renewal. When sales development, account executives and customer success use different tools, each handoff loses context, and the customer repeats themselves.
It also makes reporting possible: you cannot follow a customer journey across tools that disagree on who the customer is.
What should RevOps standardise first
Standardise the definitions and the customer record before the tools. Teams that share definitions can work in different interfaces; teams that do not will disagree whatever tool they use.
- Definitions: lead, qualified lead, opportunity, customer and churn.
- The customer record: one system, with shared required fields.
- Handoff rules: what must be filled in before a lead or account moves on.
- Naming: stages, segments, campaigns and tags.
How do you choose which tools become standard
Map each job to the teams that do it and pick one tool per job, favouring tools that connect to the customer record. Where a team has a genuinely different job, such as customer success running onboarding, it can keep a specialist tool, as long as it writes back to the shared record.
How do you roll out standard tooling
Roll it out one team or one job at a time, with training, a clear switch-over date and a named owner for questions.
Start where the pain is most visible, often the handoff from sales development to account executives, so the benefit is clear early. Retire old tools on a schedule rather than leaving them running beside the new ones.
How do you keep the standard from drifting
Keep it with a simple request process for new tools, regular access reviews and a yearly audit of what each team uses. Drift usually starts with one team buying a tool to solve an urgent problem, so make the request route quicker than buying around it.
Where Pebbles Ai fits
- CapabilityAI workspaceThe AI workspace gives every team the same Marketing and Strategy assistants, with projects to group related chats and approval cards for actions that need confirmation in your execution mode.
- FoundationAgent memoryCompany memory reaches colleagues' assistants, so a fact one team shares with its assistant is available to the next, alongside Your memory and Project memory.
- CapabilityProspecting & customer recordsThe CRM, in Beta, holds contacts, companies and deals with admin-defined custom fields, tasks, notes, segments and saved views.
Common questions
Should SDRs, AEs and CS use the same CRM?
Yes, or at least read and write the same customer record. Separate records for each team are the main reason context gets lost at handoffs.
How long does standardising tooling take?
It depends on the number of tools and teams. Rolling out one job at a time keeps each step manageable and lets you fix problems before the next.
What if a team refuses the standard tool?
Find out which job the standard tool does not do for them. Either fix the gap, approve a specialist tool that writes back to the shared record, or explain the trade-off and agree a date.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
