# David Arnoux

David Arnoux builds AI-powered systems for B2B sales and go-to-market teams. His work covers using AI agents in revenue operations, automating business workflows, and choosing the tools and data that support them.

- Profile: https://b2binfluencer.marketing/creators/david-arnoux/
- LinkedIn: https://www.linkedin.com/in/davidarnoux
- LinkedIn followers: 45,646
- Median of last 9 posts: 18 reactions, 10 comments (checked 2026-11-02)
- Topics: artificial-intelligence, revenue-operations
- Based on 8 dated posts, latest 2026-09-29

## Summary

David Arnoux is most useful for practical AI agent and go-to-market frameworks for B2B revenue teams.

- Best for: A B2B software brand selling an AI agent or RevOps platform to revenue and GTM leaders.
- Not for: A consumer brand seeking broad awareness from general consumers with no interest in B2B software decisions.
- Check first: Confirm sponsorship labels, audience breakdown, recent results, and commercial terms.

### Takeaways

- Scale AI by building shared stack once and embedding small teams in each business unit.
- Buy an agent for reliability across team tools; build for proprietary logic.
- Agents will make more software and data buying decisions, so prices must be machine-readable.

## Main ideas

- **Scale AI by building the shared stack once and embedding small teams in each business unit**: Arnoux says the common paths fail: a central top-down programme that produces slides but ships nothing, and scattered per-team proofs of concept that never reach production or get reused. His alternative starts with three prerequisites — executive buy-in with urgency and a budget, the right team, and aggressive prioritisation that says no to everything else for now. One AI centre of excellence owns guardrails, governance, cross-unit trade-offs, leadership education, and shared components, meeting monthly. Each business unit gets a small embedded team: an executive sponsor, an internal product owner, someone close to the tooling, and an AI-native engineer, meeting weekly. Use cases sit on one ranked backlog scored on impact and ease. He argues about 80% of the stack — data layer, connectors and access, agent runtime, guardrails and audit, patterns and evals — should be built once and reused, with the last 20% fitted per use case.
- **Buy an agent when the job needs reliability across a team's tools; build only when it needs your proprietary logic**: Arnoux uses one question to decide: does the job depend on logic only your company has, or on reliable operation across the tools a whole team already uses? Proprietary logic points to building. Team-wide reliability points to hiring an off-the-shelf agent. In both examples he keeps a human decision on outbound actions, with scoped permissions and an audit trail.
- **Agents will make more software and data buying decisions than humans, so prices and coverage have to be machine-readable**: Arnoux argues that hidden pricing behind tiers, seats and contact-sales calls worked when humans decided with relationships and emotion. An agent reads price, coverage and quality and picks, so a product whose price sits behind a demo call gets skipped. He says agents need data without contracts or minimum spends, and that pay-as-you-go replaces subscriptions.
- **Rank GTM channels by speed to payoff and pipeline strength, not by category**: Arnoux sorts B2B go-to-market motions into four boxes. Fast and strong are network and intros, executive dinners, warm LinkedIn DMs, signal-based outbound and webinars. Slow and strong are founder posting, SEO, AI search, partnerships, community and free tools, which take six to twelve months before paying and then compound. Fast and weak are paid search, LinkedIn ads, creators, cold calling, cold DMs, Product Hunt and AI SDRs, suited to capped bursts. Slow and weak, which he says to skip, are PR, big conferences, owned newsletters and generic cold email. He reasons that AI has cut the cost of running the strong motions, so a small team can keep the top half running at once.
- **Treat every AI product as a wrapper on compute, chokepoints and physical supply**: Arnoux walks a 15-layer map from energy, raw materials, refining, lithography machines, chip design and fabs, through memory and packaging, GPUs, data centres and clouds, up to models, inference routers, tool and data APIs, aggregators and applications. His argument is that everything above the foundation wraps the layers below, that the chokepoints — a handful of firms in a few countries — carry the fattest margins, and that the biggest bottlenecks sit at GPUs and data centres. He says a buyer of AI is buying the top of the stack, while price changes, outages and rate limits often start lower down.
- **Design guardrails instead of assuming a human can review every step**: From the AI Business Summit, Arnoux reports that attendees were working from Claude Code, that companies are building a second brain with playbooks, skills, agents and workflows layered on top, and that headless and command-line interfaces still have a long adoption runway. He argues the human-in-the-loop idea is largely a myth once guardrails, compliance, security and branding are designed in, because the volume of activity is too high for people to review at every step. He also stresses that distribution still decides outcomes when everyone can build.

