You're a one-person RevOps team at a $3M-$15M SaaS company. Here's what to build first.

Solo RevOps hire with no existing process or data model? Here's the exact build sequence for early-stage SaaS, from diagnosis to measurement to governance.

Jay Filiatrault
revops hubspot-implementation gtm-operations early-stage-saas one-person-revops

A solo RevOps hire walking into a $3M-$15M SaaS company with no existing process, no clean data model, and no GTM governance should start with diagnosis before touching a single HubSpot workflow. The sequence matters: build in the wrong order and you’ll spend six months automating chaos. Build in the right order and you give the company its first real operating system.

This post walks through exactly what to prioritize, in what order, and why, based on what we see repeatedly in the early-stage SaaS companies we work with.

Key takeaways

  • Diagnose your growth stage before you build anything. The right metrics at $4M ARR are different from the right metrics at $14M ARR.
  • Your first deliverable should be a shared data model, not a dashboard. Dashboards built on undefined stages are noise.
  • The full customer lifecycle, pre-sale through retention and expansion, needs to be in scope from day one, even if you only have two CSMs.
  • Process documentation and CRM configuration are the same project. Do them together.
  • Governance (a standing cross-functional review) is what keeps your builds from rotting after 90 days.

Why the build order matters more than the tools

Most solo RevOps hires get handed a HubSpot instance, a Slack channel, and a list of complaints. The instinct is to start fixing the loudest problem: the pipeline report nobody trusts, the lead routing that sends everything to the wrong rep, the deal stages nobody uses consistently.

That instinct will burn you.

Fix a symptom without understanding the underlying system and you’ll be back fixing the same problem in a different form in 90 days. The companies we work with that see the fastest improvement aren’t the ones who moved fastest on tactics. They’re the ones who spent two to three weeks on diagnosis before writing a single workflow.

Here’s the sequence we follow.

Step 1: Diagnose where the company actually is

The first question is not “what’s broken.” It’s “what stage is this business in, and what does that mean for what we should be measuring?”

At $3M-$15M ARR, most SaaS companies are squarely in a phase where the central question is: can we grow repeatably? Not “are we profitable” and not “will customers stay forever.” Those are real questions, but they’re not the first ones.

In our engagements, we map the company’s ARR to a rough growth stage and identify the two or three active constraints blocking the next phase. At this ARR band, the most common constraints are:

  • No repeatable sales process (non-founder AEs close at half the rate founders do)
  • No shared definition of a qualified opportunity
  • No visibility into where deals stall or why they’re lost
  • Post-sale is a black box (CS team exists but no one knows what “good” looks like)

You need to know which of these applies before you configure a single pipeline stage.

How to run the diagnosis in week one

  1. Pull the last 12 months of closed-won and closed-lost deals from whatever system exists. Even if the data is messy, the patterns are there.
  2. Interview three to five reps and ask: “Walk me through the last deal you closed. When did you know it was real?” Listen for where their answers diverge.
  3. Talk to whoever owns CS. Ask: “What does a successful customer look like at 90 days?” If they can’t answer with a number, that’s your first gap.
  4. Talk to the CFO or VP of Finance. Ask what ARR, growth rate, and new logo count look like month over month. These three numbers tell you if the growth engine is working at all.

By the end of week one you should know: which part of the business is the biggest constraint, and whether the problem is primarily pre-sale, at the sale, or post-sale.

Step 2: Define the data model before you build anything in HubSpot

This is the most skipped step and the most important one. Every dashboard, every report, every automation you build in HubSpot will only be as good as the underlying stage definitions.

A data model is just a shared answer to: what are the stages a prospect or customer moves through, and what has to be true to move from one to the next?

For a $3M-$15M SaaS company, your data model needs to cover the full lifecycle, not just the sales funnel. That means:

  • How does a lead become a qualified opportunity? What criteria must be met?
  • What stages does an opportunity move through before close?
  • What happens between closed-won and a customer who’s fully onboarded and getting value?
  • When does a customer go from “retained” to “expansion-ready”?

Most early-stage CRM setups only define the first part. The post-sale stages are either missing or vague. This creates a data gap that makes it impossible to understand why customers churn or expand.

