# Anatomy OS — GTM Anatomy > The full build: an AI-native operating system for your go-to-market team. A 40-question intake, a two-week alignment sprint, training, and a system that is yours at handover, after enablement. $25,000. Source: https://gtmanatomy.ai/offerings/anatomy-os.html --- _Offering 02_ # Anatomy OS. The full build. An AI-native operating system for your go-to-market team, with your context, your standards, and your governance written in. _$25,000_ _Three to six weeks_ _Two-week sprint_ _Yours at handover, after enablement_ ## What it is Anatomy OS is the complete build: infrastructure and skills built for your business, plus enablement and training for your go-to-market (GTM) team to drive adoption. It starts with a two-week sprint that gets your leadership team aligned on the foundations, and ends with those foundations written into a system your team runs every day. Anatomy OS is what we call it. What you are buying is an AI-native go-to-market operating system, tuned to your business, your brand, and your goals. It starts with the GTM team, because that is where the pressure is, and it is architected to scale across the rest of the organization, so every function that represents the brand is eventually working from the same context. ## How it works _Intake, a two-week sprint, then enablement_ _Before the sprint_ **Intake** A 40-question intake, which we use to validate your market position, your messaging, and your customers' challenges before anyone is in the room. _Two weeks_ **Alignment sprint** We meet for one hour a day to verify what the intake found and align your leadership team on each foundation, one at a time. _As we go_ **Written into the system** Each deliverable is written for internal use, then committed to your repository, where it becomes part of your intelligence layer. _After the sprint_ **Enable and hand over** Two training and enablement sessions and two hours of office hours, then the documentation, quick guides, and the operating system itself. ## In the room ### What we align your leadership team on. Each daily session takes one foundation, tests it against what the intake surfaced, and leaves with a decision rather than a draft. **Market position and competition** Where you sit, who you are really up against, and where the market is moving. **Ideal customer profile (ICP)** Who you sell to, who you do not, and the signals that tell the two apart. **Personas** For each persona: the outcomes they want, the challenges in the way, and the key metrics they are held to. **Messaging and positioning** What you say, how you say it, and the differentiators every skill and agent will carry. **Product portfolio** How the offering fits together, and how each part is positioned for the buyer. And the other foundations your intake surfaces. The list follows your business, not a template. ## What you get ### Inside the engagement. **Foundations your leadership team has agreed on** Validated against your intake, then confirmed in the room, so the whole team is working from one version of the story. **An intelligence layer in your own repository** Every deliverable is written to the repo and becomes part of the layer your skills and agents draw on. Update it once and everything downstream is current. **Skills built on your foundations** Built from your material and integrated into the systems your team already uses. **Written AI operating standards and governance** What agents may touch, which data they read, who approves a change, and what the review cadence is. Something finance and security can actually read. **Two training sessions and two hours of office hours** Enablement for the team that will run it, then time to bring us the questions that only come up once you are using it. **Documentation, quick guides, and the operating system** All delivered at the conclusion of the engagement. Yours at handover, after enablement, and you own all of it. ## Before you book ### Questions we get. **What happens before the sprint starts?** You complete a 40-question intake. We use your answers to validate your market position, your messaging, and your customers' challenges, so the sprint sessions are spent confirming and deciding rather than starting from a blank page. **How much of our time does it take?** The intake, then one hour a day with your leadership team across the two-week sprint, then two training sessions and two hours of office hours after it. **Who needs to be in the room?** Your leadership team. The sprint exists to align them, so the decisions made in the hour are the ones that stick. **The sprint is two weeks. Why three to six?** The sprint is two weeks. The rest is the intake before it and the enablement after it, and where a build lands in that range depends on how quickly your team turns around the intake and how fast we can schedule the sessions together. **What do we have at the end?** The documentation, the quick guides, and the operating system itself, with your foundations already written into the repository. Handover follows enablement, so your team is trained on it before it is yours. ## Why you need it A lean go-to-market team is expected to produce like a large one. That is only possible if the work you do once is used every time, by everyone, without being re-explained. That is what an operating system is. The alternative is what most teams have right now: the same models everyone else has, pointed at context nobody has agreed on, producing more of what the market already sounds like, faster. Humans and AI working as one system is bigger than the sum of its parts. Humans and AI working from different versions of the story is just louder. ## How we work ### What we hold ourselves to. - Built from your own material, never a template, so the differentiation is structural rather than editorial. - Standards and governance are written down, so security and finance have something to review rather than a demo to trust. - Everything transfers, once your team is enabled on it. There is no version of this where the system leaves when we do. The Anatomy Scan sizes this → The Anatomy Scan sizes the build and the roadmap sequences it. Start there, and the $5,000 fee credits into the $25,000 build.