Building a Dynamic GTM Tech Stack A conversation with Jamie Edwards, Former Head of GTM Operations & Tools at Gusto. Executive summary This blog distills Jamie Edwards’ playbook for building a go-to-market stack that delivers measurable impact. You will learn how to organize sales, marketing, and customer success operations under a single RevOps structure, evaluate software by fit to process rather than hype, and design systems that seasoned enterprise sellers will actually use. Jamie explains what belongs in the CRM versus the data warehouse, how to tag buying roles for cleaner handoffs, and why perfect attribution remains unsolved but manageable with clear context. A Gusto routing case illustrates time returned to ops as valid ROI. Practical takeaways include a vendor scorecard, adoption guardrails, a write-back policy, an AI use-case matrix with human checkpoints, and a 90-day rollout plan that moves from strategy baseline to AI pilots. Facebook Twitter Youtube The Big Idea A durable GTM stack starts with a clear operating model, not with a shopping list. Integrate sales, marketing, and customer success operations under one roof, select tools to amplify what already works, design for frontline adoption, and centralize data with context so AI can enhance rather than replace human judgment.  “Start with a strategy that would still work if all the tools went dark. Then add software to amplify what already works.” Why RevOps is a Structure, Not a Label Jamie pushes back on the casual use of the term RevOps as a job title applied to everyone. In his view, only a handful of leaders truly run revenue operations end to end. Under them sit specific functions: sales operations, marketing operations, and CS operations. When these teams sit together, tool decisions get better, data flows improve, and handoffs tighten. What this looks like in practice: Marketing ops inside RevOps, not inside brand or demand teams CS ops aligned with sales ops, since account management and customer success motions mirror each other Shared system ownership and shared technical roadmap across the funnel https://www.youtube.com/watch?v=i5y4QS7qHVc Tool Evaluation: Popular Is Not a Strategy Jamie estimates only marginal capability differences among top tools within a category. The point is not to chase the flashiest features. The point is to choose the tool that strengthens your motion without breaking your ecosystem.  “There is maybe a one to two percent difference among the best tools. Buy the fit for your motion, not the sizzle.” A checklist for tool decisions: Start with your non-negotiables: which processes are proven and will not change Map the work, not the logos: define the seller or CSM job to be done step by step Score for integration first: how cleanly it writes to the CRM and to your warehouse Price the ops time: if a tool returns hours to ops and analytics, count that as ROI Decide the data home: CRM versus warehouse, avoid muddy write-backs Run a kill-switch test: if the tool disappeared, would the process still stand Creating a GTM Tech Stack From Scratch Jamie would anchor on a strong CRM, then add selectively. CRM as the operational hubThe place sellers organize their day, leaders inspect pipeline and activity, and ops runs hygiene and routing. Do not name-chase. Pick what your team can maintain. Cadence management depends on segment High velocity teams can often keep it simple in the CRM Enterprise motions benefit from cadence tools for multi-threaded, multi-meeting pursuits Delay heavy BI until the data merits itStart with CRM reporting. Add BI when cross-system analysis becomes essential. Adoption is a Product Problem Veteran enterprise sellers resist rigid sequences that ignore account nuance. Edwards’ advice is to treat sellers like artists and give them the right canvas with sensible guardrails.  “Let the artist be an artist. Provide the canvas and paint, then set guardrails.” Framework: Guardrails over Handcuffs Standardize: global steps, minimum activity baselines, shared libraries Personalize: allow custom sequences for named accounts, adjustable spacing, manual steps Instrument: capture step outcomes, replies, meetings set, conversion by step and persona Coach: use CI notes and call outcomes to tune personal cadences rather than force one pattern Checklist: Designing for Adoption Give tenured reps a custom sequence budget per quarter Add skip and pause controls tied to account context Track usage and results, then publish a quarterly “best of” library Connect sequences to calendar tasks and pipeline stages so reps do not tab-hop Avoid compliance traps that punish reasonable deviation Data Strategy: What Belongs in the CRM, What Belongs in the Warehouse Jamie cautions against dumping everything into the CRM. Storage and performance costs are real, and some AI use cases require a cleaner warehouse layer. Attribution and the “Billion Dollar” Problem Perfect attribution across MAP, ABM, cadence tools, CI, CS platforms, and CRM remains elusive. Jamie’s guidance is to be explicit about what you credit, be consistent, and document the context behind spikes and dips that models miss. Attribution Model Selector: Use last-touch for campaign optimization and in-period lift Use position-based for budget allocation across early nurture and late stage influence Use multi-touch custom for executive reporting where sales assists and partner referrals matter Always add a context note in the deck that explains macro events or GTM shifts Case Study: Dynamic Lead Routing That Paid for Itself Gusto faced complex routing logic for small businesses, with many edge cases and time-boxed SLAs. Manual bucketing by ops burned hours and slowed responses. A dynamic routing tool reclaimed that time.  “Freeing hours from sales and marketing ops is a valid ROI. Those teams are force multipliers.” ROI Calculator Template: Dynamic Routing Inputs Number of inbound leads per week Current manual triage time per lead in minutes Ops hourly fully loaded cost SLA breach rate, pre and post Outputs Hours returned to ops per week Cost saved per quarter Lift in SLA attainment and first-touch speed Expected impact on conversion to meeting The First 90 Days: A Practical Plan Week 1 to 3: Strategy and System Baseline Map current motions, identify three non-negotiable processes Inventory tools, owners, contracts, write-backs

