João Dobbin

They debunk claims about making six figures over coffee or booking hundreds of meetings on autopilot, and recommend starting with repetitive tasks. Human review remains part of the process when accuracy matters.

An LLM checks handraiser forms for fake-lead patterns and was wrong only once across a few dozen leads.

• Another screens emails sent to shared inboxes after receiving good and bad examples; it has run for months with zero issues.
• A third reads sales or customer-success call transcripts, detects risks, and posts a readable summary to Slack, though it sometimes produces a good meeting summary without identifying risks.

Read original

Sales, marketing, and customer success can act on stages only when they’re unambiguous.

Use HubSpot's Lead Object or a custom object for MQLs; create Stage 0 opportunities when a meeting is booked; track prospects as contacts or accounts, MQLs as custom objects, and SQLs as deals; use a custom object for customer-experience stages such as onboarding and renewal; and avoid acronyms if stages need to work across channels. A bonus tip: take regular snapshots of the sales pipeline.

Read original · Original 2

Growth ambitions make CRM indispensable, the argument goes, as buyer journeys grow more complicated and customer expectations rise. The quote comes from a linked article.

The post quotes: “The actual CRM you choose is less important … than how it functions.

• The key is this: You probably have ambitions to grow and scale your company.
• CRM is no longer important to that goal — it’s indispensable.”

Read original

The quote is attributed to the linked article.

The quoted warning says: “If you continue waiting for leads to come to you, especially in a time when search traffic is declining, you will have a very hard time winning against companies employing this strategy.”

Read original

They position the tool for cohort analysis, forecasting, and migration work. The post calls the recommendation free advertising, presenting it as personal enthusiasm rather than evidence of a paid partnership.

Dobbin describes adopting Coefficient to connect Google Sheets with HubSpot, QuickBooks, SQL databases, and Google Data Studio. They say the free version is already useful and add it to a minimalist stack previously described as Slack, Zapier, and Google Sheets.

Read original

Dobbin gives a practical checklist for reviewing, updating, or building lifecycle stages: keep them simple and close to industry standards; make the criteria for moving a record to the next stage readable in the CRM; track MQLs in a dedicated object, such as HubSpot's Lead Object or a custom object; create opportunities when a meeting is booked; specify which record type tracks each stage, with prospects as contacts or accounts, MQLs as custom objects, and SQLs as deals; use a custom object for customer-experience stages such as onboarding and renewal; and avoid acronyms if stages need to work across channels. A bonus tip recommends taking regular sales-pipeline snapshots.

For brands planning a campaign

For a B2B SaaS company improving RevOps, this supports a campaign around lifecycle-stage review: a workshop or audit that tests stage definitions, MQL tracking, opportunity creation, and CRM record ownership. It also points to pipeline snapshots as a forecasting or reporting offer.

Dobbin separates AI hype from practical use.

• After warning about promises such as making six figures while having coffee or booking hundreds of meetings on autopilot, they describe three implemented RevOps workflows.
• First, an LLM checks handraiser forms for patterns that suggest fake leads, with a human double-checking its judgment.
• Second, AI screens emails sent to shared inboxes, such as marketing, sales, or support addresses, after receiving examples of good and bad emails.
• Third, an LLM reads sales or customer-success call transcripts, detects risks, formats them for readability, and shares them in Slack so leadership can spot issues early.
• They note that AI sometimes produces only a good meeting summary instead of risks, but still find the use worthwhile.

For brands planning a campaign

For a B2B SaaS audience, this supports a campaign about starting small with AI in RevOps.

• Possible angles include lead-quality automation, shared-inbox triage, and transcript-based risk signals for sales or customer-success leaders.
• The human-check detail supports credible messaging.

Dobbin recommends a strategic shift for people in B2B marketing, sales, or RevOps, quoting the argument that companies waiting for leads to come to them will struggle against those using an account-driven go-to-market strategy, especially as search traffic declines. The post is brief and links to the full argument.

For brands planning a campaign

This gives brands a reason to connect RevOps content to account-based marketing or outbound strategy. A campaign could frame CRM and lifecycle work as the operational foundation for account-driven GTM, especially for teams overly dependent on inbound search traffic.

Dobbin shares an argument that the specific CRM matters less than how it functions.

• The quote says growth ambitions make CRM indispensable rather than merely important, buyer journeys are becoming more complicated, customer expectations are rising, and systems need to be ready for that.
• The post points to an external article rather than developing the argument in detail.

For brands planning a campaign

For a CRM platform or RevOps consultancy, this supports an angle about system design, data hygiene, and process fit over tool selection alone. A campaign could ask buyers to assess how their CRM functions across the buyer journey, not just which vendor they use.

