Essays, teardowns, and frameworks from the Checkpoint team: RevOps, GTM, HubSpot, AI, and the unglamorous plumbing that decides whether a quarter lands.
Noah CharakServices firms now publish six-figure minimums and fixed monthly tiers, and AI engines quote them as the market range. Here is what actually drives geo program cost, and how to budget conservatively.
Noah CharakThe scoring model looks fine on paper. The data it reads is not. Here is the mechanism by which enrichment errors quietly corrupt lead prioritisation, and why the data layer is almost always where the real fix lives.
Noah CharakShare of voice tracks your keyword rankings. Share of model tracks your citations in AI-generated answers. As more B2B buyers start their research in ChatGPT or Perplexity, the gap between those two numbers is becoming a pipeline problem, not just a marketing metric.
Noah CharakMost marketing leaders I talk to assume their SEO program will eventually extend to AI citations. It won't. Ranking and being cited are governed by different mechanisms, and understanding that gap is the first step toward actually improving your AI search visibility.
Noah CharakIf you've been paying an SEO agency for a year and wonder why SEO isn't improving search performance in ChatGPT or Perplexity, the answer usually isn't a bad agency. It's a scope mismatch.
Noah CharakEvery major agency is now packaging AEO as a new line item. The problem is that citation by AI assistants is a structural outcome, not a service layer. Here's what an answer engine optimisation strategy actually requires.
Noah CharakWhen pipeline numbers fall short, teams instinctively audit conversion rates. But in most CRMs we touch, the revenue leak starts earlier, in the data underneath the funnel.
Noah CharakWhen a buyer asks an AI assistant who to call for RevOps, they're making a shortlist decision before ever visiting your site. Answer engine optimisation is about being in that answer, not ranking on a results page.
Noah CharakAgencies are bolting AI search on as a sixth SEO service. The instinct is understandable, but the frame is wrong. Getting cited by AI assistants is a pipeline and data discipline, not a content one.
Noah CharakA search for a RevOps firm's pricing tells you something specific about where buyers are in their evaluation. Here's the mechanism behind productised RevOps pricing, and what to ask before you commit.
Noah CharakA large HubSpot agency just launched AEO as its sixth service, and a well-known SEO agency rebuilt its entire brand around AI Search. The move makes sense on paper. But ai search optimisation that moves citations is a GTM problem, not a content problem, and bolting a service onto a HubSpot implementation shop doesn't change that.
Noah CharakOne productised RevOps firm built its entire acquisition motion around a free revenue leak scan. Here's what that kind of gtm audit gives you, and where the diagnostic ends and the real work begins.
Noah CharakThe tools are multiplying. The strategies aren't. Here's what a GEO monitoring platform's push into full-stack marketing and an SEO agency's relevance engineering rebrand mean for your GEO strategy for B2B, and who actually owns it.
Noah CharakEvery AEO point tool eventually tries to become a platform. Here's what one prominent AEO vendor's repositioning this week reveals about the debate, and why it still doesn't fix GTM without RevOps orchestration.
Noah CharakThe debate around relevance engineering vs GEO has moved from niche SEO forums to real budget conversations. The technical work is sound. The operating assumption underneath it usually isn't.
Noah CharakOne AI visibility platform's $96M Series C signals a gold rush in AI visibility tooling. The real question: is your team buying dashboards or building the operating layer that turns visibility into revenue?
Noah CharakThe buyer already has an opinion before your rep sends the first email. They asked ChatGPT, skimmed Perplexity, and read what Google AI Overviews served up. If your brand was not cited, you were not in the conversation. That is a RevOps problem.
Noah CharakOutbound works, revenue grows, and every deal still runs through the founder. The bottleneck is not headcount. It is that the playbook lives in one person’s head.
Noah CharakWhen a domain provider refuses your sequencer’s CNAME, the instinct is to fix the tracking. The better move is to ask what that number was ever telling you.
Noah CharakWhen a founder asks where a project stands and nobody can answer, the instinct is to connect the two systems holding the data. That is the wrong fix. What you need is a thin status layer above the journey, and handoffs that are gated instead of mirrored.
Noah CharakEvery revenue system has a single point of failure, and it is almost never the software. How to distribute CRM ownership before a resignation makes the decision for you.
Noah CharakAI agents now sit inside B2B evaluations, checking whether they can drive your product through MCP, an API, or a CLI. Most products fail a test they have never run on themselves.
Carolina DecastriWhen a company asks us to fix the messaging, the first question is not about the words. It is who buys this, and what are we best at for them.
Noah CharakExpansion is the cheapest revenue most B2B teams have and the worst-instrumented. Why upsell needs its own pipeline, and how to build one that does not rot your forecast.
Noah CharakThe GTM engineer is the role of the moment, but it is not the RevOps job. One makes the machine do more; the other keeps it honest. Hire the wrong one alone and your CRM quietly drifts from reality.
Noah CharakAn AI SDR multiplies an outbound motion that already works. A new product launch has no motion yet, so build the engine first.
Noah CharakRevenue does not leak in the middle of your funnel. It leaks at the two handoffs nobody owns: the lead nobody contacts in time, and the won deal nobody picks up.
Noah CharakThe signed order form is the real record of what you sold. Your CRM is a rough approximation that drifts a little further every cycle, and the renewal pays for it.
Noah CharakView sprawl is the quiet reason your team cannot agree on the numbers. The fix is not another dashboard, it is fewer, shared views that everyone reads from.
Noah CharakA CRM go-live project plan confirms the tasks are done. It does not confirm the flow works. The cheapest insurance before cutover is a timed, end-to-end dry run of the whole customer journey, with fix-time booked in before launch.
Noah CharakEvery tool now sells you buying signals. A feed of signals is not a strategy. The teams that turn signals into pipeline define the critical event first: the specific moment a buyer actually needs what you sell.
Carolina DecastriMost CRM implementations nail the build. The automation works in demos, the pipeline renders correctly. Then the team starts using it, and the first field that populates with a value nobody can explain costs you a quarter of the goodwill you just built.
Noah CharakFinance is forecasting one number. Sales is forecasting another. The board is squinting at a third. Here is why they almost never line up, and the operator change that fixes it.
Carolina DecastriEvery lifecycle workshop hits the same fork: does ICP fit gate entry to the next stage, or does it score within it? Most teams pick one without realising the choice reshapes their entire funnel.
Noah CharakThe standard advice is to wait until a lead is qualified before you create the deal. The result is a drawer of fifty hot SQLs the forecast never sees. The pre-pipeline stage fixes the visibility gap without breaking the forecast.
Noah CharakYour ad platform optimises for whatever conversion event you send it. If the only event you send is a form fill, the algorithm will buy you more form fills. The fix is to send the SQL-stage transition from your CRM back to the platform as an offline conversion. Two workflows, one webhook, six weeks. Here is how it works.
Noah CharakWhen half of your open deals are past their close date, your forecast is fiction. Here is the diagnostic we run on every inherited HubSpot or Salesforce pipeline before any forecast conversation is allowed to start.
Noah CharakA brownfield migration is the audit, not the re-platform. Here is the framework we run on every inherited HubSpot and Salesforce instance before any data moves.
Noah CharakA Salesforce-to-HubSpot migration is a field-level triage exercise, not a 1:1 mapping. Run keep / edit / delete on every Salesforce field, force the picklist consolidation, unwind the formula fields into HubSpot calculations or workflows, and translate lookups into association labels. The signed triage spreadsheet is the cutover artifact; the import is just what runs after.
Noah CharakAI-assisted RevOps automation now ships net-new HubSpot workflows from a natural-language brief, but the failure modes are small, accumulating, and invisible in the chat log. The fix is a verification protocol that reads system state instead of trusting the assistant's report: and a recovery loop that rolls back at the workflow level, not the database level.
Noah CharakMost mid-stage B2B SaaS teams reach for Salesforce CPQ when the actual problem is product-library debt and a quote document that does not reflect what was sold. The CPQ-lite stack: HubSpot line items as the source of truth, PandaDoc as the rendered quote, a disciplined product library, and three approval rules, covers most of the use case at a fraction of the cost. Below a certain rep count and SKU count it outperforms a CPQ rollout; above it, the same stack becomes the bridge to a real CPQ migration.
Noah CharakMid-stage SaaS and financial-services teams default to Sales Hub seats for relationship managers and discover after rollout that the workflow they actually need: ticket SLAs, ownership escalation, conversation routing, lives in Service Hub. The right setup is Service Hub for the RM workflow with a single Sales seat at the team-lead level for upsell deals; pick the seat before the contract, not after.
Noah CharakB2B sales motions with a parallel offer or onboarding workflow do not belong in a single HubSpot deal pipeline. The right architecture is a deal pipeline owned by the AE running in parallel with a ticket pipeline owned by RevOps, with the deal gated from Closed Won until the ticket is closed. Modelling the operational work as deal stages turns the AE into a coordinator and slows pipeline.
Carolina DecastriSelling B2B SaaS into Italy is not a translated version of the DACH or UK motion. The buying conversation is relationship-anchored, the pricing frame arrives by call two, and the HubSpot architecture needs preferred-language and routing-region as first-class properties on contact create, not afterthoughts.
Noah CharakMost teams buy programmatic outbound by category: sequencing, enrichment, signals, and stitch the tools together with email exports. The right architecture is signal-first, a single named trigger fires a scrape, the scrape writes into an enrichment spine, the spine routes matched contacts into the CRM with a buying-signal property, and the CRM owns the workflow that schedules the LinkedIn send. Any tool is replaceable; the signal-to-action contract is not.
Noah CharakThe five-phase Checkpoint methodology: Discovery, Design, Build, Launch, Optimise, is the load-bearing skeleton of any HubSpot implementation. The predictable failure mode is compressing Discovery, a week of conversations gets misread as alignment, Design lands on an unstable schema, and Build re-litigates decisions that should have been signed off in week two.
Carolina DecastriUTM attribution in HubSpot breaks the moment an anonymous session becomes a known contact: cookies and session tokens stop telling the same story as the contact properties. The fix is a session-token property on the contact, populated on first form fill, that maps backward into the Looker session table, turning attribution from a guess into a join.
Noah CharakMost stalled HubSpot implementations are not technical failures, they are ownership failures. The rubric Checkpoint runs assigns one controlling owner across the project, named domain owners across marketing, CRM, external data, service, and reporting, and a short approver list with a defined response window. With it in place, the third-week disagreement over a property is a fifteen-minute decision, not a meeting series.
Carolina DecastriMost B2B SaaS teams treat the sales-to-CS handover as a kickoff meeting, which is why CS opens every onboarding cold. The fix is a sales-room artifact captured before close that names the buyer's outcome, the champion, the blocker the seller solved, and the success criteria. CS reads the artifact in week one and runs the kickoff as a confirmation, not a discovery.
Noah CharakThe HubSpot MCP integration with Claude turns a meaningful slice of CRM administration into a conversation: bulk property renames, property-group reorganisations, and workflow pauses now ship end-to-end against a sandbox without a developer in the loop. The pattern works today because those operations are declarative and idempotent, which is the class of change a language model can scope cleanly. The operating question is not whether to use it, it is which three guardrails you wrap around it before any change touches production.
Carolina DecastriMost HubSpot instances ship with a single lead source property and three teams disagreeing about what it means. The fix is property architecture, not a better dashboard: a first-touch field (write-once on contact create), a last-touch field (updatable by integration), and a converting-touch field (locked at MQL or form submit). Each report picks one property; none of the reports average them.
Harmeet ObhraiWhen an embedded RevOps consultant rotates out, the relationship doesn't transfer, the schema does. The artifact that holds 90 days post-rotation is a written record of every object, property, association label, and workflow trigger, with one sentence of rationale per non-obvious decision. A Loom is not a handover, and the next consultant reads the rationale, not the recording.
Noah CharakPlatform teams at venture funds inherit messy HubSpot instances across a dozen portfolio companies, then try to fix them one at a time. The support model that compounds is a single 90-minute audit template: pipeline definitions, lead source attribution, marketing-contact accounting, renewal hygiene, run identically across the portfolio, with interventions matched to one of four problem categories rather than to the company.
Carolina DecastriThe default booth-CSV import marks every conference attendee as a marketing contact, doubles the HubSpot bill, and triggers the wrong workflows. Import as non-marketing contacts, tag with a campaign property, run a single-step subscription confirmation, and only flip to marketing-contact once opt-in is recorded. Sales follow-up runs on a parallel event-lead property, not on subscription status.
Noah CharakBefore any data moves, the binary question is whether your CRM project is a clean rebuild (greenfield) or an inheritance (brownfield). Three diagnostic questions decide it: history value, deadline pressure, and schema-debt scope. Two of three pointing the same direction is enough to commit; one of three is the conversation worth slowing down for.
Carolina DecastriMost HubSpot renewal forecasts break because reps treat the deal amount as a single typed-in number while finance reconciles at the line-item level. The fix is to anchor renewal deals to the originating subscription's line items, lock GAV to the sum of active line items, and split upsell and downgrade into associated sub-deals. The dashboard then matches the invoicing system without changing what the rep does day-to-day.
Noah CharakMost B2B SaaS pipelines collapse to three stages: qualified, proposal, closed, and lose deals in the gap between problem confirmed and contract signed. The five-stage model that survives contact with real pipelines is Educate, Discover, Value, Setup, Closed Won, where each stage maps to a distinct buyer behaviour and a distinct seller action. The Value stage is the one most teams skip, and skipping it is why deals die in legal.
Harmeet ObhraiWhen a HubSpot portfolio custom object lives one hop away from the deal, through the primary contact, the deal's native association table will not surface it. The three options are a native association table, a report-table embed, and a custom UI extension; the workable answer is a workflow that auto-associates every portfolio on the primary contact onto the deal at creation, even if it surfaces four or five records instead of one.
Noah CharakSales methodology is not a religion; it is a forcing function for deal reviews. Pick by deal complexity and seller experience: BANT for high-velocity inbound, MEDDPICC for committee deals where missing roles slip quarters, and SPICED as the defensible default for everything in between.
Carolina DecastriMost HubSpot instances run a single lead grade that averages company fit and behavioural engagement, and neither team trusts it. Split the score into two contact-level properties: a fit score for cold-list filtering and an engagement score for inbound queue prioritisation. Each team weights the one that drives its actual next action.
Noah CharakMost mid-stage SaaS teams overbuy Salesforce: Service licenses, integration platform tiers, and community seats accumulate quietly between renewals. The cost-control move is a 90-day pre-renewal license audit that converts the conversation from price to scope. The audit is the leverage; the negotiation falls out of it.
Carolina DecastriMost HubSpot pipelines have stages whose definitions have drifted across reps, which is why the forecast no longer means anything. The fix is a one-page entry/exit-criteria sheet: definition, entry, exit, owner, that the team agrees on in a workshop before any reporting work happens. Anything that can't be defined in one sentence is two stages, not one; anything where entry and exit criteria match is a flag, not a stage.
Noah CharakBefore a pre-PMF founder hires a RevOps consultant, runs paid ads, or invests in outbound, the cheapest falsifiable next step is ten ICP conversations. The ten meetings rule hardens that advice into a checklist with a single, defensible exit condition: at least seven yes-yes-yes outcomes, or the ICP is not real yet.
Occasional, useful, and never noisy. RevOps and GTM essays from the Checkpoint team.