Lead scoring used to feel like grown-up marketing. A neat little system that turned chaos into order. A tidy number that told sales who to call first. A dashboard that made everyone feel like the funnel was being managed by competent adults. And then real life happened. Buying committees got bigger. Intent got noisier. Forms got optional. Cookies got nerfed. Inboxes got hostile. Sales cycles became less linear and more like a drunken treasure hunt. Yet somehow, a lot of teams are still proudly running the same scoring model they built when people downloaded whitepapers for fun and marketing could pretend it “handed leads to sales” like a factory line. That’s why lead scoring now is often cosplay. Not because scoring is inherently bad, but because most scoring models are pretending the world works the way it did when the model was invented. Why your lead score is confidently wrong Most lead scoring systems break for three reasons. First, they’re built on activities that are easy to track, not activities that predict revenue. Email opens, page views, webinar attendance, “visited pricing page”, “downloaded asset”, “clicked CTA”. All observable. All measurable. Many only weakly tied to a buying decision. Second, they assume the buyer is a single person moving through a funnel. In reality, the person filling out the form is often not the person with budget. Sometimes they are not even the person with a problem. They might be a researcher, an intern, a manager asked to “look into it”, or someone collecting screenshots for an internal deck. Your model gives them 82 points and everyone panics, while the actual decision maker never touches your website. Third, they confuse engagement with intent. Engagement can be curiosity, education, boredom, or comparison shopping. Intent is “we have a problem, we are prioritising it, and we are moving towards a decision”. Most scoring models treat the first as a proxy for the second. That’s the fundamental lie. If you’ve ever watched an account rack up score like a slot machine and then ghost you completely, you’ve seen this lie in the wild. The hidden cost of lead scoring theatre Bad scoring isn’t neutral. It doesn’t just fail quietly. It actively wastes time and damages trust. Sales loses faith and starts ignoring anything marketing sends. Marketing then tries to “fix adoption” with enablement sessions, new dashboards, or another scoring tweak. That makes it worse, because the problem is not communication. The problem is the signal. Meanwhile, truly winnable opportunities sit in the shadows because they don’t behave like your model expects. They don’t click the right emails. They don’t fill the right forms. They might come in through a partner. They might show up in pipeline because a rep already has a relationship. Your model shrugs and calls them “low score”. And when leadership asks, “Why are we not converting more MQLs?”, the answer becomes a shrug wrapped in charts. The goal isn’t a better score. The goal is better prioritisation. So let’s talk about what actually predicts revenue now. What predicts revenue now: Fewer signals, better signals Revenue prediction in B2B isn’t about counting more clicks. It’s about identifying the conditions that exist when a deal is genuinely likely to happen. Those conditions are usually not individual behaviours. They’re patterns. And they’re often account-level, not lead-level. Think in terms of three layers: Fit : Should this account buy from you, in a realistic universe? Readiness : Are they in a buying window, or just browsing? Momentum : Are they moving forward in a way that resembles real deals you’ve won? Lead scoring usually over-indexes on layer two, and mostly measures the wrong thing. The best predictors combine all three. Predictor 1: Verified ICP fit that sales actually agrees with This sounds obvious. It’s not. Most teams have a “target customer” slide and a CRM full of everyone anyway. Fit is still the strongest baseline predictor of revenue, but only if you define it like you mean it. Fit is not “company size and industry”. That’s demographic cosplay, too. Fit is: Do they have the problem you solve, at the scale you solve it, with the constraints you can handle? If your scoring model can’t clearly separate “perfect fit but quiet” from “loud but wrong fit”, you’re going to keep feeding sales junk. Fit should be a gate. If fit is poor, you don’t “nurture harder”. You deprioritise and stop wasting time. Predictor 2: Buying group emergence, not individual activity Revenue happens when a group forms around a decision. So the question is not “Did Jamie click the pricing page?” The question is “Is a buying group forming inside this account?” Buying group emergence looks like: Multiple people engaging from the same domain within a short window. Engagement coming from different functions (for example, marketing plus ops plus leadership). One person’s activity causing another person to appear (forwarding, internal sharing, follow-on visits). Conversations that shift from “what is this?” to “how would this work for us?” A single person binge-reading your blog can be a fan. Or a competitor. Or someone building a business case they will never get approved. Three to six relevant people showing up within a month is the kind of pattern that starts to smell like revenue. And no, this doesn’t require creepy tracking. Even with imperfect tracking, you can observe account-level patterns: Domains, meeting attendees, inbound sources, and the pace of interactions across contacts. Predictor 3: Problem intensity signals, not content consumption Content consumption is often a lagging indicator of curiosity. Problem intensity is closer to a leading indicator of action. Problem intensity looks like: Operational disruption: Migration, re-org, new leadership, tool consolidation, compliance deadlines. Performance pressure: Pipeline targets missed, CAC creeping up, SDR efficiency dropping, conversion rates flat. Technical pressure: Systems breaking, data quality issues, workflow debt, integration failures. Internal urgency: Hiring for ops roles, firing agencies, changing tools, leadership mandates. These signals rarely show up as “clicked email #3 ”. They show up in conversations, in CRM notes, in support tickets, in inbound form fields, in job descriptions, and in the way prospects describe their situation. If your model can’t ingest these, at least design your process to capture them when they appear. A simple “why now?” field that sales actually fills, plus a few required dropdowns about current state, can outperform 50 points of email clicks. Predictor 4: High-intent actions that cost the buyer something A strong signal often has a cost. Not a monetary cost, but a time cost, a political cost, or a commitment cost. High-intent actions include: Requesting a tailored demo (not a generic “learn more”). Bringing colleagues to a call. Asking about implementation, security, procurement, or contract terms. Sharing internal constraints and timelines. Asking for a proposal, SOW, or business case help. Engaging in mutual planning: Next steps with dates, not vibes. These are harder to fake. They’re harder to do casually. If your scoring model treats “webinar attended” as equal to “introduced their IT lead”, you’ve built a points costume, not a revenue predictor. Predictor 5: Momentum patterns that match your won deals Most teams score leads as if every deal moves the same way. But you already have the answer to “what predicts revenue”: it’s in your closed-won history. Not as a generic attribution report. As a behavioural pattern. Take your last 30 closed-won deals and ask: What happened in the 30 to 90 days before the opportunity was created? Look for common sequences like: Multi-contact engagement followed by a consult request. A spike in product-related page views followed by a stakeholder call. Partner referral plus leadership attendee on call one. Pricing conversation within two meetings of first contact. Security review triggered early, not late. Then look at your last 30 closed-lost deals and ask: What did they do that looked promising but went nowhere? You will often find patterns that your score currently rewards, even though they correlate with failure. That’s a fun day. Momentum is not “more activity”. Momentum is “the right activity in the right order”. Replace “lead scoring” with “pipeline readiness” If you want a disruptive idea that actually works, stop calling it lead scoring. Call it pipeline readiness. This simple naming shift forces the right questions. Pipeline readiness asks: Is this person or account likely to enter pipeline soon, and if they do, is it likely to progress? That pushes you away from vanity engagement and towards decision conditions. Pipeline readiness is built from a small set of signals that you can defend in a room with sales leadership. And crucially, it’s not one number. It’s a simple classification that drives action. For example: Not ready : Wrong fit or no buying window. Warming : Fit is strong, early buying group signals. Active : Clear buying window, high-intent actions present. Sales engaged : Meetings happening, mutual plan forming. Give sales something they can understand without a training session. Give marketing something they can improve without inventing new points. The scoring model you can actually run without hating your life Here’s a practical approach that doesn’t require perfection. Step 1: Set a “fit gate” that blocks nonsense Create a fit classification based on a handful of fields that are stable: Segment (size band that matches your pricing and delivery). Use case match (the problem you actually solve). Environment match (tech, complexity, constraints). Exclusions (industries you don’t serve, geographies you can’t support, unrealistic budgets). Fit should be a simple label: strong, medium, weak. If you can’t confidently label fit, default to medium, not strong. Strong should be earned. Step 2: Track buying group emergence at the account level Stop pretending lead-level alone can guide prioritisation. Set up a rolling 14 to 30 day view of account engagement across contacts: Number of engaged contacts from the domain. Variety of roles engaged. Recency and frequency of meaningful interactions. Meaningful interactions are not all clicks. Weight things that indicate effort: Form submissions, meeting requests, product documentation, implementation content, pricing, comparison pages, and replies. If your tracking is imperfect, still do it. Imperfect account-level signals can outperform perfect lead-level vanity metrics. Step 3: Define 5 to 7 “high intent” events and treat them as sacred Pick a short list. No more than seven. These should be actions that are clearly tied to revenue outcomes in your world. Examples: Demo request with a real company email. Meeting booked that includes more than one attendee. Request for pricing, proposal, or security information. Reply that answers “why now?” Product trial activation plus meaningful usage milestone (if relevant). Then design your process so these events trigger immediate, human follow-up. Not a nurture email. Not a “wait until they hit 100 points”. If you can’t act on the event within a day, don’t pretend the score matters. Step 4: Bake “momentum” into your sales process, not just your dashboards Momentum is often captured in conversation, not clicks. So build lightweight capture into the workflow: A required field for timeline (even if it’s “unknown”). A dropdown for current solution or status quo. A simple “primary pain” field. A checkbox for “buying group identified” with a minimum of two named stakeholders. This is not admin theatre. It’s the information you need to predict revenue. If reps won’t fill it, that’s feedback: Either the fields are junk, or the process has no consequence. Fix that before you blame the CRM. The uncomfortable truth: The best predictor is still a good salesperson Marketing Ops can build cleaner signals, better routing, and smarter prioritisation. But you cannot automate your way out of fundamental sales quality. If sales follow-up is slow, inconsistent, or purely transactional, no scoring model will save you. If reps can’t diagnose pain, map stakeholders, and create urgency ethically, then the problem isn’t your score. It’s execution. The goal of pipeline readiness is to make good sales teams faster and more consistent, not to create “hot leads” that close themselves. So what should you do this week, not this quarter? Kill anything that feels like scoring for scoring’s sake. Then do three practical moves. First, audit your last 20 opportunities that became real pipeline and identify what happened immediately before they did. Not what your dashboards say. What actually happened. Second, reduce your scoring inputs. If your model uses 40 signals, you are not sophisticated. You are overwhelmed. Third, move from lead-level obsession to account-level readiness. If your business sells to buying committees and you are still scoring individuals like it’s 2014, you’re choosing to be wrong. You don’t need a perfect model. You need a model you can defend, a process you can run, and signals that match how revenue actually happens now. Because the job isn’t to create high-scoring leads. It’s to create deals. Discover our Services

