Manager, Revenue Operations Systems

Job description

**About CoLab** At CoLab, we help mechanical engineering teams bring life-changing products to market years sooner. We build AI for engineers designing cars, medical devices, and jet engines. Products this complex aren't sketched and sent to production. Teams spend months on iterations, reviews, and tests, predicting how every part performs before anything is built. CoLab is where those reviews happen, and we capture the rationale behind every change. Other tools show what changed between versions. Only CoLab knows why. That's how our AI helps manufacturers like Bobcat, Triumph Motorcycles, and GE Appliances make better decisions, eliminate rework cycles, and get to market faster. Proudly based in St. John’s, Newfoundland, CoLab started with one customer in 2018. Since then we’ve raised a [$72M Series C](https://financialpost.com/pmn/business-wire-news-releases-pmn/ai-is-changing-engineering-colab-just-raised-72m-to-lead-the-transformation), been named the 57th fastest growing company in North America by Deloitte ([Fast 500™](https://financialpost.com/pmn/business-wire-news-releases-pmn/colab-ranked-number-57-fastest-growing-company-in-north-america-on-the-2025-deloitte-technology-fast-500)), signed multi-year [AI partnerships with companies like Bombardier](https://www.theglobeandmail.com/business/article-bombardier-signs-contract-colab-ai-software/), and grown to a team of 250+. **About the Role** The **Manager, Revenue Operations Systems** will be the technical backbone of CoLab’s revenue operations team. You’ll own the architecture, build, and integration of the tools and data model that Sales, Marketing, and Customer Success run on — and the reporting infrastructure that leadership uses to inspect the business. This is a hands-on ownership role, not an oversight role. You’ll design the data governance architecture alongside the SVP of Operations and then build it yourself. You’ll partner closely with a Revenue Operations counterpart who owns process, hygiene operations, and rep-facing enablement, and you’ll be the technical depth behind that partnership. #### **What you’ll do:** - Revenue tech stack ownership: - Own the implementation, integrations, workflow design, and ongoing management of the tools serving the revenue organization, including CRM (Salesforce), business intelligence (Tableau), sales engagement (Salesloft/Outreach), CPQ and quoting, conversation intelligence (Gong), data enrichment (ZoomInfo), product analytics (Mixpanel), internal app building (Retool), AI assistants, and the Slack and Google Workspace integrations that connect them. - Ensure all systems are optimized for performance and scale with the business, and stay aligned to how revenue teams actually work. - Technical Integrations: - Oversee integrations across the tech stack to ensure seamless data flow and functionality. - Own implementation and rollout once a tooling decision is made, including migration planning and cutover, partnering with IT on provisioning and security. - Process Automation and Optimization**:** - Develop and implement automation workflows to streamline revenue operations and measurably reduce manual work across Sales, Marketing, and CS. - Continuously evaluate systems for process improvement opportunities. - Data model and governance architecture: - Own the Salesforce data model and the governance architecture that protects it: object and field design, validation rules, required-field and stage-gating logic, permissions, and record-type structure. - Design governance standards in partnership with the SVP of Operations, then build and maintain the enforcement layer that makes those standards hold — so data quality is structural rather than dependent on cleanup after the fact. - Partner with Sales Operations, who maintains governance standards day to day and drives the rep behaviour that keeps data clean inside the architecture you build. - Build and maintain the reporting layer that powers the revenue operating cadence: pipeline health views (stage and aging flags, at-risk identification, segment benchmarks), forecast and quota attainment reporting, and GRR/NRR views. - Ensure reporting is accurate, accessible, and trusted without rework, including at the SLT and board level, and document data definitions so the business shares one version of the truth. - Request intake and systems debt: - Own the RevOps request queue: intake, triage, and prioritization of system, reporting, and data requests from across the revenue organization — balancing fast turnaround on transactional work against the architectural fixes that reduce the volume of requests over time. - Take on a standing backlog of systems debt, including enforcement gaps in the CRM (stage validation and required-field logic that doesn’t yet exist), price book consolidation and product SKU structure, field and product data that has drifted out of alignment, and manual provisioning workflows that should be automated. - Distinguish between requests that need a fix and requests that signal a structural problem, and make the case for the second when it’s the better use of time. - Adoption and enablement: - Collaborate with Sales, Marketing, and Customer Success to align system capabilities with business needs. - Provide training and assistance to teams on tools and best practices, and build reusable documentation and how-to assets. - Collaborate with Enablement to land system and process changes, anchoring them in how each team actually works day to day rather than in how the system is configured. - Tooling evaluation and rollout: own evaluation end to end — requirements, technical and integration assessment, security review, and business case. Sales Operations co-owns the decision and owns commercial negotiation with vendors. - Cross-functional project ownership: own operational initiatives that sit outside any single team’s ownership — for example a lead-to-close process audit across Sales and Marketing, or a reporting consolidation spanning CS and Sales — owning the project plan, stakeholder communication, and outcome, not just the technical execution. #### **What you’ll need:** - Experience: - 5+ years in revenue operations, sales operations, business systems, or a comparable systems-ownership role in B2B SaaS. - Track record as the primary owner of a revenue tech stack — not a contributor to someone else’s. - Technical Skills: - Deep Salesforce administration experience (Admin certification or equivalent): data model design, Flow, validation rules, permissions and sharing, and integration architecture. Apex or scripting experience is an asset, not a requirement. - Hands-on experience with Tableau or similar BI tools for advanced data visualization — dashboards the business relies on, not one-off reports. - Experience with a sales engagement platform such as SalesLoft or Outreach. - Experience integrating a revenue stack across tools, with an understanding of where data breaks between systems and how to prevent it. - Nice to have: CPQ or quoting configuration, Gong, ZoomInfo, Retool or similar low-code app building, Mixpanel or comparable product analytics, Chili Piper, Zendesk, HubSpot, and LinkedIn Sales Navigator. - Experience building revenue reporting: forecasting, quota attainment, pipeline health, and GRR/NRR. - How you work: - Excellent communication skills, with the ability to work cross-functionally with sales, marketing, customer success and finance teams. - Strong problem-solving abilities and attention to detail. - Ability to prioritize and manage multiple tasks in a fast-paced environment. - Focus on quality and rigor - assessing and surfacing impacts of changes before they are deployed - Ability to prioritize requests for development work based on business needs - Strong project management skills with experience championing cross-departmental initiatives. - Proven ability to drive adoption of systems and process change across Sales, Marketing, and CS — earning alignment without positional authority, and navigating friction directly rather than escalating or deprioritizing. - Fluency with how a B2B SaaS revenue organization runs: pipeline stages and exit criteria, forecast categories, segmentation, quota and comp mechanics, renewals, and GRR/NRR reporting.