Key takeaways
- Sales leadership owns the why, the budget and the final decision on changes to how the team sells.
- Sales ops or RevOps owns requirements detail, evaluation, setup and day-to-day running.
- Reps, finance and security are consulted, not decision makers.
- Write the model down so disagreements have a referee.
Why tooling ownership causes friction
Tooling ownership causes friction because a sales tool is both a strategy choice and a system that someone has to run. Leaders choose tools for what they promise; operations teams inherit the integrations, the data and the support.
When those two views meet only at renewal, the stack fills with tools that nobody fully uses.
What a clear ownership model looks like
A clear model names, for each kind of decision, who decides, who is consulted and who is informed. Leadership decides on new tools and budget, with ops consulted; ops decides on configuration and integrations, with leadership informed; reps are consulted on anything that changes their daily work.
- Buy or retire a tool: leadership decides, ops recommends.
- Configure fields, stages and templates: ops decides, leadership is informed.
- Connect tools to each other: ops decides, security is consulted.
- Change how reps work: leadership decides, reps and ops are consulted.
How does company size change who owns tooling
In a small company the head of sales often owns everything, with a senior rep doing the setup. As the team grows, a sales ops or RevOps role takes the running of tools so that leaders can focus on the team.
In larger organisations, RevOps often owns the shared stack across sales, marketing and customer success, while each leader keeps a say over tools specific to their team.
How do you resolve a disagreement about a tool
Resolve it by going back to the written requirements and testing the tool against them, with both sides agreeing the test first. If the disagreement is really about strategy, it goes to sales leadership; if it is about integration or data, ops has the stronger say.
Where Pebbles Ai fits
- CapabilityAI workspaceThe AI workspace has three execution modes: in Manual, actions that reach the outside world ask for approval; in Plan, they are queued rather than run; in Auto, they run without asking, except a template send and a calendar delete, which always ask. Ops and leadership can agree which mode the team works in.
- FoundationIntegrationsEach person connects their own Gmail or Outlook inbox and their own MCP servers from the Pebbles Ai catalogue, while an admin connects workspace tools such as Notion and the Pebbles bot in Slack, which mirrors a split between personal tools and shared ones.
Common questions
Is sales ops the same as RevOps?
Not quite. Sales ops supports the sales team; RevOps covers sales, marketing and customer success together. In many companies one team holds both roles.
Should reps choose their own outbound tools?
Reps should be consulted, because they use the tools every day. Letting each rep buy their own leads to scattered data and tools nobody else can support.
Who should approve a new sales tool contract?
Sales leadership, usually with finance, and security for anything that touches customer data. Ops should have checked the tool against requirements first.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