AI in HubSpot is not a magic layer you sprinkle on top of chaos. It is more like a turbocharger. If the engine is healthy, you feel the lift immediately. If the engine is full of duct tape and mystery fluids, you just reach the next breakdown faster. The good news is you do not need a “perfect” portal to benefit. You need a set of foundations that make HubSpot reliable, predictable, and safe to automate. Do that, and the AI features become genuinely useful: Better routing, faster content drafts, quicker summaries, more consistent service responses, and fewer tasks that exist purely to keep humans busy. HubSpot’s current AI experience sits under its Breeze umbrella, including assistants and agents that work across marketing, sales, and service. The exact features available will depend on your subscription, region, and the feature itself, but the pattern is consistent: The best outcomes come from clean data, clear definitions, controlled access, and strong reference material.  Start with the boring truth: AI can only work with what you give it Most teams think their HubSpot issues are “ AI readiness ” issues. They are usually “ we do not agree on what anything means ” issues. If your lifecycle stages are used as vibes rather than definitions, nobody (human or machine) can make good decisions. If sales reps log activities in five different ways, any summary will be incomplete. If a single contact can be both “customer” and “open deal” with no rules for which wins, automation becomes a lottery. AI works best when your CRM behaves like a system, not a scrapbook. So your first foundation is not an AI setting. It is operational clarity. Foundation 1: Define your customer language (and lock it) AI gets better when your business is consistent. Consistency starts with shared definitions. The minimum set of definitions you need You do not need a dictionary of every edge case. You need a handful of “truth anchors” that everyone agrees on: Lifecycle stages : What triggers each stage, who owns the change, and what evidence is required. Keep it simple and auditable. Lead statuses : What each status means, what the next action is, and who is responsible. Deal stages : What must be true for a deal to move forward, and what data must be captured at each stage. Company ownership : When the company record is the source of truth versus the contact record. If you have those nailed down, you have created something precious: Context that does not change depending on who is looking at it. Then you make it enforceable. Use required properties at key moments, pipeline rules, and validation where appropriate. The goal is not to police people, the goal is to stop “creative interpretation” from leaking into your data model. Foundation 2: Make your data fit for automation, not just reporting Most CRM clean-up projects aim for prettier dashboards. AI readiness aims for dependable behaviour. You want your data to answer questions like: Can we trust this field enough to route a lead? Can we trust this stage enough to trigger a customer experience? Can we trust this source enough to measure performance? If the answer is “sometimes”, automation turns into support tickets. The practical fix: design for the decisions you want to automate Pick the highest value decisions you want HubSpot to make faster. Then work backwards to the data required. Examples: If you want an agent to resolve common support questions, you need a strong knowledge base and clear categorisation of issues. If you want automated lead qualification, you need consistent capture of company size, territory, intent signals, and a definition of what “qualified” means in your world. If you want sales summaries that actually help, you need activity logging that is standardised, plus key properties that capture deal reality rather than hope. HubSpot is increasingly building AI into features that rely on your CRM context, so the more structured and dependable that context is, the more you get out of it.  Foundation 3: Get serious about consent, sensitive data, and guardrails If your AI rollout ignores privacy, it will get blocked, quietly sabotaged, or turned off after one uncomfortable meeting. HubSpot has an AI Trust and safety approach that includes controls like data masking for personal information in select features. It also publishes information about its AI infrastructure and how it works with AI service providers. For example, HubSpot states it does not allow the AI service providers it uses for Subscription Services to train on customer data, and it aims to minimise retention, including “zero-day” retention where possible.  That said, you still need to govern what you put into HubSpot and how features are used. Your job: Decide what should never be used as input Create a simple rule-set for teams: What types of data are sensitive in your business? Which properties should be treated as restricted? Where should sensitive information live if it should not be in HubSpot at all? HubSpot’s own documentation notes that if you enable Sensitive Data, the sensitive data properties you create will not be used to train Breeze models. It also notes that other customer data in your account may be used to train Breeze models, and that you can opt out by contacting HubSpot.  So do not pretend this is a purely technical decision. Make it a policy decision, then configure around it. If you need to opt out, do it early, not after you have trained habits across the team.  Foundation 4: Fix your permissions model before you add more power AI makes it easier to act quickly. That is the point. But it is also the risk. If everyone can change lifecycle stages, edit key properties, create workflows, and rewrite templates, you do not have a CRM. You have a shared Google Doc with better branding. At minimum: Limit who can create and publish workflows. Limit who can edit critical properties, pipelines, and lifecycle settings. Use teams and partitioning where appropriate. Separate experimentation from production where possible. This is not about distrust. It is about protecting the system so you can move faster with confidence. Foundation 5: Build your “knowledge spine” (this is where agents win or fail) If you want AI to help customers, prospects, or your internal team, it needs reference material that is accurate and current. HubSpot’s Breeze Customer Agent is positioned as a way to qualify leads, answer questions, and resolve support issues 24/7, and HubSpot provides guidance on training and deploying it. It also announced expanded availability for Customer Agent via HubSpot Credits for Pro and Enterprise customers starting June 2, 2025.  None of that matters if your help content is thin, outdated, or written like it was created under duress. The knowledge spine is not “more articles” It is: A clear structure: categories, tags, and consistent naming. Coverage of the top issues: the questions customers ask repeatedly. A single source of truth: avoid three competing answers across PDFs, old pages, and random internal docs. A refresh habit: ownership, review cycles, and expiry rules. When that exists, AI becomes a multiplier. When it does not, AI becomes a confident way to spread confusion. Foundation 6: Stop treating integrations like plumbing AI readiness is integration readiness. Breeze is designed to work inside HubSpot, but it also benefits from a connected ecosystem, because your team’s reality is spread across email, calls, meetings, documents, and support conversations. HubSpot highlights that its AI capabilities can connect with your broader tools and use CRM context to help with meeting prep, content, and analysis.  If your integration layer is unreliable, your AI layer will inherit that unreliability. The foundations here look like: One integration owner per system. Clear field mapping and documentation. A change control process that prevents “quick fixes” from becoming permanent data damage. Monitoring for sync errors, duplicates, and unexpected overwrites. If you do not have this, you will spend your AI rollout explaining why “the system said” something that is not true. Foundation 7: Standardise activity capture (because summaries depend on it) Teams love the idea of automatic summaries, meeting prep, and record insights. Breeze Assistant is positioned to help with things like refining content, preparing for meetings, and summarising data inside HubSpot.  But a summary is only as good as the underlying trail. So decide: What counts as a meaningful activity? How do you log it? Where does it live? What must be captured after key moments like discovery calls, demos, and implementation milestones? This is where most teams need fewer fields and more discipline. Do not add fifteen properties for “completeness”. Add five that you will actually maintain, and design the process so they are easy to keep current. Foundation 8: Create a safe sandbox for experimentation AI features encourage experimentation. That is fine. It is also how production portals get trashed. Build a simple rule: Experiment in a controlled space. Publish changes through an agreed process. Document what you ship and why. If you have access to sandboxes or separate environments, use them. If you do not, create operational sandboxes: Test lists, test pipelines, and staging assets that do not touch live routing and reporting. Your goal is to make it easy to try things without making your CRM feel unstable. Foundation 9: Make brand voice a system, not a person Content generation is one of the first things teams try, because it is immediate. But “AI-ready content” is not about pushing a button for a blog post. It is about capturing what makes your content sound like you, then making it reusable. That means: Clear messaging pillars. Approved claims and proof points. A library of examples that represent your voice. Rules for tone by channel: support, sales outreach, marketing emails, landing pages. Then you build templates and prompts around those assets. Do that, and your drafts get closer to publishable. Skip it, and you get content that sounds like it was written by a polite stranger who read your homepage once. Foundation 10: Design human-in-the-loop on purpose The fastest way to make AI “not pay off” is to either let it run unchecked, then panic when it makes a mistake, or force a manual review of everything, then wonder why nobody uses it. Pick your risk points and add review there. For example: Customer-facing responses might require a tighter approval model at first. Internal summaries can be low risk and rolled out broadly. Lead qualification can start as recommendations before it becomes automated routing. This matches how HubSpot positions trust and controls around its AI features: build confidence, understand the flows, then scale usage.  What “AI-ready” looks like in practice When the foundations are in place, you will notice a few things quickly: Sales reps stop arguing with the CRM because it starts reflecting reality. Marketing stops building lists that need three disclaimers. Service stops re-answering the same questions. Ops stops playing whack-a-mole with workflows. At that point, AI becomes less of a headline and more of a daily advantage: Faster handoffs, better consistency, and fewer “how did this happen” moments. And the best part is that these foundations pay off even if you never touch a single AI feature. They make HubSpot perform better as a platform, full stop. Discover our Services

