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.
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.
Key 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.
Check first: Confirm audience demographics, engagement, and conflicts with Frontal or promoted tools before contacting them.
Main ideas
Outbound should be one connected workflow, not a stack of disconnected tools · LinkedIn engagement is qualification data, not just reach · Sales teams need an intelligence layer under their reps
Kenny Damian is known for explaining how B2B sales teams can connect account research, buying signals, AI-assisted outreach, and sales coordination into one operating system.
In posts about Frontal, the company describes its work as having shifted from building lists and writing emails to senior operators running go-to-market systems inside clients’ tools.
Damian’s writing makes that shift tangible: examples range from a six-stage account-based marketing process to a shared repository for sales-team AI skills.
Readers looking for practical guidance on GTM engineering, outbound, and account-based marketing will find detailed workflows as well as arguments about how those systems should support sales teams.
Damian’s distinctive contribution in this material is showing how separate GTM tasks fit together, while spelling out the operating details that make a workflow repeatable.
The outbound walkthrough traces a campaign from ICP-based account sourcing through scoring, contact verification, copy, launch, and CRM sync; the ABM post connects account selection and buyer mapping to signals, prioritization, coordinated campaigns, and reporting.
A different post addresses what happens after a useful AI skill is built: team rules, shared files, ownership, review, and version control help prevent each rep from working from a different copy.
Together, these examples make his work useful for understanding both automation and the team processes around it.
His posts also promote tools and describe company results, so product claims and performance figures are best treated as the author’s own assertions, not independent evaluations.
Kenny Damian's recurring argument is that B2B outbound and account-based marketing should run as one repeatable system: target accounts, buying signals, scoring, contacts, copy, and CRM updates connected rather than stitched across tabs and tools.
Read more
The priorities underneath that argument are shared team infrastructure instead of individual AI skills, one target-account list and one score for ads/outbound/sales, and context quality before agent automation. His company, Frontal, sells GTM engineering services built on that view.
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.
Read more
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.
In the post, Lusha's API pulls matching companies by industry, size, region, and revenue; checks each account for live intent; Claude writes scoring logic that tiers accounts; Lusha returns decision makers with direct dials; emails and phone numbers are verified in one pass; and the campaign launches in Lemlist. The post ends with a Lusha free-plan signup link, so it is a partner-adjacent walkthrough rather than neutral advice.
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.
Read more
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.
A person who engaged with a Claude Code post gets an opener about AI workflows; a signals post gets a signal-engine message; a Clay post gets enrichment and TAM mapping; an ABM post gets account warming before outbound. The engaging person is contacted through lemlist, then colleagues receive email through Instantly.ai.
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.
Read more
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.
The named stack is Lusha for verified contacts and live buying signals, Claude for research and first-draft copy, Clay to orchestrate, Lemlist and Instantly to run outreach, all syncing back into HubSpot. The contrast is with SDRs researching one prospect at a time and AEs buried in follow-ups and note taking.
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.
Read more
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.
The payoff he states is that the same skill, context, and output are available whether the user is the best rep or someone on day one. The repository structure itself is the concrete example: CLAUDE.md for rules, skills/ for individual skills, clay/ for CLI workflows, and context/ for ICP, personas, proof points, and transcripts.
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.
Read more
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.
A cold account fits the ICP but has no activity, so it receives ads only.
A warm account shows a signal, so ads continue and outbound starts to mapped buyers.
A hot account has several buying-committee members moving, so sales gets a Slack alert and a CRM task with context.
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.
Read more
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 practical to-do list he draws from the keynote is to get data into Audiences, write the Knowledge Hub like an onboarding document, and move inbound routing into Workflows along with other high-volume flows that used to be tables. The release labels are alpha, open beta, and waitlist, so the post distinguishes what is generally available from what is not.
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.
Read more
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.
The stated shift is from selling list building, email finding, and copywriting to running outbound, ABM, paid, and content against the same target accounts for fewer clients, with pipeline as the agreed measure. The pipeline figure and tool-count claim are the company's own assertions in the post, not independently confirmed evidence.
Earlier in the company's history, clients paid for the list, the emails, and the writing; now those tasks are described as minutes of Claude Code work, so the offer leads with the people who run the systems.
Start here if you want to know who Kenny Damian is commercially before reading any workflow breakdown: this is the clearest statement of what the company sells, to whom, and on what terms.
Read more
Announcing a from-scratch rebuild of frontal.so, Kenny Damian says the company began doing GTM engineering in 2022, "before it had a name," when clients paid for lists, email finding, and copywriting.
The point of the post is that those tasks now take minutes in Claude Code, so the offer has moved to the people: senior operators who build and run the work inside a client's CRM and Slack.
The system is described as four steps — right accounts, buying signals, every channel, qualified pipeline — with success measured against a pipeline goal agreed up front and reviewed each round.
The post also says the companies being targeted already pay for roughly 15 tools nobody uses, and it names a case study (AirOps, $7.83M in qualified pipeline over 10 months) plus 28 documented GTM plays.
For brands planning a campaign
Useful when a brand is weighing an agency or partner over in-house tooling: this is the vendor's own framing of what it replaces and how it claims to be measured. Treat the pipeline figure and the tool-count claim as the company's assertions rather than audited results.
This is the most complete worked example of the workflow Kenny Damian talks about elsewhere: one session that goes from company list to live campaign, with each step and its output spelled out.
Read more
The post walks through six numbered steps: sourcing companies by describing an ICP in plain English, checking accounts for live buying signals, scoring and tiering accounts on fit plus intent, finding decision makers at tier 1 and tier 2 accounts, verifying emails and direct dials, and writing a sequenced campaign with personalization tokens.
It states that Lusha's API powers most of the data steps, that Claude writes the scoring logic and the copy from a stored framework, and that the campaign was launched in Lemlist and synced back to a CRM (HubSpot or Salesforce).
The stated unlocks are switching from a multi-tool enrichment waterfall to a single verified pass and letting intent data set timing.
The post ends with a Lusha free-plan signup link, so read it as a partner-adjacent walkthrough rather than neutral tooling advice.
For brands planning a campaign
A template for what a brand could ask a GTM engineer to build or audit, and a checklist for the questions to ask about data sources, scoring rules, and CRM write-back. The performance figures (95%+ accuracy, GDPR/CCPA compliance) are the poster's claims, not independently verified.
The clearest long-form explanation of how the pieces fit together: account selection, buyer mapping, signals, scoring, coordinated campaigns, and reporting as one loop rather than six separate projects.
Read more
Six stages are laid out with the tools used at each.
Account selection starts from closed-won and closed-lost records in the CRM, builds an ICP model from firmographics and technographics, maps the total addressable market with lookalikes, and tiers accounts 1 to 3.
Buyer mapping identifies the decision maker, champion, influencers, and end users per account and writes contacts back to the CRM.
Signals are split into first-party (site and pricing-page visits, replies), second-party (ad and post engagement, champion job changes), and third-party (hiring, funding, tech-stack changes).
Every signal rolls into one cold-to-hot score that updates daily, with hot accounts producing a Slack alert and a CRM task.
The closing argument is that ads, outbound, and sales should all work from the same named-account list in the same week.
For brands planning a campaign
Best used as a scoping document for an account-based campaign: it shows what a brand needs to have in place — CRM history, buyer maps, signal sources, one agreed score — before coordinated paid and outbound activity makes sense. Named tools are the author's stack, not the only options.
Shows how Kenny Damian evaluates platform releases and translates them into a practical to-do list.
Read more
Read it to see the judgment behind the recommendations, not just the feature list.
The post summarizes Clay's Sculpt keynote around one idea: a self-learning revenue engine where plays run, the platform observes what converts, and it rewrites the plays.
Four items are highlighted — a Clay agent with a Knowledge Hub that takes an outcome like "50 more opportunities this month" and builds the target market, scores and routes accounts, sends reps their top accounts in Slack, and checks back every three days; a Workflows canvas that can branch, loop, run code, or call an agent across millions of records with run traces; an inbound SDR agent that qualifies and demos before routing; and a 12-launches-in-12-weeks roadmap.
Each item is labeled with its release stage (alpha, open beta, waitlist).
The stated takeaway is that agents are only as good as the context underneath them.
For brands planning a campaign
Useful for timing: it distinguishes what is generally available from what is alpha or waitlisted, and it names the context work — data in Audiences, a Knowledge Hub written like an onboarding doc, inbound routing moved into Workflows — that has to be done first. Feature availability moves fast, so re-check anything before it becomes a dependency.
The most concrete piece of team-operations advice in the set: what to do when good AI workflows stay stuck on one rep's laptop, with the file and folder structure spelled out.
Read more
The described problem is a familiar one: one rep builds a skill that researches accounts and drafts first emails, it stays local, colleagues rebuild their own versions, and nobody knows who updates the copy when the ICP changes.
The proposed fix is one private team repository holding a CLAUDE.md of team rules (ICP, tone, what never to send), a skills folder, Clay workflows run through a CLI, and a context folder with personas, proof points, and call transcripts.
Sharing is one command that opens a pull request from a filled-in template; a skill owner tests and merges; everyone pulls and installs.
The rules that keep it working are one owner per skill, a common template, a changelog people read, editing the source rather than a copy, and keeping API keys in each rep's environment file.
For brands planning a campaign
Relevant to any brand running AI-assisted sales work with more than one person: it frames version control and ownership as the difference between a demo and a repeatable process. Also a direct source of interview questions for a GTM engineering hire.
A complete demand-generation loop where organic content and outbound feed each other.
Read more
Read it to see how post topics are used as qualification data, not just as reach.
Weekly posts from the team, each covering what that person actually builds (AI workflows, signals, Clay, ABM), are captured through a tool that pulls every reaction, comment, and repost, plus a visitor-identification tool for people who read without engaging.
Everything lands in one pool.
Qualification runs through three gates: company fit (industry, headcount, funding, tech stack, with existing customers and competitors removed), job title (founders, GTM, RevOps, and marketing leaders stay), and which post the person engaged with.
That third gate drives the opener — a Claude Code post gets an AI-workflow message, a Clay post gets enrichment and TAM mapping.
The engaging person is messaged on LinkedIn first, and their colleagues on the buying committee get email a few days later.
The post closes by suggesting competitors' pages as an alternative for teams that do not post.
For brands planning a campaign
A model for brands whose creators or executives publish: engagement becomes the segmentation layer for outbound, and post topic becomes the reason for the first contact. It depends on volume of posting and on having buying-committee data, so it is heavier to run than it first appears.
The thesis that ties the workflow posts together — what changes for a sales team when research, signals, and routing are automated — with the tool stack in one place.
Read more
The post contrasts an old way (SDRs setting appointments, cold calling, researching one prospect at a time; account executives buried in demos, follow-ups, and CRM updates) with a new division of labour: RevOps owns the ICP model, data pipelines, signal tracking, lead scoring, and routing, while a GTM engineer runs AI account research, target-market mapping, verified data, and automated outreach.
The stated stack is Lusha for contacts and signals, Claude for research and first-draft copy, Clay for orchestration, Lemlist and Instantly for outreach, syncing into HubSpot.
The explicit argument is that this is not about needing fewer people but about giving existing reps better information, arriving with a strong starting point on what to say.
For brands planning a campaign
Use this when a brand wants to argue a positioning point rather than copy a workflow: the claim is that relevance comes from an intelligence layer, not from more activity. It is also the clearest list of which roles a brand has to own internally versus hire for.
Building a full outbound campaign inside Claude Code
Kenny Damian walks through running an outbound campaign end to end in Claude Code, with Lusha's API handling most of the data work.
Read more
The sequence covers describing an ICP in plain English, pulling matching companies on industry, size, region and revenue, checking accounts for live buying signals, scoring and tiering them on fit plus intent, sourcing decision makers with direct dials, verifying emails and phone numbers in one pass, generating sequenced copy from a saved framework, launching in Lemlist, and syncing contacts back to HubSpot or Salesforce. The stated purpose is replacing manual list building and multi-tool enrichment waterfalls with one connected session.
Published as a numbered six-step workflow with an outcome block and a closing question to the audience. Named tools: Claude Code, Lusha, Lemlist or Instantly, HubSpot or Salesforce.
For brands planning a campaign
Useful as a concrete operating blueprint for a sales-tech brand that wants to show AI-run outbound.
A brand could build a demo or worked example from this sequence, or have Damian document its own stack in the same step-by-step format.
Treat the performance figures he cites for Lusha as his claims, not audited results.
Turning LinkedIn engagement into a self-building outbound list
Damian describes treating his team's LinkedIn activity as a prospecting source.
Read more
Team members post weekly on AI workflows, signals, Clay and ABM; Apify captures every reaction, comment and repost, and Teamfluence captures profile visitors who read without engaging.
Everything lands in one Clay pool, then passes three gates: company fits the ICP, job title is a likely buyer, and which post the person engaged with.
The engagement topic shapes the opener, the engaging contact gets a LinkedIn message first through lemlist, and colleagues on the buying committee receive email a few days later through Instantly.ai.
He notes the same approach can run against competitors' pages if a team does not post.
Described as a five-step workflow, with the qualification gates spelled out separately from the outreach sequence. Teams can implement without publishing, using competitor pages instead.
For brands planning a campaign
A brand selling social listening, intent data or multi-channel outreach can evaluate Damian against this use case directly, since he has published the whole chain including the qualification logic. The post also shows he thinks in terms of buying committees rather than single contacts, which matters if a brief involves multi-threading an account.
Damian argues that the strongest sales teams no longer do research, list building and note taking by hand, and instead run an intelligence layer beneath their reps.
Read more
In his framing, 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.
The stack he names for this is Lusha for contacts and buying signals, Claude for research and first-draft copy, Clay to orchestrate, Lemlist and Instantly for outreach, all syncing into HubSpot.
He is explicit that the point is not headcount reduction but feeding existing reps better information and timing.
Framed as an old way versus new way contrast, with role ownership mapped to responsibilities.
For brands planning a campaign
Directly relevant to a sales-tech brief about AI-powered outbound, because it defines who does what inside a modern GTM function and where each tool category fits. A brand pitching into RevOps or sales leadership can use this role split as the shape of its campaign narrative, or ask Damian to write the equivalent argument for its own product category.
Damian describes a common pattern where one rep builds a useful Claude skill and it stays on their laptop, then lays out how to run it as a team system instead.
Read more
The setup is one private 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 who builds something useful runs a single command that opens a pull request, the skill owner tests and merges it, and every rep pulls the same version.
He pairs this with rules: one owner per skill, a common template, a changelog the team reads, editing the source rather than copies, and keeping keys out of the repository.
Written as four steps plus a separate list of operating rules. The problem is stated before the method, and the payoff is framed as day-one reps producing the same output as the best rep.
For brands planning a campaign
Shows a second, internal-facing side of his work: enablement and knowledge-sharing infrastructure, not only lead generation. A brand selling collaboration, knowledge-management or AI tooling for sales teams can evaluate him on this topic, and it is the clearest evidence that his material covers how teams adopt AI rather than only which tools to buy.
Damian published a breakdown of what Clay announced at Sculpt, framing the theme as a self-learning revenue engine where plays run, Clay observes what converts, and rewrites the plays.
Read more
He describes the Clay agent and Knowledge Hub taking an outcome such as fifty more opportunities a month and building the TAM, scoring and routing accounts, sending reps their top accounts in Slack and checking back every three days; Workflows as one canvas that can branch, loop, run code or call an agent across large record volumes with run tracing; and an Inbound SDR Agent that qualifies inbound leads and demos a product before routing. He closes by arguing agents are only as good as the context underneath them.
A product cheat sheet built from a conference keynote, ending with a save-and-share prompt. Named tools: Clay agent, Knowledge Hub, Workflows, Inbound SDR Agent, Search, Audiences, CLI and API, MCP, Ads, Sequencer.
For brands planning a campaign
Useful if a brand needs a creator who can translate a dense product launch into a short, structured explainer for practitioners. It also shows his stated view that data and context quality, not the agent itself, determines results, which is a workable positioning angle for a data or enrichment vendor.
A six-stage ABM playbook and the tool stack behind it
Damian lays out an account-based marketing playbook in six stages: account selection from closed-won and closed-lost data plus an ICP model and TAM map, 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 with one owner and one message in the same week, and account-level pipeline reporting that feeds results back into the first stage.
Read more
The organizing principle is one shared target-account list and one score that ads, outbound and sales all work from.
Six explicitly numbered stages, each with a short list of inputs and named tools: Clay, AI Ark, Ocean, Prospeo, Findymail, BounceBan, RB2B, Fibbler, Apify, Instantly.ai, lemlist.
For brands planning a campaign
The most complete account-level view he has published, so it is the natural anchor if a brand's brief involves ABM, target-account selection or coordination between paid, outbound and sales. A brand in that space can ask him to adapt the same six stages to its own category as campaign content, or evaluate whether its product already occupies a stage in his stack.
Frontal, GTM engineering and the pipeline-first pitch
Alongside the tactical breakdowns, Damian writes about the business he runs.
Read more
Announcing a rebuilt Frontal site, he says the company has been doing GTM engineering since 2022, has worked with more than three hundred B2B companies, and now works with fewer clients while running outbound, ABM, paid and content against the same target accounts.
The pitch is that target companies already pay for roughly fifteen tools nobody uses, so the site leads with senior operators who build and run the work inside the client's CRM and Slack, a system spanning accounts, buying signals and channels, and a pipeline goal agreed up front and reviewed each round.
He cites taking AirOps to $7.83M in qualified pipeline over ten months and publishing 28 GTM plays.
A company and positioning update rather than a how-to, organized around who you work with, the system, and how results are measured.
This is the one reviewed post that is promotional for his own business; the pipeline and client-count figures are his own claims and are not corroborated by other evidence in the packet.
For brands planning a campaign
Relevant for a brand that wants a creator with an agency-side view of GTM, since Damian can speak to how systems are sold and measured, not only how they are built. It also identifies his commercial interest, which a brand should weigh against sponsorship or partnership discussions.
Kenny Damian's posts document two kinds of brand connection.
Read more
The clearest is Frontal, the GTM-engineering company he refers to in the first person and describes as the team he works with; its tooling stack runs through nearly everything he writes.
The other is a group of sales and data tools — Lusha, Clay, Lemlist, Instantly, Apify, Teamfluence, HubSpot, and Claude — that appear as the platforms he builds outbound and account-based marketing workflows on.
Only Lusha comes with anything resembling a commercial disclosure: the post that calls Lusha's API the backbone of the workflow also carries a Lusha sign-up link.
The rest are tools he uses and explains, with no stated commercial relationship.
Frontal
Employment
Damian writes about Frontal in the first person and treats it as the company he works with.
Read more
Announcing the rebuilt site, he says, "The new frontal.so is live today.
We rebuilt it from scratch," and dates the GTM-engineering work to 2022 and "300+ B2B companies later."
A separate post describes "the teams we work with at Frontal" and lays out the stack Frontal runs for clients: Lusha for verified contacts and buying signals, Claude for research and first-draft copy, Clay to orchestrate, Lemlist and Instantly for outreach, all syncing back into HubSpot.
Another post speaks of "helping clients get their data into Audiences" and writing Clay's Knowledge Hub "like an onboarding doc."
The posts do not state a job title, ownership stake, or formal role.
Damian's step-by-step account of building an outbound campaign end to end in Claude Code names Lusha's API as "the data backbone the whole workflow runs on" — sourcing companies from an ICP description, flagging live buying signals, sourcing decision makers with direct dials, and verifying emails — and reports 95%+ accuracy with GDPR and CCPA compliance.
Read more
The post closes with a Lusha sign-up link and a note that Lusha has a free plan.
Lusha also appears in his description of the toolstack Frontal runs.
The posts do not label the commercial arrangement, so the relationship is treated here as an undisclosed-type partnership rather than a stated sponsorship.
Original disclosure
Lusha has a free plan, so you can wire up the first version without paying anything. Sign up to build your first workflow
Clay recurs across Damian's posts as the orchestration layer for outbound and account-based marketing.
Read more
He breaks down Clay's Sculpt launch in detail — the Clay agent and Knowledge Hub, Workflows as one canvas for any play, the inbound SDR agent, and the summer launch run — and organizes his six-stage ABM playbook around Clay with AI data tools.
He describes moving inbound routing into Workflows and helping clients load their data into Audiences.
Named as the tool where the outbound campaign goes live — "Campaign live in Lemlist (Instantly works the same way)" — and as the channel for the first LinkedIn message in his engagement-to-outbound workflow, because that is where the prospect already knows the team.
Appears alongside Lemlist as an interchangeable sending tool for the campaign he builds, and in the LinkedIn-engagement workflow where colleagues on a buying committee get an email a few days after the person who engaged is messaged.
Used in his team's own inbound workflow: Apify fetches every reaction, comment, and repost across the team's LinkedIn profiles, with everything landing in one pool in Clay for qualification.
Read more
It also appears in the list of tools used for signal tracking. No commercial relationship is stated.
Catches profile visitors for the team's engagement-to-outbound workflow — the people who read posts but never like or comment, whom Damian calls often the most interested.
Claude is the writing and research layer in Damian's workflows: he builds a full outbound campaign in Claude Code, has Claude write account-scoring logic and campaign copy from a stored framework, and writes about turning a team's Claude skills from single player into multiplayer through a shared repo with CLAUDE.md, skills, Clay CLI workflows, and context files.
Kenny Damian publishes short, numbered breakdowns of how B2B outbound and account-based marketing run inside a modern AI toolchain.
Read more
To get the measure of the work, start with the six-stage ABM playbook, which moves from account selection to pipeline reporting and names the tools at each step, and with the end-to-end Claude Code campaign build, which runs sourcing, buying signals, scoring, contact discovery, verification, copy and CRM sync in a single session.
If the question is how sales teams adopt AI rather than which tools to buy, the pieces on sharing Claude skills through one team repository and on the intelligence layer under reps are the place to begin.
He also writes about his own company, Frontal, and turns platform launches into practitioner explainers, as in the Clay Sculpt recap where each item is labelled alpha, beta or waitlist.
The through-line across the posts is that context and data quality matter more than the agent, and that ads, outbound and sales should work from one target-account list and one score.
The format is consistent: a stated problem, numbered steps, named tools, and a closing question to readers.
Writes about go-to-market engineering on the same tooling Damian uses, including Clay and Lusha, and treats the data layer as what sets outreach timing.
Read more
Both explain how signals such as hiring and funding decide when a company is worth contacting, and both write for practitioners building prospecting pipelines rather than for a general marketing audience.
Zwebti also writes about governing AI agents once they are running, covering least-privilege access, audit trails and what happens when an agent acts outside its scope. Damian stays closer to playbook execution and agency delivery, with less material on agent operations and control.
Works from the same Claude-based go-to-market stack and publishes practical workflows for building, enriching and testing contact lists, including a lean pairing of Claude with a prospecting data tool for fast segment tests.
Read more
Like Damian, Turewicz treats checking the output as part of the method rather than trusting a first pass.
Turewicz's published focus is quality control and quick experiments for client segments, including running a second session purely to check the first. Damian publishes whole campaign systems and a six-stage account-based playbook tied to how his agency runs the work.
Writes about account-based marketing as a staged motion and about where AI genuinely helps versus where it only speeds up the same volume.
Read more
Both break the topic into numbered stages a reader can follow step by step.
Plassard frames the problem around operational queues, review cycles and keeping relevance as an account list grows from twenty to two hundred, with little tool-by-tool detail. Damian names the specific tools at each stage and shows multi-channel coordination between ads, outbound and sales.
Start with the decision this section can support: Kenny Damian offers a small, specialized audience rather than broad reach, so he suits a campaign that needs a niche of B2B GTM and sales-tech operators.
Read more
His LinkedIn profile showed 14,963 followers when observed on 8 October 2026.
The work those followers see is practical build-along content — outbound workflows, Clay and Lusha tooling, ABM playbooks, and how AI agents fit inside a sales team — written for people who run or buy these systems.
That is a topic match, not a measured audience composition.
No follower geography, seniority, company size, industry split, or engagement rate came with the material reviewed, so the match is a hypothesis to verify rather than a proven fit.
Before committing budget, ask Damian for two things: a LinkedIn follower-demographics export covering location, seniority, industry, and company size, and recent results for comparable posts — workflow breakdowns, ABM playbooks, or Claude and Clay release explainers — including impressions and engagement rate, plus any past sponsored campaign outcomes on outbound or GTM topics.
Those two items answer the buyer questions the current evidence cannot: whether the people following are the buyers in the brief, and whether comparable content draws them in.
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.
Read more
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.
Tool-vendor workflow breakdown
Buyer requirement
Supply a product with a working API and a real end-to-end workflow, plus a tracked signup or demo link. The example post walks a full outbound campaign through six stages — sourcing companies, live buying signals, account scoring, contact sourcing, email and dial verification, and sequence copy — so the vendor has to be willing to have its actual steps, accuracy claims, and integrations described in public detail rather than summarised as a tagline.
Product-launch explainer
Buyer requirement
A launch or feature set large enough to carry a single cheat-sheet post, with release names, current availability status, and a concrete call to action.
The Clay Sculpt breakdown lists each announcement with its stage — agent and knowledge hub in alpha, workflows in open beta, inbound agent on a waitlist, twelve launches across twelve weeks — and closes by telling readers to send it to whoever owns the workspace.
Buyers should expect the post to be built around the vendor's own announcement material and to name features exactly as the company does.
A B2B sales-tech company that wants to build AI-powered outbound workflows is the brief Kenny Damian fits, because that is the subject of nearly everything reviewed.
Read more
The published work walks through an end-to-end outbound campaign built in Claude Code — sourcing companies from a plain-English ICP, checking live buying signals, scoring accounts on fit plus intent, finding decision makers, verifying emails and dials, writing sequenced copy, launching, and syncing back to the CRM — and a six-stage ABM playbook covering account selection, buyer mapping, signal categories, a cold-to-hot score, coordinated ads and outbound, and pipeline reporting.
Damian also runs Frontal, a GTM engineering firm selling this work as a service, so they can speak to implementation rather than comment from the sidelines.
The commercial format matches too: the posts are worked, step-by-step breakdowns of one tool or launch, ending in a signup link or a save-and-share prompt.
A sponsored workflow breakdown reads as native content here rather than an interruption, and puts the brand's name inside a walkthrough practitioners keep and forward.
Three things to settle before booking: no audience demographics or engagement rate were available, a paid placement would sit beside Damian's own agency promotion, and the reviewed posts promote specific vendors such as Lusha and Clay, so a brand competing with those tools or with Frontal's services should raise the conflict directly.
Cycle time on any brief is the biggest open risk — Damian has built Clay workflows end to end, but the post does not say how long the build took or how much copy was written from a stored framework versus from scratch.
When to choose a specialist
An HR-tech company selling an employee-engagement platform, targeting HR directors and VP People with a video-led awareness campaign and a firm impression guarantee, is a poor fit.
Read more
The seven posts read in full stay inside sales and go-to-market tooling: outbound sourcing, buying signals, account scoring, CRM sync-back, Claude skill-sharing for SDRs, Clay releases, and ABM orchestration.
There is no people-ops, workplace, or HR content in the reviewed material, so the topic overlap is effectively zero.
Two structural gaps compound that.
First, the evidence contains no video or spoken work at all — text posts are the only format available, so a video-led brief cannot be assessed from what is known.
Second, nothing in the material reports audience geography, seniority, industry, or engagement rate; the profile showed 14,963 followers on 8 October 2026, but the composition of that following is unknown.
A brief that requires a composition or impression guarantee cannot be supported by the reviewed evidence, and promising one would overstate what is known.
The format also cuts the wrong way: a numbered operator walkthrough that names fifteen tools serves practitioners, not HR leadership.
What would change this decision is a follower-demographics export showing HR or people leaders, plus examples of video or event work.
Until then, a broad-reach or non-sales audience brief is better served elsewhere.
A worked campaign example
For the sales-tech brief, the strongest angle is a sponsored build-along series that puts the brand inside a real outbound build rather than adjacent to it. Three LinkedIn posts, each following the structure Damian already uses — numbered steps, a named tool at each step, a stated output, and a closing question.
Post one, sourcing and tiering: describe an ICP in plain English, have the brand's product return the matching accounts, then score and tier them. Opening line in Damian's register: "We rebuilt our target list in Claude Code, and [brand] did the part that used to take three tabs."
Post two, signals and timing: show how live buying signals change priority, and where the brand's data sits in that decision. Post three, copy, launch, and write-back: generate the sequence from a stored framework, launch, and sync every contact back to the CRM.
Close the series with one cheat sheet post that compresses the three steps into a single saveable image or list, the way the Clay launch breakdown and the six-stage ABM playbook are compressed.
Measure on tracked signups or demo requests from a campaign-specific link, plus saves, shares, comment replies, and one short form asking which step readers get stuck on — that answer is the seed of the next campaign.
Keep any performance or accuracy numbers attributed as the creator's own claims, not audited results.
No rate card, exclusivity term, or turnaround commitment is published in the reviewed material, so scope, approval rounds, and revision limits need direct negotiation.
Rami Zwebti is the stronger pick when the campaign's job is to argue a category position rather than show a build.
Read more
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.
The material shows argument and analysis, not a repeatable build.
Where Kenny Damian publishes numbered steps that end with a named tool at each stage, output, and a launch, Zwebti's posts stop at the case for the approach and the shape of the data behind it.
A reader who wants to copy a workflow gets less from Zwebti; a reader who needs to be convinced the workflow is worth copying gets more.
No service, delivery model, or client work is documented in the reviewed posts, so an implementation-partner brief is better answered by Damian.
David Turewicz fits a brief built around checking AI output or testing a new segment fast, rather than running a full campaign.
Read more
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.
Turewicz covers two steps of the pipeline well and the rest not at all.
There is no signal scoring, no coordinated ads and outbound, no launch-to-CRM reporting loop, and no agency offer described in the reviewed posts.
The two-minute segment build is the creator's own figure, not an audited result, so a campaign that needs proof of speed cannot lean on it.
Choose Turewicz when the decision a buyer is making is 'how do we trust and test this', and Damian when the decision is 'how do we run the whole motion'.
Vincent Plassard is the better choice when the brief is about ABM programme design and keeping relevance as the account list grows.
Read more
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.
Plassard gives the diagnosis and the principle, not the toolchain.
There is no numbered stack of named vendors, no scoring logic, and no end-to-end workflow a practitioner can reproduce from the posts alone; compared with Damian's step-by-step material, the practical detail a hands-on operator needs is thinner.
The value sits in the framing of why ABM motions stall, which is the right input for a leadership audience and the wrong one for a build-along campaign.
This profile is built from seven complete LinkedIn posts written by Kenny Damian, read in full rather than sampled from titles or excerpts.
They cover an end-to-end outbound campaign built in Claude Code, a LinkedIn engagement-to-outbound workflow, an argument about the intelligence layer under sales teams, a method for sharing Claude skills across a team, a six-stage account-based marketing playbook, a breakdown of Clay's Sculpt product launch, and a company update about Frontal.
A LinkedIn profile observed on 8 October 2026 reported 14,963 followers; no post-level publication dates were supplied, so the order in which these ideas developed is not established.
The evidence is short-form written social posts only.
No videos, podcasts, longer articles, or third-party coverage were available, no audience demographics or engagement rates were measured, and the figures the posts cite — email verification accuracy, client counts, pipeline value — are the author's own statements and have not been independently confirmed.
Tool mentions, including Lusha's sign-up link, are reported as they appear in the posts, without inferring a commercial arrangement beyond what is written.
Recent engagement
Across their last 6 LinkedIn posts, the median post got 101 reactions and 56 comments. Checked 2026-11-02.
