Replacing Your Agency? Define What Done Means.
Before replacing your paid-social agency with one operator, agree what finished work looks like. Name the deliverable, the evidence you will inspect, the person who accepts it and the inputs your team must supply. Do that for media buying, creative, landing pages and tracking. A service list alone leaves too much room for two different versions of “done.”
I am Timofei Tskhovrebov. I own Meta media buying, AI creative, landing pages and tracking within an agreed scope. You work directly with the person making the account decisions. That makes the responsibility easier to locate. It still needs a clear definition.
Here is the acceptance checklist I would use when scoping that engagement. It is a proposed working template you can fill in with an operator or agency, not a record from a client account.
Separate finished work from the result it must earn
A landing page can be published, checked and ready for traffic before there is enough evidence to judge its effect on acquisition cost. A creative batch can match the approved brief and still lose in the account. You need to assess both delivery and performance, at different points.
Write down three things separately: the ongoing responsibility, the specific delivery and the business target. For example, I might own the page work within a management engagement; the agreed delivery could be a revised signup page; the target could be more qualified activations at a sustainable acquisition cost. Passing the page checks does not establish that commercial result.
Equally, a low acquisition cost should not excuse an unapproved budget change or a broken form. The acceptance checks protect the agreed implementation. The subsequent performance review decides what deserves more time, more spend or a different approach.
Define acceptance for four connected workstreams
Start with the table below. Replace the examples with your actual accounts, assets, URLs and event names. Agree the number of deliverables, review steps and due dates where they apply. Ongoing account management also needs agreed decision authority and review expectations; it cannot be reduced to a one-time file handover.
| Workstream | Define the delivery | Inspect before accepting |
|---|---|---|
| Media buying | The approved change in named campaigns and accounts, within the agreed budget authority. | The implemented settings match the approved change. The record identifies what changed, who made it and any exceptions still open. |
| AI static creative | The agreed concepts, variants, formats and source assets, with a named version of the brief. | Files match the offer and formats. Required reviews and revisions are recorded. Agreed source assets are accessible to the business. |
| Landing pages | The named page, approved content and specified conversion path. | The URL is live. Agreed device, link and form checks pass. Unresolved defects have an owner and a decision. |
| Tracking | The named event, its definition and the agreed implementation or reporting fix. | Test evidence matches that definition. Sources and reporting differences are documented. Remaining engineering dependencies are explicit. |
“Creative delivered” is too vague if you expected launch-ready files and received a folder of unreviewed generations. “Tracking fixed” is too vague if the event fires but counts the wrong action. Ask for the evidence that answers the actual delivery question.
For creative, the brief-to-campaign workflow connects the assets to the buying idea and launch. For tracking, keep the event check separate from the expectation that two reporting systems should show identical totals. The Meta and Shopify reconciliation checklist explains how to inspect those differences.
Name the input that can stop each delivery
Direct ownership does not give an operator access to everything inside your business. The scope should say what you supply and who resolves a missing input.
- Media: account access, commercial targets and budget approval. Name who can authorize an increase.
- Creative: product facts, brand assets, usage rights and the person approving the offer. Identify any specialist production separately.
- Pages: site access, approved copy, integration details and the developer responsible for work outside the operator's access or scope.
- Tracking: the business definition of the event, relevant data, consent decisions and the engineering contact for backend changes.
Record the missing input, its owner and which delivery waits for it. If the launch date cannot move, agree whether to reduce the scope, use a verified existing path or defer the affected work. Do not leave a dependency buried in an old message while everyone assumes the launch is covered.
A fictional page delivery: complete, returned or waiting?
Suppose an ecommerce founder agrees one revised landing page for an existing US offer. The operator will update the page and check the agreed mobile and desktop paths. The client's developer owns the checkout integration. This example is fictional.
The operator supplies the exact URL, approved offer version and the page-check record. The mobile form submits, but the developer has not confirmed whether the submission arrives in the destination system. The visual page work may be finished. End-to-end delivery is still waiting on that integration check.
I would record the acceptance decision against the agreed requirement:
- Accept: the specified checks pass and the named reviewer accepts that version.
- Return for correction: the delivered page differs from the approved offer or fails an agreed check. Identify the defect and the retest required.
- Waiting on a dependency: the required integration check cannot be completed. Name its owner and the next action; do not report the whole delivery as accepted.
Keep the version and date with the decision. Otherwise, a later edit can make an old acceptance record look as if it covers work nobody reviewed. Use the weekly decision log to record what shipped and what happened afterward.
A new country and a video shoot are a scope decision
Now extend that fictional request: the founder wants a second country and a location-shot video before launch. Neither is in the original agreement. “You own growth” does not settle the production, localization, landing-page or tracking work involved.
I would first separate work already covered from work that needs a new agreement. An approved static variation in an included format may fit the existing scope. A shoot needs its own production owner, assets, rights, cost and timing. A new country needs commercial readiness and an explicit review of the affected pages, offer and measurement.
There are three useful decisions: approve within existing scope, agree a revised scope before work, or defer until the required inputs are ready. Write down which applies to each part. If something new displaces agreed work, say what moves and who approves that trade-off.
This is where a solo operator should be precise. I can own connected paid-social work without pretending every specialist task is included. Keep a specialist supplier where the work requires one. Price and coordinate that contribution before treating an agency replacement as a complete cost saving.
Inspect the operator, then agree the scope
A clear checklist cannot make an inexperienced operator good at the account. Inspect the underlying work too. In my anonymous AI SaaS case, December 2025 spend was $17,852.93 at $139.48 per purchase. May 2026 spend reached $148,907.37 at $131.08. I owned the structure, tracking, creative direction and scaling decisions.
My full-stack growth operation costs 5% of monthly ad spend or $3,000 per month minimum, whichever is greater. Media spend is separate. We agree the media buying, AI static creative, page and tracking work on the call. Specialist production and the separately priced AI Systems Build are not automatically included.
Use my pricing and scope comparison for the fee calculation. Use this checklist to establish the work and evidence behind that fee. Then compare the actual proposal with what your agency currently delivers.
If you spend at least $15,000 a month on Meta and want direct senior ownership, bring the account and your current scope to me. I will explain what I can own, what your team needs to supply and where another specialist belongs.