# Jacob Tuwiner

Jacob Tuwiner writes about and builds B2B go-to-market systems, including inbound lead scoring and company-data enrichment workflows.

- Profile: https://b2binfluencer.marketing/creators/jacob-tuwiner/
- LinkedIn: https://www.linkedin.com/in/jacob-tuwiner
- LinkedIn followers: 11,219
- YouTube: https://www.youtube.com/channel/UCUWJUagz_SwLM2kofmg6TZQ
- Topics: artificial-intelligence, sales, healthcare, crm-data-quality
- Based on 9 dated posts, latest 2026-10-05

## Summary

Most useful for B2B teams that need help prioritising inbound leads and checking enrichment data quality.

- Best for: B2B SaaS campaigns about lead scoring, enrichment, CRM hygiene, and GTM tooling.
- Not for: Consumer lifestyle or savings brands seeking high-volume awareness with short-form video.
- Check first: Confirm audience survey results and comparable post performance before committing budget.

### Takeaways

- Lead scoring compares first-come-first-served follow-up with working the best 300 leads first.
- A wrong LinkedIn company URL can poison segmentation, routing, TAM modelling, and lead scoring.
- Employee-count benchmark across 100 companies found cost per correct answer from $0.01 to $0.21.

## Main ideas

- **Inbound lead scoring is really a rep-capacity problem**: Jacob Tuwiner argues that the useful question in inbound sales is not whether some leads are better than others, but which leads a limited team can actually work. An inbound rep gets through roughly 50 meaningful touches a day, and a new lead needs three to four touches while it is still hot, so one rep can properly work about 300 of 1,000 monthly leads. The other 700 get slow or no follow-up. Because most teams work leads first-come-first-served, reps spend their best hours on the weakest half. The fix is a prioritized queue: rank the leads and work the best 300 first.
- **A wrong company identity poisons every number after it**: Jacob Tuwiner argues that data providers often fail before returning any data by matching the wrong LinkedIn company URL. If the company identity is wrong, the employee count is already unreliable, and employee count drives account segmentation, territory routing, TAM modeling, lead scoring, and mid-market versus enterprise rules. Accuracy should be measured at the identity layer, not just the field level: a plausible-looking headcount built on the wrong entity is worse than a missing one.
- **Diagnosis should ship as a working tool**: A second priority is turning an audit into software rather than leaving it as a report. The employee-count benchmark is presented as one play inside the CRM Report Card, a plugin that grades a CRM, surfaces specific problems, and recommends actions to fix them. Most B2B teams do not know how degraded their CRM data has become; naming each defect in a scoreboard makes the fix routine instead of discretionary.
- **Platform loyalty is conditional — and can be reversed**: Jacob Tuwiner argues that tools that win over early operators can lose them by growing upmarket. A platform that adds higher-tier pricing and a partner program ranking large shops first, while shipping headline features before basic functionality, pushes the small agencies and practitioners who evangelized it to ask whether it is still the only option. The platform does not necessarily become bad, but the priorities that produce growth come at a cost: losing the edge-of-GTM audience.

## Work to read

- [The math behind working the best 300 inbound leads first](https://www.linkedin.com/posts/jacob-tuwiner_288m-a-year-vs-156m-from-the-same-inbound-activity-7493705540704071680-RFhD)
- [What a six-provider employee-count benchmark says about data-provider accuracy](https://www.linkedin.com/posts/jacob-tuwiner_we-tested-6-employee-count-providers-across-activity-7487955071490682880-5X2i)
- [Clay's move upmarket, seen by an early Claygency founder](https://www.linkedin.com/posts/jacob-tuwiner_in-2024-if-someone-asked-me-to-describe-activity-7495146737750282240-JhkL)

## Brand relationships

- **Clay** (disclosed_partnership)
- **The CRM Report Card** (owned_business)
- **Deepline** (mention)
- **Crustdata** (mention)
- **LeadMagic** (mention)
- **Limadata** (mention)
- **People Data Labs** (mention)

## Partnerships

Jacob Tuwiner's posts show a direct-response publishing pattern: free deep reports and a lead-scoring calculator gated by email signup, a waitlist for a CRM Report Card plugin built with Deepline and Claude workflows, and a promised inbound lead-scoring course. The employee-count benchmark post uses a comment-to-receive mechanic and points readers to a pinned comment for the calculator. These are their own offers and audience-capture routes, not paid sponsor slots. A buyer proposing a paid advisory or content collaboration would need to settle scope, deliverables, disclosure and pricing directly; the posts do not publicly package those terms.

## Alternatives

- Jani Vrancsik: Choose Jani Vrancsik when the client wants someone to build the GTM system, not just make the case for prioritising the queue. The 7-figure pipeline post documents the whole motion: LinkedIn content across 7+ profiles driving 80% of pipeline at 650,000 monthly impressions in Q2, SEO resource pages and mini-tools, and cold outbound personalised by Claude using HubSpot and Clay enrichment data. Scoping starts from a working stack (Clay, Instantly, Lemlist, Apify, RB2B, HubSpot) rather than a blank page. The ATLAS post is the sharper match for a content collaboration: six Claude skills that produce market research, an ICP hypothesis, a 25+ signal library, battlecards, 18 messaging variants and an 11-tab playbook ready for a sales team. They are a better fit than Jacob Tuwiner when the deliverable is implementation and enablement across several channels, and the buyer wants an agency team that can run them at once.
- Sara McNamara: Choose Sara McNamara when the client's real obstacle is ownership, org design and process definition rather than pipeline math. The RevOps shake-up post operates at the leadership level: 19 of 23 tracked RevOps leadership roles mention AI or automation, and 20 of 23 call for technical architecture. It lays out two competing models: the existing RevOps leader becomes AI-native, or a separate GTM AI leader emerges. That's the conversation a buyer needs to have before deciding who will run a scoring and enrichment programme. The spec-and-agent post matches a common failure mode in enrichment projects: it argues that the job is shifting from hand-building every automation to writing a clean SOP precise enough for an agent to build from. The hard part is setting guardrails: where the normal path breaks, what the process should never touch, what happens when data is missing or contradictory, and how to prove it works before launch. For a client whose scoring rules keep drifting because nobody owns them, that framing is more useful than another prioritisation model.
- Cristian Frunze: Choose Cristian Frunze when the constraint is outbound sending infrastructure and deliverability, not inbound prioritisation. The HubSpot warning sets out a concrete operational risk: cold email through a CRM breaks the terms of Salesforce, HubSpot and Close; volume and complaint thresholds (around 5,000 cold emails a month) can trigger account bans with no appeals or grace period. The blast radius includes the warm list, CRM data, deal history, calendar and SEO. The proposed fix is to use dedicated domains and a dedicated cold-email sequencer, separate from the primary domain. A client sending cold mail from its CRM while also worrying about lead scoring should fix the larger failure first. The second post adds a build-versus-buy opinion from someone who ran an eight-person SDR team on the standard stack, got about 60 calls a month and rebuilt in Python. It's useful when a buyer wants the case against operating a twelve-tool stack and hiring a GTM engineer to run it.

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