# Kenny Damian

Kenny Damian builds B2B go-to-market systems, including AI-powered outbound and account-based marketing workflows that help sales teams find and prioritize accounts, reach the right buyers, and coordinate campaigns.

- Profile: https://b2binfluencer.marketing/creators/kenny-damian/
- LinkedIn: https://www.linkedin.com/in/kenny-damian-90aba221a
- LinkedIn followers: 14,963
- Median of last 6 posts: 101 reactions, 56 comments (checked 2026-11-02)
- Topics: artificial-intelligence, sales, account-based-marketing, sales-and-marketing-alignment
- Based on 8 dated posts, latest 2026-10-01

## Summary

Most useful for practical B2B GTM workflows, AI outbound, and account-based marketing systems.

- Best for: A B2B sales-tech company wanting AI-powered outbound or ABM workflow content.
- Not for: HR-tech employee engagement campaigns for HR or People leaders with video-led awareness.
- Check first: Confirm audience demographics, engagement, and conflicts with Frontal or promoted tools before contacting them.

### Takeaways

- Outbound should be one connected workflow, not a stack of disconnected tools.
- LinkedIn engagement is qualification data, not just reach.
- ABM works when ads, outbound, and sales share one target-account list and one score.

## Main ideas

- **Outbound should be one connected workflow, not a stack of disconnected tools**: Kenny Damian argues that an entire campaign can be built in one Claude Code session, with Lusha's API handling the data work. The reasoning is that one verified pass beats a multi-tool enrichment waterfall, that intent data should set timing rather than be added later, and that scoring rules written once can score every future list. The workflow moves from describing an ideal customer profile in plain English to sourcing companies, flagging buying signals, scoring and tiering accounts on fit plus intent, finding decision makers, verifying emails and direct dials, generating copy from a saved framework, launching in Lemlist, and syncing contacts back to HubSpot or Salesforce.
- **LinkedIn engagement is qualification data, not just reach**: Kenny Damian describes treating a team's weekly LinkedIn posts as an outbound list that builds itself. The reasoning is that different post topics pull in different buyers, so the topic a person engaged with can shape the opening message and the offer. The process captures reactions, comments, reposts, and profile visitors into one Clay pool; qualifies people through three gates covering company fit, job title, and which post they engaged with; messages the engaging person first on LinkedIn; and emails colleagues on the buying committee a few days later. He notes the same approach can run against competitors' pages if a team does not post.
- **Sales teams need an intelligence layer under their reps**: Kenny Damian argues that the best sales teams in 2026 are not grinding through manual research, list building, appointment setting, and CRM updates. Instead, they run an intelligence layer: RevOps owns the ICP model, data pipelines, signal tracking, lead scoring, and routing, while a GTM engineer runs AI account research, TAM mapping, verified data, and automated outreach. He is explicit that this is not about needing fewer people but about feeding existing SDRs and AEs the right contacts at the right time with a strong starting point on what to say.
- **AI sales skills should be shared team infrastructure, not laptop artifacts**: Kenny Damian describes a common failure pattern: one rep builds a useful Claude skill, it stays local, colleagues rebuild their own versions, and nobody knows who updates it when the ICP changes. The proposed fix is multiplayer infrastructure: one private team repository holding team rules in a CLAUDE.md file, a folder per skill, Clay CLI workflows anyone can rerun, and shared context covering ICP, personas, proof points, and call transcripts. A rep runs one command to open a pull request, the skill owner tests and merges it, and every rep pulls the same version. The rules are one owner per skill, a common template, a changelog the team reads, editing the source rather than copies, and keeping API keys out of the repository.
- **ABM works when ads, outbound, and sales share one target-account list and one score**: Kenny Damian lays out an account-based marketing playbook in six stages: account selection from CRM closed-won and closed-lost data plus an ICP model, TAM map, and lookalikes; buyer mapping across decision makers, champions, influencers, and end users; signal collection across first-, second-, and third-party sources; a prioritization score that moves accounts from cold to warm to hot; coordinated campaigns across ads, outbound, and sales; and account-level pipeline reporting that feeds results back into the first stage. The organizing argument is that ads, outbound, and sales should work from the same named-account list in the same week, with one owner and one message.
- **Platform releases should be translated into context work before agents**: Kenny Damian's breakdown of Clay's Sculpt keynote frames the theme as a self-learning revenue engine: plays run, Clay observes what converts, and it rewrites the plays. He highlights an agent with a Knowledge Hub that takes an outcome like fifty more opportunities a month and builds the TAM, scores and routes accounts, sends reps top accounts in Slack, and checks back every three days; Workflows as one canvas that can branch, loop, run code, or call an agent across large record volumes; and an inbound SDR agent that qualifies leads and demos a product before routing. He labels each item by release stage and closes by arguing that agents are only as good as the context underneath them.
- **The service model has shifted from doing tasks to placing operators inside the client's systems**: Announcing a rebuilt Frontal site, Kenny Damian says the company began doing GTM engineering in 2022, before the term had a name, when clients paid for lists, email finding, and copywriting. The argument is that those tasks now take minutes in Claude Code, so the offer has moved to senior operators who build and run the work inside a client's CRM and Slack. Frontal describes the system as right accounts, buying signals, every channel, and qualified pipeline, measured against a pipeline goal agreed up front and reviewed each round. The post also says target companies already pay for about fifteen tools nobody uses, and it names a case study and 28 documented GTM plays.

