# Ben Hood

Ben Hood writes about B2B sales and revenue operations, including building SDR teams, improving sales data capture, and using AI in go-to-market work.

- Profile: https://b2binfluencer.marketing/creators/ben-hood/
- LinkedIn: https://www.linkedin.com/in/benjaminrhood
- LinkedIn followers: 3,486
- Topics: artificial-intelligence, sales, revenue-operations, ai-in-sales, sales-development
- Based on 10 dated posts, latest 2026-10-06

## Summary

Most useful for practical B2B sales and RevOps ideas on SDR hiring, data capture, and AI tools.

- Best for: A B2B SaaS company building an SDR function and improving sales data for AI.
- Not for: Consumer brands or campaigns seeking paid reach, sponsorship, or a media kit.
- Check first: Ask for audience survey results, platform demographics, and recent performance on comparable posts.

### Takeaways

- Consider door-to-door home-services sellers for SDR roles because they are used to rejection.
- Fix data capture before buying AI: find uncaptured interactions and unlinked call recordings.
- Built an outreach tool with Power Automate and AI without adding new technology.

## Main ideas

- **Hire SDRs for resilience, not SaaS résumés**: Ben Hood argues that SDR teams often overlook people who have spent their working days hearing no. Door-to-door home-services reps, often on commission-only pay, are self-motivated and practiced at handling rejection. A skills-first approach evaluates that evidence of persistence instead of checking for a familiar software sales title.
- **Fix data capture before buying AI for sales**: Hood reads recent acquisition activity as a set of plays for data and argues that if AI is going to carry more of the revenue motion, data is the fuel. The practical instruction to sales leaders: find where the organization leaks information before adding AI. AI insight is only as accurate or valuable as the records going in.
- **Use AI to build inside the stack you already have**: Rather than recommend new platforms, Hood describes using AI to build a working tool inside software the team already owns. They also suggest AI role-play to practice an elevator pitch or an interview. The argument: creative curiosity matters more than a new purchase when the tool you need is unlikely to arrive through normal channels.
- **Position a product around what rivals have not commoditized**: Hood argues that call recording has become table stakes while the deal board and deal insights remain Gong's real asset. The broader judgment: find the part of a product competitors have not neutralized and concentrate the story there.

## Work to read

- [Hire SDRs from door-to-door sales](https://www.linkedin.com/posts/benjaminrhood_skillsfirst-skillsfirst-sdr-activity-7349083751269715969-oTy-)
- [Sales leaders should fix data capture before AI](https://www.linkedin.com/posts/benjaminrhood_salesleadership-aisalesleaders-ai-activity-7333501225952309248-whic)
- [Building an outreach tool inside an existing stack](https://www.linkedin.com/posts/benjaminrhood_aiingtm-gtm-revops-activity-7364741624356032513-55mB)
- [Gong’s advantage is the deal board, not call recording](https://www.linkedin.com/posts/benjaminrhood_productmarketing-marketing-saasmarketing-activity-7336417255913611264-H7i1)

## Brand relationships

- **Gong** (mention)
- **Microsoft Power Automate** (mention)

## Partnerships

Ben Hood’s posts target sales and revenue-operations audiences, covering SDR hiring, sales data capture, AI in go-to-market work, and product marketing. They discuss building and leading SDR teams, improving CRM and call-recording data capture, and applying AI within existing tooling, offering a sense of what campaign material might fit. Hood does not describe a partnership, sponsorship, or paid-collaboration format, or mention a rate card, media kit, sponsored placement, affiliate arrangement, or brand-partner disclosure. No official partnership policy, specification, or inquiry route is published. Before committing budget, ask whether Hood accepts sponsored or partnered work and under what terms.

## Alternatives

- Mohan Sundar: Mohan Sundar is the stronger pick when the main need is the handoff between SDRs and account executives, not the hiring channel. The Rippling account describes a rebuilt outbound process: SDRs qualified Stage 1 meetings for authority, need, and timeline, then passed context, timing, lead source, and the call recording to AEs. Before Stage 2, an AI workflow in Salesforce checked the Gong recording against rules of engagement and recommended whether the deal should advance, leaving managers to settle only disagreements. New SDRs trained on inbound before moving to outbound, turning the entry point into a pipeline for AE, account management, and leadership roles. For a campaign focused on connecting SDRs and AEs, that is ready-made operating detail for the days 31-60 and 61-90 phases, which need to show how AI-powered data capture is wired into a sales process. Sundar's other post makes the underlying argument: continuous win-loss analysis, where every call, pricing objection, and competitor mention feeds a live feedback loop instead of a quarterly retrospective, and demand for RevOps expands as AI makes the work cheaper.
- Stacey Justice: Stacey Justice is the better choice when adoption is the risk. The book-club post describes a RevOps and Enablement team choosing The Goal before building anything, specifically to develop a common language and agree on the goal. It reports the questions now showing up in conversation: what is the goal, is this the constraint, are we optimizing the system or a local process, and how does this affect the goal. The argument is that enablement's job is business outcomes rather than programs. For the same campaign decision, that is the change-management layer behind a data-capture rollout that Hood's posts assume rather than address: Hood says to fix the leaks in the CRM and link call recordings; Justice's material is about getting a team to agree on which leak is the constraint before anyone starts fixing it. The Gong Enrich post adds the diagnosis that seller productivity is lost in the seams between systems—finding the right contact, researching an account, filling in missing information, switching tools, updating CRM—and that these small inefficiencies compound across an entire revenue organization.
- Paul Acott: Paul Acott is the stronger pick when the need is to pressure-test AI claims before money moves. Acott's post argues that implementing AI tools is not transformation; transformation means changing how a business sells, markets, serves customers, manages people, measures success, and makes decisions. For a hiring need focused on a leader who has "led an AI transformation," the suggested replacement question—what commercial outcomes improved because of AI—comes with a specific scorecard: revenue, win rate, sales cycle, forecast accuracy, customer retention, productivity per seller. The second post supplies an unusually concrete cost test for any plan that removes work from salespeople: delegating a one-minute task can become a minute to explain, a minute for someone else to do, and a minute to check, turning one minute into three minutes of organizational work before queueing, errors, context loss, and an extra customer handoff. That is directly usable in the days 61-90 measurement phase, which needs to assess what AI helped with and where it did not: released capacity only counts if it is banked against more prospecting, customer time, account planning, multi-threading, or deal progression.

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