Dobbin describes Coefficient as a simple but transformative tool adopted during the year.

• It connects Google Sheets to systems including CRMs such as HubSpot, finance tools such as QuickBooks, SQL databases, and Google Data Studio.
• They highlight automated updates and data snapshots for forecasting, and list use cases such as cohort analysis, forecasting, and migration to or from a new tool.
• They say the free version is already useful and add Coefficient to a minimalist stack previously described as Slack, Zapier, and Google Sheets.
• The post states plainly that this is free advertising for a tool they like.

For brands planning a campaign

For a spreadsheet, automation, or RevOps-tooling brand, this supports content about connecting operational data to CRM and finance systems, forecasting snapshots, cohort analysis, and migration work. The post's unpaid disclosure does not establish a commercial partnership.

They warn that AI scams promise unrealistic autopilot results and recommend starting small, with human review where accuracy matters.

Teaches through named workflows, observed results, and a human-in-the-loop check rather than general AI claims.

João Dobbin notes that the transcript tool sometimes produces a good meeting summary instead of detecting risks, and that the lead check was wrong once across a few dozen leads.

For brands planning a campaign

A B2B SaaS brand can use this as a practical hook for AI-in-RevOps content: lead triage, shared-inbox qualification, and post-call risk review. The posts support a start-small, measured AI narrative, not an autopilot promise.

Examples: Source 1

A bonus tip recommends pipeline snapshots and names Coefficient.

A numbered checklist with concrete record mapping across contacts, accounts, custom objects, and deals.

For brands planning a campaign

A SaaS company assessing João Dobbin for a RevOps brief can use this as ready-made content on lifecycle-stage mechanics. The detail suits a campaign about CRM hygiene, MQL handoffs, and sales-ready definitions.

Examples: Source 1 · Source 2

As growth ambitions rise, CRM becomes indispensable, buyer journeys grow more complicated, and customer expectations keep rising, so systems need to be ready.

A quote-led post that frames CRM as an operating requirement.

The post links to a longer article that is not reproduced here, so only the quoted argument can be assessed.

For brands planning a campaign

For a CRM/RevOps campaign, this offers a strategic message: evaluate systems by fit, function, and readiness for complex buyer journeys. João Dobbin is a candidate for content that lifts the conversation above tool comparisons.

Examples: Source 1

The quoted warning: waiting for leads, especially as search traffic declines, makes it hard to win against companies using this strategy.

A pointer-style post that uses a direct quote to frame the urgency.

The underlying article is not included in the post; the post is a recommendation and quote, not a full method.

For brands planning a campaign

A brand can evaluate João Dobbin for content on shifting from inbound waiting to account-driven motions. The topic connects RevOps, marketing, and sales around target-account execution.

Examples: Source 1

They highlight automated updates and data snapshots for forecasting, with use cases in cohort analysis, forecasting, and migration. They say the free version is already useful and add Coefficient to a minimalist stack of Slack, Zapier, and Google Sheets.

A firsthand adoption story with tool features, use cases, and a free-version note.

João Dobbin calls the post free advertising, framing the recommendation as personal enthusiasm rather than evidence of a paid partnership.

For brands planning a campaign

A brand can assess João Dobbin for hands-on tool content around CRM integrations, pipeline snapshots, forecasting, and lightweight RevOps stacks. The practical demo angle is stronger than a general software review.

Examples: Source 1

Their style is practical and plain, with advice to start small, review AI outputs with a human, and account for tools missing the mark. Two posts point to external reads rather than offer full explanations.

Patterns across five posts: workflow lists, record mapping, adoption stories, and quote-led recommendations.

For brands planning a campaign

For campaign planning, this suggests formats a brand can commission or adapt: workflow teardowns, lifecycle checklists, AI pilot notes, tool-stack walkthroughs, and short account-driven GTM arguments. The posts favor practical, example-led content over high-level thought leadership.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5

They add it to a minimalist stack alongside Slack, Zapier, and Google Sheets.

• In a separate post on lifecycle stages, they recommend coefficient.io for sales-pipeline snapshots for HubSpot or Salesforce users.
• Both posts are unpaid recommendations, not a disclosed commercial relationship.

Original disclosure

Yes, this is free advertising! This is how much I like it

View example

These posts show a practitioner's tool of choice, not a stated employer, client, or sponsorship arrangement.

View example

Tveter stays close to HubSpot product mechanics and rep-level routines, such as call prep, logging calls, and deal progression configuration. Dobbin works a level up on RevOps architecture: lifecycle-stage design, which CRM record tracks each stage, and bounded AI checks for lead and inbox triage.

Read original · Original 2

Both flag practical rollout conditions rather than treating the tool as self-sufficient.