The big picture: eprivacy didn’t get replaced, it got stuck… and then quietly killed For years, everyone waited for the EU’s ePrivacy Regulation  to replace the old ePrivacy Directive and finally standardise cookie rules across Europe. That wait is over. The European Commission formally withdrew the ePrivacy Regulation proposal  in 2025, and the European Parliament’s legislative tracker lists the file as withdrawn , with the withdrawal announced in the Official Journal in October 2025.  What that means in practice: The ePrivacy Directive still runs the show  for cookies and similar tracking tech in the EU, and it’s still implemented through national laws . So yes: you still have a “European” standard, but enforcement and cookie banner expectations can vary by country (and by regulator mood). If you’re a Marketing Ops team supporting multi-region websites, this is the part where you stop pretending one banner configuration works everywhere. Change #1: “cookies” now means a lot more than cookies, and regulators are spelling it out Most Marketing Ops teams still talk about “cookie consent” like it’s just GA + a couple of pixels. Regulators don’t. The European Data Protection Board published Guidelines 2/2023 (final version 2.0)  clarifying the technical scope  of the ePrivacy cookie rule (Article 5(3)). It’s explicitly aimed at newer tracking methods replacing third-party cookies.  Translation into Marketing Ops reality: Tracking pixels, device fingerprinting approaches, identifiers stored in browser storage, SDK identifiers in apps, and other “cookie-like” tricks are still within scope if they store/access info on a user’s device (or gain access to info already stored).  “Server-side tagging” is not a magic cloak. If you’re still dropping identifiers or reading from the device, you’re still in the same consent conversation... you’ve just moved the furniture. If you’re doing any of the following, you should treat it as part of your consent architecture, not a side quest: Identity stitching / probabilistic matching Fingerprinting (including “privacy-safe” variants) Persistent IDs passed through tags or SDKs Cross-domain tracking setups Clean-room style matching where the web layer still drops identifiers Change #2: Cookie banner UX is now a compliance surface, not just a conversion surface Regulators have been consistent about one thing: If it’s easier to accept than reject, you’re nudging  - and nudging is increasingly treated as non-compliance. Across Europe, “reject” being as visible/easy as “accept” has become a baseline expectation in cookie UX enforcement (country by country). Spain’s regulator (AEPD) is one of the clearer examples: Guidance updates moved Spain toward requiring a reject button at the first layer .  France (CNIL) has also pushed hard against “dark pattern” cookie banners, including formal notices and enforcement attention around misleading designs.  Marketing Ops takeaway: Your cookie banner is now effectively a regulated UI component. It needs: Symmetry (accept/reject equally prominent) Clear purpose descriptions (no “enhance your experience” nonsense) Granular choices that actually do something A withdrawal path that’s as easy as consent If you’re A/B testing consent banners: fine, but every variant must still meet valid consent requirements. Don’t “test” your way into an enforcement letter. Change #3: You can record “no” but be careful what you store to remember it Marketing teams often ask: “Can we remember a user’s rejection so we don’t keep pestering them?” Yes, sometimes you can store a refusal signal to reduce repeated prompts, but the details matter. In the draft joint guidance on the interplay between GDPR and the Digital Markets Act (DMA), the European Commission and the European Data Protection Board point out that recording a refusal may be necessary for effectiveness, but they recommend that a record of “negative consent” should not contain a unique identifier .  Marketing Ops implication: If your “remember rejection” mechanism becomes a stealth identifier, you’re creating the very tracking you claim you’re avoiding. Practical pattern that usually behaves better: Store a short-lived, non-unique refusal flag (or a strictly local preference) Avoid building a cross-session identity just to remember someone said “no” Change #4: “Consent or pay” got official scrutiny and it spills into marketing patterns While this is most famous in publisher/media land, it matters for Marketing Ops because the same logic shows up in: “Download the whitepaper only if you consent to tracking” “Use the site only if you accept marketing cookies” “Access pricing only if you opt into marketing” The European Data Protection Board adopted Opinion 08/2024  on “consent or pay” models used by large online platforms for behavioural advertising, warning that these models can undermine the idea of freely given  consent and should offer real choice.  Now, you’re probably not Meta. But enforcement logic spreads downhill. What to do with your gated content and forms: Separate “get the thing” (contract/legitimate interest) from “track me everywhere” (consent) If you require an email for a download, don’t bundle it with behavioural advertising consent Give a real alternative path if you’re asking for optional processing If your consent mechanism starts sounding like a bouncer, regulators start acting like the police. Change #5: The UK quietly raised the stakes for eprivacy enforcement (massively) If you operate in the UK (or have UK traffic/customers), this is not subtle. The UK’s Data (Use and Access) Act 2025  has been rolling in changes between June 2025 and June 2026.  A major batch of provisions took effect on 5 February 2026 .  The headline Marketing Ops change: PECR fines now look like GDPR fines The UK regulator, the Information Commissioner’s Office, confirmed the Act gives it power to issue PECR fines up to £17.5m or 4% of global turnover  (previously capped much lower).  Why Marketing Ops should care: In the UK, a lot of “marketing enforcement” happens under PECR  (cookies, email marketing), not just UK GDPR. Raising PECR penalties is basically putting a turbo engine on the thing that already hits marketers most often. UK cookie rules: More exceptions, but don’t celebrate like it’s a free-for-all The ICO has updated guidance on “storage and access technologies” to reflect PECR changes and added a section explaining exceptions.  Depending on your exact use case, some low-risk  cookies/tech may be easier to justify without consent in the UK than in many EU countries... but: Advertising cookies are still advertising cookies Cross-site tracking is still cross-site tracking “Analytics” can be low-risk or  very much not, depending on how it’s configured and shared Marketing Ops action:   Treat the UK as its own compliance configuration and not a copy/paste of your EU setup. Change #6: GDPR itself isn’t being rewritten, but targeted “simplification” is moving through the system In the EU, there’s an active policy push to reduce admin burden - especially for SMEs and “small mid-caps”. In May 2025, the Commission published a proposal that would amend GDPR Article 30(5)  (records of processing activities / ROPA). It aims to broaden exemptions and shift the trigger toward processing that’s likely to result in high risk .  The European Data Protection Supervisor and the European Data Protection Board responded via a joint opinion in July 2025.  Important nuance:  this is a proposal , not “GDPR changed yesterday”. But it signals direction: Regulators want to reduce paperwork for smaller orgs without weakening core principles. Marketing Ops reality check: Even if ROPA thresholds loosen for some organisations, Marketing Ops still needs a working data inventory to survive: DSARs vendor reviews cookie audits consent proof incident response AI and enrichment governance So yes, you might get less paperwork. No, you don’t get to be less organised. Change #7: “Digital rulebook” overlap is becoming a real compliance factor Marketing Ops used to treat GDPR like the privacy layer and everything else like “someone else’s problem”. That era is ending. The European Data Protection Board adopted guidelines on the interplay between the Digital Services Act (DSA)  and GDPR in September 2025.  And the European Commission + EDPB ran a public consultation on draft guidance for the interplay between the Digital Markets Act (DMA)  and GDPR from October–December 2025, with finalisation expected some time in 2026.  Why this matters for Marketing Ops: Consent, personalised ads, profiling, and data-sharing can be scrutinised under multiple frameworks Platform changes (especially by “gatekeepers”) can ripple into your tracking stack and measurement model Your “compliance by CMP” strategy won’t cover everything if your downstream processing is messy Discover our MOPs Maturity Indicator So what should Marketing Ops do now? Here’s a practical plan that doesn’t require you to become an EU lawyer or develop a sudden love for policy PDFs - although your company red tape department really needs to be involved ASAP. 1) Treat consent as infrastructure, not a banner If your CMP is just “a thing we installed,” you’re behind. You need: A consent state that flows into tag management, CDP rules, ad platforms, and CRM sync logic Proof trails (what was shown, what was chosen, when it was applied) A way to prevent “shadow firing” tags when consent is missing Also: Audit what your site actually  does, not what your tag map says it does. Tag maps lie. Browsers don’t. 2) Reclassify your tracking methods using the EDPB’s broader scope Use the EDPB technical scope guidelines as your internal taxonomy refresh.  Specifically, update your tracking register to include: Pixels and non-cookie identifiers Fingerprinting-like techniques SDK-based tracking in apps Identity matching flows If you can’t describe it clearly, you can’t justify it credibly. 3) Fix banner UX where it’s obviously indefensible If your reject button is hidden behind “Manage options” but accept is a big shiny button… you already know how that looks. Aim for: equal prominence plain language no guilt-tripping no pre-ticked toggles no “legitimate interest” switcheroo that behaves like consent 4) Split “marketing” into lawful buckets (and stop mixing them) Marketing Ops teams get in trouble because they treat all growth activity as one blob. You need separate rules for: Service messaging  (contract / legitimate interest) Customer marketing  (soft opt-in may apply in some jurisdictions; check local rules) Prospecting  (legitimate interest may be possible, but transparency + opt-out must be real) Behavioural advertising  (usually consent-heavy, especially once ePrivacy applies) The ICO’s direct marketing guidance is a solid operational reference point for UK interpretations.  5) UK-specific: review PECR risk like it’s GDPR risk now Because the penalty ceiling just moved into grown-up territory.  Do a UK pass on: Cookie classifications and exceptions (based on the ICO’s updated storage/access guidance)  Email marketing basis (consent vs soft opt-in vs B2B rules) Suppression lists, opt-out mechanisms, and proof of consent where required 6) Prepare for the boring-but-deadly bits: DSARs and complaints The UK reform programme is phased, and some obligations land later (including elements around complaints handling during 2026).  Even if you’re EU-only, DSAR operational maturity is often where orgs fail in practice: You can’t find data fast enough You can’t delete it cleanly You can’t explain why you have it Marketing Ops is usually the owner of half the systems involved. Lucky you. A quick “what to tell your team” summary EU ePrivacy Regulation is dead ; the ePrivacy Directive lives on , so cookie rules stay fragmented across member states.  The EDPB has clarified that tracking beyond cookies  still falls into the consent regime.  Banner UX is enforcement fuel: R eject must be easy , dark patterns are a liability.  “Consent or pay” scrutiny is real and the logic spreads into gated experiences.  The UK has escalated PECR enforcement: £17.5m / 4%  is now on the table.  GDPR “simplification” is in motion (especially around ROPA thresholds), but it’s not a free pass to be messy.  Discover our Services

You promised better pipeline, a cleaner CRM, and fewer late-night “where did that lead go?” panic emails next year. Good. This guide will get you there without buzzwords, or vague platitudes. It’s a practical, step-by-step plan you can start today (yes, today) so your next quarter doesn’t smell like 2024’s data dumpster fire. This isn’t a checklist you print and forget. It’s a playbook: Triage, triage again, fix the real problems first, then tidy up. Expect decisions, compromises, and a little corporate bravery. Someone will need to own it. Make that person you or make it someone you can glare at until it gets done. First things first... who needs to be in the room Before you touch anything: Gather three roles (one person can play multiple roles, but don’t make a single martyr do everything): An Operations lead (HubSpot admin or Marketing Ops), S data owner (Sales ops or a senior rep who cares about lists and deals), A stakeholder (Sales leader or CMO who will sign off on rules and deletions). If your org can spare a business analyst or developer for an afternoon, bring them. If not, at least brief the person who handles integrations... those are the things that’ll embarrass you later. Triage: Find the things that actually hurt Not all mess is equal. Start by identifying what’s actively costing you time or money. Focus on four pain zones: Duplicate records, stale contacts/companies, broken automations, and bad reporting. Run these quick checks: How many contacts haven’t been touched in 18 months? (That’s candidate stale.) How many automations have run in the past 90 days vs how many workflows exist? (Alert: Unused workflows are future liabilities.) Which lists have more than 30% exclusions or errors? (Lists that lie are worse than no lists.) Are there integrations writing bad or duplicate data (Forms, events, Salesforce, ad platforms)? The goal is to find the high-impact fixes first. Don’t get lost prettifying contact property labels while the lead-to-deal conversion is leaking like a sieve. Step 1. Duplicate cleanup (but don’t be a trigger-happy scrubber) Duplicates are the low-hanging fruit. HubSpot has built-in de-duplication for contacts by email, and companies by domain, but it misses clever duplicates (e.g., same person with work and personal emails, or +aliases). Start with a conservative merge policy: Identify duplicates by email and company domain, Flag fuzzy duplicates (name + phone, email variations) for human review, Merge confirmed duplicates, preserving the most complete record and timeline. Important : Export a full backup of records you’re about to merge. Yes, export. If someone yells later (“where’s my notes?”), you can restore data or explain what changed. Also document your merging rules... future you will thank past you. Step 2. Archive the dead (stale contacts & companies) “ Stale ” is different by business, but a practical threshold is 12–18 months of no opens, clicks, site visits, form submissions, deals, or calls. Don’t delete on day one though... archive. Create an “archived - inactive 18m” lifecycle stage or property and: Move contacts to a low-cost marketing list (or suppress them from campaigns), Set a re-engagement campaign that runs for 45 days with two honest offers, If no response, move them to a final archive (or mark them for deletion after 90 days). This keeps your database lean, reduces send costs, and improves deliverability, and you can still re-activate a lead if they come back. Step 3. Stop the bad inputs at the source Broken forms, weird API pushes, and over-eager Zapier paths make a mess faster than people clean it. Audit every inbound source: Public forms, Landing pages, Chatbots, Integrations (Salesforce, e-commerce, ad platforms), Manual CSV imports in the last 12 months. For each source, ask: What fields are we writing? Are we mapping them consistently? Who owns that source? Fix the ones creating garbage: normalise property mappings, add validation on forms, and lock down who can import. If you have external teams hitting HubSpot (agencies, contractors), revoke access and set up a controlled import process. No more “we’ll just upload a CSV.” Step 4. Workflow triage: Keep the useful, kill the rest Workflows that don’t run aren’t “assets.” They’re technical debt. Filter workflows by “last run” and owner. Then: Archive workflows that haven’t run in 90 days and have no business purpose, Fix workflows throwing errors (those red logs scream for attention), Consolidate overlapping workflows (multiple flows doing the same thing = chaos), Label workflows clearly: Purpose, owner, last modified date. Add a naming convention: [team] - [purpose] - [owner initials] - [YYYYMMDD]. It’s boring, but future you will not have to guess who killed the lead. Discover our Podcast Step 5. Property tidy: Less is more HubSpot instances accumulate properties like trophies from short, painful projects. Ask: Is this property used in lists, workflows, filters, or reports? If not, it’s probably a candidate for deletion or consolidation. Process: Export a list of custom properties and where they’re used, Mark properties as “in use,” “duplicate,” or “orphaned”, Merge duplicates and delete orphaned properties after a 30-day warning period. Rename properties only if you can update all dependencies. Keep an audit sheet: Property name, apiName, purpose, owner, and last used. Step 6. Standardise lifecycle stages and lead scoring If Sales and Marketing disagree about what a lead is, nothing works. Agree on definitions for lifecycle stages (lead, mql, sql, opportunity, customer) and who moves the stages. Make them simple and enforceable. For lead scoring: Keep it meaningful. Remove noisy signals (e.g., pageviews with low intent), prioritise fit and intent, and map scores to clear actions. Test scoring thresholds with a 30-day run and adjust. Document everything and publish the definitions to Sales. Then make sure workflows align to these definitions, otherwise you’ll have people operating on different planets. Step 7. Fix reporting so you can stop guessing If your dashboards are full of “last 90 days” widgets that mean nothing, rebuild them. Identify five core metrics your execs actually use (e.g., MQL to SQL conversion, average sales cycle, pipeline by stage, lead source ROI, email deliverability). Build one clean dashboard that tells the truth. When rebuilding reports: Use consistent date ranges, Standardise UTM tracking and source attribution, Avoid duplicated metrics across dashboards (confusing). If reports disagree, trace them back to source definitions, often the disagreement is a definition problem, not a math problem. Step 8. Lock down access & reduce human error Too many admins = too many ways to break things. Audit user permissions. Make a strict admin group and a broader editor group. Enforce: Two-person approval for automation that can change lifecycle stage or delete data, Limited API keys with named owners and expiration dates, Logging and a change request process for major modifications. Yes, it adds friction. You want friction for things that can break revenue. Step 9. Communication and change management Cleaning HubSpot is a political act. Tell people what you’re doing before you do it. Run a short internal campaign: A kickoff email that explains why (no drama, just facts), A 30-day “watch period” where changes are flagged but reversible, Training docs and a recording for any new flows or dashboards. Include a short FAQ: What will be deleted, who to contact if a record disappears, and where the backup lives. The goal is fewer surprise Slack freakouts. (If you want, use this subject line: “FYI: HubSpot clean-up. What’s changing and why.” Short, direct, no panic.) Step 10. Create a maintenance rhythm Once clean, keep it clean. Schedule: Monthly duplicate and error reports, Quarterly property reviews, Bi-weekly workflow review for any new builds, An annual archive purge. Make these tasks part of someone’s role and include them in your ops calendar. If it’s not scheduled, it won’t happen. Final safety net. Backup & rollback Before you delete or merge anything irreversible: Export. Full exports of contacts, companies, deals, and properties should be saved with a timestamp and stored in a shared drive. If an automated process goes sideways, you need a rollback plan and a contact who can execute it. Also keep a change log: What was changed, why, who approved it, and links to the export. This is not busywork, it’s insurance. Sample 30-/60-/90 day plan (high level) 30 days : Triage, duplicate merges, archive clearly stale records, stop bad inputs, start stakeholder comms. 60 days : Workflow consolidation, property cleanup, reporting rebuild, lock down access. 90 days : Finalise deletions/archives, train teams, schedule maintenance cadence. Adjust timing to your org size; small teams move faster, big teams need more approvals. The point is momentum: Fix the biggest leaks first. Wrap-up: What success looks like Clean data, fewer manual fixes, reports you can trust, faster handoffs to sales, and a predictable ops rhythm. You’ll lose some vanity properties and bad automations, but you’ll get a CRM that earns its keep. If there’s one last thing: Stop treating HubSpot like a dumping ground. Make it a system of record, not a personal playground. When people know there’s ownership, standards, and consequences, behaviour changes. And your next quarter will thank you for it. Discover our Services