## Work to read

- [The new Frontal site, and what GTM engineering looks like as a service](https://www.linkedin.com/posts/kenny-damian-90aba221a_the-new-frontalso-is-live-today-we-rebuilt-activity-7518663553604665344-UkDI)
- [Building an entire outbound campaign end to end in Claude Code](https://www.linkedin.com/posts/kenny-damian-90aba221a_i-just-built-an-entire-outbound-campaign-activity-7498370519399022592-wgih)
- [The ABM playbook in six stages](https://www.linkedin.com/posts/kenny-damian-90aba221a_the-abm-playbook-we-run-in-6-steps-one-activity-7521202192121438209-N0X8)
- [Breaking down everything Clay launched at Sculpt](https://www.linkedin.com/posts/kenny-damian-90aba221a_i-broke-down-everything-clay-launched-at-activity-7518298791129661440-8UJ4)
- [Turning Claude work from single player into multiplayer](https://www.linkedin.com/posts/kenny-damian-90aba221a_how-to-turn-your-teams-claude-work-from-activity-7520477542852677632-t-fu)
- [Turning LinkedIn engagement into an outbound list that builds itself](https://www.linkedin.com/posts/kenny-damian-90aba221a_our-linkedin-posts-are-an-outbound-list-that-activity-7523016003639939074-yOcp)
- [The case for an intelligence layer under sales teams](https://www.linkedin.com/posts/kenny-damian-90aba221a_the-best-sales-teams-in-2026-arent-grinding-activity-7510692846094524416-toD1)

## Brand relationships

- **Frontal** (employment)
- **Lusha** (disclosed_partnership)
- **Clay** (mention)
- **Lemlist** (mention)
- **Instantly** (mention)
- **Apify** (mention)
- **Teamfluence** (mention)
- **HubSpot** (mention)
- **Claude** (mention)
- **AirOps** (client)

## Partnerships

The reviewed posts contain no published sponsorship policy, rate card, media kit, or partnership inquiry route, so there is no official package a brand can book from this material. What the posts do show is a recurring commercial format: worked, step-by-step breakdowns of a specific tool or launch, usually ending in a signup link or a save-and-share prompt. Kenny Damian also markets his own GTM engineering firm in the same feed, which means a paid placement would sit alongside his own agency promotion rather than being a standalone media product. Treat partnership terms as something to negotiate directly; nothing here states payment, exclusivity, or turnaround terms.

## Alternatives

- Rami Zwebti: Rami Zwebti is the stronger pick when the campaign's job is to argue a category position rather than show a build. Zwebti's posts make the case that distribution decides which AI-era startups win, and walk through what a data layer actually contains once a prospecting workflow is wired up — contact and company counts, the volume of signals processed weekly, and why hiring, promotion, and funding events are the timing triggers worth acting on. That framing suits a brand selling the data or infrastructure underneath an outbound stack, or one that needs founders and GTM leaders to accept the premise before they will look at a tool. Zwebti also covers what happens when autonomous agents run unsupervised — least-privilege access, checkpointing, verifying consequential writes, and an audit trail — which is the right angle for a sponsor whose product governs or contains agent behaviour rather than generating the outbound itself.
- David Turewicz: David Turewicz fits a brief built around checking AI output or testing a new segment fast, rather than running a full campaign. One post sets out a working method for quality control: load the session with every relevant client conversation and CRM record, give the model a summary to react to, run a second session whose only job is to check the first, and then verify specific fields by hand against the CRM. The other describes a lean stack for when a client wants to trial a new ICP segment or offer on a small batch — a targeting brief covering filters, signals, intent, and tech stack, turned into search parameters, enriched and verified in the same conversation, with a claimed build-and-test time of about two minutes. For a sponsor selling verification, enrichment, or a fast pilot capability, that is a more precise match than a full outbound walkthrough.
- Vincent Plassard: Vincent Plassard is the better choice when the brief is about ABM programme design and keeping relevance as the account list grows. One post reframes ABM as a queue problem — intelligence, creative production, distribution, bid optimisation, and visibility each waiting on someone's calendar — and argues the fix is fewer queues rather than a smaller team, with humans keeping the judgment about brand, targeting, and offer. The second lays out the trade-off that comes with scale directly: at 20 accounts someone knows which accounts are evaluating and which story will help, and at 200 that context disappears, so AI is worth using to route different accounts through different plays rather than to produce more versions of the same campaign. That suits a sponsor whose product relieves one of those bottlenecks, particularly creative production, paid optimisation overnight, or getting engagement back in front of sales while it is still warm.

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