10
questions, with what a bad answer sounds like and what ours is.
Ask these live, take notes on the actual answers, and compare on the answers rather than the polish of the pitch.
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.
Vague answers about a delivery team, or a named lead who is 'overseeing' the work.
One person. I scope it, I build it, there is no account manager between us and nothing gets handed down.
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.
Generalities about methodology. No specifics about objects, fields or what went wrong.
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.
Why it matters: A consultant who always recommends more consulting is selling, not advising.
Never arriving at that answer, or arriving at it only after a paid engagement.
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.
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 final deliverable that is a slide deck. No documentation of what was built or why.
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.
Why it matters: RevOps influences pipeline and efficiency. Anyone guaranteeing closed revenue is either naive or dishonest.
Promises of revenue growth. No baseline taken before the work starts.
Whatever your reporting can actually support, with a baseline taken in the audit so the before and after are comparable. Not a revenue guarantee.
Why it matters: If the plan starts with a tool migration in week one, no diagnostic work has been done.
A proposal in week one. A recommendation to buy something before anyone has read your system.
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.
Why it matters: Scope creep and change orders are where consulting engagements go wrong.
Pricing that requires a call. Day rates with no ceiling. Separate line items for things you assumed were included.
$4,000 a month, on the pricing page, Kaypo included. No onboarding fee, no minimum term, no change orders.
Why it matters: A partner margin on a tool recommendation is a conflict you will not see on the invoice.
Reseller or partner status that only surfaces after the recommendation.
No. Sapwood takes no vendor commissions and resells nothing. The usual recommendation is to use what you already pay for.
Why it matters: RevOps for a $5M company looks nothing like RevOps for a $500M one.
Logos with no numbers attached. Case studies from companies ten times your size.
Real systems with the figures each one moved, on the proof page, no form in front of it.
Why it matters: A minimum term before any work is done is a way of making the decision hard to reverse.
Annual contracts. Notice periods measured in months. A penalty for leaving early.
You stop. No contract, no notice period, nothing to cancel, and you keep everything built up to that point.
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.
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.
Collect these before you give notice, because the conversation is easier while the engagement is still running:
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.
We use browser storage to run the site and to understand how it is used. You can accept all or necessary only. See our privacy notice.