Technical Revenue Operations Consultant

Why this role exists We’re a RevOps consulting partner. Our clients usually don’t come to us saying, “our revenue architecture is broken.” They say things like: • “Our pipeline numbers don’t match.” • “Marketing says they generated the lead, Sales says they didn’t.” • “Reps aren’t updating Salesforce.” • “Leads are going to the wrong people.” • “We have six tools doing roughly the same thing.” • “Finance doesn’t trust the forecast.” • “We need another field.” Your job is to figure out what’s actually broken. You’ll work across people, process, data and technology to understand how revenue moves through a business, design a better way of operating, and turn that design into systems that actually work. You’ll own projects from discovery through implementation and get hands-on with the technology along the way. What makes this different We run an AI-assisted delivery model. Approved designs become structured build specifications that can be executed across our delivery team and increasingly through AI-assisted build agents — from data models and automation through QA and UAT. That changes the role of the consultant. Your job isn’t to become a ticket-writing middleman. You need to understand the business problem well enough to design the solution and the technology well enough to know whether it will actually work. Your specification is part of the product. A requirement like “automatically route leads to the correct rep” isn’t finished. What determines the correct rep? Territory? Segment? Account ownership? Geography? Product? Existing relationship? What happens when two rules match? What happens when none match? Precision matters. We want AI doing the repetitive work, not the thinking. You should spend more of your time on discovery, architecture, experimentation, clients and difficult problems — and less time manually creating the same 40 fields. What you’ll do • Run discovery across Sales, Marketing, Customer Success, Finance, Operations and leadership • Map how revenue actually moves through the business — from first touch through lead, opportunity, customer, expansion and renewal • Identify operational problems, revenue leakage, unnecessary manual work and gaps between teams or systems • Translate business requirements into technical solutions across CRM, marketing automation, sales technology, customer success and data platforms • Design lifecycle architecture — stages, statuses, qualification criteria, conversion points, handoffs and ownership • Design lead and account management — routing, scoring, enrichment, deduplication, assignment, territories and SLAs • Design sales processes — pipeline stages, opportunity architecture, forecasting, activities, approvals and rep workflows • Design marketing operations — campaign structure, attribution, lead capture, scoring, nurture, segmentation and marketing-to-sales handoff • Design customer lifecycle processes — onboarding, account management, expansion, renewal, churn and Customer Success handoffs • Build automation across systems using tools such as Salesforce Flow, HubSpot Workflows, n8n, Make, Zapier and APIs • Design integrations between CRM and the wider GTM stack • Build reporting and dashboards that leadership can actually use to run the business • Audit existing technology stacks and recommend what to keep, replace, consolidate or remove • Clean up messy CRM estates — duplicate fields, broken automation, inconsistent lifecycle stages, poor data and accumulated technical debt • Write technical specifications covering data models, fields, automation, integrations, permissions, migration requirements and test scenarios • Get hands-on with implementation where it matters • Own testing, UAT, deployment and adoption with the client • Support pre-sales through discovery, solution shaping, technical scoping and estimates What you need Revenue Operations You understand RevOps as an operating model, not a collection of software tools. You understand how Marketing, Sales, Customer Success and Finance connect and where processes commonly break between them. You’re comfortable working across: • Lead-to-revenue • Marketing-to-sales handoff • Lead and account lifecycle management • Pipeline management and forecasting • Territory and ownership models • Customer lifecycle • Expansion and renewal • Attribution • Data quality and governance • Reporting and analytics • GTM systems architecture You should be able to take a whiteboard and draw how revenue moves through a business before opening Salesforce. CRM You need strong hands-on experience with at least one major CRM. Salesforce is strongly preferred. HubSpot experience is valuable. You understand: • CRM data models • Leads, Contacts, Accounts and Opportunities • Custom objects and relationships • Lifecycle and stage architecture • Fields and validation • Routing and assignment • Automation • Permissions and security • Reports and dashboards • Data migration • Integrations You don’t need to be a Salesforce developer, but you shouldn’t be afraid of opening an org and figuring out what’s happening. Marketing Operations You understand how marketing systems connect into the wider revenue engine. Experience with platforms such as HubSpot, Marketo, Account Engagement (Pardot) or Marketing Cloud is valuable. You understand forms, campaigns, scoring, segmentation, nurture, consent, attribution and lifecycle management. Most importantly, you understand what happens to the data after somebody clicks Submit. Sales Technology You’re comfortable working with the wider GTM stack. That might include tools such as Gong, Outreach, Salesloft, Apollo, ZoomInfo, Clay, LinkedIn Sales Navigator, Calendly, Chili Piper and other sales engagement or conversation intelligence platforms. We don’t expect you to have used every tool. We do expect you to understand the problems they’re trying to solve and how they should interact with the CRM. Automation