marketing_ops · saas · workflow
Genesis builds enterprise ABM program with a two-person team using Mutiny
Genesis's two-person marketing team needed to execute enterprise-grade ABM but had no design, dev, or ops support. Building a single personalized landing page took more than a week, making it impossible to respond to time-sensitive sales moments at scale.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Sales signal triggers asset need
A real-time sales request or intent signal creates an immediate need for a personalized asset.
Tools used
Mutiny
Outcome
Kevin achieved a 3x increase in outbound meeting booking rate, an 80% reduction in asset creation time, and created 20+ personalized landing pages in a single day. The direct mail campaign converted 10% of cold accounts to meetings, versus an industry benchmark of less than 3–5%.
Results
Time saved80%
Volume3x increase
Source
https://www.mutinyhq.com/case-studies/how-genesis-built-an-enterprise-abm-program-with-a-team-of-two
Grounding & classification
Source type: vendor customer story
27 fields verified against source quotes.
agentic workflowcontent generationpersonalizationcall recordingknowledge basemetric backednamed customerproduction runtime claimedsource backedtools describedworkflow describedsoftwareconversion increaseemployee productivitythroughput increasetime savedvendor customer storylead processingmarketing opssales outreachagentic task executiondata sync enrichment