An asynchronous creative testing partnership for DTC growth agencies, with three production cycles per monthly period and an included post-test readback for each cycle.
Each cycle connects an evidence review, working hypothesis, Creative Brief, static batch and media buyer handoff. Your media buyer runs the test; I review the agreed results your team supplies.
In a standard all-static month, the package includes 12–18 distinct static units in 4:5 and 9:16: 24–36 image files.
The three cycles can serve one DTC client account or be divided across up to two. This is three cycles in total, not three per account. Allocation and account-specific inputs are agreed before the month begins.
What is included
Three Working Hypotheses & Creative Briefs: One per cycle, recording the question, intended variable, fixed conditions, asset specifications and readback criteria.
Three Static Production Batches: 4–6 distinct units per cycle in both aspect ratios.
Three Traceable Handoffs: Named assets, briefs and comparison/setup notes.
Three Post-Test Readbacks: One written review per cycle after its complete agreed result pack is returned.
Monthly Signal Summary: What the returned evidence supports, what remains open and which decisions need further data.
All three readbacks are included. Their dates depend on when your media buyer finishes the tests and returns the evidence. The third readback may follow the monthly production period; it remains part of that cycle's included scope.
Optional 2.5D motion
When account-side evidence supports the agreed criteria for a static winner, one production slot may be reassigned to controlled 2.5D adaptations.
Motion replaces that slot's static production. It is not an additional unlimited batch. Before approval, the written scope specifies the motion assets, formats, delivery date and revised static total. With two static cycles remaining, the month contains 8–12 static units, or 16–24 static image files, plus the agreed motion package.
Written workflow
Inputs, brief sign-off, handoffs and readbacks use agreed written checkpoints across time zones. No recurring client calls or agency Slack channel is required.
Your agency retains the client, accounts, spend and performance decisions. Your media buyer owns setup, launch, tracking and result return. I deliver test planning, briefs, production, handoff and included creative readbacks.
Media buying, account management, unscoped creative requests and performance guarantees are outside this service.
Delivery process
Before the month: Agree the three-cycle allocation across one or up to two accounts, inputs, production dates, written approvals and result-pack requirements.
Cycle 1 — Days 1–10: Hypothesis, brief, 4–6 static units in both formats and handoff.
Cycle 2 — Days 11–20: Hypothesis, brief, 4–6 static units and handoff. Use Cycle 1's readback when comparable results are available.
Cycle 3 — Days 21–30: Hypothesis, brief, 4–6 static units and handoff, or the agreed motion substitution. Prepare the monthly summary.
Readbacks 1, 2 and 3: Each follows the corresponding complete result pack. We confirm the written readback date on receipt; the account-side test window is not guaranteed by the production calendar.
If an earlier test is still running, we may progress an independently scoped question when its inputs and comparison conditions are ready. A dependent iteration waits for the evidence it needs. Missing inputs or approvals can change the production schedule; revised dates are confirmed in writing.
An asynchronous creative testing partnership for DTC growth agencies, with three production cycles per monthly period and an included post-test readback for each cycle.
Each cycle connects an evidence review, working hypothesis, Creative Brief, static batch and media buyer handoff. Your media buyer runs the test; I review the agreed results your team supplies.
In a standard all-static month, the package includes 12–18 distinct static units in 4:5 and 9:16: 24–36 image files.
The three cycles can serve one DTC client account or be divided across up to two. This is three cycles in total, not three per account. Allocation and account-specific inputs are agreed before the month begins.
What is included
Three Working Hypotheses & Creative Briefs: One per cycle, recording the question, intended variable, fixed conditions, asset specifications and readback criteria.
Three Static Production Batches: 4–6 distinct units per cycle in both aspect ratios.
Three Traceable Handoffs: Named assets, briefs and comparison/setup notes.
Three Post-Test Readbacks: One written review per cycle after its complete agreed result pack is returned.
Monthly Signal Summary: What the returned evidence supports, what remains open and which decisions need further data.
All three readbacks are included. Their dates depend on when your media buyer finishes the tests and returns the evidence. The third readback may follow the monthly production period; it remains part of that cycle's included scope.
Optional 2.5D motion
When account-side evidence supports the agreed criteria for a static winner, one production slot may be reassigned to controlled 2.5D adaptations.
Motion replaces that slot's static production. It is not an additional unlimited batch. Before approval, the written scope specifies the motion assets, formats, delivery date and revised static total. With two static cycles remaining, the month contains 8–12 static units, or 16–24 static image files, plus the agreed motion package.
Written workflow
Inputs, brief sign-off, handoffs and readbacks use agreed written checkpoints across time zones. No recurring client calls or agency Slack channel is required.
Your agency retains the client, accounts, spend and performance decisions. Your media buyer owns setup, launch, tracking and result return. I deliver test planning, briefs, production, handoff and included creative readbacks.
Media buying, account management, unscoped creative requests and performance guarantees are outside this service.
Delivery process
Before the month: Agree the three-cycle allocation across one or up to two accounts, inputs, production dates, written approvals and result-pack requirements.
Cycle 1 — Days 1–10: Hypothesis, brief, 4–6 static units in both formats and handoff.
Cycle 2 — Days 11–20: Hypothesis, brief, 4–6 static units and handoff. Use Cycle 1's readback when comparable results are available.
Cycle 3 — Days 21–30: Hypothesis, brief, 4–6 static units and handoff, or the agreed motion substitution. Prepare the monthly summary.
Readbacks 1, 2 and 3: Each follows the corresponding complete result pack. We confirm the written readback date on receipt; the account-side test window is not guaranteed by the production calendar.
If an earlier test is still running, we may progress an independently scoped question when its inputs and comparison conditions are ready. A dependent iteration waits for the evidence it needs. Missing inputs or approvals can change the production schedule; revised dates are confirmed in writing.