Building an enterprise ABM system with a team of two.

Enterprise ambition. Startup resources.

Genesis needed an enterprise-grade account-based motion, but the marketing team consisted of two people without dedicated design, development, analytics, or marketing operations support. Traditional production workflows would have turned every personalized campaign into a queue.

The public story identifies Kevin Jong and Esther Katz as that team. It attributes the design of the closed-loop GTM engine to Kevin, with Mutiny serving as the personalized asset-creation layer. That separates the operating architecture from the tool used to produce the assets.

A loop, not a campaign assembly line.

The system brought CRM fields, account research, call transcripts, intent signals, campaign performance, and field feedback into one operating model. AI accelerated research and production, while templates and human review preserved relevance and brand quality.

The GTM architecture connected four responsibilities: capture useful context, interpret it, activate a relevant experience, and learn from the response. The GTM engineering work connected that model to repeatable field execution. This describes an operating model, not a specification of a fully autonomous software platform.

1. 01Capture

   Collect account context, buyer behavior, and field intelligence. Keep the originating context attached to the signal.

2. 02Interpret

   Turn fragmented signals into an account thesis and a next action. Apply product knowledge and human judgment to the interpretation.

3. 03Activate

   Create personalized experiences and equip sellers at the moment of need. Keep the account context intact through the handoff.

4. 04Learn

   Feed response and performance information back into the next cycle. Refine the account context, message, and field action together.

Speed became part of the strategy.

Personalized pages that once required more than a week of cross-functional handoffs could be created in a day. Follow-up assets could be ready while an active deal still had momentum, and the field received material grounded in actual account context instead of generic automation.

The reported campaign results support the customer story's account of faster execution. They do not isolate the effect of AI, the software, or any single part of the operating model. The source does not publish enough measurement detail to establish that causal attribution.

AI was most useful as a force multiplier inside a sound operating model. It did not replace the fundamentals of audience, message, timing, or judgment.