| Ownership | The client retains day-to-day ownership. EffDes diagnoses and helps fix the agreed priority. | EffDes and the client share responsibility for a meaningful part of the acquisition system. | EffDes leads the agreed acquisition system work across the highest-priority bottlenecks. | EffDes leads across paid acquisition, conversion, attribution, landing pages, follow-up, automation and necessary development. |
|---|
| Active priorities | One limited, clearly agreed priority. | Paid acquisition and attribution, with one active CRO or conversion priority at a time. | Multiple active priorities across acquisition, conversion, attribution and the landing-page or follow-up path. | Multiple acquisition-system priorities, sequenced by business impact rather than a fixed service checklist. |
|---|
| Paid acquisition | Available when it is the one agreed priority. | Active support. | Can run as a connected active priority. | Prioritized across the campaign-to-customer system. |
|---|
| Attribution / measurement | Available when it is the one agreed priority. | Active support. | Can run as a connected active priority. | Prioritized across the campaign-to-customer system. |
|---|
| CRO / conversion | Available when it is the one agreed priority. | One active CRO or conversion priority at a time. | Can run as a connected active priority. | Prioritized across the campaign-to-customer system. |
|---|
| Automation | Separately scoped beyond the agreed priority. | Included only when part of the agreed work. | Can support the follow-up path within the agreed scope. | Prioritized across the campaign-to-customer system. |
|---|
| Development capacity | Separately scoped beyond the agreed priority. | Included only when part of the agreed work; larger work is scoped separately. | Broader implementation capacity within an agreed scope. | Highest bounded implementation capacity within the written scope. |
|---|
| Cadence | Focused communication around that priority. | Approximately biweekly review and optimization communication. | Weekly active operating involvement where appropriate. | Active weekly operating involvement and the closest ongoing collaboration. |
|---|
| Client responsibility | Development or automation beyond the agreed problem is scoped separately. | The client provides access, decisions and internal follow-through while EffDes manages the agreed work. | Broader implementation capacity within an agreed scope; capacity is not unlimited. | The highest implementation capacity of the plans, bounded by the written scope and current priorities. |
|---|