Each project must define included pages/domains/numbers, qualification flows, captured fields, routing outcomes, knowledge, users, connectors and allowed actions, revision rounds, monthly updates, acceptance criteria, launch requirements, stabilization, support, and handover formats.
The Starter baseline is one flow, up to five fields, three routing outcomes, one activation/UAT revision round, and one monthly knowledge-update batch of up to ten changed items, without an external connector. Growth includes up to three flows, twelve fields total, eight routing outcomes, two revision rounds, two monthly update batches with up to twenty-five changed items in total, and one standard Google Sheets or Cal.com connector with written actions. Page, knowledge, user, domain, number, and AI Answer limits follow the service card and SOW.
One revision round is one consolidated feedback list from one client PIC. A defect that fails accepted criteria does not consume revision allowance during stabilization. Changes to direction, preference, content, flow, integration, or features after approval consume the allowance or become a change request.
Custom must state exact counts, named systems, data direction/actions, revisions, reporting, retention, support/SLA, UAT, stabilization, activation price, and monthly price. Out-of-scope work starts only after written approval of price and timeline impact.