A 30-60-90 Day Playbook for First-Time RevOps Leaders A conversation with Hassan Irshad, Director of RevOps at FEVTutor. Revenue Operations (RevOps) isn’t just a support function anymore. It’s the strategic engine that powers alignment, productivity, and visibility across the go-to-market (GTM) teams. And for first-time RevOps leaders stepping into the role, the first 90 days are absolutely critical. Your success depends on how well you can listen, diagnose, align, and act. In this deep-dive, Hassan Irshad—former Director of RevOps at FEVTutor and a veteran in building RevOps functions from the ground up across multiple B2B SaaS organizations—shares a tactical, proven playbook for the first 90 days in the job. Structured into three phases, this playbook helps new leaders set up a high-impact, scalable RevOps engine. Facebook Twitter Youtube Phase 1: The First 30 Days — Discovery and Trust-Building Hassan calls this the “Discovery Phase,” and it’s arguably the most important segment of your 90-day plan. Here, the goal isn’t to solve every problem. It’s to understand the lay of the land, build stakeholder trust, and uncover real pain points. “Think of yourself as a doctor. If you don’t listen well enough, you’ll misdiagnose the pain.” Start by meeting with stakeholders across departments: Sales, Marketing, Customer Success, Finance, Product, and HR. Identify their KPIs, their blockers, and their goals. Create a document that captures all your findings—Hassan refers to this as the “Lay of the Land” doc. At the same time, shadow end users. Sit with BDRs, AEs, and CSMs. Watch how they use tools. How do they enter data? Where do they get stuck? Walk through your CRM. Is reporting intuitive or a tangled mess? Don’t stop there. Run a detailed tech stack audit. Map every tool in the ecosystem. What integrates with CRM? What’s shelfware? What’s overused or underused? Hassan emphasizes talking to users, not just system owners. You should also: Immerse yourself in the product: attend demos, listen to sales calls. Map existing processes: selling, onboarding, renewals. Identify low-hanging fruit for early wins: improve field logic, add help text, or train users on hidden CRM features. Key Objectives: Establish trust Conduct a stakeholder audit Perform a tech and process audit Map current workflows Identify quick wins 💡 Action Items: Task Description Stakeholder Interviews Meet leaders from Sales, Marketing, CX, Finance, HR, and Product. Understand their KPIs, pain points, and top priorities. Create a “Lay of the Land” Document A central repository of org structure, current GTM processes, key workflows, and metrics. Shadow GTM Teams Sit with BDRs, AEs, and CSMs to understand how data is entered, how tools are used, and where bottlenecks occur. Tech Stack Audit List every tool in use, usage rates, integrations, costs, redundancies, and gaps. Process Mapping Map the end-to-end selling, marketing, and renewal processes. Identify handoffs, duplication, and inefficiencies. Product Immersion Attend a demo, listen to sales calls, and understand the sales pitch and product-market fit.   ✅ Quick Wins Template: Win Type Example Usability Fix Clarify error messages in CRM workflows Dashboard Build Build a simple commissions dashboard for reps Training Conduct a quick session on a misunderstood feature Phase 2: Days 31-60 — Alignment and Control This is the phase where you start “flexing your RevOps muscles,” as Hassan puts it. While discovery continues in some areas, you now begin putting controls and alignment mechanisms in place. Hassan calls this phase “Alignment and Control.” “You need to be the catalyst for cross-functional collaboration. Nobody else is connecting the dots across sales, marketing, and CX.” Start with KPI alignment. You’ll have already collected the individual KPIs in Phase 1. Now, assess whether those KPIs roll up into the broader company strategy. If they don’t, that’s a red flag—and your opportunity to bring the teams together. Hold cross-functional syncs to align Sales, Marketing, and CS around shared quarterly goals. Create dashboards and reporting frameworks that reflect this shared accountability. Also, start implementing operational controls: Are close dates in CRM accurate? Is forecasting behavior consistent? Are stage definitions clear? Don’t impose controls abruptly. Hassan suggests using logic and transparency. Example: If a rep uses spreadsheets to track deals, propose a CRM-based inline-editable report that feels like a spreadsheet but ensures visibility. And begin vetting your tools: Is a forecasting tool duplicating features available in Salesforce? Are reps logging into a tool? Can licenses be consolidated? Key Objectives: Improve GTM team collaboration Put control mechanisms in place Begin strategic alignment Validate process improvements 💡 Action Items: Task Description Cross-Functional Alignment Facilitate regular syncs between Sales, Marketing, and CX to align on quarterly goals. KPI Rationalization Align individual department KPIs with the company’s strategic objectives. Identify siloed or conflicting goals. Governance Setup Define request intake processes, project documentation standards, and response SLAs. Control Implementation Use logic and data to drive compliance (e.g., inline editable reports to update close dates instead of spreadsheets). Change Management Prep Identify stakeholders who will sponsor or resist change. Begin conversations to create buy-in. https://www.youtube.com/watch?v=sVDJ9KI1tGw&t=1343s Phase 3: Days 61-90 — Vision and Execution By now, you’ve earned trust, understood the landscape, and started building momentum. Phase three is about turning that momentum into long-term strategy and execution. Hassan calls this the “Vision and Execution” phase. “You’re now setting the foundation for your long-term roadmap. Think beyond tickets—think strategy.” At this point, you should be ready to publish a two-quarter RevOps roadmap. This roadmap includes: Strategic initiatives tied to revenue goals Operational improvements already underway Planned enhancements to the tech stack This is also the time to start tracking and showcasing impact. Go back to the baselines you gathered in Phase 1. Show how time-to-insight improved, or how a forecast accuracy initiative reduced missed commits. Make your work visible. Remember, this is also where change management becomes critical. Stakeholders may resist new processes. Hassan advises using your discovery-phase insights to preempt resistance. Understand their motivations and frame changes as value drivers. Key Objectives: Publish a roadmap Begin implementation Showcase wins Plan for continuous improvement 💡 Action Items: Task Description Publish a RevOps