At about $10M ARR, a CRM that was fine at $2M starts to cost real money: forecasts miss, reports disagree, and every new process adds another workaround. Once leadership decides on a CRM rebuild, the first question is often a hiring one: do we start with a RevOps lead, a CRM admin, or an implementation partner?
The answer depends on where your bottleneck is. This guide covers what each role actually does, how to tell which bottleneck you have, and what the first 90 days look like. For the wider question of fractional versus in-house versus consultant, see who to hire for a SaaS CRM rebuild. This post is about sequence and roles.
The short version: Hire for the bottleneck. If the problem is deciding what the system should be, start with a RevOps lead or a partner who designs. If the design exists and nobody can build it, start with a partner or an admin. A CRM admin is a poor first hire for a rebuild when nobody has decided the target design, because an admin executes decisions and does not make them.
Three roles that get confused
| Role | Owns | Does not do | Start here when |
|---|---|---|---|
| RevOps lead | Strategy, definitions, process, forecasting, cross-team alignment | Day-to-day configuration at scale | Decisions about process and definitions are unmade or disputed |
| CRM admin | Configuration, user support, data upkeep, small automations | System design or cross-team decisions | The design is settled and daily maintenance is the constraint |
| Implementation partner | Design and build of a defined project, specialist skills, speed | Ongoing ownership once the project ends | You need a rebuilt system in weeks and have no internal builder |
Find your real bottleneck
Answer three questions in order.
- Is there agreement on definitions and process? If sales, marketing, and customer success still disagree about what a qualified lead, a closed deal, or a renewal is, you have a decision bottleneck. Adding hands does not help. You need someone with the authority and skill to settle it.
- Is there a written target design? If a design exists, a data model, pipelines, lifecycle stages, and reports, you have a build bottleneck, and the next hire is a builder.
- Does anyone inside understand the current system? If not, you cannot rebuild safely until someone documents what exists. That is usually a partner's first job.
| Your situation | Hire first |
|---|---|
| Definitions disputed, no design, no owner | RevOps lead, or a partner running design with an executive owner |
| Design agreed, nobody to build it | Implementation partner, or an experienced CRM admin if scope is small |
| Nobody understands the current system | Implementation partner for discovery, then decide |
| Rebuild is done, upkeep is the issue | CRM admin |
| A large rebuild and no RevOps function | Partner to build, RevOps lead to own it afterward |
Why a CRM admin is rarely the right first hire
Admins are valuable and often undervalued, but they are hired to keep a system running. A rebuild asks for architecture and cross-team negotiation. Placing an admin in that position tends to produce a faithful copy of the old system, because the person has no mandate to change the process. If you already have an admin, treat that person as the future maintainer of the rebuilt system and involve them early. If you do not, hire one after the design exists.
The first 90 days
| Days | Focus | Output |
|---|---|---|
| 1 to 30 | Decide | An inventory of the current system, agreed definitions, a target design, and a sequenced plan |
| 31 to 60 | Build | The core data model, pipelines, lifecycle rules, routing, and migrated data, tested in a sandbox |
| 61 to 90 | Adopt | Training, a cutover, rebuilt reports, a documented handover, and a baseline for forecast accuracy |
Whoever you hire first, make the 30-day output specific. A rebuild that has no written design at day 30 is behind, regardless of how much configuration has happened.
What to define before the first hire
- Scope. Which systems and processes are inside the rebuild.
- Success measures. For example, one agreed funnel definition, complete required fields on open deals, and a forecast you can reconcile to billing.
- Executive owner. One leader who settles disputes between teams.
- Time from your team. Interviews, reviews, and testing take real hours.
- Documentation. What you must own at the end.
Mistakes that cost the most
- Hiring an admin to design and then wondering why the system looks the same.
- Starting the build before the definitions are agreed.
- Treating the rebuild as an IT project with no revenue owner.
- Hiring the permanent RevOps lead into a half-built, contested project.
- Skipping documentation and ending up dependent on one person.
Three ideas worth borrowing from outside RevOps
Architect, contractor, and facilities manager, from construction. Someone designs the building, someone builds it, and someone maintains it. They are three different jobs. A RevOps lead, an implementation partner, and a CRM admin map onto the same split.
Theory of constraints, from manufacturing. Improve the narrowest point first. Adding capacity anywhere else makes no difference. Find the bottleneck, then hire for it.
Reversible and irreversible decisions, from decision science. Data model and lifecycle decisions are hard to reverse, so make them slowly and with senior input. Field labels and layouts are easy to change, so delegate them.
Frequently asked questions
- Who should you hire first for a CRM rebuild at $10M ARR?
- Hire for the bottleneck. A RevOps lead or a design-focused partner if definitions and process are unsettled, a partner or experienced admin if the design exists and needs building, and an admin after the rebuild for upkeep.
- Do you need a RevOps lead before a CRM rebuild?
- Not always, but someone must own definitions and make cross-team decisions. If you cannot hire a RevOps lead yet, a partner with an internal executive owner can fill that role during the project.
- Is a CRM admin enough to rebuild a CRM?
- Usually not when the design is undecided. An admin can build a settled design well, but is rarely given the authority or has the cross-functional mandate to decide what the system should be.
- How long does a CRM rebuild take at $10M ARR?
- Typically one to four months, depending on integrations, data quality, and how quickly stakeholders agree on definitions.
- Should you hire a partner and a full-time person at the same time?
- Often yes. A partner builds while the permanent owner joins during the second half of the project, learns the system as it is built, and takes over documentation.
- What is the biggest risk in a CRM rebuild?
- Building before the definitions are agreed. The system then encodes the disagreement, and the problem returns in a new form.