When Journeys Outnumber Staff, Price the Maintenance Not the Build
Should an agency quote a marketing automation engagement on the number of workflows built, or on the ongoing journey, integration, and approval load those workflows create? Price the engagement on the count of journeys, integrations, approvals, and maintenance obligations, and put that count in the contract before any build starts.
By InnovaAI ResearchPublished
“Should an agency quote a marketing automation engagement on the number of workflows built, or on the ongoing journey, integration, and approval load those workflows create?”
Price the engagement on the count of journeys, integrations, approvals, and maintenance obligations, and put that count in the contract before any build starts.
Quoting a flat retainer against the build and treating ongoing journey maintenance, integration breakage, and approval cycles as goodwill, then discovering that each new channel (a WhatsApp flow in AiSensy or Getgabs, a chat funnel in Manychat, a lifecycle sequence in Klaviyo) adds a permanent maintenance obligation the retainer never covered.
The unit of work in this category is the workflow, not the send, so CRM integrity, attribution, exception handling, and documentation are what determine implementation quality and therefore the real cost to serve. Autonomy raises that cost rather than lowering it: a public test of 11 agents against a single onboarding flow saw only 3 complete the full loop, and production agent work now demands tracing, evaluation, and monitoring before launch rather than after. With 83% of B2C marketing decision makers already working with AI agents, clients treat multi-step automation as a baseline expectation, which means the margin sits in maintenance discipline, not in the novelty of the build.
- •A client asks for a fixed monthly retainer covering an automation platform before anyone has counted the live journeys, connected systems, and approval steps
- •The proposed scope spans more than one channel, so email, SMS, and WhatsApp flows share lead records and suppression logic
- •The client's CRM is the system of record and its field hygiene has not been audited in the last two quarters
- •An AI agent or chatbot layer is being added to an existing nurture sequence that already runs unattended
- •The agency is inheriting a build from a previous vendor with no written handoff or operating baseline