Marketing technology governance is the operational equivalent of flossing. Nobody brags about it. Nobody puts it in a slide deck with fireworks. And almost nobody does it properly. Yet the teams that take it seriously spend less, move faster, and avoid the slow, painful decay that turns once-promising MarTech stacks into expensive, brittle messes. Governance has a branding problem. Say the word in a meeting and half the room hears “approval gates”, “process police”, or “IT says no”. The other half quietly checks out because it sounds like admin. That’s unfortunate, because good governance isn’t about slowing marketing down. It’s about stopping money, data, and momentum from leaking out of the system. What governance actually means (and what it definitely doesn’t) Let’s clear the air early. Marketing technology governance is not  about adding more approval layers. It’s not about centralising power. And it’s not about locking tools away behind bureaucracy. At its core, governance answers four very simple questions: Who owns this platform? What is it for (and what is it not for)? How do changes get made safely? How do we know it’s still earning its keep? That’s it. Good governance is clarity, not control. It creates shared understanding so teams can move independently without breaking things, duplicating effort, or quietly racking up unnecessary spend. In high-performing teams, governance is often invisible. It lives in lightweight documentation, clear ownership, and predictable change patterns. People don’t feel governed. They feel confident. Bad governance, on the other hand, is loud. It shows up as rigid approval workflows, endless forms, and blanket rules that ignore context. That’s not governance. That’s organisational anxiety wearing a process hat. The silent cost of unowned platforms Every MarTech stack has at least one orphaned tool. You know the one. It was bought for a very specific reason three years ago. The person who championed it has moved on. The integration “mostly works”. Nobody is quite sure who can make changes without breaking something. The invoice still arrives. Faithfully. Monthly. Annoyingly. Unowned platforms are where budgets go to die. Without clear ownership, a tool slowly drifts. Features go unused. Configurations grow inconsistent. Integrations degrade as upstream and downstream systems evolve. Data quality erodes so gradually that nobody notices until reporting becomes unreliable. And when something breaks, everyone assumes someone else is responsible. This is where governance earns its keep. Assigning ownership doesn’t mean one person does all the work. It means someone is accountable for: Defining the platform’s purpose Maintaining its configuration standards Coordinating changes Making the call on renewals or retirement Ownership creates decision velocity. Without it, teams default to indecision, workarounds, or buying yet another tool to solve a problem they technically already own. That’s how stacks bloat. Not through bad intent, but through neglect . Documentation that people actually use Most teams don’t have a documentation problem. They have a documentation trust problem . Either it’s too high-level to be useful, or so detailed it’s immediately outdated. Often both. The result is predictable: People stop reading it and rely on tribal knowledge instead. Effective governance documentation has a very different goal. It’s not trying to capture everything. It’s trying to capture the decisions that matter . At minimum, every core platform should have: A clear purpose statement Defined ownership and escalation paths Key integrations and dependencies Configuration principles (not step-by-step instructions) Known risks and constraints Notice what’s missing: Screenshots of every setting. Those rot fast. Principles last longer. Good documentation is opinionated. It explains why  things are set up the way they are, not just how . That context is what allows new team members, agencies, or AI tools to work safely without reverse-engineering the system. And yes, it should be short. If it takes longer to read than to ask someone on Slack, you’ve already lost. Change control without killing momentum This is where most governance efforts fall apart. Marketing Ops teams hear “change control” and immediately imagine ticket queues, CAB meetings, and two-week waits to update a form. That fear isn’t irrational. Many organisations have experienced exactly that. But change control doesn’t have to mean friction. It means predictability . High-performing teams distinguish between different types of change: Low-risk changes that can be made freely Medium-risk changes that require peer review High-risk changes that need coordination and testing This tiered approach keeps velocity high while protecting the foundations. Nobody needs approval to update an email template. But changes to lifecycle logic, scoring models, or core integrations probably deserve a second pair of eyes. The key is making these rules explicit. When people know what they can do safely, they stop hesitating. When they know when to slow down, incidents drop dramatically. Ironically, the teams with the strongest governance often move faster than those without it. They spend less time fixing mistakes, rolling back changes, or debating who broke what. Discover our Podcast Governance as an enabler, not a blocker Here’s the uncomfortable truth: Most marketing teams already have governance. It’s just accidental. It lives in unspoken rules, personal preferences, and historical decisions nobody remembers making. That kind of governance is fragile. It only works while the same people stick around. Intentional governance externalises that knowledge. It turns “how we do things” into something the organisation owns, not just individuals. This matters enormously as teams scale, outsource, or adopt new capabilities. Without governance, every change becomes risky. With it, experimentation becomes safer because the blast radius is understood. And this is exactly why governance “converts”. Executives don’t wake up excited about documentation. They care about predictability, cost control, and risk reduction. Governance delivers all three without asking for headcount increases or flashy new tools. How governance enables AI safely AI has poured accelerant on every existing weakness in MarTech stacks. Suddenly tools can generate campaigns, update data, create workflows, and personalise content at scale. That’s powerful. It’s also dangerous if the underlying systems aren’t well governed. AI doesn’t understand intent. It understands instructions and patterns. Without clear governance, those instructions are inconsistent, outdated, or simply wrong. Good MarTech governance creates the guardrails AI needs to be useful, rather than destructive. Clear ownership defines who is responsible for AI-driven changes. Documentation provides the context models need to operate correctly. Change control ensures automated actions are tested before they go live. Most importantly, governance defines where AI is allowed to act autonomously and where it isn’t . This isn’t about fear. It’s about alignment. AI thrives in environments with clear rules, clean data, and consistent patterns. Governance creates exactly that. Teams that skip this step don’t move faster. They just accumulate invisible risk at machine speed. The maturity curve nobody talks about There’s a pattern that shows up again and again. Early-stage teams move fast with almost no governance. It works because everything is small and visible. As complexity grows, cracks appear. Data inconsistencies. Duplicate tools. Conflicting processes. At this point, many organisations double down on speed instead of structure. They add more tools, more automations, more “quick fixes”. This works briefly, then collapses under its own weight. Governance is what allows teams to exit this cycle. It doesn’t require perfection. It requires intentionality. A willingness to decide how the stack should behave, not just react to how it currently behaves. Teams that make this shift don’t talk about governance much. They talk about clarity. About confidence. About finally trusting their numbers again. Why this feels boring (and why that’s a good sign) Governance doesn’t demo well. You can’t show it in a sales deck with animated arrows. You can’t easily quantify it in isolation. When it’s working, nothing dramatic happens. Campaigns launch smoothly. Data behaves. Renewals get questioned instead of rubber-stamped. That’s precisely why it’s valuable. The best operational disciplines feel dull because they remove drama. They turn chaos into routine. They replace heroics with systems. If your MarTech stack feels exciting all the time, something is probably wrong. Getting started without boiling the ocean The mistake most teams make is trying to “fix governance” all at once. You don’t need a framework, a steering committee, or a six-month initiative. You need to start answering the uncomfortable questions you’ve been avoiding. Who actually owns each platform? Which tools are critical, and which are just nice to have? Where do changes currently go wrong? What knowledge lives only in people’s heads? Start there. Document the answers. Socialise them. Adjust as reality pushes back. Governance is iterative. It improves through use, not theory. The commercial reality nobody says out loud Here’s the part people rarely admit: Governance is one of the easiest ways to unlock budget without asking for more money. It reveals shelfware. It exposes overlapping capabilities. It highlights processes that cost more to maintain than they return. For consultancies and internal ops teams alike, this is where real value lives. Not in selling another tool, but in making the existing stack behave like a coherent system. That’s why governance conversations resonate so strongly once they land. They speak to pain executives already feel but struggle to articulate. Final thought Marketing technology governance will never win awards for creativity. It won’t make your brand more exciting. It won’t give you something flashy to post on LinkedIn. What it will do is stop your stack from quietly draining time, money, and trust. In a world obsessed with speed, governance is how you move fast without  breaking everything. And yes, it’s unsexy. That’s exactly why it works. If your stack has grown faster than your confidence in it, governance isn’t a “nice to have”. It’s the discipline that makes everything else work properly again. Discover our Services

