# heyarnoux.

> David Arnoux is a fractional GTM x AI architect. He goes inside companies, from
> seed stage to unicorn or enterprise, and builds the go-to-market engine together
> with their team: the signals, the workflows, the agents, the reporting. This site
> holds the reference explainers for the roles that work depends on, the engagement
> pages for the work itself, and the open-source systems it is built on.

The explainers are the part written to be quoted. Each one answers the question in
its own title, and where a page carries a statistic it names the source and the
publication date in the body. Between them they cover a set of roles the
go-to-market world is still settling on: the GTM engineer, the forward deployed
engineer, and the forward deployed engineer pointed at go-to-market rather than at
product delivery.

Every URL below is that page's own declared canonical. Pages carrying a noindex robots
meta tag are deliberately not listed here.

## Definitions and explainers

- [What Is a GTM Engineer? Role, Skills, Salary and Org Design](https://www.heyarnoux.com/marketing-becoming-engineering-function/): Answers what a GTM engineer is and does, what the six outputs of the job are, what GTM stands for inside the title, and where the role divides from RevOps and marketing ops. Salary and posting-growth figures are attributed inline to Bloomberry, Clay and eMarketer with publication dates.
- [What Is a Forward Deployed Engineer? Role, Origin, GTM Version](https://www.heyarnoux.com/forward-deployed-engineer/): Answers what a forward deployed engineer actually does, where Palantir built the role and why the start date is contested, why enterprise AI revived the title, and how the job differs from a solutions engineer and an AI engineer.
- [FDE Stands for Forward Deployed Engineer](https://www.heyarnoux.com/fde/): Answers what the acronym FDE means in an engineering context, separates that meaning from Flat Dark Earth in firearms and full disk encryption in security, and traces where the search demand for the role came from.
- [AI-native GTM transformation, one BU at a time](https://www.heyarnoux.com/transformation/): Answers what GTM transformation means when it is run as an engineering project rather than a strategy deck, which business unit to start with, and what the first one has to ship before the pattern scales.

## Working with David Arnoux

- [heyarnoux. GTM x AI, done with you](https://www.heyarnoux.com/): The homepage. Implementation rather than advice, the three ways to work together, the shapes the build takes, and the companies the pattern has been run with.
- [Let's build your GTM x AI engine](https://www.heyarnoux.com/collab/): The fractional engagement itself, described step by step: the diagnostic sprint that maps where revenue leaks, picking the first motion, and building it with the client's own team so the capability stays in the building.
- [GTM engineering agency, example engineer profiles](https://www.heyarnoux.com/gtm-engineers/): What a GTM engineering agency does, what it costs, and how that differs from a GTM strategy consultancy. Anonymized example profiles in the format real ones arrive in, plus the matching flow and the guarantees attached to it.

## Open-source systems and playbooks

- [GTM OS](https://www.heyarnoux.com/gtmos/): Open-source go-to-market infrastructure meant to be owned and run on your own data, inside your own walls, from an agent you already work in. The engines, the skills and the playbooks, with the code owned rather than rented.
- [The GTM Simulator](https://www.heyarnoux.com/gtmos/gtm-simulator/): A world model of a go-to-market. Answers what running the experiment before spending the budget looks like: what to run, what to kill, and when you will know. Runnable on the page.
- [Claude Code for teams](https://www.heyarnoux.com/teams/): A step-by-step playbook for running Claude Code across a small team of developers, marketers, sales and ops. Covers repo architecture, MCP scoping, hooks as guardrails, isolation, cost governance and compliance, with a quarterly audit checklist.
- [The GTM x AI Second Brain](https://www.heyarnoux.com/gtm-brain/): A ready-to-use second brain of go-to-market playbooks, skills and workflows, built across real client engagements and meant to be adapted rather than read.
- [How the GTM x AI Second Brain works](https://www.heyarnoux.com/gtm-brain/how-it-works/): Answers how the second brain is actually assembled: the layers it stacks, from the instruction file up through memory, skills, agents, playbooks and workflows, and the level system it grows through.
- [Mental Models OS](https://www.heyarnoux.com/gtm-brain/mental-models-os/): Mental models turned into executable skills for Claude Code rather than content to read, so a decision framework runs as infrastructure and compounds session over session.

## Optional

- [The full second brain library](https://www.heyarnoux.com/gtm-brain/library): The playbook and framework catalogue by category. Useful for checking whether a specific play exists, not for understanding the system.
- [Speaking and workshops](https://www.heyarnoux.com/speaking/): Keynotes, workshops and AI hackathons on GTM x AI for commercial teams. Booking information rather than reference material.