# João Dobbin

João Dobbin shares practical advice on revenue operations, CRM and sales lifecycle design, and small-scale AI uses for sales and customer-success workflows.

- Profile: https://b2binfluencer.marketing/creators/jo-o-dobbin/
- LinkedIn: https://www.linkedin.com/in/joaodobbin
- LinkedIn followers: 4,081
- Topics: artificial-intelligence, revenue-operations, email-marketing
- Based on 12 dated posts, latest 2026-10-08

## Summary

João Dobbin is most useful for practical revenue operations, CRM lifecycle design, and small AI workflow advice.

- Best for: A B2B SaaS company selling to revenue, sales, or customer-success teams improving RevOps and CRM workflows.
- Not for: Consumer brands, broad awareness pushes, high-volume reach, or video-first campaigns do not fit.
- Check first: Confirm partnership terms, pricing, deliverables, and audience role, seniority, and country data.

### Takeaways

- Lifecycle stages should be simple, readable, and tied to named CRM records.
- AI quick wins include lead checks, shared-inbox screening, and call-risk summaries.
- CRM capability matters more than platform choice; data connections and snapshots help forecasting.

## Main ideas

- **AI belongs in small, annoying RevOps tasks—not autopilot promises**: Dobbin separates AI hype from implemented workflows. 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.
- **Lifecycle stages should be simple, readable, and tied to named CRM records**: Dobbin's checklist calls for stages close to industry standards, readable trigger criteria in the CRM, a dedicated object for MQLs, opportunities created when a meeting is booked, and a clear record type for each stage. Sales, marketing, and customer success can act on stages only when they’re unambiguous.
- **A CRM is infrastructure: how it functions matters more than which one you buy**: Dobbin shares a quoted argument that how a CRM functions matters more than which one a company chooses. 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.
- **Waiting for inbound leads is risky as search traffic declines**: Dobbin recommends an account-driven go-to-market read for B2B marketing, sales, and RevOps, and shares its warning that companies waiting for leads will struggle to compete with those using this strategy. The quote is attributed to the linked article.
- **Connect operational data to the CRM layer for snapshots and forecasting**: Dobbin includes spreadsheet-to-CRM connections in a practical RevOps stack, highlighting automated updates and data snapshots for forecasting. 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.

## Work to read

- [Lifecycle stages: seven rules for usable CRM stages](https://www.linkedin.com/posts/joaodobbin_if-youre-working-on-reviewing-updating-activity-7292976379581620225-rg-h)
- [Three AI quick wins in RevOps: lead checks, inbox screening, and call-risk summaries](https://www.linkedin.com/posts/joaodobbin_there-are-a-lot-of-scams-nowadays-regarding-activity-7422377933295677440-1DYw)
- [The account-driven GTM shift: why waiting for inbound leads is risky](https://www.linkedin.com/posts/joaodobbin_the-shift-to-account-driven-gtm-activity-7297362231028060160--5L8)
- [Why CRM choice matters less than how it functions](https://www.linkedin.com/posts/joaodobbin_how-to-align-systems-around-the-crm-activity-6851918195574509568-JUSP)
- [The simple RevOps stack addition Dobbin calls transformative: Coefficient](https://www.linkedin.com/posts/joaodobbin_by-far-one-of-the-most-simple-yet-transformative-activity-7145450981219098624-olW3)

## Brand relationships

- **Coefficient** (mention)
- **HubSpot** (mention)

## Partnerships

João Dobbin's five posts, spanning October 2021 to January 2026, offer practical writing on revenue operations, CRM and lifecycle-stage design, and small AI workflows. None is a sponsored placement or describes partnership terms, deliverables, sponsorship audience figures, or how brands can approach them about paid work. The one commercial-adjacent mention is an endorsement: Dobbin recommends Coefficient for connecting spreadsheets to a CRM and sales-pipeline snapshots, explicitly labeling it "free advertising," which reads as an unpaid recommendation rather than a disclosed sponsorship. Brands considering a paid collaboration should ask directly about format, deliverables, and pricing; the posts provide no official inquiry route.

## Alternatives

- Etienne Turner: Choose Etienne Turner when the campaign decision is whether a specific AI spend pays for itself inside HubSpot, or how to sequence a connected quote-to-cash rollout. 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.
- Chris Tveter: Choose Chris Tveter when the buyer decision is which CRM AI features to switch on and what each needs before it works. 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.
- Mohan Sundar: Choose Mohan Sundar when the need is a leadership or budget case for expanding RevOps work, rather than a build decision. 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.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/