Jasper Meurs shares practical B2B marketing and revenue-operations analysis, including CRM lifecycle reporting, pipeline hygiene, and preparing business data to give AI useful context.
A seven-year-old CRM contact closed a deal this quarter.
AI needs clean CRM data, documented ICP, logged call notes, written brand voice.
Pipeline hygiene affects what lifecycle reporting can reveal about old leads.
Check first: Ask for recent per-post results and audience insights before committing.
Main ideas
AI is only as useful as the business context behind it · Read CRM lifecycles for outliers, not averages · Pipeline hygiene decides what lifecycle reporting can reveal
Jasper Meurs writes about practical B2B marketing and revenue operations, connecting CRM data and team processes to better decisions.
In one client report, a seven-year-old CRM contact became a customer; in another post, they argue that AI needs reliable business context—not just wider adoption.
They also help conference attendees turn a crowded program into a focused plan.
Meurs makes operational problems visible through specific examples and clear next questions.
A CRM lifecycle report revealed that the client’s oldest deal came from a contact who had been in the system for seven years.
They connect that finding to two practical issues: old leads can become valuable again, and incomplete closed-lost records can conceal the pattern.
In a post on AI adoption and business context, they argue that speed is not enough if AI lacks clean CRM data, a documented ideal customer profile, logged call notes or a written brand voice.
The work gives marketing and revenue teams useful questions to ask about reporting, pipeline hygiene and AI readiness.
They also take a collaborative approach to conference planning, bringing practitioners together to help attendees build a focused agenda.
Across three LinkedIn posts, Jasper Meurs returns to three practical priorities: AI adoption is moving faster than the business context that makes AI useful; CRM lifecycle reporting should focus on outliers and re-engagement, not averages; and conference attendance works better when people prepare and leave with a concrete plan.
Read more
The arguments draw on client reporting examples, a benchmark statistic, and a practitioner quote from a conference session.
AI is only as useful as the business context behind it
Meurs argues that rising AI adoption numbers do not show whether AI is improving outcomes.
Read more
The key questions: Is AI being used on work where context matters most?
Has the business built systems that give AI that context, including clean CRM data, a documented ideal customer profile, logged call notes, and a written brand voice?
A team can move twice as fast and still send the wrong message to the wrong account if AI lacks what the representative knows.
The position is not anti-AI; it sets a limit on what adoption can deliver without context.
Meurs cites KPMG's Q3 AI Pulse finding that 44% of organizations reported significant workforce AI adoption, up from 23% the quarter before.
At UNBOUND, Yamini Rangan said, "AI with bad context is worse than no AI at all," and noted that 90% of decision makers use AI while only 6% report real transformation.
Meurs pairs those points and asks readers to check whether their context has kept pace with adoption.
Meurs treats a lifecycle report as a diagnostic, not a dashboard.
Read more
Average time from contact creation to closed deal can hide the deals that matter most, especially those from people who raised a hand years earlier, went quiet, and returned when their situation changed. Segment closed deals by contact age, examine the oldest outliers, and treat long-dormant contacts as a nurture list instead of dead pipeline.
Meurs built a lifecycle report for a client where the average time from contact creation to closed deal was about eight months that year.
Most closed deals had been in the system for over a year, and the top three had been there 6 years, 6.5 years, and 7 years.
They call these re-engagements rather than new leads, concluding that old leads are not dead, just early.
Pipeline hygiene decides what lifecycle reporting can reveal
Meurs argues that the re-engagement pattern only appears when a team marks deals closed lost instead of letting them sit in the pipeline.
Read more
When representatives skip that step, reporting loses part of the story. Lifecycle analysis depends on sales discipline that many teams treat as administrative work.
In the same client lifecycle report, Meurs notes that half the story remained invisible because representatives skipped the closed-lost step. As a result, the reporting could not show the full pattern of old contacts returning.
Conference value comes from preparation and a usable plan
Meurs argues that the difference between a good conference and a great one usually comes down to preparation.
Read more
They turn attendee goals into a concrete agenda rather than leaving learning to chance. The format is collaborative and practical: speaker previews, live polling, and a tangible plan attendees leave with.
Meurs co-hosted "Build Your UNBOUND26 Game Plan," a virtual event with Nick Lafakis and Sean McGauley, twelve days before UNBOUND, when the agenda had 200+ sessions.
Nine speakers previewed their sessions, including Rachel Decker of ClearSync on separating practical AI workflows from overhyped promises; Kristeen Romero of Hey Hei Ops on what HubSpot admins and RevOps people should explore around AI and automation; George B.
Thomas of Sidekick Strategies on making conference lessons change something at home; and Jay Schwedelson of GURU Media Hub on outdated assumptions about calls to action and landing pages.
The event also featured live goal polling, a "What to Watch" segment on AI, Smart CRM, and unified data, and help building a three-day agenda on the call.
Shows why faster AI adoption does not necessarily improve results.
Read more
Start here for the central constraint in Meurs's writing: the business systems that give AI useful context.
Meurs cites KPMG's Q3 AI Pulse finding that 44% of organizations reported significant workforce AI adoption, up from 23% the quarter before.
At UNBOUND, Yamini Rangan said, "AI with bad context is worse than no AI at all," and noted that 90% of decision makers use AI while only 6% report real transformation.
Meurs argues that asking whether a team is getting more efficient with AI is the wrong question: a team can move twice as fast and still send the wrong message if the AI lacks the rep's context.
The post names the systems that matter: clean CRM data, a documented ICP, logged call notes, and a written brand voice.
For brands planning a campaign
Supports an AI-context readiness engagement. A brand could ask Meurs to turn this diagnosis into a practical audit or workshop covering CRM data, ICP documentation, call logging, and brand voice before scaling AI workflows.
Shows whether old leads are dead—and why pipeline hygiene determines what you can measure.
Read more
Start here for the clearest example of Meurs building a lifecycle report and interpreting the outliers.
Meurs describes building a lifecycle report for a client.
Average time from contact creation to closed deal was about eight months that year, but the outliers told the real story: most closed deals had been in the system for over a year, and the top three were 6 years, 6.5 years, and 7 years old.
These were re-engagements, not new leads.
The pattern only emerges when teams mark deals closed lost instead of letting them sit in the pipeline.
Reps skipped that step, leaving half the story out of the client's reporting.
For brands planning a campaign
Supports a CRM lifecycle reporting or pipeline hygiene engagement. A brand could ask Meurs to build a lifecycle report or review closed-lost discipline, making re-engagement opportunities visible instead of leaving them buried in stale pipeline.
Shows how Meurs works with other practitioners and what a collaborative format looks like.
Read more
Start here for events, community programming, or partner-led sessions rather than written analysis.
Meurs announced a virtual event, "Build Your UNBOUND26 Game Plan," hosted with Nick Lafakis and Sean McGauley for September 10 at 11am ET.
With UNBOUND twelve days away and 200+ sessions on the agenda, nine speakers would preview their sessions and answer planning questions.
They included Rachel Decker of ClearSync on separating practical AI workflows from overhyped promises, Kristeen Romero of Hey Hei Ops on what HubSpot admins and RevOps people should explore around AI and automation, George B.
Thomas of Sidekick Strategies on making conference lessons change something back home, and Jay Schwedelson of GURU Media Hub on outdated assumptions about CTAs and landing pages.
The event also featured live goal polling, a "What to Watch" segment on AI, Smart CRM, and unified data, and help building a three-day agenda.
For brands planning a campaign
A lighter fit than the analytical posts, suited to event moderation, community programming, or a partner-led session. A brand could ask Meurs to convene practitioners around a conference or product event and turn attendee goals into a shared agenda.
CRM lifecycle reporting as a diagnostic, not a dashboard
Meurs builds lifecycle reports for clients, looking for outliers rather than averages.
Read more
In one client example, the average time from contact creation to closed deal was about eight months this year, but the deals that mattered had been sitting in the CRM for six, 6.5 and seven years before closing.
They describe these as re-engagements: people who raised a hand years earlier, went quiet and came back when their situation changed.
A lifecycle view can surface revenue that a pipeline snapshot hides.
Segment closed deals by contact age, focus on the oldest outliers rather than the mean, and treat long-dormant contacts as a nurture list rather than dead pipeline.
For brands planning a campaign
A CRM lifecycle reporting brief can call for a clear piece of work: analyze closed deals by contact age, identify outliers and develop a re-engagement angle for the nurture list. The value for a brand lies in the analysis and interpretation, not just the report build.
Pipeline hygiene is the precondition for lifecycle insight
Meurs argues that the re-engagement pattern is visible only if the team marks deals closed lost instead of letting them sit in the pipeline.
Read more
In the client example, half the story stayed invisible in reporting because reps skipped that step. The quality of a lifecycle report depends on a sales discipline many teams treat as admin.
Audit whether closed-lost outcomes are being recorded before trusting any time-to-close or re-engagement analysis.
Meurs puts the case plainly: old leads are not dead, they are early. That reframing is the argument a brand would be buying into, not just a reporting technique.
For brands planning a campaign
Any engagement scope should include closed-lost discipline as a deliverable.
Without that step, the report will stall where the client's did.
The campaign brief should make this clear before work starts.
AI context readiness as the real adoption question
Meurs sets KPMG's Q3 AI Pulse finding—that 44% of organizations report significant workforce AI adoption, up from 23% the previous quarter—against a line from Yamini Rangan at UNBOUND: AI with bad context is worse than no AI at all.
Read more
They add Rangan's other figure, that 90% of decision makers use AI but only 6% report real transformation, and use the pairing to argue that efficiency is the wrong question. A team can move twice as fast and still send the wrong message because the AI did not know what the rep knew.
Pair a benchmark adoption statistic with a practitioner quote, then turn to a diagnostic question rather than a tool recommendation. Meurs asks whether AI is being applied where context matters most and whether the business has built systems that feed it context.
For brands planning a campaign
For a CRM or RevOps engagement, frame the work around context infrastructure rather than AI tooling.
Meurs names four concrete inputs: clean CRM data, a documented ICP, logged call notes and a written brand voice.
A brief can specify these scoping items, making the engagement measurable.
Meurs co-hosted a virtual event to help people plan their UNBOUND conference week, working with Nick Lafakis and Sean McGauley and bringing in nine additional speakers to preview sessions.
Read more
The agenda covered how to separate practical AI workflows from hype, what HubSpot admins and RevOps people should explore, how to turn conference learning into action after the trip, and outdated CTA and landing-page assumptions.
It also included live goal polling, a segment on AI, Smart CRM and unified data, and a session to build an actual three-day agenda on the call.
Registration was free, and the event had 30-plus sign-ups at the time of posting.
Community webinar format built around a specific event: speaker previews, live polling, a themes segment and a tangible output for attendees.
For brands planning a campaign
Meurs can lead a co-produced pre-event or community webinar as well as analysis work. A brand could support planning content around an industry event or commission a session that gives attendees a usable artifact rather than a brand message.
Meurs's posts do not state a sponsorship, paid partnership, employment, ownership stake, or named client.
Read more
Two brands appear as mentions: HubSpot, whose UNBOUND conference they built a free virtual prep event around and whose chief executive they quote, and KPMG, whose Q3 AI Pulse survey they cite in their argument about AI context. A separate client engagement appears in a CRM lifecycle post, but the client is never named; ask for its identity before treating it as a brand item.
HubSpot
Mention
Meurs organized and hosted "Build Your UNBOUND26 Game Plan," a free virtual event to help attendees plan for HubSpot's UNBOUND conference, with nine speakers including HubSpot's Jennifer Nixon and Kyle Jepson previewing their sessions.
Read more
A later post quotes HubSpot chief executive Yamini Rangan on AI without enough context. Ask whether Meurs has any sponsorship, employment, paid partnership, or client relationship with HubSpot.
Meurs cites KPMG's Q3 AI Pulse survey, which found 44% of organizations reporting significant workforce AI adoption, up from 23% the prior quarter, to support their argument that AI adoption is outpacing the context systems behind it.
Read more
They discuss the findings rather than promote a KPMG product or service.
Jasper Meurs writes about the gap between AI adoption and AI results, and what a well-built CRM can show when someone actually reads it.
Read more
The posts cluster into two strands.
One is client work: a lifecycle report where the average time from contact to closed deal was about eight months, but the deals that mattered had sat in the CRM for six, 6.5, and seven years before closing.
Meurs calls these re-engagements and argues that old leads are not dead, just early — and that the pattern stays invisible unless reps mark deals closed lost.
The other strand is context: rising adoption numbers are the wrong measure if the AI never knew what the rep knew.
If you care about pipeline reporting, start with the lifecycle post.
If you run events, the conference-planning post is the practical one.
O'Malley makes the same argument as Meurs: context quality determines whether AI helps a business or drags it backwards.
Read more
O'Malley writes that most context is generic and poor context is worse than none.
A sales rep instinctively knows when a deal stage is wrong, while AI acts on whatever information it has — recommending discontinued products, analysing pipeline against wrong numbers, and drafting outreach for buyers who left.
Meurs quotes Yamini Rangan to a similar end, then asks readers to check whether their own systems feed AI clean CRM data, a documented ICP, logged call notes, and a written brand voice.
O'Malley writes from inside a platform vendor, framing the argument around product moves — Growth Context, a self-updating Smart CRM, a Context Home launched at a conference — and field reporting on events and teams.
Meurs works from a single client's reporting and ends with a diagnostic question rather than a product.
Follow O'Malley for where the platform says it is going; read Meurs for how to check whether your own data supports any of it.
Marguglio splits the same problem Meurs raises into two sides.
Read more
Internal context — CRM data, processes, customer history, sales conversations, support tickets — lets AI agents reason and act, making CRM structure and data quality more important, not less.
External context is what ChatGPT, Gemini, Claude, and AI Overviews understand about a brand; that is where answer engine optimization comes in.
Meurs covers the internal half in the same terms.
Marguglio writes as an agency owner building a service line: he describes a 13-year HubSpot practice evolving into an AEO growth agency, quotes a client review, and asks prospective buyers which will matter most: HubSpot adoption or AEO strategy.
Meurs's posts stay analytical and stop at the finding.
Read Marguglio for what an AEO-plus-HubSpot engagement looks like; read Meurs for the reporting that tells you whether you need one.
Meurs draws directly on Rangan's framing that AI with bad context is worse than no AI at all, and that 90% of decision makers use AI while only 6% report real transformation.
Read more
Rangan's own writing carries the same thread: a CRM that updates itself so the record reflects what actually happened, and a warning that vibe coding a workflow is not the same as building a platform with integrations, permissions, governance, and trusted data. Both treat the data foundation, not the model, as what determines whether AI delivers.
Rangan writes at platform scale, announcing marketing and CRM releases and answering objections about trust, integrations, and security audits.
Meurs writes about one client's lifecycle report.
Follow Rangan for where the tooling is heading; turn to Meurs for what to do with what you already have.
The posts support a small-audience placement, not a reach buy.
Read more
Jasper Meurs' LinkedIn account showed 1,827 followers in a snapshot taken 11 October 2026.
The three posts from 28 August to 29 September 2026 carry no engagement or impression figures, so treat this as an early-stage professional account where relevance and message fit matter more than scale.
The content points to a marketing, RevOps and CRM operations readership rather than a general one.
The posts mix conference planning for HubSpot's UNBOUND event, CRM lifecycle reporting (a client report showing closed deals originating from contacts sitting in the system for six to seven years), and AI adoption, quoting KPMG's Q3 AI Pulse and HubSpot's Yamini Rangan on context quality.
For a campaign about CRM lifecycle reporting and AI-context readiness, the topic match is direct.
Before committing, ask for recent per-post results on comparable subject matter and format, plus any audience survey or platform insights covering job function, seniority, geography, age, gender and employer.
LinkedIn followers
1,827
LinkedIn profile snapshot for Jasper Meurs · 2026-10-11
Jasper Meurs’s posts do not offer partnerships or sponsorships.
Read more
The three posts include no rate card, media kit, sponsor policy, brand-collaboration terms or purchasable format.
They do show event collaboration: Meurs co-hosted a free virtual planning session ahead of the UNBOUND conference with Nick Lafakis and Sean McGauley, lined up nine speakers to preview their sessions and opened registration for free.
This was a peer-organized community event, not a paid sponsorship format.
No official partnership inquiry route appears in the posts, so no inquiry link is published.
To explore an engagement, a brand would need to raise it directly and discuss specific work, such as CRM lifecycle reporting or preparing business data to give AI useful context—the subjects the posts address.
A B2B SaaS or RevOps-focused company seeking a content or advisory engagement on CRM lifecycle reporting and AI-context readiness is a strong fit.
Read more
Jasper Meurs’s posts show them tackling both challenges.
In a lifecycle report, they analyzed a client’s closed deals and found that while the average time from contact creation to close was about eight months, the deals that mattered had been in the CRM for six, 6.5, and seven years.
The practical takeaway was not a dashboard but a re-engagement argument: old leads are not dead; they are early.
Meurs also connected the insight to pipeline hygiene, noting that the pattern stays invisible when reps do not mark deals closed lost.
Their AI post applies the same diagnostic instinct: KPMG’s Q3 AI Pulse showed adoption rising from 23% to 44%, while Yamini Rangan’s line at UNBOUND — AI with bad context is worse than no AI at all — and the 90% versus 6% transformation gap led them to name the context inputs a company needs: clean CRM data, a documented ICP, logged call notes, and a written brand voice.
A brand can scope an engagement around those inputs and define measurable deliverables.
Their LinkedIn profile had 1,827 followers in October 2026, but no per-post engagement figures are available, so the evidence supports topic relevance rather than scale.
Their posts disclose no sponsorship inventory; a brand should discuss advisory, co-produced analysis, or a workshop directly rather than plan a media buy.
This fit is strongest for a company that wants Meurs’s diagnostic, practitioner-level thinking applied to its own CRM and AI context, not reach.
When to choose a specialist
A broad-reach brand-awareness campaign needs guaranteed impressions, multi-channel reach, and a documented paid sponsorship product—for example, a consumer or horizontal software brand buying a scaled social package with performance commitments.
Read more
Meurs is a poor fit for that brief.
Their LinkedIn profile showed 1,827 followers on 11 October 2026, but there are no engagement, impression, or demographic figures to support a scale or audience-targeting promise.
Their posts disclose no rate card, media kit, sponsor policy, or paid format.
The only event mentioned is a free, peer-organized UNBOUND planning session co-hosted with Nick Lafakis and Sean McGauley and nine other speakers; it is community programming, not sponsor inventory.
The available material comprises three LinkedIn posts, with no transcripts, video, long-form articles, or other channels.
It supports narrow, topic-led work, not a mass-reach sponsorship.
A brand that still wants to work with Meurs should supply its own reach, use the engagement for subject-matter advisory or co-produced content, and accept that the posts do not support performance guarantees.
A worked campaign example
Worked campaign angle for a good-fit engagement: “Context Before Velocity.”
Phase 1 — Lifecycle outlier audit.
The company provides de-identified CRM data.
Meurs segments closed deals by contact age, reproduces the eight-month average versus long-dormant outliers pattern from the client lifecycle post, and checks whether closed-lost outcomes are being recorded.
Deliverable: a short written diagnostic and a re-engagement shortlist that identifies hygiene gaps.
Phase 2 — AI-context readiness checklist.
Using the four inputs named in Meurs’s AI post—clean CRM data, a documented ICP, logged call notes, and a written brand voice—the engagement runs a scored review and produces a one-page readiness scorecard.
Phase 3 — Practical content handoff.
Meurs co-produces one field-guide article or webinar for the company’s RevOps audience, based on the audit’s actual findings rather than a generic AI message, with an optional follow-up session to turn the scorecard into a 30-day action list.
Campaign angle: “Your AI adoption number went up.
Did your context?”
The hook comes from the AI post, which contrasts rising adoption with the context gap.
The lifecycle audit gives the company a concrete revenue example; the hygiene check addresses Meurs’s stated precondition for insight; and the context scorecard turns the AI post’s argument into a defined scope.
Measurable outputs could include closed-lost completion rate, number of re-engaged opportunities identified, and completion of the context scorecard.
Meurs’s posts do not state their commercial terms, so the company must agree scope and fees directly.
Avoid promising sponsored reach; frame this as advisory or co-produced content.
Choose O'Malley when the company already runs on HubSpot and wants the engagement framed at platform level: how the CRM feeds context into AI, where the gaps sit, and what a vendor roadmap means for a multi-country or upmarket team.
Read more
The DMEXCO post shows a full go-to-market organisation working a two-day event in Cologne, with marketing, sales, services, channel and business development on one stand.
The UNBOUND post makes the case a buyer selling a CRM or context programme internally needs: most context is generic, and poor context is worse than none, because AI will recommend discontinued products, analyse pipeline against the wrong numbers and draft outreach to buyers who left months ago.
O'Malley points to HubSpot's self-updating Smart CRM and Growth Context, citing companies on HubSpot creating nearly 3.6x more MQLs, winning 3.2x more deals, and closing over 2x more tickets.
For a buyer who has to sell a CRM or context programme internally, this is the argument, delivered from inside a large EMEA team.
The posts make the case for HubSpot's context products rather than diagnosing a reader's own records.
They offer no client-level analysis comparable to the lifecycle report: no deal-age outliers, closed-lost hygiene check or re-engagement shortlist.
The numbers cited are the vendor's own benefit figures, not a report pulled from a customer's CRM.
If you need an independent audit that identifies gaps in existing data, Jasper Meurs is the closer fit; if you need an internal case for the platform and the team around it, O'Malley's framing does more of the work.
Marguglio fits when the engagement includes implementation, not just diagnosis.
Read more
His AEO post names the three capabilities he treats as necessary: deep HubSpot CRM expertise, proven SEO and AEO strategy, and the ability to connect AI, marketing, sales and service through CRM data.
The post traces an agency history of 24 years in business and more than 13 years on HubSpot, moving from web and SEO to inbound, then growth, then AI-powered inbound, to what they now call an AEO HubSpot growth agency.
It anchors that history with a client CRM-onboarding review.
The UNBOUND recap adds the internal and external context split: clean CRM data, processes and logged conversations so your own agents can reason and act, plus a consistent web presence so ChatGPT, Gemini, Google AI Overviews and Claude can understand the brand.
For a company that wants one partner to clean the CRM and then make the brand legible to AI assistants, that combined scope is the closer match.
Marguglio's posts focus on agency marketing.
One centres on a five-star onboarding review and a service-line history.
They do not show a client data example like an eight-month average close time or contacts dormant for six to seven years.
The framing assumes an agency relationship, with onboarding, implementation and ongoing growth work, rather than a single audit, workshop or co-produced piece.
Choose Marguglio when the company needs build-and-run work with an implementation partner; choose Meurs when it needs a narrow, report-first engagement that starts from its own closed deals.
Rangan is the alternative when a company needs keynote-level authority on where the platform is heading.
Read more
The UNBOUND post walks through HubSpot's announcements: Marketing Studio for planning and running omnichannel campaigns from a single goal prompt, a CRM that pulls information from calls, emails, meetings and notes in real time and moves deals forward on its own, and a rebuilt assistant that answers questions, builds agents and drafts proposals from a plain description.
The through-line is the same as the need to set an AI-context agenda, stated product-first: AI needs rich context about your business, your customers and your team to deliver outcomes.
For a company that wants a senior platform voice to set the AI-context agenda at its own event or for its leadership audience, Rangan brings a stage presence a practitioner post cannot.
Rangan describes product direction, not fieldwork with a customer's records.
The post takes an announcement format: features, prompt examples and a link to the release notes, with no audit method, deal-age analysis or readiness checklist a company could run against its own data.
A buyer choosing this route gets authority and reach inside a vendor's narrative, but gives up the diagnostic detail that lets a RevOps team locate its own gaps.
If the deliverable has to come from the company's actual CRM, the lifecycle and context work is the better base.
Jasper Meurs's three LinkedIn posts here are about a UNBOUND conference-planning event, a client CRM lifecycle report, and AI adoption and business context.
No transcripts, long-form articles, video, or other channels are available here, and no per-post engagement or audience-demographic data is available.
The LinkedIn account showed 1,827 followers in a snapshot dated 11 October 2026; no publication dates accompany the post texts.
Where the page compares Meurs with other writers, those comparisons rest on the arguments in the posts rather than on follower counts or hiring scenarios.
