Marketing Automation Rule: Price the Journey Count, Not the Platform Seat
How should an agency scope and price a marketing automation engagement so the retainer reflects the actual number of journeys, integrations, approvals, and maintenance obligations rather than a per-seat platform fee? Count the journeys, integrations, approval gates, and monthly maintenance hours first, then set the retainer against that count instead of the number of platform logins.
By InnovaAI ResearchPublished
“How should an agency scope and price a marketing automation engagement so the retainer reflects the actual number of journeys, integrations, approvals, and maintenance obligations rather than a per-seat platform fee?”
Count the journeys, integrations, approval gates, and monthly maintenance hours first, then set the retainer against that count instead of the number of platform logins.
Quoting a flat per-month retainer based on the platform's list price or seat count, then discovering during delivery that each additional journey, integration, and approval gate consumes hours nobody priced. The retainer looks healthy in month one and turns unprofitable by month four, and the client has no operating baseline to judge whether the automation is actually working.
The category description is explicit that the unit of work is the workflow rather than a single send, and that commercial terms should follow the actual number of journeys, integrations, approvals, and maintenance obligations. That framing matches what is happening upstream: predictive systems now trigger actions autonomously, which turns oversight checkpoints into billable scope rather than an afterthought, and agencies that skip the count end up absorbing that work. The same discipline applies to the tooling layer, where a WhatsApp-first build on AiSensy or Getgabs carries different integration and approval counts than an email-led build on Campaigner or Klaviyo, so a single blended rate hides the variance.
- •A client asks for a fixed monthly retainer before anyone has counted the live workflows, connected systems, or approval gates involved
- •The proposed stack spans email, SMS, and chat channels, so each journey touches more than one sending surface (for example ActiveCampaign, Brevo, or Manychat)
- •Lead scoring, behavioral triggers, and sales handoff all sit inside the same build, which multiplies exception paths rather than adding one more send
- •The client expects autonomous actions such as budget shifts or list suppression to run without a human review gate
- •A handoff to an in-house team is planned within 6 to 12 months, so documentation and a measurable operating baseline become deliverables, not extras