Molly Devin writes about sales execution, RevOps, and how AI agents could help sales teams do complex deal work. Her posts draw on sales-leadership questions and Devin's early weeks at Fluint.
Useful for a discussion-led LinkedIn series on sales execution and AI agents for sales and RevOps audiences.
Best for
B2B SaaS selling sales-AI or RevOps to sales leaders, enablement, and RevOps buyers.
Not for
Consumer or high-reach paid sponsorship with rate card, impressions, video, demos, vendor comparisons.
Key takeaways
AI can write the business case but cannot read the deal.
RevOps rollouts fail in a layer nobody owns.
Agents that do not remember or coordinate are the bottleneck, not agent count.
Check first: Confirm available formats, rates, terms, inquiry route, and recent reach and engagement results.
Main ideas
Knowledge is not judgment: AI can write the business case but cannot read the deal · The recurring question: why does mid-funnel work not happen · RevOps rollouts fail in a layer nobody owns
Molly Devin writes about sales execution, RevOps, and AI agents, with a focus on why sales plans and tools do not always translate into consistent work.
In posts about their early weeks at Fluint and broader sales questions, they examine stalled mid-funnel deals, the gap between AI knowledge and sales judgment, and whether separate agents can share context.
The work is useful to readers interested in how sales teams put strategy into practice and where AI might help—or fall short.
Devin makes abstract sales-AI problems concrete.
One post contrasts a polished, three-page AI-written business case with what a particular buyer needs: a one-page brief before a CFO presentation, framed against the competitor in the deal.
Another uses questions about whether one agent can pass a CFO’s projection limit to another to explain the coordination problem.
Devin also asks where strategy fails between a plan and its execution, and explicitly invites the strongest counterexample to that theory.
This mix of practical scenarios and open questions gives readers a way to examine their own sales processes, rather than just hear general claims about AI.
Some posts are commercially situated: Devin argues for Fluint’s Olli agent as an alternative to building an agent system, while the early-ramp post includes an unfilled example placeholder.
Devin's recurring subject is the gap between knowing what good sales work looks like and getting it done.
Read more
The posts return to one question — why mid-funnel work slips even when sellers and leaders know better — and offer different explanations: judgment that is not written in a playbook, a layer between strategy and execution that nobody owns, and AI agents that carry knowledge but not context.
Another priority runs alongside it: RevOps should be measured on finding efficient revenue rather than reporting, and teams should weigh their assembled agent stack honestly against buying one.
The writing mixes hypotheses open to disagreement, field notes from early weeks at Fluint, and product-adjacent build-versus-buy arguments.
Knowledge is not judgment: AI can write the business case but cannot read the deal
Devin's clearest position on sales AI: a model knows how to structure a business case — its sections, format, and general argument — but not which buyer needs a one-pager, that speed beats thoroughness because the champion presents to the CFO tomorrow, or that this deal calls for a risk-based frame against a competitor who leads with ROI.
Read more
They distinguish knowledge — knowing what to do — from judgment: knowing what matters right now, based on patterns and outcomes the best reps carry without being able to explain them. That reframes the purchase: you are not buying documents; you are buying the judgment that produces them.
A rep asks Claude for a business case, gets a polished three-page document in 30 seconds, sends it, and the deal stalls. Devin uses the scenario to illustrate the gap; it is not a documented case.
The recurring question: why does mid-funnel work not happen
Sellers drawing $120K+ base salaries know they should write business cases, build account plans, and multithread into new stakeholders.
Read more
But the work does not happen consistently, deals slip at stage 3, and pipeline dies.
Devin lays out the problem and asks sales, enablement, and RevOps leaders whether the cause is people, process, capacity, or leadership — whether reps do not know what to do, or know but lack the time to execute.
The post aims to collect answers, not deliver one.
Deal reviews repeat the same questions — do we have a champion, have we multithreaded, where is the business case, is this still closing on March 1?
The answers come back as some version of "I'm working on it."
Devin names a long list of practitioners in the post to draw them into the discussion.
Other posts explore the same gap from the technical side: agents that cannot share context, and the case for having an agent do the work rather than making sellers faster at work they are already skipping.
Devin's hypothesis: when a RevOps rollout fails, it is almost never the plan and almost never the rep.
Read more
It is the space in between — a layer nobody owns, hires for, or names, where good strategy quietly fails to happen. They offer the idea as a theory to falsify, with a request for the strongest counterexample rather than agreement.
The post is the test itself: "Tell me where this breaks. I'm looking for the strongest counterexample, not agreement."
Agent posts approach the same gap from another direction, treating missing shared memory and coordination between sales agents as a technical form of the unowned layer.
Build versus buy: pricing the homegrown agent stack
Devin walks through what "we'll just build our own agent" actually requires: 30-plus specialized agents covering research, discovery, business case writing, multithreading, executive messaging, and deal scoring; orchestration so they talk to each other; training on your methodology, case studies, and closed-won patterns; data storage linking CRM, transcripts, and documents; an ML model rather than only an LLM, to learn from your deal outcomes; and ongoing maintenance as deals change.
Read more
They estimate 6 to 12-plus months of engineering, then contrast that with hiring one agent already trained on 150,000+ complex B2B cycles and live the same week.
The frame is tool versus hire: a tool makes sellers faster at work they are already not doing; a hire does the work.
The cycle figure and timeline are Devin's own, and the post argues a product position rather than an independent comparison.
The checklist is the example: each item is work a buyer would have to do in-house, set against "Or you could just hire 'Olli.'"
RevOps is judged on finding efficient revenue, not on cleaner dashboards
Devin argues that RevOps is judged not on cleaner dashboards but on whether it can find the next efficient dollar of revenue.
Read more
They cite CFO attention to CAC payback and headcount efficiency, CEO appetite for ARPU growth without another pricing battle, and boards fixed on retention and net revenue retention.
With payouts, FX, and issuing tapped out and margins flat, workforce spend leaking outside the organization's ecosystem becomes the unfilled lever.
Devin asks FinTech RevOps leaders which lever would change how they are seen heading into 2026.
Devin paints a scenario in which a RevOps leader plugs the leak: finds expansion revenue without touching pricing, keeps customers stickier longer, and gets cited in the next board deck. They assert, rather than evidence, that the lever remains available.
Ramp method: study closed-won deals before writing new plays
Instead of product training and role plays, Devin spent a first week pulling every closed-won deal from the past 12 months and looking for patterns: what buyers actually cared about, what language champions used to sell internally, where deals accelerated or stalled, and what content moved deals forward rather than creating noise.
Read more
The takeaways: the best sellers execute the same three or four moves consistently; buyers use different words than vendors do; and the data makes gaps obvious. Devin rules out building new frameworks from scratch, guessing at messaging, or waiting to feel ready, and offers to share the documents being built.
The concrete finding is a language gap: the vendor's "AI-powered sales enablement" is the buyer's "get deals unstuck faster."
One bracketed placeholder — "[insert 1-2 specific gaps you found...]" — remains unfilled in the published text, leaving the note as a working draft.
This is Devin's clearest statement, in their own words, of what they argue about sales AI, making it the fastest way to assess whether their point of view fits a campaign.
Read more
Devin describes a familiar scene: a sales rep asks Claude for a business case, gets a polished three-page document in 30 seconds, sends it, and the deal stalls.
The explanation: the tool knows the format but lacks judgment about the specific deal.
It does not know the buyer needed a one-pager, that the champion presents to the CFO tomorrow so speed beats thoroughness, or that the deal needs a risk-based frame against a competitor who leads with ROI.
Devin distinguishes “knowledge is knowing what to do” from “judgment is knowing what matters right now,” and says the best reps' judgment is not written in the playbook.
The post closes by asking which sales decisions run on gut feel rather than the playbook.
The stalled deal is an illustration, not a documented case.
For brands planning a campaign
A sales-AI campaign can build on this knowledge-versus-judgment split rather than generic productivity claims. Devin asks a direct question and invites replies, making the post a better fit for a discussion-led collaboration than a broadcast placement.
In a few lines, Devin states their recurring question — where execution breaks between strategy and reps — and shows how they frame an argument to invite disagreement rather than agreement.
Read more
In this short post, Devin advances a theory they say they would like to be wrong about: when a RevOps rollout fails, it is almost never the plan and almost never the rep.
It is the space in between — “the layer nobody owns, nobody hires for, and nobody really names,” where good strategy quietly does not happen.
Devin presents the post as a hypothesis and asks for the strongest counterexample.
For brands planning a campaign
Works as an opener for debate formats, a roundtable, or a webinar where the audience is asked to bring counterexamples. The explicit invitation to falsify is a specific, usable stance rather than generic thought-leadership tone.
Devin sets out the technical problem they keep returning to — memory and coordination between sales agents — through the dialogue that made the point, in plain language.
Read more
Devin recounts a call with a former teammate now leading RevOps at a Series C company.
That team had built 30-plus agents with Claude, custom GPTs, prompt libraries, and connected workflows.
Devin asked whether the agents talk to each other: if the research agent learns the CFO caps projections at 8%, does the business case agent know?
If a rep corrects the email agent once, does the correction carry forward?
The answer was no: the agents are separate.
Devin names the problem as making agents remember and coordinate, says it is genuinely hard, and asks readers how they are approaching it.
The account is secondhand; ask for the platform details before making vendor-specific claims.
For brands planning a campaign
Supports a technical-education angle on agent orchestration and shared memory. The detail is secondhand; ask for support before making claims about a specific platform or vendor.
Shows how Devin turns an abstract RevOps debate into a concrete comparison and makes their commercial interest clear.
Read more
The post sets out the build path as a checklist: 30-plus specialized agents covering research, discovery, business case writing, multithreading, executive messaging, and deal scoring; orchestration so they talk to each other; training on your methodology and closed-won patterns; data storage linking CRM, transcripts, and documents; an ML model that learns from your deal outcomes; and ongoing maintenance.
Devin puts that at 6–12+ months of engineering, then offers the alternative: hire “Olli,” one agent already trained and learning from 150,000+ complex B2B cycles, live the same week.
The framing is “tool” versus “hire,” with the argument that generic AI still leaves mid-funnel work on reps' plates.
Ask for support for the 150,000-cycle figure and timeline before using them as independently verified claims.
For brands planning a campaign
A campaign with a competing or complementary platform needs to account for this post's specific vendor position, rather than contradict it by accident.
Shows who Devin writes for and the revenue-efficiency language they use with finance-side buyers.
Read more
Devin opens with a hard truth: RevOps is judged not on cleaner dashboards but on finding the next efficient dollar of revenue.
The post recaps pressure they say they hear from every RevOps leader: CFOs watching CAC payback and headcount efficiency, CEOs wanting ARPU growth without another pricing fight, and boards fixed on retention and NRR.
Payouts, FX, and issuing are described as tapped out with flat margins, while workforce spend leaking outside the organization's ecosystem is presented as the unfilled lever.
The post closes with a question to FinTech RevOps leaders about the lever that would change how they are seen in 2026, followed by hashtags.
Ask for evidence that this lever is available.
For brands planning a campaign
Fits fintech, spend-management, or payments campaigns aimed at RevOps and finance-adjacent leaders: the post speaks their language and asks them a direct question.
Devin frames the central question the other posts try to answer and uses a public question to gather practitioner input.
Read more
Devin notes that sellers on $120K+ base salaries know they should write business cases, build account plans, and multithread into new stakeholders, but do not do it consistently.
Deals slip at stage three, pipeline dies, and deal reviews repeat the same questions about champions, multithreading, business cases, and close dates, with answers like “I'm working on it.”
Top performers know what good looks like even when the playbook exists, Devin says.
They ask sales, enablement, and RevOps leaders whether the cause is people, process, capacity, or leadership — do reps not know what to do, or do they know and lack the time?
The post tags a long list of practitioners by name.
For brands planning a campaign
Useful for a survey, research report, or roundtable campaign: the open question gives a brand a natural way to co-host the conversation and collect answers from the same audience Devin already reaches.
Shows the working method Devin brings into a new role and the language gap between what vendors say and what buyers say.
Read more
A ramp note from Devin’s first week at Fluint.
Instead of product training and role plays, they pulled every closed-won deal from the past 12 months and looked for patterns: what buyers cared about, what language champions used to sell internally, where deals accelerated or stalled, and what content moved deals forward.
The takeaways: the best reps consistently execute the same three or four moves; buyers use different words than vendors (“AI-powered sales enablement” versus “get deals unstuck faster”); and gaps show up in the data.
The published text still has an unfilled placeholder — “[insert 1-2 specific gaps you found…]” — so ask for the specific gaps before treating the post as finished.
It ends with an offer to share the documents being built.
For brands planning a campaign
A concrete angle for enablement or deal-analytics brands. The unfilled placeholder shows this post is part of a build-in-public thread, making it better suited to a series collaboration than a one-off placement.
Format: short field notes, numbered observations, and direct questions6
Mid-funnel execution is the recurring sales problem1
RevOps is judged on finding efficient revenue, not cleaner reporting1
AI agents fail when they do not share context1
Build versus buy is a live RevOps buying question1
Knowledge is not judgment in AI-assisted deal work1
Rollouts fail in the layer nobody owns1
Ramp method: study winning patterns before building new frameworks1
Mid-funnel execution is the recurring sales problem
In one post, Molly Devin describes experienced sellers who know they should write business cases, build account plans, and multithread, but do not do it consistently.
Read more
Deals slip at stage 3, pipeline dies, and deal reviews repeat the same questions: Do we have a champion?
Have we multithreaded?
Where is the business case?
They ask whether the cause is people, process, capacity, or leadership—and whether sellers know what to do but lack time to execute.
For brands planning a campaign
Useful for a sales-AI campaign aimed at sales leaders and RevOps buyers. Devin can address the gap between knowing what good looks like and getting mid-funnel work done, supporting a message about removing execution work—not adding another playbook or dashboard.
RevOps is judged on finding efficient revenue, not cleaner reporting
Devin argues that RevOps leaders are judged not on cleaner dashboards but on whether they can find the next efficient dollar of revenue.
Read more
The post names CFO pressure on CAC payback and headcount efficiency, CEO pressure for ARPU growth without another pricing battle, and board obsession with retention and net revenue retention. Payouts, FX, and issuing are described as tapped out, while workforce spend still leaks outside the organization’s ecosystem.
For brands planning a campaign
Good fit for a FinTech or RevOps campaign connecting AI to margin, retention, and revenue efficiency.
Devin can address CFO- and board-level pressure without reducing the pitch to dashboard cleanup.
The post also gives the campaign a concrete audience: RevOps leaders heading into annual planning.
In a field-note post, Devin recounts a conversation with a former teammate who is now a Head of RevOps at a Series C company.
Read more
The team had built more than 30 agents through Claude, custom GPTs, prompt libraries, and agentic workflows.
Asked whether the agents talk to each other, the teammate said no; they were separate.
Devin asks whether a research agent that learns a CFO caps projections at 8% can pass that insight to a business case agent, and whether a correction made to an email agent carries forward.
For brands planning a campaign
Strong for a campaign about orchestration, shared memory, and context across sales-AI workflows. Devin can address a specific problem facing RevOps and sales-enablement leaders: teams can build many agents but still lose corrections and context between them.
Devin lays out the build-versus-buy argument for sales and RevOps agents.
Read more
Building an internal system means creating 30-plus specialized agents, solving orchestration, training each agent on methodology and closed-won patterns, linking CRM, transcripts, and documents, creating an ML model rather than only an LLM, and maintaining everything as deals change.
They estimate 6 to 12-plus months of engineering work, then contrast that with hiring a single agent already trained on complex B2B cycles and live the same week.
The post frames the choice as a tool versus a hire.
For brands planning a campaign
Useful for a vendor campaign justifying the purchase of an AI sales agent over building one. Devin can address the hidden engineering and maintenance costs, and the difference between making sellers faster at work they already skip and having an agent do the work.
Knowledge is not judgment in AI-assisted deal work
Devin describes a sales rep asking Claude to write a business case.
Read more
Claude produced a structured three-page document in 30 seconds.
The rep sent it, and the deal stalled.
In their account, Claude knew how to write a business case but lacked judgment: it did not know the buyer needed a one-pager, that speed mattered because the champion was presenting to the CFO the next day, or that the deal needed a risk-based frame against a competitor leading with ROI.
Devin argues that top reps have judgment that is not in the playbook and reframes the purchase as buying the judgment that produces documents.
For brands planning a campaign
A clear message for sales-AI positioning around contextual judgment, not document-generation speed. Devin can support a campaign showing how AI must account for buyer context, deal stage, and competitive pressure before producing seller-facing material.
Devin proposes that RevOps rollout failures are rarely caused by the plan or the rep.
Read more
They happen in the layer between them—a space nobody owns, hires for, or names, where good strategy quietly does not happen. The post ends by asking for the strongest counterexample, not agreement.
For brands planning a campaign
Relevant for a campaign about implementation, ownership, and change management. Devin can frame the problem as strategy-to-execution friction, giving a tool or service a reason to exist beyond features or reporting.
Ramp method: study winning patterns before building new frameworks
In a week-three-day update at Fluint, Devin describes pulling every closed-won deal from the past 12 months and looking for patterns: what buyers cared about, what language champions used internally, where deals accelerated or stalled, and what content moved deals forward.
Read more
They conclude that the best sellers execute the same three or four moves consistently, buyers use different language than sellers do, and data makes gaps visible. Devin explicitly avoids building new frameworks from scratch, guessing at messaging, or waiting to feel ready.
First-person ramp log: review closed-won deals, extract buyer language and repeatable moves, then test rather than build new frameworks.
For brands planning a campaign
Shows an evidence-first working style and a test-and-learn approach to sales messaging. A campaign can use Devin to model data-driven sales execution or discuss how AI can surface winning patterns from deal data.
Format: short field notes, numbered observations, and direct questions
The posts follow a consistent short-form LinkedIn format: narrative openings, numbered or bulleted observations, first-person field notes from weeks at Fluint, and direct questions to sales, enablement, and RevOps readers.
Read more
Some are theory prompts asking for counterexamples; others are product-adjacent build-versus-buy arguments. They rely on concrete scenarios rather than abstract claims.
For brands planning a campaign
A collaboration can use the same structure: one clear sales or RevOps problem, a specific scenario, a short list of observations, and a question that invites buyer discussion. The format suits a campaign seeking comment-level engagement from sales leaders rather than a broadcast announcement.
The posts describe one business relationship: Molly Devin writes from inside Fluint, counting their weeks there and explaining the company's AI agent, Olli, as the buy-side option in a build-versus-buy decision.
Read more
No other brand is named in a way that shows a relationship — the remaining posts discuss sales leadership, RevOps, and AI agents generically, or thank individual colleagues rather than companies. Some posts mention tools such as Claude in passing.
Fluint
Employment
Their posts count their weeks at Fluint — "Week 3 at Fluint," "Week 4 Update at Fluint," and "here's to WEEK 5.5 at Fluint" — alongside a new-hire ramp post about studying closed/won deals rather than doing product training.
Read more
The Week 4 post argues buyers should hire Fluint's agent, Olli, instead of building a custom stack of 30-plus agents.
Read together, the posts present Molly Devin as an employee writing ramp-up notes and product commentary from inside the company.
Ask for their title, start date, and contract terms.
Devin writes about the gap between knowing how good sales work is done and actually getting it done.
Read more
Start with the mid-funnel posts: business cases, account plans, and multithreading that sellers know matter but skip when deals get busy and pipeline slips.
The AI posts form a continuous argument: models carry knowledge but not judgment, leaving teams with agents that produce polished documents without reading the deal and stacks that do not share what each agent learns.
Another thread treats revenue operations as a function judged by its ability to find efficient revenue, not by cleaner reporting.
Most pieces are short LinkedIn notes built around a single scene and question.
Several invite readers to offer a counterexample or share their experience, and two are first-person notes from early weeks in a new role.
The posts suit readers following how AI is actually being used and debated in B2B sales, rather than those looking for playbook summaries.
Browse by tag for sales AI, revenue operations, and mid-funnel execution; use the three creators below to compare how they approach the same questions with different evidence and formats.
Both work on the same problem from the same perspective.
Read more
Karuppanan argues that personalized outreach was the easy target and that the real leverage sits in the middle of the funnel, where deals stall unnoticed.
They draw the same dividing line Devin draws between AI applied to repeatable judgment—reading transcripts, scoring signals, spotting patterns across deals—and contextual judgment that stays human, such as which three stalled accounts to call this week.
Both write short LinkedIn posts anchored in a specific deal scene and a concrete list of steps.
Karuppanan publishes a named working toolkit: ten Claude skills for account-based marketing, covering deal reporting, ad-spend suppression against CRM data, field-marketing attribution, and stall diagnosis.
The skills are tied to HubSpot and Salesforce stacks, and posts close with a direct offer to share outputs.
Devin writes more often from the sales-leader and operations seat, framing hypotheses for debate, build-versus-buy arguments, and notes from early weeks in a role, with fewer product walkthroughs.
Both address revenue operations and sales leaders, and build arguments from a specific operating scenario toward a pointed rule.
Read more
Aleman shows how a hiring plan that assumes ten reps add ten quotas breaks when ramp curves, pipeline slicing, and rep frustration are left out of the finance model.
They also argue that deal risk is better read from behavior—a pushed close date, a quiet champion, no meeting on the calendar—than from a status field.
Both use compact LinkedIn posts to name the friction leadership ignores.
Aleman focuses on forecasting mechanics, capacity math, territory effects, and deal inspection discipline. Devin routes nearly every argument through what AI and agents can and cannot do, centering mid-funnel execution and the judgment gap rather than headcount and forecast math.
Both write long, first-person LinkedIn posts in the HubSpot and revenue-operations partner world, narrating a decision and backing it with specific figures—close rate, deal size, headcount, project volume.
Read more
Devin uses concrete numbers to narrate a call, an audit, or a build-versus-buy calculation. Both are operator and leadership voices rather than commentators.
The subject matter differs.
Byler writes about career transitions and market positioning: leaving one company with a summary of what was built, joining another, and making the case that HubSpot work in healthcare needs specialists rather than generalist consultants.
Devin focuses on daily sales execution, revenue operations, and AI judgment in deal work.
Their posts share an ecosystem but differ in format, voice, and argument.
Treat Molly Devin as a candidate to test for a sales-execution or RevOps collaboration aimed at practitioners, not as a proven reach purchase.
Read more
Their posts report 2,390 LinkedIn followers, recorded on 8 October 2026.
The writing is built for sales leaders, RevOps and enablement teams, and people wiring AI agents into deal work.
They also tag named sales and RevOps practitioners, pointing to a peer network rather than a measured readership.
Before committing budget, ask for recent reach and engagement results on business-case and agentic-AI posts comparable in length and depth to the proposed collaboration, and ask whether an audience survey records job role, seniority or geography.
Molly Devin’s LinkedIn posts are organic commentary on sales execution, RevOps, AI agents, and their early weeks at Fluint.
Read more
They contain no sponsored placements, affiliate links, or disclosed commercial terms, and publish no media kit, rate card, sponsorship policy, format list, or official inquiry route. There’s no package to price or schedule; brands should ask directly about available formats, rates, terms, and how to inquire.
Brief A: a B2B SaaS company selling a sales-AI or RevOps product to sales leaders, enablement teams, and RevOps buyers wants a short LinkedIn discussion series (three posts, plus an optional co-hosted survey or roundtable) on why AI-assisted deal work stalls in the middle of the funnel, with the product positioned as relief from execution work rather than another dashboard.
Read more
Decision: yes.
The strongest use is a discussion-led series, not a broadcast placement.
Why it fits: The audience already matches.
The posts address sales leaders, enablement, and RevOps directly, and two tag named practitioners into the conversation.
That points to a peer network, the audience this campaign needs.
They have a documented point of view a campaign can build on rather than invent.
Four claims recur: the layer between strategy and reps where rollouts quietly fail; knowledge versus judgment in AI-written deal material; agents that cannot share context or carry a correction forward; and build-versus-buy as a live RevOps decision.
Any of these can frame a series without contradicting what they already say publicly.
The format is repeatable.
The posts follow a consistent shape: a narrative opening, numbered or bulleted observations, and a direct question that invites answers or counterexamples.
That structure produces comment-level engagement from practitioners, which is what a discussion series is buying.
They also bring a ready content engine.
The ramp note describes pulling twelve months of closed-won deals to extract buyer language, repeatable moves, and the gaps between them.
It names the vendor-versus-buyer language gap directly: sellers say "AI-powered sales enablement," buyers say "get deals unstuck faster."
A collaboration can run that same exercise in public and give the vendor a concrete, useful artefact.
What to check before committing: the only published audience figure is 2,390 LinkedIn followers; there are no impressions, engagement counts, or role and seniority figures.
Treat this as a peer-distribution pilot rather than a reach purchase, and ask for comparable post engagement results before signing.
The posts list no media kit, rate card, or inquiry route, so negotiate directly.
They work at Fluint and argue publicly for its agent, so do not ask for a neutral comparison of competing vendors; disclose the affiliation in campaign copy.
When to choose a specialist
Brief B: a consumer or high-reach brand — for example a consumer finance app — wants a paid sponsorship with a published rate card, guaranteed impressions, video-first creative, and a product-demo webinar, and asks the creator to compare several competing vendors fairly.
Read more
Decision: no, not against what the posts show.
Why it does not fit: There is no package to buy.
Their posts contain no sponsored placements, affiliate links, or disclosed commercial terms, and publish no media kit, rate card, format list, or official inquiry route.
A brand cannot schedule or price a sponsorship from these posts; anything would require a from-scratch negotiation, not a guaranteed-impressions campaign.
The posts cannot support a reach guarantee.
The only published audience figure is 2,390 LinkedIn followers recorded on 8 October 2026.
There are no impressions, engagement counts, or figures for geography, age, gender, employer, or seniority, so a delivery-volume commitment has no basis.
The format does not fit.
All the posts are short-form written LinkedIn posts; there is no video, podcast, webinar, or transcript material to assess for a video-first or live-demo campaign.
The topic does not carry over.
The posts cover B2B sales execution, RevOps, AI agents in selling, and revenue efficiency.
Nothing shows a consumer brand reaching its buyers through this author.
A neutral vendor comparison is the wrong ask.
The build-versus-buy post argues for the agent their employer sells, and the figure of 150,000-plus B2B cycles and the six-to-twelve-month engineering estimate come from the author rather than an independent source.
Asking for an even-handed comparison would put them in a role the public posts do not support.
A narrower version could work if rewritten for a B2B sales or fintech audience, using written posts rather than video, without a delivery guarantee, and with a disclosed commercial relationship.
That is a different campaign, not a repair of this one.
A worked campaign example
A worked campaign angle for Brief A: "Where mid-funnel work goes missing." A three-post written LinkedIn series plus a short practitioner survey.
Post 1, the opening debate.
Use the unowned-layer argument: a RevOps rollout rarely fails because of the plan or the rep, but because of the space between them where good strategy quietly does not happen.
Open the series with a recognisable situation — a plan agreed in a Q4 review that never reaches deal work — and ask for the strongest counterexample rather than agreement.
The vendor's own comment offers a diagnostic frame instead of a pitch, keeping a debate-format post from reading as an advert.
Post 2, the language gap.
Run the closed-won exercise in public.
Pull a real, anonymised set of won deals from the vendor's own data and show where buyers' words diverge from vendor words: "AI-powered sales enablement" against "get deals unstuck faster," and the same gap in whatever the vendor's category language is.
The observation is the value; the product appears as the thing that surfaced the pattern, not as the headline.
Close by asking readers to post the mismatch they hear most.
Post 3, the specific failure.
Use the business-case scene from the strongest post: a polished three-page document produced in thirty seconds, sent, and followed by a stalled deal because the tool did not know the buyer needed a one-pager, that speed mattered ahead of a CFO meeting, or that the deal needed a risk-based frame.
Carry the knowledge-versus-judgment split into the vendor's own claim: the useful purchase is the judgment behind the document.
End by asking which decisions in readers' sales process run on gut feel rather than the playbook.
Follow-up asset.
They have a standing open question: when mid-funnel work is not getting done, is it people, process, capacity, or leadership?
Co-host a short survey or roundtable on exactly that question, collect practitioner answers, and publish the results as a fourth piece.
This gives both parties an asset that outlives the campaign and a reason for sales and RevOps leaders to respond.
Practical notes for the campaign.
Keep every piece written; the posts are written-only.
Agree the format, number of posts, and review and approval steps in writing, and disclose their Fluint affiliation in campaign copy.
Before signing, ask for engagement results on business-case and agentic-AI posts at comparable length and depth, so expectations rest on observed response rather than follower count.
Judge the series on replies, practitioner answers, and survey responses, not impressions alone.
The posts provide no per-post publication dates, engagement data, long-form or video material, or audience composition figures. The campaign angle is built from seven written posts and a follower snapshot dated 8 October 2026; ask for relevant engagement data before drafting if it affects the campaign decision.
Pick Karuppanan when the campaign has to show the mechanics of the fix, not just name the problem.
Read more
The two posts make the same mid-funnel argument Devin's series would open with, but from inside a live ABM programme: five named AI skills for deal reporting, audience targeting, account research, field marketing, and stall diagnosis; the inputs each one reads, including CRM closed-lost and closed-won data, meeting transcripts, website engagement, ad accounts, and webinar Q&A; and one audited figure: 31 stalled accounts reviewed, with 17 showing a trigger event in the last 60 days that nobody acted on. If the deliverable is a usable artefact readers can copy into their own stack, these posts go further than a debate post, and the diagnosis matches Devin's: AI saturated the top of the funnel; the edge sits where deals quietly stall.
The tradeoff is framing and audience.
Karuppanan writes as a practitioner selling execution programmes: both posts close with a direct invitation to make contact, and the skill walkthroughs assume a HubSpot-based ABM stack wired into Claude.
Readers outside that stack get less from the detail.
Devin writes to sales leaders and enablement as a peer inside a vendor, producing arguments, counterexamples, and an explicit question at the end of each post.
That question-led shape is what a discussion series is buying; Karuppanan's posts neither end with a prompt nor tag anyone into the conversation.
A sponsor wanting replies about judgement and priority gets more from Devin; one wanting to show what the work looks like gets more from Karuppanan.
Choose Aleman when the campaign targets revenue operations and planning buyers rather than AI tooling.
Read more
The posts answer questions that audience actually argues about: why hiring ten reps does not add ten quotas to the forecast; why a five-month sales cycle makes a 90-day ramp assumption mathematically impossible; why doubling headcount without adding pipeline just slices the same pipe into smaller pieces; why a top rep handed a smaller patch reads success as punishment; and why boards can plan around a miss they saw coming in week three but not a surprise they learn about in week eleven. If the sponsor is selling forecast accuracy, capacity planning, or deal-risk discipline to a VP of Revenue Operations or a finance-adjacent buyer, this framing sits closer to the decision than an argument about what agents cannot do.
The tradeoff is that this is operator analysis, not conversation.
Both posts are one-way arguments with no closing question, so a comment-driven series would need a host to open the discussion.
There is no AI-agent content: the build-versus-buy, orchestration, and knowledge-versus-judgement themes that make Devin a fit for a sales-AI campaign are absent.
A vendor selling agentic deal support would have to supply that layer itself; the two bodies of work would not be interchangeable in the same campaign.
The examples come from the author's own operating experience and have no named sources, so a sponsor that wants to inspect the basis for the claims should treat them as position rather than proof.
Choose Byler when the campaign needs executive and partner-ecosystem credibility plus a vertical story.
Read more
The two posts document a leadership track at a HubSpot partner, described in the author's own terms: sales org rebuilt, team scaled from 3 to 13, close rate up 15%, average deal size up five times, more than 200 deals closed, and partner standing moved to second in North America in 2023 and second globally in 2024.
The second post states the position that move set up: HubSpot for healthcare, specialist partners over generalist consultancies, more than 150 completed projects, and three to five EMR integrations a month where top partners do three to five a year.
For a campaign aimed at HubSpot partners, healthcare technology buyers, or growth leadership, that mix of operating record and explicit market thesis is a better fit than a peer discussion series.
The posts assert outcomes rather than asking for counterexamples.
The tradeoff is subject and format.
The posts cover HubSpot partner growth, healthcare IT, and career transitions; none addresses mid-funnel deal execution or AI agents in selling, the subject a campaign for a sales-AI sponsor is built around.
The sponsor would be paying for a different conversation.
Both posts are announcement narratives rather than recurring arguments, offering a story but no repeatable series shape; Devin's numbered observations and open question make a three-post discussion runnable.
The numbers here, including revenue growth, rankings, and integration volume, are the author's own account of work not shown in the posts.
Treat them in campaign planning notes as claims to check, not verified results.