Field notes on CRM migrations, data governance, deliverability and the operational decisions behind reliable B2B SaaS growth.
Lead lifecycle stages are the defined statuses a contact moves through from first touch to closed revenue — typically from new lead, to marketing qualified, to sales accepted, to opportunity, to customer. Their job is simple: at any moment, everyone in the go-to-market team should be able to answer “who owns this record, and what happens to it next?”
Read the postCRM data hygiene is the ongoing practice of keeping customer records accurate, deduplicated, complete and consistently formatted — as a system with owners and cadences, not as a one-off cleanup project. That distinction is the entire subject of this article, because the cleanup-project version fails almost every time.
Read the postLead routing is the process — ideally automated — of assigning each new lead to the right owner, fast. Every routing system is answering three questions: *Is this lead real? Who should own it? How quickly did they act on it?* Most routing failures trace back to answering the second question elaborately while ignoring the first and third.
Read the postA RevOps audit is a structured review of the systems, data, processes and reporting that carry a lead from first touch to closed revenue — designed to find where records, handoffs and dollars are leaking. A good one produces three things: a prioritized list of what’s broken, an estimate of what each break costs, and a sequence for fixing them.
Read the postWhen the HubSpot–Salesforce sync breaks, it rarely announces itself. Leads keep arriving, dashboards keep rendering — and somewhere in the middle, records stop crossing, fields overwrite each other nightly, or two thousand sync errors pile up in a queue nobody has opened since spring. The damage shows up weeks later, as marketing and sales quietly diverge into two versions of the funnel.
Read the postIf your B2B emails started underperforming and someone said “check your authentication,” this is the missing briefing. SPF, DKIM and DMARC are three DNS records that prove your email is really from you — and since Google and Yahoo tightened bulk-sender requirements in 2024, they’ve moved from best practice to table stakes: senders above volume thresholds must authenticate with SPF, DKIM and DMARC, offer one-click unsubscribe, and keep spam complaint rates low, or watch mail get filtered or rejected outright.
Read the postUTM governance is the set of rules, vocabularies and enforcement mechanisms that make campaign tags consistent enough to report on — deciding what each parameter means, which values are allowed, who can create links, and how tags are captured in your CRM. It exists because attribution doesn’t fail in the dashboard. It fails months earlier, in a spreadsheet cell where one person typed LinkedIn, another typed linkedin, and a third typed li_paid.
Read the postThe short answer, for those mid-evaluation: **HubSpot generally wins for B2B SaaS companies under roughly 500 employees on ease of administration, time-to-value, and total cost of operation; Marketo retains real advantages for complex enterprise motions — deep Salesforce-centric architectures, elaborate multi-touch programs, strict regional/data-residency structures — where its flexibility justifies its overhead.** The decision hinges less on feature checklists than on one question: *do you have (and want to keep paying for) the specialist capacity Marketo assumes?*
Read the postAI in revenue operations, as practiced rather than pitched, means using language models and machine learning to do the funnel’s expensive manual work — researching accounts, enriching and normalizing records, summarizing conversations into CRM fields, and mining closed-lost text for patterns — inside guardrails that keep a human accountable for what enters the system of record.
Read the postThe short answer: a B2B SaaS company needs RevOps not at a headcount or ARR milestone, but at a **symptom threshold** — the point where deals, data and reporting start leaking value faster than ad-hoc fixes can patch, typically somewhere between ~15 and 50 employees or approaching the first few million in ARR. The better question than “when do we hire?” is “which symptoms do we have, and what’s the cheapest adequate response?” — because hiring is only one of four options, and it’s rarely the right first one.
Read the post
