What would you do in the first 30 days if you inherited our CRM?

Buyers are routinely advised to ask a consultant what they would do in the first thirty days, because a good one can describe a diagnostic approach without immediately selling a large implementation.

Sapwood is a revenue operations and GTM engineering shop in Denver. The diagnostic is free. Retainer $2,000 a month for up to 15 hours a week, Kaypo included. included in the retainer outside it.
See every price

Week one is inventory with nothing changed: object model, field usage, stage definitions, duplicate rates, routing, and the attribution chain, ending in a written findings summary. Week two is the working session and the plan. Weeks three and four are the build, in a sandbox, with you reviewing before anything reaches production. You should ask every consultant this question, and be suspicious of anyone who answers with a proposal instead of a process.

Last updated September 2026

Published prices. The diagnostic is free. Retainer $2,000 a month for up to 15 hours a week, Kaypo included.

The thirty days

Days 1 to 5, inventory, changing nothing

Object model, field usage, stage definitions and whether they carry exit criteria, duplicate rates, routing logic, the attribution chain, and what reporting exists versus what is trusted.

Day 5, written findings

Scored and ranked by what each issue is costing you, with a prioritized fix list and effort estimates. Yours to keep regardless of what happens next.

Days 6 to 10, the working session

Two hours with whoever knows how you actually sell. This is where stage definitions get decided, and it is the only part we cannot do without you.

Days 8 to 10, the plan

A one page scope and a start date. If the right answer is that you do not need us, this is where we say so.

Days 11 to 25, the build

In a sandbox. Data, objects, stages, routing, handoffs, and reporting, with you reviewing at checkpoints rather than at the end.

Days 26 to 30, deployment and handoff

Production changes in an agreed window with a rollback plan, then documentation, a recorded walkthrough, and live training with the team who will use it.

Want the first week without committing to the rest?

That is exactly what the free diagnostic is. One week, written findings ranked by cost, and no obligation to continue.

Why we publish this

It is a good test, so we have answered it in public rather than saving it for a call. If another firm cannot answer it as specifically, that is useful information.

Common questions

Every price we charge is on the site.

No gated pricing and no call required to see a number. If you want to talk it through, the first one is free and takes thirty minutes.

Let's chat See pricing

What it covers and what it costs

What we built and what it changed

What a week of reading an existing system turns up, the order a rebuild has to happen in, and what has to hold as you grow.

  • What an audit covers Scope and output
  • What RevOps is A plain definition
  • RevOps vs sales ops Where the line is

Questions

What should I ask a RevOps consultant before hiring them?

What they would do in the first thirty days, what will be shipped by week two, where documentation will live, whether your team can modify the automations afterwards, and whether they take commissions from software vendors.

Should a consultant charge for the first thirty days?

The diagnostic portion, yes. Free audits are sales instruments and tend to find problems the firm is best positioned to sell against. Paying a small fee changes the incentive.

What do you need from us in the first thirty days?

Access in week one, two hours for the working session, and one person who can approve a stage definition without a committee.

What if the findings say we do not need you?

Then we say so and you keep the document. It happens, and it is better for both sides than a project nobody needed.

Let us look under the hood.

Read-only access to your systems, and a written report you keep either way.

Start the free diagnostic

Let's chat.

Thirty minutes. Tell us what you are working on and we will tell you on the call whether we can help.

Add your name and a work email so we know who we are talking to.

Thank you!

We will reach out to you shortly. If you have not heard from us by tomorrow, email hello@sapwood.io.

While you wait, keep reading