You don’t have a RevOps function. You might not even have a RevOps hire. What you have is a CRM nobody trusts, processes that live in people’s heads, and a board asking for revenue data you can’t produce. This is the playbook that gets you from zero to operational in 90 days.
How Do You Build RevOps from Scratch?
You build RevOps from scratch by following a phased 30-60-90 day plan: audit and establish governance in the first month, design processes and configure tools in the second, then automate and enable the team in the third. The biggest mistake companies make is trying to automate before they have clean data and documented processes—that just automates the chaos faster. Start with the foundation, build methodically, and resist the urge to skip ahead.
This playbook is part of our Fractional GTM Leadership guide. For help assessing where you are before you start building, see our RevOps Maturity Model.
Days 1–30: Audit, Quick Wins, and Governance Foundation
The first 30 days are about understanding the current state, establishing credibility with quick wins, and laying the governance foundation that everything else will be built on. This phase is diagnostic and foundational—not transformational. Resist the temptation to redesign everything on Day 3.
Before hiring, work through the fractional CRO vs full-time comparison—it shapes the budget for everything you build here.
Week 1–2: The Revenue Audit
Before you build anything, you need to know what you’re working with. The audit covers four domains:
- Data quality assessment: How clean is the CRM? What’s the duplicate rate? How many contacts have valid email addresses? What percentage of deals have accurate close dates and amounts?
- Process mapping: Document every existing revenue process as it actually works (not how people think it works). Map the lead-to-close journey, the marketing-to-sales handoff, and the client success lifecycle.
- Tech stack inventory: Catalog every tool that touches revenue data. CRM, marketing automation, client success platform, BI tools, spreadsheets, one-off integrations—everything. Note what’s connected, what’s siloed, and what nobody uses.
- Stakeholder interviews: Talk to sales leadership, marketing leadership, client success leadership, and finance. Ask each team what data they need, what they don’t trust, and where their biggest operational pain points are.
Week 2–3: Quick Wins
Quick wins build credibility and buy you the political capital to make bigger changes in months two and three. Focus on visible, high-impact improvements that the revenue team will notice immediately:
- Fix the pipeline view: Clean up deal stages, remove dead deals, update close dates to reflect reality. Give sales leadership a pipeline they can actually trust.
- Build three essential dashboards: Pipeline summary, monthly revenue tracking, and lead/opportunity conversion rates. Keep them simple, accurate, and automated.
- Deduplicate the database: Run a deduplication pass on contacts and companies. This single action improves data quality, reduces confusion, and signals that someone is finally taking care of the CRM.
- Fix one broken integration: Identify the integration that causes the most daily frustration and fix it. Whether it’s a Slack notification that doesn’t work or a form submission that doesn’t create a contact, fixing one visible pain point establishes trust.
Week 3–4: Governance Foundation
Governance is Day 1 priority because everything you build in months two and three depends on it. Without governance, you’re building a house on sand. Establish the rules of the road now—before the team develops habits around the new processes. For a comprehensive governance framework, see our CRM Governance Framework guide.
- Naming conventions: Standardize how campaigns, lists, workflows, templates, and properties are named. This sounds trivial. It prevents 80% of the organizational chaos that plagues mature CRM instances.
- Required fields and data entry standards: Define what information must be captured at each stage of the revenue process. Make critical fields required at the system level, not optional.
- User permissions architecture: Design who can see what, who can edit what, and who can delete what. Don’t give everyone admin access and hope for the best.
- Change management process: Establish a lightweight process for requesting and approving changes to the CRM configuration. Even a simple intake form prevents the “too many cooks” problem.
Days 31–60: Process Design, Tool Configuration, and Reporting
The second month is where the real building happens. The audit told you what’s broken. The governance framework gave you the rules. Now you design the processes and configure the tools to support them.
For PE-backed companies building from scratch, our fractional RevOps PE playbook layers portfolio-level standards on top of this foundation.
Sales Process Standardization
- Define pipeline stages with clear entry and exit criteria
- Establish deal progression requirements—what must be true before a deal moves to the next stage
- Build the forecast methodology: weighted pipeline, commit categories, deal scoring
- Create the sales playbook: qualification criteria, discovery framework, objection handling
- Implement activity tracking standards: what gets logged, where, and by whom
Marketing-to-Sales Handoff
- Define MQL criteria and the lead scoring model
- Build the lead routing logic—round robin, territory-based, or account-based
- Establish the SLA: how fast sales must follow up, what constitutes a valid attempt, when leads recycle
- Create the feedback loop: how sales reports lead quality back to marketing
Reporting Infrastructure
- Build the executive dashboard: pipeline health, revenue attainment, forecast vs. actual
- Build team-level dashboards: activity metrics, conversion rates, deal velocity
- Build the board reporting package: standardized format that pulls automatically from the CRM
- Establish reporting cadence: daily pipeline review, weekly revenue review, monthly board prep
Tool Configuration and Integration
- Configure the CRM to match the new processes—custom properties, required fields, deal stage criteria
- Connect marketing automation to the CRM with proper field mapping and sync rules
- Integrate the client success platform for unified lifecycle reporting
- Consolidate or eliminate redundant tools identified in the audit
Days 61–90: Automation, Optimization, and Team Enablement
The third month is about scaling what you built in month two. Processes are documented and working. Tools are configured and integrated. Now you automate the repeatable parts, optimize based on early data, and enable the team to operate the system without constant hand-holding.
By day 90 you'll need to decide on headcount—see our RevOps compensation 2026 benchmarks to budget accurately.
Workflow Automation
- Lead routing automation: Automatic assignment based on territory, round robin, or account ownership
- Deal progression alerts: Notifications when deals stall, age past threshold, or miss activity targets
- Lifecycle stage automation: Automatic progression from subscriber to MQL to SQL based on behavior and scoring
- Task creation: Automated task assignment when specific triggers fire—new deal created, contract renewal approaching, client health score drops
- Data hygiene automation: Scheduled workflows that flag duplicates, identify incomplete records, and enforce data standards
Early Optimization
- Review the first 60 days of data against baseline metrics from the audit
- Identify which process changes are driving improvement and which need adjustment
- Refine lead scoring based on actual conversion data instead of assumptions
- Adjust dashboard KPIs based on what leadership actually uses versus what goes ignored
Team Enablement and Training
- Sales team training: CRM usage standards, pipeline management expectations, reporting access
- Marketing team training: Campaign setup processes, lead management workflows, attribution tracking
- Leadership training: Dashboard navigation, forecast methodology, data interpretation
- Documentation: Process playbooks, system guides, and FAQ documents that enable self-service for common questions
Common Mistakes When Building RevOps from Scratch
Most RevOps builds fail for the same reasons. Avoid these and you’re already ahead of 80% of companies attempting the same journey.
- Automating before documenting: Automating a broken process just breaks things faster. Document the process, run it manually until it works, then automate.
- Boiling the ocean: Trying to fix everything in the first month leads to burnout and half-finished initiatives. Pick the highest-impact problems, solve them completely, then move on.
- Ignoring change management: The best-designed process is worthless if the team won’t use it. Invest in training, communicate the “why” behind every change, and make it easier to follow the new process than to work around it.
- Building for today only: Design systems that can handle 3–5x your current volume. Adding two more reps shouldn’t require a CRM redesign.
- No executive sponsor: RevOps changes touch every revenue team. Without a C-level champion who enforces adoption, every process change is optional—and optional processes don’t get followed.
- Hiring too senior too early: You don’t need a $300K VP to build the foundation. A strong manager or a fractional leader can build the infrastructure, and then you hire the VP to scale it. See our maturity model for the right hire at each stage.
Frequently Asked Questions
How do you build RevOps from scratch?
Build RevOps from scratch using a phased 30-60-90 day approach. Days 1–30: audit current state, establish data governance, and deliver quick wins. Days 31–60: design standardized processes, configure tools, and build reporting infrastructure. Days 61–90: automate workflows, optimize based on early data, and train the team. The critical rule is to never automate before you have clean data and documented processes.
What should a RevOps team do in the first 90 days?
In the first 90 days, a RevOps team should: complete a full revenue operations audit (weeks 1–2), deliver quick wins like pipeline cleanup and essential dashboards (weeks 2–3), establish governance foundations (weeks 3–4), design and implement standardized sales processes and reporting (month 2), then automate, optimize, and train the team (month 3). Prioritize foundation over sophistication.
What is a 30-60-90 day plan for a new RevOps leader?
A new RevOps leader’s 30-60-90 plan: First 30 days—audit data quality, map existing processes, inventory the tech stack, build credibility with quick wins. Days 31–60—standardize the sales process, build marketing-to-sales handoff SLAs, configure reporting infrastructure, integrate core systems. Days 61–90—automate repeatable workflows, optimize based on early metrics, train all revenue-facing teams, and document everything for sustainability.
What should a company’s first RevOps hire focus on?
A company’s first RevOps hire should focus on three things: data quality and governance (clean the CRM and establish rules to keep it clean), process standardization (document and enforce the lead-to-close process), and reporting (build dashboards the leadership team actually uses). Avoid chasing automation, AI, or advanced analytics until these foundations are solid. The first hire should be a strong operator, not a strategist.
Start Building. The Runway Is Shorter Than You Think.
Every month without revenue operations is a month of compounding data debt, process entropy, and missed opportunity. The 90-day playbook gives you the fastest path from zero to operational—but only if you start. The companies that win don’t wait for the perfect hire or the perfect moment. They build the foundation now and refine it as they grow.
Book a Discovery Call to discuss how Squad4 helps companies build RevOps from scratch—with fractional leadership that brings the playbook, the experience, and the team to execute it. Or explore Mission Control on Launchpad to see the 90-day transformation in action.