There’s a familiar conversation happening inside a lot of B2B companies right now. Marketing Ops says, “This sits with us.” Revenue Ops says, “No, this is ours now.” Leadership nods politely, adds another role to the org chart, and hopes the noise dies down. It rarely does. Because this isn’t really a role problem. It’s a design problem. And MarTech platforms have a habit of exposing design problems very quickly. Why this debate exists in the first place A few years ago, nobody was arguing about this. Marketing Ops had a fairly clear remit. Own the tools. Run the campaigns. Keep the data usable. Try not to break anything important. Then things shifted . Marketing automation stopped being “top of funnel software” and became core infrastructure. HubSpot is a great example as it evolved from a marketing platform into a CRM, a sales system, a service platform, and eventually a full revenue engine. At the same time, leadership started asking better questions. Questions like why pipeline looked healthy but revenue didn’t. Why forecasts changed depending on who built the report. Why marketing and sales could sit in the same meeting and talk about entirely different numbers. So organisations reacted. They created Revenue Ops. Not because Marketing Ops failed, but because the business outgrew the way responsibility had been set up. Where marketing ops genuinely ends Marketing Ops is still critical. That hasn’t changed. In a well-run HubSpot setup, Marketing Ops is usually responsible for how demand is generated, captured, and prepared for sales. Campaign architecture, lifecycle logic at the marketing level, lead capture and enrichment, consent and compliance, attribution, and the overall health of the marketing side of the platform. This is not admin work. It’s skilled, technical, and often underappreciated . But there’s a line that matters. Marketing Ops shouldn’t be responsible for defining how revenue works. Not how pipelines are structured. Not how deals progress. Not how forecasts are calculated. And not how success is measured once money is involved. When Marketing Ops is pulled into those decisions, it’s rarely because they want to be. It’s usually because nobody else has taken ownership. Where revenue ops genuinely begins Revenue Ops exists to answer a very simple but uncomfortable question. How does revenue actually move through this business? In simple terms, that means owning the structure that sits underneath the numbers leadership cares about. The CRM data model, lifecycle alignment across teams, pipeline definitions, forecasting logic, reporting consistency, and the rules that govern handoffs between functions. Revenue Ops is not a fancier name for Marketing Ops. And it’s not a replacement for Sales Ops either. It’s the layer that connects how teams work to how revenue is reported and predicted. When that layer is missing or unclear, everyone ends up filling the gap in their own way. What good ownership really looks like High-performing organisations don’t spend much time debating who owns what. They’ve already decided. Marketing Ops focuses on generating and qualifying demand. Revenue Ops focuses on how that demand converts, scales, and shows up in revenue numbers. Sales Ops focuses on enabling reps to execute within that model. Leadership focuses on priorities and trade-offs when things get messy. No single role “owns MarTech” end to end. The system is shared. Responsibility is deliberately split. That’s the difference between teams that argue about tools and teams that use them properly. The real issue hiding underneath the debate Most companies never design an operating model. They hire roles. They buy software. They assume clarity will emerge over time. It doesn’t. Without an explicit operating model, people default to protecting their patch. Data becomes political. Reports become negotiable. HubSpot turns into a very expensive collection of half-working processes. When things go wrong, the conversation drifts back to job titles instead of structure. Marketing Ops vs Revenue Ops is the wrong argument. The real question is whether the way your business operates has ever been intentionally designed. Stop arguing. Start designing. If your teams are debating boundaries, that’s not dysfunction. It’s a signal that the business has changed and the operating model hasn’t caught up yet. The fix isn’t another hire or another tool. It’s deciding how your revenue engine is meant to work, then aligning roles around that reality. If your MarTech feels powerful but oddly underwhelming, and if your teams spend more time debating ownership than improving performance, an Operating model workshop  is the fastest way to reset. Design the system once. Stop having the same argument every quarter. Discover our Services

A marketing automation audit is a systematic review of everything running inside your marketing automation platform - the workflows, the data, the integrations, the scoring models, the consent records, and the campaigns - to identify what's working, what's broken, what's redundant, and what's creating risk. It's the single most effective way to improve platform performance, reduce operational debt, and ensure your automation environment is fit for purpose. At Sojourn Solutions, audits are one of the most common starting points for our client engagements. The pattern is consistent: an organisation has been running their marketing automation platform for two or more years, things have accumulated, and nobody has taken a full accounting of what's actually in there. This checklist reflects what we review and what we recommend every marketing operations team checks at least annually. When to run an audit An audit should happen at least once a year as standard practice. Beyond that, specific triggers should prompt an immediate review: A platform migration is being planned A new AI feature or agent is being activated Campaign performance has declined without a clear cause The team has experienced significant turnover A regulatory change affects how personal data is processed The organisation has gone through a reorg, product pivot, or market shift Nobody can confidently explain what all active automations do If any of these apply, the audit is already overdue. 1. Platform hygiene This is the foundation. Before looking at strategy or performance, check whether the platform itself is clean and well-maintained. Active vs inactive programmes. How many programmes, campaigns, or workflows are currently active? How many of those are actually in use vs running on autopilot with no owner? Most instances that have been running for two or more years have a significant percentage of active programmes that nobody monitors. Identify everything that's active, confirm whether it should be, and deactivate or archive anything that's no longer needed. Orphaned assets. Emails, landing pages, forms, snippets, and templates that aren't connected to any active programme. These accumulate over time and create clutter that makes the instance harder to navigate and maintain. Flag anything that hasn't been used in six months and review whether it should be archived. Folder structure and naming conventions. A consistent folder structure and naming convention makes the platform navigable, auditable, and manageable at scale. If your instance has evolved organically over several years, the folder structure has likely drifted. Review whether current naming conventions are documented, followed consistently, and make it possible to find any asset quickly. User access and permissions. Review who has access to the platform, what permissions they hold, and whether those permissions are appropriate. People leave organisations, change roles, or accumulate access over time. Audit active users against current team members, remove access for anyone who no longer needs it, and verify that permission levels match current responsibilities. 2. Data quality and integrity Bad data is the most common cause of automation failures, poor campaign performance, and compliance risk. This section is where most audits uncover the biggest problems. Duplicate records. Check the volume and distribution of duplicate contacts in your database. Duplicates cause inflated reporting, inconsistent personalisation, and conflicting automation behaviour. Identify the sources of duplication - form submissions, list imports, CRM sync issues - and address both the existing duplicates and the root cause. Field completeness and consistency. Review critical fields across your database: email, company, job title, country, lifecycle stage, consent status. What percentage are populated? Are values consistent - or are there 15 variations of "United Kingdom" across the country field? Inconsistent field values break segmentation, scoring, and personalisation. Data decay. Contact data degrades over time. People change jobs, companies rebrand, email addresses become invalid. Check your bounce rate trends, the age distribution of your database, and when records were last updated. A database where 30% of records haven't been touched in two years is a database with a significant decay problem. Integration health. Review every integration between your MAP and other systems - CRM, enrichment tools, analytics platforms, webinar tools, event platforms. Is data syncing correctly in both directions? Are field mappings still accurate? Are there sync errors accumulating that nobody's monitoring? Integration failures are a common source of data quality issues that compound over time. 3. Lead management and scoring Lead scoring and lifecycle management are the operational backbone of how marketing passes leads to sales. If these are misconfigured, everything downstream suffers. Scoring model calibration. When was the lead scoring model last reviewed against actual conversion data? Pull your closed-won deals from the past six months and check what their lead scores were at the point of handoff to sales. If high-scoring leads aren't converting, or low-scoring leads are, the model needs recalibration. Scoring models should be reviewed at least every six months. Score distribution. What does the current score distribution look like across your database? If a large percentage of records sit above your MQL threshold, the threshold is either too low or the scoring logic is too generous. If almost nobody reaches the threshold, it's too restrictive. A healthy distribution should show a clear concentration of records at lower scores with a meaningful but manageable volume at MQL level and above. Lifecycle stage definitions. Are lifecycle stages clearly defined, documented, and consistently applied? Can everyone on the team explain the criteria for moving from one stage to the next? If lifecycle stages are being updated manually by different people using different criteria, the data is unreliable and reporting based on it is meaningless. Lead routing and SLA. Review how leads are being routed to sales. Are routing rules current - do they reflect the current territory model, the current sales team structure, and the current qualification criteria? How quickly are routed leads being followed up? If leads are sitting in a queue for days, the routing is functional but the handoff process is broken. 4. Campaign and workflow operations This is where operational debt accumulates fastest. Every campaign that gets built adds to the total complexity of the instance, and very few teams actively retire campaigns when they're no longer needed. Active automation inventory. Create a complete list of every active automation, trigger campaign, nurture programme, and workflow. For each one, document what it does, what data it uses, when it was last reviewed, and who owns it. This is the single most valuable output of any audit - and in most organisations, it's never been done. Workflow logic review. For each active automation, trace the logic end to end. Are there conditional branches that reference deprecated fields? Wait steps that no longer make sense? Triggers that fire on activities that are no longer tracked? Workflow logic that was correct when built can drift as the platform, the data model, and the business change around it. Email deliverability. Review key deliverability metrics: bounce rates, complaint rates, inbox placement, and sender reputation. Check authentication records - SPF, DKIM, and DMARC should all be properly configured. Review whether you're on any blocklists. Deliverability problems often have root causes in data quality (sending to invalid addresses) or consent management (sending to people who don't want to hear from you), so this section connects directly to the data and consent sections. A/B testing and optimisation. Are campaigns being tested and optimised, or are they running on the same configuration they launched with? Review whether subject lines, send times, content variants, and audience segments are being tested systematically. A campaign that's been running for six months without any testing is a campaign that's been stagnating for six months. 5. Reporting and attribution If your reporting is wrong, every decision based on it is wrong too. This section is where most organisations discover that the numbers they've been presenting to leadership don't mean what they think they mean. Report accuracy. Pull three reports your team relies on - pipeline contribution, campaign performance, lead volume by source. Now rebuild them from scratch using raw data. Do the numbers match? In most instances, they don't. Reports built years ago often reference fields, stages, or definitions that have since changed. Nobody updated the report because nobody questioned the output. Attribution model configuration. If you're running multi-touch attribution, check whether the model reflects your actual buyer journey. First-touch, last-touch, linear, W-shaped - each tells a different story. The question isn't which model is best. It's whether the model you're using is configured correctly against current touchpoints and whether anyone on the team can explain what it's measuring and why. Dashboard hygiene. How many dashboards exist? How many are actively used? Who built them, and do they still reflect current KPIs? Dashboards accumulate just like everything else in a MAP. The ones nobody looks at should be archived. The ones leadership relies on should be verified quarterly against actual data. CRM-to-MAP reporting alignment. Does your MAP report the same numbers as your CRM for shared metrics like MQLs, pipeline contribution, and conversion rates? If not, find where the discrepancy originates. This is one of the fastest ways to lose credibility with sales and leadership - two systems showing different numbers for the same metric. 6. Templates and brand consistency Templates drift. What was on-brand and functional two years ago may not be now. This section is quick but catches problems that affect every campaign going out the door. Email template review. Are your email templates current, mobile-responsive, and consistent with your brand guidelines? Check rendering across major email clients - Outlook, Gmail, Apple Mail. Templates that look fine in preview but break in Outlook are more common than anyone wants to admit. If your templates haven't been updated in over a year, they're probably overdue. Landing page and form templates. Same check - are they on-brand, mobile-responsive, and functional? Test every active form. Do submissions route correctly? Do they trigger the right automations? Do they capture the right data? A form that's been live for two years without being tested is a form that might have been broken for months without anyone knowing. Template governance. Is there a process for creating new templates, or does anyone with platform access build their own? Ungoverned template creation leads to brand inconsistency and technical debt. Define which templates are approved, who can create new ones, and what the review process looks like. 7. Consent and compliance This section has become significantly more important as AI features make autonomous decisions based on consent data. Consent that was valid two years ago may not cover current processing purposes. Consent record currency. When was consent captured for the records in your database? What was it captured for? Does it cover your current campaign types and processing purposes? If your preference centre offers categories that don't map to the campaigns you actually run, the consent data is structurally misleading — technically valid but operationally inaccurate. Suppression list integrity. Review every suppression list and suppression rule. Are contacts suppressed for valid, current reasons? Are there rules that were written for campaigns or business conditions that no longer exist? Suppression rules accumulate over time and can silently exclude contacts who should be contactable — or fail to exclude contacts who shouldn't be. Regulatory alignment. Are your consent management practices aligned with the regulations that apply to your contacts? GDPR, CASL, CAN-SPAM, CCPA, and the EU AI Act all have implications for how marketing automation handles personal data. If your database spans multiple jurisdictions, review whether consent is managed appropriately for each one. Privacy and data processing documentation. Can you produce a record of what personal data your MAP processes, where it comes from, who has access, and what automated decisions are made based on it? If a regulator, auditor, or enterprise customer asks this question, you need to be able to answer it clearly and quickly. 8. AI features and governance This is the newest section of any marketing automation audit and one that most organisations haven't addressed yet. Every major MAP now includes AI-powered features, and many of them are active without anyone having made a deliberate decision to deploy them. AI feature inventory. Which AI features are currently active in your platform? Predictive scoring, automated segmentation, content recommendations, send-time optimisation, AI-assisted campaign building - catalogue what's turned on and what it does. Many AI features get activated during platform upgrades or by individual team members without formal approval. AI data dependencies. What data is each AI feature consuming? AI features are only as good as the data they act on. If a predictive scoring model is using fields that haven't been updated in two years, the predictions are based on stale information. Map each AI feature to the data it depends on and verify that data is current and accurate. AI decision documentation. Can you explain how each AI feature makes its decisions? Not at a technical level - at an operational level. If someone asks "why was this lead scored highly" or "why was this contact suppressed," can you trace the decision back to the AI feature's logic and the data it used? If not, the AI is operating as a black box inside your operations. AI governance ownership. Who is responsible for monitoring, reviewing, and maintaining AI features in your platform? In most organisations, the answer is nobody - AI features were activated and then left to run. Assign a named owner for each AI feature with responsibility for periodic review. How to use this checklist Don't try to do everything at once. Prioritise based on where the biggest risks and inefficiencies are likely to sit. If your main concern is campaign performance, start with sections 2 (data quality), 3 (scoring), 4 (campaigns), and 5 (reporting). If your main concern is compliance and risk, start with sections 7 (consent) and 8 (AI governance). If you're preparing for a migration, start with section 1 (platform hygiene) and section 2 (data quality) - cleaning up before you migrate saves significant time and cost. If you're activating AI features, start with sections 2 (data quality) and 8 (AI governance) - AI amplifies whatever state your data and operations are in, good or bad. If leadership is questioning marketing's numbers, start with section 5 (reporting) - nothing kills credibility faster than two systems showing different pipeline figures. For organisations that haven't audited their marketing automation platform in over a year, a full review across all eight sections is recommended. At Sojourn Solutions, our platform audits follow this structure - and every one ends the same way: a clear plan, named owners, and a team that finally knows what's actually running in their instance. If your marketing automation platform hasn't been audited in over a year, it's overdue. We'd welcome the conversation. Discover our Services

