Revenue operations consulting is the practice of bringing in an external team to audit, redesign, and operate the systems that connect how your company generates revenue. For product companies doing $2M to $20M, this means connecting the dots between marketing spend, sales activity, order management, fulfillment, and financial reporting into a single, measurable system. When those dots are not connected, revenue leaks through the gaps. When they are, every dollar of growth effort is visible, attributable, and compounding.
This guide covers what a revenue operations strategy actually looks like for product companies, why the SaaS-centric RevOps playbook does not apply to businesses that ship physical goods, what a consulting engagement looks like in practice, and how to decide whether your company needs external RevOps consulting or an internal hire.
What Revenue Operations Actually Means
Revenue operations is the function that connects sales, marketing, and customer success into a single system with shared data, shared goals, and shared accountability. The term originated in SaaS, where companies realized that having separate operations teams for marketing (marketing ops), sales operations (sales ops), and customer success (CS ops) created silos that hurt revenue growth. If you have heard of sales operations consulting, RevOps is the evolution: instead of optimizing the sales function in isolation, a revenue operations strategy connects every revenue-generating function into one system.
RevOps eliminates those silos by creating one team, one data model, and one set of metrics that span the entire revenue lifecycle.
The RevOps Mandate
A RevOps function is responsible for four things:
1. Process design. How does a lead become a customer? How does a customer become a repeat buyer? Every handoff between departments should be documented, measured, and optimized. Process design answers: what happens, in what order, and who is responsible at each step?
2. Technology management. Your CRM, ERP, ecommerce platform, marketing automation, analytics tools, and reporting dashboards are the infrastructure of revenue. RevOps owns the configuration, integration, and maintenance of this stack. Not IT. Not individual departments. One team that sees how all the pieces connect.
3. Data integrity. If marketing says revenue is $1.2M this quarter and finance says it is $1.05M, you do not have a revenue number. You have two guesses. RevOps establishes the single source of truth: where data lives, how it flows between systems, and what definitions are used across the organization.
4. Analytics and reporting. Dashboards that show what happened are table stakes. RevOps builds reporting that answers why it happened and what to do next. Attribution modeling, pipeline velocity analysis, channel performance, and customer lifetime value are RevOps outputs, not just marketing or finance outputs.
What RevOps Is Not
RevOps is not a new name for sales ops. It is not CRM administration. It is not a tool or a piece of software. It is not a strategy deck.
RevOps is an operating model. It is the decision to manage your revenue-generating functions as one connected system instead of three or four independent departments. The consulting engagement is what gets you from the current state (disconnected, manual, siloed) to the target state (integrated, automated, measurable).
Why Product Company RevOps Is Different
Most RevOps content on the internet is written for SaaS companies. SaaS RevOps focuses on pipeline management, subscription billing, churn reduction, and product-led growth metrics. If you are a product company reading that content, roughly half of it does not apply to your business.
Here is why.
You Have Physical Operations
A SaaS company’s “fulfillment” is turning on an account. A product company’s fulfillment involves inventory management, manufacturing or sourcing, warehousing, shipping, returns, and warranty. The systems that manage these operations (ERP, WMS, 3PL integrations) are not part of the SaaS RevOps playbook, but they are central to yours.
Revenue operations for a product company must connect the marketing and sales data (CRM, ad platforms, email/SMS, website analytics) to the operational and financial data (ERP, inventory, fulfillment, accounting). Without that connection, you cannot answer the most important question in your business: when I spend a dollar on marketing, how much net profit does it generate after cost of goods, fulfillment, and returns?
Your Revenue Channels Are More Complex
A SaaS company typically sells through one or two channels: direct sales and self-serve signup. A product company might sell through direct-to-consumer ecommerce, wholesale, marketplace (Amazon, Walmart), dealer networks, trade shows, and phone/email orders. Each channel has its own data source, margin structure, and customer acquisition cost.
RevOps for product companies means building a reporting layer that normalizes revenue data across all these channels so you can compare apples to apples. What is the customer acquisition cost for a D2C customer versus a wholesale account? What is the lifetime value of a marketplace buyer versus someone who came through your website? These questions are unanswerable without RevOps infrastructure.
Your Data Lives in More Systems
A SaaS company might run on five core systems: CRM, billing, product analytics, marketing automation, and a support tool. A product company typically runs on twice that: ecommerce platform, CRM, ERP, warehouse management, shipping/3PL, marketplace integrations, POS (if retail), marketing automation, ad platforms, and accounting software. Some of these systems were designed to talk to each other. Most were not.
The integration layer — the middleware and data pipelines that connect these systems — is the hardest and most valuable part of RevOps for product companies. It is also the part that SaaS-focused RevOps consultants are least equipped to handle.
Your Metrics Are Different
SaaS RevOps tracks monthly recurring revenue, churn rate, net revenue retention, and expansion revenue. These metrics do not apply to most product companies. Your metrics need to account for:
- Cost of goods sold (COGS) that varies by product, material costs, and manufacturing batch
- Inventory carrying costs that tie up capital
- Fulfillment costs that vary by channel, geography, and order size
- Return rates that differ dramatically by product category and channel
- Wholesale margin compression when selling through distributors or retailers
- Seasonality that can swing monthly revenue by 300% or more
RevOps for product companies means building reporting that tracks gross margin by channel, contribution margin by product, and customer profitability after all operational costs. This requires data from systems that SaaS companies do not use.
What a RevOps Consulting Engagement Looks Like
A RevOps consulting engagement for a product company follows a predictable arc. The specifics depend on your starting point, but the phases are consistent.
The first deliverable is a clear picture of what you currently have: what systems are in place, how data flows between them (or does not), where manual processes create bottlenecks, and where data integrity breaks down.
- Tech stack inventory. Every tool that touches revenue data, who uses it, and how. This includes the tools people use informally (spreadsheets, shared drives, email threads).
- Data flow mapping. How does a lead get created? Where does the order go after a sale? How does fulfillment data get back to finance? Every handoff is documented.
- Process assessment. Where are the manual steps? How long do they take? What is the error rate? What would happen if the person who runs this process left tomorrow?
- Metrics review. What numbers does the team currently track? Where do those numbers come from? Do the same metrics match across different systems?
- Gap analysis. What can you not measure today that you need to measure? What decisions are being made on gut feel because the data is not available?
The output is a findings document that gives leadership a clear, honest picture of where the operation stands and what needs to change.
Based on the audit findings, the RevOps team designs the target state: the systems, integrations, processes, and reporting that the business needs to operate at its next stage of growth.
- Tech stack recommendations. Keep, replace, or add systems. Not change for the sake of change — only where the current tool genuinely cannot support the next phase.
- Integration design. What data needs to flow between which systems, in what direction, at what frequency. This is the blueprint for the middleware layer.
- Process redesign. Simplified, documented workflows that eliminate unnecessary manual steps. Each process has a clear owner and measurable output.
- Data model. Definitions for key entities (customer, order, product, channel) that are consistent across all systems.
- Reporting framework. What dashboards will exist, what metrics they will show, where the data will come from, and how often they will refresh.
- Implementation roadmap. Sequenced by business impact: what gets built first, what can wait, and what depends on what.
This is where the designed system gets built. Implementation is sequenced based on the roadmap from Phase 2, starting with the highest-impact, lowest-risk changes.
- CRM cleanup and configuration. Standardize fields, clean duplicate records, configure pipeline stages, set up automation rules for lead routing and deal progression.
- Integration development. Build the data pipelines that connect your CRM, ERP, ecommerce platform, and marketing tools. This is typically the longest workstream.
- Reporting and dashboards. Build the dashboards defined in the architecture phase. Start with the executive dashboard and work down to departmental views.
- Process deployment. Train teams on new workflows. Document standard operating procedures. Set up monitoring to catch process breakdowns early.
- Automation setup. Configure marketing automation flows, order routing rules, inventory alerts, and any other trigger-based workflows.
Implementation for a product company doing $5M to $15M typically takes 8 to 12 weeks when scoped properly. Companies with more complex tech stacks or multiple sales channels may need 12 to 16 weeks.
RevOps is not a project. It is an ongoing function. After the initial build, the consulting engagement shifts to operation, monitoring, and continuous improvement.
- Dashboard monitoring. Weekly review of key metrics, identification of anomalies, and investigation of root causes.
- System maintenance. Keeping integrations running, updating automations as processes evolve, managing CRM data quality.
- Quarterly optimization. Reviewing process performance, identifying new automation opportunities, and adjusting the strategy as the business evolves.
- New channel integration. When the business adds a sales channel (launches on Amazon, opens wholesale, adds a retail location), the RevOps layer expands to include it.
This is where the RevOps as a service model shines for product companies in the $2M to $20M range. A full-time RevOps hire costs $120,000 to $180,000 per year. An embedded consulting team delivers the same ongoing capability at $8,000 to $15,000 per month while also bringing cross-client experience and a broader skill set than any single hire.
The RevOps Tech Stack for Product Companies
The right RevOps stack depends on your business, but the categories are consistent. Here is what the typical mid-market product company needs and the common tool choices in each category.
CRM: The Customer Record
Your CRM is the system of record for every customer relationship. It tracks leads, deals, contacts, and account history.
Common choices: HubSpot (most common for companies in the $2M to $10M range), Salesforce (more common above $10M or with complex sales processes), Pipedrive or Close (for smaller, sales-led teams).
What RevOps configures: Pipeline stages mapped to your actual sales process. Custom properties for data your team needs (revenue range, product interest, channel). Automation rules for lead assignment, follow-up reminders, and deal stage progression. Integration with marketing tools for attribution.
ERP: The Operational Record
Your ERP manages inventory, orders, manufacturing (if applicable), purchasing, and accounting. For product companies, this is the backbone of the operation.
Common choices: NetSuite (most capable for mid-market), QuickBooks (for smaller operations), Sage (common in manufacturing), Odoo (open-source option), industry-specific ERPs.
What RevOps configures: Order flow from CRM to ERP (automated or streamlined). Inventory visibility for sales and marketing teams. Cost data that feeds into profitability reporting. Financial data that reconciles with CRM revenue data.
Ecommerce Platform: The Storefront
If you sell direct to consumer, your ecommerce platform generates transaction data that feeds into RevOps reporting.
Common choices: Shopify (most common D2C), WooCommerce (for companies needing more customization), BigCommerce (strong for B2B + B2C hybrid), custom builds (for complex configurator requirements).
What RevOps connects: Order data flowing to ERP and CRM. Customer data syncing between storefront and CRM. Marketing attribution from ad clicks to completed orders. Inventory levels reflecting across storefront and ERP.
Marketing Automation: The Nurture Layer
Marketing automation manages email flows, SMS campaigns, abandoned cart recovery, and lifecycle marketing.
Common choices: Klaviyo (strongest for ecommerce), HubSpot Marketing Hub (if CRM is HubSpot), Mailchimp (basic needs), ActiveCampaign (mid-market alternative).
What RevOps connects: Campaign performance data flowing to attribution models. Customer lifecycle stages syncing between CRM and automation platform. Revenue attributed to specific campaigns and flows.
Data Warehouse and Reporting: The Truth Layer
For companies outgrowing the built-in reporting of individual tools, a data warehouse centralizes data from all systems into one queryable location.
Common choices: BigQuery (Google Cloud, cost-effective for mid-market), Snowflake (more powerful, higher cost), PostgreSQL (self-managed, lowest cost). Visualization via Looker Studio, Metabase, or custom dashboards.
What RevOps builds: ETL pipelines that pull data from all source systems into the warehouse. Unified data models that reconcile customers, orders, and revenue across all channels. Dashboards that answer cross-system questions (marketing spend to delivered revenue, channel profitability, customer lifetime value by acquisition source).
Integration Middleware: The Glue
The middleware layer is what makes everything else work together. It handles data transformation, routing, and orchestration between systems.
Common choices: n8n (open-source, self-hosted, extremely flexible), Make (visual builder, good for moderate complexity), Zapier (simplest but limited for complex workflows), custom API integrations (when off-the-shelf tools cannot handle the logic).
What RevOps builds: Automated data syncs between CRM and ERP. Order routing workflows from ecommerce to fulfillment. Inventory level alerts and restock triggers. Customer data enrichment flows. Error handling and monitoring for all integrations.
How to Evaluate Whether You Need a Revenue Operations Strategy
Not every product company needs a RevOps consulting engagement. Some are too early. Some have the internal capability. Here is a framework for deciding.
- More time compiling reports than acting on them. If your Monday morning meeting starts with someone pulling data from three tools into a spreadsheet, your reporting infrastructure is not working.
- Can’t trace a marketing dollar to a delivered order. If someone asks “what was the ROI on our Google Ads last quarter?” and the answer takes a week of manual analysis, your systems are not connected.
- CRM and ERP disagree on basic numbers. If the revenue in your CRM does not match the revenue in your accounting system, you have a data integrity problem that RevOps fixes at the root.
- Growing but margins are shrinking. Revenue is up but profit is not keeping pace. This often signals operational inefficiency that RevOps provides the visibility to diagnose and fix.
- About to add a sales channel. Building the RevOps infrastructure before the new channel launches is dramatically cheaper than retrofitting after.
- Manual processes are creating errors. Orders get entered wrong. Customers receive incorrect invoices. Inventory counts are off. These are symptoms of disconnected systems.
- You are under $1M in revenue. Focus on product-market fit and sales. RevOps infrastructure at this stage is premature optimization.
- You sell through one channel with simple operations. If you run a Shopify store with Klaviyo and ShipStation, and all three tools work well together, you may not need more than that right now.
- You have a strong internal ops person who just needs tools. If you have someone with the skills and authority to do this work, they may just need a budget for tools and integration development, not a consulting engagement.
RevOps Consulting vs. Internal Hire
The decision between hiring a RevOps consultant and hiring a full-time RevOps person comes down to three factors:
Breadth of skills needed. RevOps requires CRM administration, data engineering, business process design, analytics, and project management. It is rare to find one person who does all of this well. A consulting team brings the full skill set from day one.
Speed of impact. An internal hire needs 3 to 6 months to onboard, audit, and start making changes. A consulting team with cross-client experience can compress this to 3 to 5 weeks because they have seen the patterns before.
Cost. A full-time RevOps hire at a product company costs $120,000 to $180,000 per year in total compensation. A consulting engagement costs $96,000 to $180,000 per year but delivers a team (not just one person) and can be scaled up or down as needs change.
For most product companies in the $2M to $20M range, the consulting model wins on all three factors until the company reaches the point where it needs a full-time internal RevOps team (typically $15M+ with 50+ employees). At that point, the consulting engagement often transitions to a coaching and support role while the internal team takes ownership.
Getting Started
If you recognize your company in the signals above, here is a practical starting point:
List every tool that touches revenue data. Draw the connections between them (even if the connection is “someone copies data manually”). This is your current-state map.
Where is the most time wasted? Where do errors happen most often? Where do you lack visibility? This is your starting point for improvement.
How many hours per week does your team spend on manual data work? What is the error rate on orders or invoices? What revenue decisions are you making without data? These numbers build the case for investment.
RevOps for product companies is specialized work. The team you bring in should understand your industry, your systems, and the specific challenges of connecting marketing data to operational data in a business that ships physical products.
At Umbral, our operations team works with product companies to audit, architect, and implement the RevOps infrastructure that connects your revenue engine. We combine the process thinking with the technical build, covering CRM configuration, integration development, data warehousing, and reporting dashboards. If your operations are the bottleneck between where you are and where you want to be, let’s talk about it.
For a deeper look at building the technical stack from scratch, see our guide on building a revenue operations stack. For companies where the quoting process is the primary bottleneck, start with our guides on configure price quote systems and automating the quote-to-cash cycle.