Ten questions that tell you whether a RevOps consultant can actually do the work

10

questions, with what a bad answer sounds like and what ours is.

Use this on us

Why this page exists

Every article about hiring a RevOps consultant is written by someone selling RevOps consulting, and so is this one. The difference is that our answers are on the page, next to the questions, so you can judge them before you ever speak to us.

Take the list to whoever else you are talking to. If their answers are better, hire them.

Ask these live, take notes on the actual answers, and compare on the answers rather than the polish of the pitch.

01Who actually does the work?

Why it matters: The person who scoped the engagement is often not the person who delivers it. You meet a senior strategist, you get a junior account manager and an offshore implementation team.

A bad answer sounds like

Vague answers about a delivery team, or a named lead who is 'overseeing' the work.

Our answer

One person. I scope it, I build it, there is no account manager between us and nothing gets handed down.

02Walk me through the last CRM migration you did hands-on.

Why it matters: This separates operators from advisors. Someone who has only consulted cannot get specific about field mapping, dedupe logic or what broke at 2am.

A bad answer sounds like

Generalities about methodology. No specifics about objects, fields or what went wrong.

Our answer

233,000 Salesforce records down to 30,000. 148,000 records corrected, with creation rules that stopped duplicates coming back. I can walk you through the field map.

03What happens if the answer is that I should hire someone instead?

Why it matters: A consultant who always recommends more consulting is selling, not advising.

A bad answer sounds like

Never arriving at that answer, or arriving at it only after a paid engagement.

Our answer

Then I say so in the audit, for free, and I will write the job description and the scoring rubric. Several people have taken that and never come back.

04Who owns the system when this ends?

Why it matters: An arms-length engagement leaves you with a document and a gap. The question is whether you can run it without them.

A bad answer sounds like

A final deliverable that is a slide deck. No documentation of what was built or why.

Our answer

You do. Everything is built inside the systems you already own, documented so it does not live in one head, and handed over whether we continue or not.

05What will you measure, and when will I see it?

Why it matters: RevOps influences pipeline and efficiency. Anyone guaranteeing closed revenue is either naive or dishonest.

A bad answer sounds like

Promises of revenue growth. No baseline taken before the work starts.

Our answer

Whatever your reporting can actually support, with a baseline taken in the audit so the before and after are comparable. Not a revenue guarantee.

06What does the first two weeks look like?

Why it matters: If the plan starts with a tool migration in week one, no diagnostic work has been done.

A bad answer sounds like

A proposal in week one. A recommendation to buy something before anyone has read your system.

Our answer

Read-only access, six systems read end to end, and a written document with every gap priced by what it costs you a year. Before anything is touched.

07What is the price, and what is not included?

Why it matters: Scope creep and change orders are where consulting engagements go wrong.

A bad answer sounds like

Pricing that requires a call. Day rates with no ceiling. Separate line items for things you assumed were included.

Our answer

$4,000 a month, on the pricing page, Kaypo included. No onboarding fee, no minimum term, no change orders.

08Do you resell any of the tools you would recommend?

Why it matters: A partner margin on a tool recommendation is a conflict you will not see on the invoice.

A bad answer sounds like

Reseller or partner status that only surfaces after the recommendation.

Our answer

No. Sapwood takes no vendor commissions and resells nothing. The usual recommendation is to use what you already pay for.

09Can you show me numbers from a company at my stage?

Why it matters: RevOps for a $5M company looks nothing like RevOps for a $500M one.

A bad answer sounds like

Logos with no numbers attached. Case studies from companies ten times your size.

Our answer

Real systems with the figures each one moved, on the proof page, no form in front of it.

10What happens if I want to stop?

Why it matters: A minimum term before any work is done is a way of making the decision hard to reverse.

A bad answer sounds like

Annual contracts. Notice periods measured in months. A penalty for leaving early.

Our answer

You stop. No contract, no notice period, nothing to cancel, and you keep everything built up to that point.

Red flags that should end the conversation

  • Paid discovery that ends in a proposal rather than a document you keep.
  • Refusal to work read only first.
  • Building in their own accounts or tenancy rather than yours.
  • Vendor commissions they will not disclose.
  • No named person doing the work.
  • A minimum term before any diagnosis has happened.
  • A price that only appears after a call.

Contract terms to check before you sign

The monthly number is the least interesting part of the agreement. Several published providers use six month initial terms and a one time onboarding fee of around $5,000, which is real money before anything is built.

  • The minimum term, and the notice period after it.
  • Any onboarding or setup fee.
  • Whose accounts the work is built in.
  • Who owns the documentation, configuration and code on delivery.
  • What happens to the build if you stop.

How to choose between two providers

Ask the same six things of everyone: who does the work, how many hours you actually get, whether everything is built in your own accounts, what document you receive, whether they resell software, and what happens in month seven when something breaks.

Then divide the monthly fee by the hours included. Between $200 and $400 an hour is the normal band for senior work. Below it, ask who is really doing the work. Above it, ask what you get that a senior operator would not give you.

Switching providers without losing the build

Collect these before you give notice, because the conversation is easier while the engagement is still running:

  • Admin credentials in your own name for every system they touched.
  • A written description of what was built and why each piece exists.
  • A list of anything unfinished.
  • Exports of any automation that lives in their tenancy rather than yours.
  • A recorded handover session with whoever will own it next.

If the provider built in their own tenancy, have that conversation first. It is the one that decides how much of the work survives the switch.

Ask us all ten on a call.Thirty minutes. If the answers do not hold up, you have lost half an hour and gained a list.
Book 30 minutes →