What to actually build in the data model

For each stage, define three things:

  1. Entry criteria: What must be true for a record to enter this stage? (Not “what does the rep think” but what is documented and verifiable.)
  2. Exit criteria: What event or action moves the record to the next stage?
  3. Owner: Which role is responsible for records in this stage?

Do this for the full lifecycle. In our builds, this document typically runs three to five pages and takes one to two weeks of iteration with sales, CS, and leadership. It’s the most contentious thing we do because it forces alignment that didn’t exist before. That’s exactly why it’s valuable.

Only once this document is agreed on do you configure HubSpot to match it.

Step 3: Configure HubSpot to reflect reality, not aspiration

Once your stage definitions exist, HubSpot configuration is mostly execution. A few principles that save a lot of rework:

Map your CRM stages to the full lifecycle. Use deal stages for pre-sale. Use a separate pipeline or object (we typically use HubSpot’s customer success tools or a custom object) to track post-sale stages. Don’t try to cram onboarding and retention status into deal stage fields.

Build required fields at stage transitions. If a deal can’t move from “Discovery” to “Proposal” without a documented pain and a confirmed decision timeline, make those fields required in HubSpot. This isn’t about being controlling. It’s about making your data trustworthy.

Don’t automate what isn’t working manually first. This is a rule we enforce in every engagement. If the SDR-to-AE handoff is broken, automating it makes it faster to be broken. Fix the process on paper, run it manually for two to four weeks, then automate.

Create three to five core reports before anything else:

  • Pipeline by stage (volume and value)
  • Stage conversion rates, month over month
  • Average time in each stage
  • Closed-lost reasons by stage
  • New customers by month, with source

These five reports will tell you more about where to focus than any dashboard a consultant will sell you.

Step 4: Establish the metrics that actually matter at this stage

At $3M-$15M ARR, you are in a growth phase. The metrics that matter are the ones that tell you whether the acquisition engine is working and whether customers are staying long enough to justify the cost of acquiring them.

Here’s the short list:

Acquisition side:

  • New logos per month (are you adding customers consistently?)
  • Pipeline created per month (is there enough in the funnel?)
  • Conversion rate from qualified opportunity to closed-won (are reps actually closing?)
  • Average sales cycle length (is it getting longer? That’s a warning sign.)
  • Average contract value, trended (is ACV drifting down? That’s a GTM misalignment problem.)

Post-sale side:

  • Gross revenue retention (what percentage of ARR from existing customers are you keeping, excluding expansion?)
  • Onboarding completion rate (are customers actually getting set up?)
  • Time to first value (how long from signed contract to a customer getting a real outcome?)

At this ARR level, gross revenue retention is more important than net revenue retention. Net retention includes expansion, which can mask a retention problem. If you’re losing 15% of customers but expanding the ones who stay, your net number looks fine while your foundation is cracking.

Target: 85% or better gross retention for most SaaS models at this stage. If you’re below that, the post-sale motion needs attention before you scale acquisition.

Step 5: Document process ownership before you build more automation

One thing we see consistently in early-stage companies: everyone assumes someone else owns the handoff.

The AE thinks CS gets the customer context from the CRM. CS thinks the AE briefs them on a call. Neither is happening consistently. The result is customers who feel like they’re starting over after they sign.

Process documentation doesn’t have to be complicated. For each major handoff in your lifecycle, write down:

  • Who initiates it
  • What information transfers (and in what format)
  • What the receiving role does in the first 48 hours
  • How you know the handoff succeeded

The two handoffs that matter most at this stage:

  1. Qualified lead to AE: What does “qualified” mean? What information does the AE need to run a good discovery call? Who is responsible for making sure that information is in the CRM before the handoff?

  2. Closed-won to CS: What does CS need to know to run a successful kickoff? What did the customer say their goals were? What did you promise? Who are the stakeholders? This information needs to live in HubSpot, not in the AE’s memory.

Document these two handoffs first. Everything else can wait.

Step 6: Set up a standing GTM review

This is the step most solo RevOps hires skip because it feels like “someone else’s job.” It is not.

