RevOps Maturity with Matt Sinise

Matt describes this phase as the Wild West. Sales can be founder-led, systems remain manual and the business is still identifying its ideal customer profile, key personas and strongest use cases. RevOps should preserve agility, support quick frontline action and create fast feedback loops instead of over-engineering an unproven process.

Matt favours a simple CRM over spreadsheets, capturing only essential information without excessive fields or manual entry. Basic lifecycle and volume data establish useful habits. Customer-journey mapping and advanced planning can remain outside the CRM. These foundations also reduce future technical debt.

A first RevOps hire often works alone in a reactive environment, tackling fires and the most urgent requests. Matt says the immediate task is reliable measurement of revenue and a few top-level metrics. These include top-of-funnel activity, customer additions and other volume measures. Forecasting and reporting cadences can stay basic while learning continues.

The function should enable quick action without creating costly operational debt. Teams should track lifecycle stages, basic conversion rates, open and lost deals, contract value and revenue against goals. These foundations must work before deeper analysis. Otherwise, RevOps risks rebuilding the CRM when it should address larger scaling projects.

Matt cautions against investing disproportionately in acquisition, often when RevOps reports to a CRO or sales leader. Much of a company’s lifetime revenue sits with customers. RevOps should build KPIs across the journey, measuring volume, conversion and time through each phase. Its roadmap should follow the strongest business opportunities, not one department’s priorities.

Full-funnel visibility shows whether successful activity produces suitable customers. MQL volume alone cannot show how many leads become customers or achieve lasting success. Disconnected systems let teams blame one another. RevOps should connect stages, identify improvements and use downstream evidence to refine ICP and acquisition choices.

At this stage, organisations shift from reactive work to proactive, targeted execution. Matt says technology becomes more advanced, automation increases and teams segment accounts across the funnel. They can tier accounts, allocate resources, define sales processes and formalise handovers between marketing, sales and customer success. Information should follow customers across transitions.

Teams should continually review lead scoring, top-of-funnel work, sales execution and customer targeting. Specialisation risks narrowing each function’s focus to its own measures. Operational design should connect segments, qualification criteria and handovers across the customer journey. It should not make one team look more productive without attracting suitable customers.

Matt recommends weekly tracking against a top-down or bottom-up revenue plan. Leaders should focus on five to seven top-level KPIs. If one trails the plan, RevOps can investigate deeper to find the responsible segment, team or process. Measures include opportunity and SQL creation, customer additions, customer size, sales velocity, pipeline coverage, forecast accuracy, retention and churn warnings.

Efficiency and cohort analysis matter more as the model matures. Segment measures indicate profitability and resourcing, while cohorts show whether results improve over time. At scale, RevOps should run prepared weekly reviews, business reviews, forecasting and board reporting. Each cadence needs defined inputs, actions and purpose, helping teams expose issues early instead of exchanging unstructured updates.

Matt says effective RevOps teams manage roadmaps like product organisations. They plan quarterly around capacity, reserve some capacity for urgent fires and select larger priorities for the rest. Planning should involve go-to-market and enablement teams, not remain in an operational silo. A visible roadmap helps leaders compare new requests with current work and decide whether urgent items deserve priority.

Projects become longer and involve more stakeholders as organisations scale. Early teams complete small routing, reporting or process changes. Mature teams can undertake only one or two substantial quarterly initiatives. This shift demands proactive planning, project management and communication. RevOps leaders should also propose work linked to sales plans, marketing plans, KPIs and company goals.

At scale, more financial, contracting and legal systems connect around the CRM. Alerts and scoring models should return useful information to a central source. Matt stresses that each tool must address an underlying problem. Software adopted because a leader used it elsewhere can treat a symptom while adding implementation work, maintenance, cost and complications. Correcting the process can remove the need.

Readiness matters as much as functionality. A call-recording platform offers little value without practices and resources to use its insights. Syncing activity to the CRM alone does not justify the distraction. Refining the ICP or lead scoring can deserve priority. Matt asks whether implementation will improve customer experience or impact. If teams cannot act on or maintain its output, they should defer it.

Matt says Mural moved through growth at exceptional speed during the pandemic, leaving little time to implement processes thoroughly. Heavy inbound demand shifted attention to response time, routing and prospect handling instead of outbound development. Separate operational structures emerged when central RevOps lacked capacity. This contributed to top-of-funnel systems and processes that did not always connect cleanly with the customer journey.

Looking back, Matt would emphasise efficiency, profitability and business health over growth alone. That means earlier full-journey attention, greater customer-success investment and clearer separation of product-led and sales-led motions. Each needs its own journey, processes and segmented conversion analysis. Teams should find specific conversion or retention improvements instead of assuming doubled leads will double revenue.