Turner concentrates on HubSpot AI credit economics and quote-to-cash with Revenue Hub, including contracts and pricing data readiness. Dobbin concentrates on lifecycle-stage mechanics, CRM record mapping, and small AI wins in handraiser forms and shared inboxes.

Read original · Original 2

Both also explore how sales processes and handoffs are structured.

Sundar works through industry-level arguments and case stories, such as Jevons Paradox applied to RevOps and a scaled SDR organisation, for a broad revenue audience. Dobbin writes hands-on checklists and tool notes that RevOps practitioners can apply directly.

Read original · Original 2

Their posts put prices on HubSpot AI actions and reframe the budget question: instead of asking how to use fewer credits, ask what work is worth paying AI to do.

• The post values a resolved Customer Agent conversation at 50 credits, or about $0.50; a Data Agent response on one record at 10 credits, about $0.10; a Prospecting Agent recommendation at 100 credits, about $1; and an AI-powered workflow action at 10 credits.
• It then sets four checks before spending: the human time the task costs today, the cost of the AI action, what happens at scale, and whether the quality is good enough to trust the outcome.
• The second post tackles the same buyer decision from the process side, arguing that a Revenue Hub rollout should start with clean deal, product, pricing and customer data; begin with one product line or customer segment end to end; design around the contracts object from the start; and land and expand.
• That gives a vendor both a cost-justification angle and a rollout-sequence angle in one placement.

The tradeoff is scope and stance.

• Turner's material assumes readers are HubSpot customers evaluating its credit model and product roadmap.
• It does not offer the practitioner-side lifecycle-stage rules another creator supplies: how to keep stage names readable across channels, which record type should hold an MQL, and when to open an opportunity.
• Ask for start-small implementation examples with reported accuracy or failure rates.
• The Revenue Hub post ends with a consultancy pitch for that rollout work, so campaigns needing neutral editorial framing should account for the commercial intent; campaigns selling implementation services can use it directly.

Examples: Source 1 · Source 2

The Sales Plugin post for Claude lists eight pre-built skills and assigns a job to each: call prep ten minutes before a meeting, a daily brief that replaces scrolling a task queue, logging a call in plain language so the notes, stage change and follow-up tasks are created together, drafting the recap email from deal context, pipeline pulse before a weekly review, contact lookup, CSV or event-list import with deduplication, and a general CRM catch-all.

• It also flags the confirmation step before Claude writes to the account and recommends starting with logging calls and follow-ups.
• The Deal Progression post covers a feature rollout at the same level of detail: a new Catch-Up tab and a renamed Overview tab, the recording requirement, which deal properties the tool may update, methodology configuration for MEDDIC, BANT or SPICED with met and missing criteria shown, deal plans that generate a branded buyer portal without a HubSpot login, a re-engage prompt after 14 days of silence, and the warning that methodology and deal plans each need an admin to activate them separately.
• This is useful for campaigns offering adoption guidance or enablement training.

The tradeoff is that this is feature news and adoption instruction, not design.

• It explains what to turn on and what to check first, but not how to structure lifecycle stages, name them so they work across channels, or choose which object tracks a prospect, MQL or SQL.
• Results are reported as personal daily use, not measured outcomes, and the posts track HubSpot's release cycle, so the material may date quickly and need refreshing before a campaign runs.

Examples: Source 1 · Source 2

One post borrows Jevons Paradox to argue that when AI makes a workflow cheaper, the business expects more of it, not less.

• It applies that to win-loss analysis: continuous reading of sales calls, pricing objections and competitor mentions turns a quarterly retrospective into a live feedback loop, where patterns surface in days and positioning can change in weeks.
• It names Klue, Crayon, Hyperbound, Gong, Highspot and Avoma as tools already moving that way.
• The second post makes an organisational scaling case, describing Rippling's outbound function growing from 30-40 BDRs to more than 400, a defined SDR-to-AE handoff covering authority, need and timeline with context passed to the account executive, and an AI workflow in Salesforce that checks a Gong recording against rules of engagement before a deal reaches Stage 2, leaving managers to resolve only disagreements.
• Together, the posts suit campaigns aimed at sales or RevOps leadership justifying headcount, tooling or a process rebuild.

The tradeoff is distance from first-hand implementation.

• Both posts report other people's frameworks and cases, crediting the Jevons framing to Jeff Ignacio and the Rippling example to Ashley Kelly.
• For a campaign that needs a named practitioner's own build decisions and problem details, use João Dobbin's posts or ask for those specifics.
• The material stays at the strategic and organisational level, with no configuration steps, data-model rules or stage definitions, and the Rippling account summarizes a published case rather than walking through it.

Examples: Source 1 · Source 2