## Work to read

- [A five-part approach to making business units AI-native](https://www.linkedin.com/posts/davidarnoux_ive-made-20-bus-ai-native-this-is-my-activity-7521841325432901635--bkw)
- [When to buy an AI agent instead of building one](https://www.linkedin.com/posts/davidarnoux_aiemployee-gtm-sponsored-activity-7485261752008491008-Pk0C)
- [How Arnoux sorts B2B go-to-market channels](https://www.linkedin.com/posts/davidarnoux_which-gtm-motions-are-actually-worth-running-activity-7520759954237104128-or0_)
- [A layered model of the AI stack](https://www.linkedin.com/posts/davidarnoux_if-you-dont-understand-this-stackmodel-activity-7521117558419156992-Mzsp)
- [An AI agent for partnership replies](https://www.linkedin.com/posts/davidarnoux_partnerships-aiemployee-partnerships-activity-7521587321800978433-gK-w)

## Brand relationships

- **looot** (owned_business)
- **Viktor** (sponsor)
- **BuiltWith** (disclosed_partnership)
- **Prospeo** (disclosed_partnership)
- **n8n** (disclosed_partnership)
- **heyarnoux.com** (owned_business)
- **Anthropic** (mention)

## Partnerships

David Arnoux’s reviewed LinkedIn posts include two disclosed sponsored or paid-partnership posts for Viktor, an AI employee aimed at GTM and RevOps teams. Both posts teach a specific operational problem before naming the product and include a clear call to action with a trial or credit offer. The reviewed material contains no sponsor policy, rate card, audience specification, booking process, or official partnership inquiry route. The looot posts show a separate company-level partnership format: provider integration announcements for the looot data and tools platform, but those are not a creator sponsorship offer.

## Alternatives

- Joe Gannon: For the same campaign decision — sponsor an AI or RevOps product with a LinkedIn post plus explainer that helps RevOps and GTM leaders choose between building and buying an agent — Gannon is the better choice when the sponsor wants a founder-led, small-team testimonial instead of a buyer's decision framework. The reviewed Viktor post shows Gannon checking inbound leads across email and booking forms, adding missing leads to the CRM, building a monthly lead chart, and reporting about two hours a day back since July. That is a concrete, personal account of a ready-made AI employee doing one job, which suits a sponsor selling a lightweight agent that a founder or small agency can adopt quickly.
- João (Joe) Moura: Moura is the better choice for the same campaign decision when the sponsored explainer should teach a maturity model rather than argue a specific build-or-buy call. The reviewed posts map seven stages of AI use at work and draw a clear line between a workflow that follows written steps and an agent that receives a goal. Moura uses an accounts payable example to make the distinction concrete. That structure gives a sponsor a self-assessment hook — which stage is your team on? — and a vocabulary for agent adoption that a general business audience can follow without a product tour.
- Peter Kirk: Kirk is the better choice for the same campaign decision when the sponsor's product fixes CRM data, recovers untapped contacts, or audits automation risk before an AI agent decision. The reviewed posts show a client about to spend roughly $30,000 on intent data before finding 50,000 people already in the CRM who had never been followed up with, and a client with more than 100 workflows where one sent an old test email to 600 people. Both examples give a marketing-ops audience a reason to clean up and trust the existing system. A sponsor selling data hygiene, workflow governance, or CRM audit services fits that task more closely than an agent-platform message.

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