Not every Marketing Operations success story is about doing more. Some of the most valuable work is about stopping waste before it quietly drains budget, time, and credibility. For UCLA Health, the problem wasn’t campaign performance or engagement. It was structural. Their Oracle Eloqua environment was costing more than it should and was on track to cost even more. Sojourn Solutions was brought in to fix it. Permanently. The challenge: When contacts quietly become a liability UCLA Health’s Eloqua contract capped total contacts at 1.5 million across two instances. On paper, this seemed manageable. In reality, it wasn’t. Because Eloqua counts duplicate email addresses separately across instances, the combined contact volume exceeded the contractual limit by roughly 200,000 contacts. The secondary instance, originally built to support strategic acquisition initiatives, contained approximately 175,000 contacts - but by this point, it was no longer delivering meaningful business value. Instead, it had become a workaround. For nearly six months, the secondary instance was being kept alive primarily to warm IP and domain reputation, requiring the team to repurpose and deploy a bi-weekly newsletter with minimal strategic impact. Meanwhile, growth in the primary instance was constrained, and UCLA Health faced a looming choice: Pay recurring monthly overage fees or commit to an expensive contract upgrade. Neither option was appealing. The solution: Simplify, consolidate, and stop paying for nothing Sojourn began by assessing usage trends across both Eloqua instances. The conclusion was clear: The second instance was underutilised, operationally expensive, and no longer aligned with UCLA Health’s marketing strategy. The recommendation was decisive - decommission the secondary instance entirely. Sojourn led the full decommissioning process end to end. Active forms, landing pages, campaigns, and reports were identified and disabled. Embedded landing pages were updated and redirected appropriately to avoid broken experiences. Database records, activity history, and assets were archived to ensure nothing was lost and could be referenced in the future if needed. Engaged and relevant contacts from the secondary instance were carefully migrated into the primary instance, preserving data integrity and ensuring continuity for active marketing programs. The result was a single, cleaner Eloqua environment that the team could actually focus on and scale. Just as importantly, ongoing operational noise disappeared. No more maintaining a second instance simply to keep it “warm.” No more duplicated effort for minimal return. Building a healthier database for the long term Instance consolidation solved the immediate overage risk, but Sojourn didn’t stop there. To enable sustainable growth, Sojourn also supports UCLA Health with an annual, ad hoc database hygiene process designed to reduce contact counts without compromising compliance or data integrity. This process manually identifies and removes non-emailable contacts such as hard bounces, long-term inactive leads, and deceased patients. Given UCLA Health’s daily full-file patient feeds, this work is coordinated closely with the Office of Health Informatics and Analytics (OHIA) to ensure suppression happens at the source - preventing removed records from being unintentionally re-created in Eloqua. Deceased patients are flagged using MRN or Patient ID to ensure they never re-enter the system. Hard bouncebacks are flagged by email address, allowing contacts to be reintroduced automatically if they update their email address in their patient record and become emailable again in future daily feeds. This hygiene process typically reduces total contact counts by an additional 10–20% each year, creating ongoing headroom for growth without triggering contract penalties. The results: Fewer contacts, lower costs, more flexibility The impact was immediate and measurable. UCLA Health reduced its total Eloqua contact count by approximately 175,000 through instance decommissioning alone, with a further 10–20% reduction driven by ongoing database hygiene efforts. By addressing the root cause rather than treating the symptoms, UCLA Health avoided recurring overage fees estimated at $5,000 per month, as well as the need for a costly contract upgrade. At the same time, Marketing Operations became simpler, leaner, and easier to manage. Most importantly, the primary Eloqua instance now has room to grow... without fear that success will be punished with unexpected costs. What the client had to say: “Sojourn helped us take a strategic, long-term approach to managing our Eloqua environment. By consolidating instances and improving database hygiene, we were able to reduce unnecessary costs, simplify our operations, and create room for future growth without disrupting active marketing programs.” The takeaway Marketing Operations isn’t always about launching more campaigns or adding more tools. Sometimes, the smartest move is knowing what to turn off. By decommissioning an unused Eloqua instance, cleaning up contact data, and putting long-term governance in place, UCLA Health transformed a growing cost risk into a scalable, sustainable foundation. No overages. No wasted effort. No unpleasant surprises in the renewal meeting. Just a cleaner system and a marketing team back in control.