Without a regular, structured meeting where sales, marketing, and CS look at the same numbers together, your data model will drift. Reps will start skipping stages. CS will stop logging activity. The CRM will slowly stop reflecting reality, and you’ll be back to square one in six months.

What this meeting looks like in practice:

  • Monthly, 60 minutes
  • Attendees: Head of Sales, Head of Marketing, Head of CS, CEO or COO, RevOps (you)
  • Agenda: Review the five core reports you built in Step 3. Identify one metric that moved in the wrong direction. Agree on one thing to fix before the next meeting.

That’s it. Don’t make it complicated. The goal is a forcing function that keeps everyone accountable to the same numbers.

In our experience, companies that run this meeting consistently improve their core conversion rates measurably within two quarters. Companies that skip it see their RevOps investments erode at roughly the same pace.

What to defer (and why)

A few things that will seem urgent but should wait:

  • Lead scoring: Build this after you have six to twelve months of clean data. Lead scoring built on dirty data is worse than no lead scoring.
  • Multi-touch attribution: Important eventually, not important now. Get the basics right first.
  • Forecasting models: You need at least two full quarters of clean pipeline data before a forecast is meaningful.
  • Account-based marketing infrastructure: Not relevant until your ICP is locked and your sales motion is repeatable.

The 90-day plan in summary

Days 1-14: Diagnose

  • Interview sales, CS, and finance
  • Pull and review 12 months of deal data
  • Identify the top two or three constraints

Days 15-30: Define

  • Write the data model (stage definitions, entry/exit criteria, owners)
  • Get it reviewed and signed off by sales and CS leadership

Days 31-60: Build

  • Configure HubSpot to match the data model
  • Build the five core reports
  • Document the two critical handoffs

Days 61-90: Govern

  • Run the first GTM review
  • Identify the first metric to improve
  • Build one process improvement (a workflow, a required field, a template) based on what the data shows

By day 90 you will have more operational clarity than most companies at this stage ever achieve. That’s the foundation everything else gets built on.

Frequently Asked Questions

What should a solo RevOps hire do in the first 30 days?

Focus entirely on diagnosis and definition. Interview stakeholders, review historical deal data, and draft a data model (stage definitions with entry and exit criteria). Do not build workflows or dashboards until the data model is agreed on. Automating undefined processes creates faster chaos, not faster growth.

How do I know if my HubSpot setup is good enough to start building reports on?

Check two things: first, are deal stages being updated consistently by reps, or do most deals sit in one stage for months? Second, do closed-lost deals have a reason logged? If either is broken, your reports will mislead you. Fix the input discipline before building the reports.

Should a solo RevOps hire own the post-sale data model too, or just sales?

Yes, own both from day one. Gross revenue retention is as important as new logo growth at $3M-$15M ARR, and you can’t measure it without post-sale stage data. If CS doesn’t have defined stages in HubSpot, build them. It’s the same project.

What’s the single most important metric for a $5M-$10M SaaS company?

New logos per month, combined with gross revenue retention. New logos tells you if the acquisition engine is working. Gross retention tells you if the foundation holds. If both are healthy, you have a real business. If new logos are growing but retention is below 85%, you’re filling a leaky bucket and it will catch up with you.

How do I get sales reps to actually use the CRM the way I’ve configured it?

Make it easier to use than not to use. Required fields at stage transitions help, but the real driver is showing reps that the data benefits them. When a rep can see their own conversion rates by stage and use that to prioritize their pipeline, they start caring about data quality. Connect the data to their outcomes, not just management’s reporting needs.

When should a solo RevOps hire start thinking about headcount or outside help?

When the volume of build work exceeds what one person can maintain without letting governance slip. In practice, this usually happens somewhere between $8M and $15M ARR, when the number of GTM motions, tools, and processes crosses a threshold that makes part-time or agency support worth the cost. If you’re spending more than 60% of your time on maintenance and less than 40% on improvement, that’s the signal.


If you’re a solo RevOps hire trying to build this from scratch, or a founder who just made the hire and wants to make sure they succeed, work with GTM Ops to get the foundation right the first time.