Key takeaways
- Delegate how tools run; keep what the tools are for.
- RevOps owns evaluation, setup, integrations, data quality and reporting.
- The VP owns the outbound motion, the budget and the definition of success.
- Write the split down so nobody buys or retires a tool by surprise.
Which outbound tooling decisions can RevOps own
RevOps can own the decisions about how tools are configured, connected and kept clean, because those need system knowledge more than sales judgement.
- Shortlisting and testing tools against requirements the VP has agreed.
- Configuration: fields, stages, templates, routing rules and permissions.
- Integrations between the CRM, inboxes, calendars and other tools.
- Data quality: deduplication, enrichment rules and list hygiene.
- Seat management, onboarding and access reviews.
- Reporting definitions and dashboards.
Which decisions should the VP of sales keep
The VP should keep the decisions that change strategy, spend or the daily work of the team. That covers which outbound motion to run, which segments to target, how much to spend, what counts as success and whether reps should change how they work.
A new tool that changes how reps spend their day is a sales decision first and a systems decision second.
How do you set guardrails for delegated decisions
Set guardrails by agreeing the requirements, a spending limit and the points where RevOps must come back for approval. For example, RevOps might change templates and fields freely, but must bring any new tool, any contract above an agreed limit and any change to the sales process to the VP.
Put the split in a short written document, and review it after every planning cycle.
What goes wrong when tooling is not delegated
When nobody owns tooling, the stack grows tool by tool. Reps buy their own tools, data spreads across systems and reports stop agreeing with one another.
When the VP keeps every decision, small fixes wait weeks and the VP spends time on settings rather than on the team.
Where Pebbles Ai fits
- CapabilityAI workspaceThe AI workspace puts Marketing and Strategy assistants, projects and approval cards in one place. In Manual mode, actions such as email sends, CRM writes and lead generation ask for approval before they run, which gives RevOps a clear checkpoint.
- FoundationIntegrationsConnect Gmail, Outlook, Google Calendar, Slack, Notion and MCP servers from the Pebbles Ai catalogue. Every connection is available on every plan.
Common questions
Should RevOps have budget authority for sales tools?
Usually up to an agreed limit. Larger contracts and anything that changes how the team works should go to the VP of sales, and often to finance.
Does a small sales team need RevOps to own tooling?
A small team may not have a RevOps hire, but someone should still own tooling. Often that is a sales operations lead or a senior rep with time set aside for it.
How often should the VP review the tool stack?
Once or twice a year, and at each planning cycle. RevOps brings usage, overlaps and gaps; the VP decides what to keep, add or retire.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