Choosing a Marketing Operations vendor is not like choosing a piece of software. Software can be swapped. Contracts can be renegotiated. Bad decisions can be undone with enough budget and patience. A Marketing Ops partner, on the other hand, gets inside how your business actually works. Your data. Your processes. Your internal politics. Your technical debt. If you choose badly, you don’t just waste money. You hard-code the wrong behaviours into your operation. Most buyers don’t realise this until it’s too late. That’s why the real risk isn’t asking the wrong questions. It’s asking the easy  ones. The questions that vendors have rehearsed answers for. The ones that sound sensible but reveal very little. If you want to make a good decision, you need to ask questions that force honesty. Questions that surface how a vendor thinks, not just what they sell. Here are ten that actually matter. 1. How do you define Marketing Operations, and where do you draw the line? This sounds philosophical. It isn’t. Marketing Ops means very different things depending on who you ask. For some vendors, it’s platform administration and campaign execution. For others, it’s governance, operating models, and performance management. Some will happily call themselves Marketing Ops while functioning as outsourced button-pushers. The answer you’re listening for isn’t a neat definition. It’s whether they understand Marketing Ops as a system. A strong vendor will talk about how strategy, process, data, technology, and people reinforce each other. They’ll be clear about what they do not do, and why. They won’t promise to “handle everything” because they know that’s how accountability disappears. If they can’t articulate their boundaries, they probably don’t have any. 2. How do you approach a new client when the problem isn’t clearly defined? Most organisations don’t come to a Marketing Ops vendor with a clean brief. They come with symptoms. Low adoption. Messy data. Reporting no one trusts. Automation that looks impressive but delivers very little. A vendor that jumps straight to solutions is telling you something important about how they operate. Good Marketing Ops work starts with diagnosis. That means asking uncomfortable questions, mapping reality instead of ambition, and resisting the urge to “fix” things too quickly. It also means being honest when the root cause isn’t technology at all. However, if their answer centres purely on frameworks, audits, or discovery phases - listen carefully to how those are used. Are they a genuine way to understand your operating model, or just a prelude to selling you more configuration work? 3. How do you balance "best practice" with how teams actually behave? This is where many engagements quietly fail. Most vendors know what good looks like in theory. Clean lifecycle models. Clear ownership. Perfectly documented processes. The problem is that most teams don’t work like that, and pretending they do doesn’t make it true. A credible Marketing Ops partner designs for reality, not aspiration. They understand where compromise is acceptable and where it isn’t. They know when to push for change and when to adapt the system to fit human behaviour. If a vendor talks only about best practice without acknowledging trade-offs, you’re likely buying a future state that never arrives. 4. How do you measure success, and who decides if it’s been achieved? This question cuts through a lot of noise very quickly. Some vendors define success as deliverables completed. Others define it as platform usage, or campaign volume, or automation built. None of those necessarily translate to better performance. Strong vendors talk about outcomes. Decision-making clarity. Time saved. Reduced friction between teams. Improved confidence in data. They also acknowledge that not everything worth measuring fits neatly into a dashboard. Pay attention to whether success is something you define together, or something they report on after the fact. Marketing Ops should increase your control, not outsource it. 5. What happens after the initial implementation work is done? Many Marketing Ops engagements die quietly at this point. The platform is live. The workflows are built. The documentation exists somewhere. And then the business moves on, while the system slowly drifts out of alignment. A good vendor will talk about enablement, not just delivery. How knowledge is transferred. How internal capability is developed. How governance is maintained when priorities change or people leave. If the long-term answer is “retainer support”, ask what that actually achieves. Support without progression is just dependency with better branding. 6. How do you handle internal resistance and conflicting priorities? Marketing Ops rarely fails for technical reasons. It fails because people don’t agree. Sales wants speed. Marketing wants control. Leadership wants reporting. No one wants extra admin. A vendor that pretends this isn’t part of the job is either inexperienced or avoiding the issue. Listen for whether they talk about stakeholder management, change management, and decision rights. Do they help clients navigate trade-offs, or do they simply take instructions from whoever shouts loudest? A strong partner understands that alignment is work, and that avoiding it only pushes the problem downstream. 7. How do you decide when not to automate something? Automation is seductive. It feels like progress. It looks impressive in demos. It also amplifies bad process faster than anything else. Experienced Marketing Ops vendors are cautious about automation for its own sake. They know that some manual steps are valuable. They know when stability matters more than scale. They know that complexity has a cost that doesn’t always show up immediately. If a vendor frames automation as the default answer, be careful. The best operators are selective, not enthusiastic. 8. How do you work with data when it’s incomplete, inconsistent, or politically sensitive? Every organisation says data matters. Very few are honest about the state it’s in. Marketing Ops sits at the intersection of systems that were never designed to agree with each other. CRM, marketing automation, analytics, finance, product. Data ownership is unclear. Definitions are contested. Trust is fragile. A serious vendor will acknowledge this openly. They will talk about pragmatism, prioritisation, and building confidence over time. They won’t promise perfect data. They’ll promise usable data that improves. If they gloss over this, you’re likely buying optimism instead of experience. 9. What does a good client look like to you? This is an underrated question, and it’s revealing in both directions. Vendors who say “we can work with anyone” usually mean “we haven’t learned where we’re most effective”. The best partners know the conditions they need to succeed, and they’re willing to say when a fit isn’t right. Listen for honesty here. Do they value clarity, sponsorship, and willingness to change? Do they expect engagement, not just approval? A vendor who cares about this is protecting both sides. 10. If we were disappointed after six months, what would you expect to have gone wrong? This question disarms rehearsed answers. It forces reflection. It surfaces assumptions. It reveals whether the vendor takes shared responsibility or defaults to blaming the client, the tools, or the brief. A thoughtful answer will include things within their control and things outside it. It will acknowledge risk, not deny it. And it will sound like someone who has learned from difficult engagements, not just successful ones. That’s the experience you want on your side. A final thought Marketing Operations is not a service you bolt on. It’s a capability you build. The right vendor doesn’t just make your systems work better. They help your organisation understand itself more clearly. How decisions are made. Where friction exists. What’s getting in the way of performance. If a vendor is willing to have these conversations before you sign, that’s usually a good sign. If they aren’t, the warning signs were there all along. Discover our Services

There is a persistent belief that somewhere out there exists the perfect MarTech stack. The right combination of platforms. The right integrations. The right configuration. Once it is all in place, everything will finally click. Reporting will make sense. Campaigns will flow effortlessly. Data will be clean. Teams will move faster. Arguments will disappear. This belief is comforting. It suggests that complexity is temporary and that clarity is only one more implementation away. It also keeps vendors in business and Marketing Ops teams in a constant state of transition. Because if the perfect stack exists, then the problem is never how you work. It is simply that you have not assembled the right tools yet... The endless rebuild cycle Most MOPs teams are quietly stuck in a loop. Something is not working. Attribution feels unreliable. Automation feels brittle. Reporting raises more questions than answers. Confidence drops. So the conversation begins again. Do we need a new platform? Do we need to upgrade? Do we need to replace this piece with something more modern? Six months later, there is a new stack diagram. New contracts. New excitement. A short honeymoon period where everything feels possible again. Then reality returns. The issues creep back in, just wearing different interfaces. What the perfect stack fantasy hides The fantasy of the perfect stack hides a harder truth. Technology does not create clarity. It reflects it. If your processes are inconsistent, the stack will feel unpredictable. If ownership is unclear, the stack will feel fragile. If decisions are political, the stack will become a battlefield. No amount of tooling fixes those problems. It simply records them more efficiently. The perfect stack does not exist because Marketing Operations is not a fixed environment. It is a moving system shaped by people, priorities, pressure, and compromise... Aspirational Marketing Ops vs actual Marketing Ops Most teams design their stack for an aspirational version of themselves. A future where processes are clean and followed. Where data is pristine and trusted. Where definitions are agreed and rarely challenged. Where everyone plays by the rules. This is the version of the organisation that shows up in strategy decks and vendor demos. It is not the version that shows up on a Tuesday afternoon when a campaign is late, a stakeholder is shouting, and someone needs a workaround right now. That future rarely arrives. And when the stack is built for it, frustration is inevitable. The danger of designing for perfection Designing for perfection creates brittle systems. Everything works as long as nothing unexpected happens. As long as no exceptions are required. As long as priorities do not shift. But Marketing Ops lives on exceptions. Urgent requests. One off campaigns. Last minute changes. Political compromises. When the stack cannot accommodate reality, teams work around it. Shortcuts appear. Logic is duplicated. Standards erode quietly. Over time, the system becomes harder to trust and harder to change. Then the stack gets blamed. Complexity is not sophistication One of the biggest misconceptions in MarTech is that complexity equals maturity. More tools. More integrations. More layers. More dashboards. It looks impressive. It feels advanced. It often signals effort rather than effectiveness. True sophistication is boring. It is repeatable. It works under pressure. It survives staff turnover and shifting priorities. Most stacks fail not because they are too simple, but because they are too clever for the organisation operating them. The hidden cost of constant change Chasing the perfect stack has a cost that rarely shows up in budgets. It drains confidence. It erodes institutional knowledge. It trains teams to wait for the next platform rather than fix today’s problems. People stop investing emotionally in systems they assume will be replaced. Documentation falls behind. Ownership weakens. Eventually, the stack becomes something people tolerate rather than trust. At that point, no tool can save it. Vendors are not the villains It is tempting to blame vendors for this cycle. Overpromising. Overhyping. Selling certainty. But vendors sell tools, not operating models. They cannot see how decisions are made inside your organisation. They cannot enforce discipline. They cannot resolve internal misalignment. Their platforms work best when the customer knows how they want to work. That is not a technology problem. It is a leadership one. Fit beats feature sets The most effective stacks are rarely the most advanced. They are the ones that fit. They fit the team’s skills. They fit the organisation’s appetite for change. They fit the reality of how work actually gets done. They may lack cutting edge features. They may look unsophisticated on a slide. But they are trusted. And trust creates speed. Why “just one more tool” never works When a MarTech stack feels broken, the instinct is to add something to fix a specific pain. Better reporting. Better orchestration. Better attribution. Each addition makes sense in isolation. Together, they increase complexity and dependency. Without addressing how decisions are made and who owns what, every new tool becomes another surface for confusion. The problem was never the missing tool. It was the missing clarity. The stacks that actually last Stacks that last share a few quiet traits. They evolve slowly. They are pruned aggressively. They are shaped by constraints, not fantasies. They prioritise consistency over novelty. They value understanding over features. Most importantly, they are supported by an operating model that people understand and respect. The stack does not carry the organisation. The organisation carries the stack. Letting go of the fantasy Letting go of the perfect stack fantasy is uncomfortable. It means accepting trade offs. It means admitting limitations. It means choosing what not to do. But it also brings relief. The conversation shifts from what we should buy to how we should work. From what we lack to what we can actually sustain. Progress replaces churn. A better question to ask Instead of asking whether your stack is perfect, ask a better question. Does this stack support how we actually behave under pressure? Not how you want to behave. Not how the process says you should behave. How you really behave when priorities collide and time runs out. If the answer is yes, you are closer to success than any vendor demo will ever get you. The truth nobody sells There is no perfect MarTech stack. There is only a stack that fits your reality today and can evolve with you tomorrow. Everything else is a distraction dressed up as progress. And the sooner teams stop chasing perfection, the sooner they can build something that actually works. Discover our MOPs Maturity Indicator

If you listen to most Marketing Operations teams talk about their problems, you would think technology is the villain. The CRM is too rigid. The automation platform is too complex. The analytics tool is not telling the full story. The integration is flaky. The dashboard is wrong again. So the solution becomes obvious. Buy something new. Replace something old. Add another layer. Plug a gap. Fix the stack. Except here is the uncomfortable truth most teams avoid. The technology usually works exactly as designed. It just exposes an operating model that does not. The stack takes the blame for human problems MarTech has become the easiest thing to blame because it is visible and expensive. When results fall short, the tools sit there like a convenient suspect. But look closely and the issues rarely start with software. They start with unclear ownership. With decisions made by committee and owned by nobody. With processes that exist on slides but not in reality. With teams that were never set up to operate as a system. Technology does not fix those things. It amplifies them. What people really mean when they say “the stack is broken” When someone says their MarTech stack is broken, they usually mean one of a few things. They do not trust the data. They are not confident in the outputs. They avoid parts of the platform because they are afraid of breaking something. They have built so much complexity that change feels dangerous. None of those are technology failures. They are operational ones. The stack is doing what it was told to do. The problem is that nobody can quite remember why it was told to do it in the first place. Tools scale behaviour, not intent This is the part that catches teams out. MarTech does not create discipline. It scales whatever discipline already exists. It does not create clarity. It magnifies whatever confusion is present. It does not create alignment. It exposes where alignment is missing. If your operating model is fuzzy, the stack will become chaotic at scale. If your operating model is fragmented, the stack will reflect that fragmentation perfectly. The technology is honest in a way people are not. Operating models are invisible until they fail Ask most MOPs teams to describe their operating model and you will get vague answers. They will talk about tools. They will talk about campaigns. They will talk about outputs. Very few will clearly articulate how decisions get made, who owns what, how priorities are set, and how trade offs are handled when things get messy. The operating model lives in the gaps between roles, systems, and meetings. It is rarely documented. Almost never designed intentionally. And yet it determines everything. When governance is missing, chaos looks like flexibility Many teams pride themselves on being agile. Flexible. Fast moving. But in practice, what they often mean is that there is no clear governance. Anyone can build anything. Changes happen ad hoc. Exceptions become the rule. Short term fixes pile up quietly. At first, this feels empowering. Over time, it becomes exhausting. The stack grows more fragile with every workaround. Confidence drops. Fewer people are willing to touch critical components. Knowledge concentrates in the hands of a few individuals. This is not agility. It is technical debt wearing a hoodie. Why more tools make weak models worse When operating models are unclear, adding more tools feels productive. Each new platform promises to solve a specific problem. Reporting. Attribution. Personalisation. Orchestration. Individually, these tools may be excellent. Collectively, they increase the surface area for failure. Every integration adds dependency. Every handoff adds friction. Every new interface adds cognitive load. Without a strong operating model, complexity compounds faster than capability. The quiet decay of marketing automation Marketing automation is where broken operating models go to hide. On day one, everything looks great. Clean programs. Logical flows. Clear intent. Eighteen months later, nobody wants to touch anything. Programs are duplicated. Logic contradicts itself. Exceptions have exceptions. New hires are warned to be careful. Changes take longer. Confidence erodes. The platform did not break itself. The way it was operated over time did. Ownership is the most underrated capability One of the clearest signals of a broken operating model is unclear ownership. Who owns the data model? Who owns lifecycle definitions? Who owns integrations when something breaks? Who has the authority to say no? If the answer is everyone or no one, the stack will suffer. Ownership does not mean control for its own sake. It means accountability for outcomes and trade offs. Without it, every decision becomes a negotiation and every problem becomes political. Process is not bureaucracy if it works Process has a branding problem within marketing. It is often associated with red tape, slow approvals, and creativity killers. So teams avoid defining it properly. The result is not freedom. It is inconsistency. Good process removes friction. It makes the right thing easier to do than the wrong thing. It creates confidence that changes will not cause unintended damage. Bad process slows teams down - No process exhausts them. The gap between strategy and execution Many organisations have marketing strategies that make perfect sense on paper. Clear positioning. Logical segmentation. Sensible priorities. Then execution tells a different story. Campaigns feel disconnected. Measurement is inconsistent. Reporting answers the wrong questions. This gap is almost always operational. Strategy sets direction. The operating model determines whether anything actually happens. Why maturity matters more than ambition Ambition is easy to articulate. Maturity is harder to admit. Teams want advanced capabilities before they have mastered the basics. They want sophistication without discipline. The stack gets blamed when advanced features are underused or misused. But maturity is not about features. It is about consistency. Can the team execute the same process well every time? Can new people onboard without tribal knowledge? Can changes be made without fear? Those are operating model questions, not technology ones. The cost of pretending everything is fine Most broken operating models limp along for years. People work around the issues. Heroic individuals keep things running. Problems are patched rather than addressed. Eventually, something snaps. A re-platform. A restructure. A sudden push for efficiency. At that point, the stack is declared broken and replaced at great expense. Six months later, the same patterns reappear. Different tools. Same outcomes. What strong operating models do differently Strong operating models are rarely flashy... They are clear on ownership. They define standards and enforce them calmly. They balance flexibility with control. They evolve deliberately rather than reactively. They make the stack feel simpler, even when it is not. People trust the system because it behaves predictably. That trust unlocks speed. The role of Marketing Ops is often misunderstood Marketing Ops is frequently treated as a support function. The people who fix things. The people who build stuff. The people who say no. In reality, Marketing Ops is the steward of the operating model. When empowered properly, it shapes how work flows, how decisions are made, and how tools are used to support outcomes. When underpowered, it becomes reactive and stretched, patching issues without the authority to address root causes. Tools do not create alignment Another common misconception is that shared tools create alignment. They do not. Alignment comes from shared understanding, incentives, and accountability. Tools simply make misalignment visible faster. If sales and marketing disagree on definitions, the CRM will not resolve that. It will record the disagreement in exquisite detail. Simplicity is a design choice Many teams talk about simplifying their stack. Few simplify their operating model. True simplicity requires saying no. It requires retiring things that sort of work. It requires resisting the urge to accommodate every edge case. This is uncomfortable. But it is necessary. Complexity accumulates naturally. Simplicity has to be designed and defended. The question that changes everything Instead of asking whether your MarTech stack is broken, ask a harder question. Does our operating model support how we actually work today? Not how you wish you worked. Not how a vendor assumes you work. How you really work, under pressure, with limited time and attention. That answer is far more useful than another platform demo. Fix the model before the stack Technology decisions should come last, not first . Define ownership. Clarify process. Agree on standards. Be honest about maturity. Then choose tools that support that reality. Do it the other way around and you will be having the same conversation again in two years. The stack is not the enemy MarTech is not the problem. It never was. It is a mirror. It reflects the choices, compromises, and assumptions baked into your operating model. If you do not like what you see, replacing the mirror will not help. Fix how you operate, and the stack will suddenly feel a lot less broken. Discover our MOPs Maturity Indicator

Best practice is one of the most dangerous phrases in modern marketing operations. It sounds reassuring. Sensible. Safe. It implies that someone smarter, richer, or more experienced has already figured this out, and all you need to do is follow the steps. No risk. No mistakes. No awkward conversations with leadership when things do not work. And that is exactly the problem. Because "best practice" marketing rarely produces the best results. More often, it produces average outcomes wrapped in confident language. It creates teams that are busy but not effective, sophisticated but not sharp, compliant but not competitive. "Best practice" is not a strategy. It is a comfort blanket. Where “best practice” actually comes from Most so called best practices come from a small and predictable set of sources. Large software vendors. Analyst firms. Agencies with templated offerings. Case studies from organisations operating at a completely different scale, budget, and level of complexity than yours. None of these sources are malicious. But they all share the same incentive. To standardise. Standardisation is how vendors scale. It is how agencies deliver repeatable revenue. It is how analysts create neat frameworks that look great on slides, but the messiness of reality does not travel well. So "best practice" becomes whatever works often enough, for enough people, under ideal conditions. What gets lost is context . Your market. Your buying cycle. Your internal politics. Your data quality. Your operating model. Your actual ability to execute consistently rather than theoretically. "Best practice" rarely asks whether something fits your organisation. It simply asks whether you are willing to adopt it. Why "best practice" spreads so easily Best practice spreads because it removes accountability. If something fails, the answer is ready made. We followed "best practice". We implemented what everyone recommended. We did what the vendor suggested. We aligned to the framework. Nobody gets fired for following "best practice". Even if the results are underwhelming. In fact, many Marketing Ops teams quietly rely on this. "Best practice" provides cover. It allows teams to look progressive while avoiding the harder work of deciding what actually matters. It feels safer to copy than to choose. The copy and paste problem... Spend enough time inside Marketing Ops teams and you start to notice a pattern. Campaign structures look eerily similar. Lifecycle stages are named the same. Lead scoring models differ only slightly. Dashboards track identical metrics. Different brands. Same playbook. This is not coincidence. It is the natural outcome of "best practice" thinking. When everyone copies the same approach, differentiation disappears at the operational level. Creativity becomes superficial rather than structural. Messaging might change, but the experience feels familiar. Predictable. Easy to ignore. The irony is that many teams believe they are being innovative because they have adopted the latest recommended approach. In reality, they have joined a very crowded middle. "Best practice" optimises for safety, not success "Best practice" is designed to minimise risk, not maximise impact. It optimises for not being wrong... rather than being right. This shows up everywhere. In channel choices that favour what is popular over what is effective. In metrics that are easy to measure rather than meaningful. In processes that prioritise governance over momentum. The result is Marketing Operations that looks impressive in presentations but struggles to move the needle in the real world. Safe MOPs rarely wins. When "best practice" becomes a ceiling One of the least discussed consequences of "best practice" is how quickly it becomes a ceiling. Once a team aligns to "best practice", questioning it becomes difficult. Any deviation requires justification. Any experiment must be defended. Any failure is seen as evidence that "best practice" was the correct choice all along. Over time, this creates organisational muscle memory. Teams stop asking why. They focus on execution within predefined boundaries. Growth stalls not because the team lacks talent, but because the system discourages thinking beyond what is already accepted. "Best practice" ignores organisational maturity A major flaw in "best practice" thinking is the assumption that all organisations are equally ready to adopt the same approaches. They are not. Marketing Ops maturity varies wildly. Some teams struggle with basic data hygiene. Others have robust governance and advanced capabilities. Applying the same playbook to both is not ambitious. It is reckless. What works for a team with dedicated Operations support, executive alignment, and clean data, will fail spectacularly in an organisation still negotiating ownership and process. "Best practice" does not account for this. It assumes a level playing field that does not exist. The cost of premature sophistication One of the most common consequences of "best practice" adoption is premature sophistication. Teams implement complex models before they have mastered the fundamentals. They chase advanced techniques without the operational discipline to support them. They build intricate systems that collapse under their own weight. This is how marketing stacks become bloated. How dashboards multiply without clarity. How automation programs decay quietly in the background. It looks advanced. It feels modern. It is deeply inefficient. Discover our Podcast "Best practice" vs right practice There is an alternative, but it requires more thought and more honesty. Right practice. Right practice starts with your reality, not someone else’s success story. It considers constraints as design inputs rather than obstacles. It evolves over time rather than being imposed all at once. Right practice asks different questions. What can we execute consistently today? What creates the most leverage for our team, not an idealised version of it? What will still work when attention shifts and priorities change? It is less elegant on paper. More effective in practice. Why right practice feels uncomfortable Right practice feels uncomfortable because it removes the safety net. There is no external authority to hide behind. No vendor deck to point to. No analyst quote to justify the decision. It requires teams to own their choices and their outcomes. This is why many organisations avoid it. It is easier to say we followed "best practice" than to say we made a deliberate trade off based on what we know about our business. But ownership is exactly what drives performance. How "best practice" dulls curiosity Over time, "best practice" thinking erodes curiosity. When answers are prepackaged, questions become unnecessary. Teams stop exploring alternatives. They stop challenging assumptions. They stop learning from their own data because the framework already knows best. Marketing Operations becomes procedural rather than exploratory. The danger is not stagnation alone. It is misalignment. The market changes, buyers evolve, channels shift, and yet the playbook remains the same. By the time teams realise something is wrong, they are deeply invested in an approach that no longer fits. The myth of universal maturity "Best practice" assumes that success looks the same everywhere. It does not. Some organisations win through speed. Others through depth. Some through consistency. Others through creativity. There is no single optimal path. Trying to force every team into the same mould ignores this reality. It flattens strategic diversity in favour of operational uniformity. Uniformity is easy to manage. Diversity is harder. But diversity is where advantage lives. What high performing teams actually do differently High performing MOPs teams are not anti "best practice". They are selectively sceptical. They understand the intent behind recommended approaches, but they adapt ruthlessly. They borrow principles, not processes. They test ideas before scaling them. They simplify aggressively. Most importantly, they revisit decisions regularly. What was right practice six months ago might not be right today. They treat it as a system, not a checklist. Letting go of borrowed confidence "Best practice" gives borrowed confidence. It feels like certainty, but it is second hand. Right practice builds earned confidence. It comes from understanding your own performance, limitations, and strengths, and this shift is subtle but powerful. Teams stop asking whether they are doing what they should be doing and start asking whether what they are doing is working. That question changes everything. The real reason "best practice" is so hard to abandon "Best practice" is hard to abandon because it is socially reinforced. Peers talk about it. Conferences celebrate it. Vendors reward it. Recruiters expect it. Job descriptions demand experience with it. Opting out feels risky. It feels like stepping off a well lit path into something less certain. But growth rarely happens on well lit paths. Choosing effectiveness over elegance "Best practice Marketing Ops" often looks elegant. Clean diagrams. Neat stages. Clear labels. Right practice is messier. It reflects reality. It evolves. It sometimes contradicts itself as conditions change. Elegance is overrated. Effectiveness is not. The goal of Marketing Operations is not to look mature. It is to create impact. The question worth asking Instead of asking whether something is "best practice", ask a better question. Is this right for us, right now? That question forces honesty. It invites trade offs. It creates ownership. It also opens the door to something far more valuable than best practice... Progress. Discover our MOPs Maturity Indicator