What it builds
Describe it in a sentence. It gets built.
A campaign, a media plan, a live dashboard, a standing report — four different things, one way of asking for them. Not a template you fill in and not a chart library you assemble. You say what you want; the thing that answers it gets made.
The line that matters runs through the middle: two of these only ever read your account, and two of them can change it — so those two are drafted complete, held paused, and wait for you.
The thing you actually want is never the one on the menu.
Every tool ships with a set of views and a set of forms someone else decided you would need. The question in your head at 9am is more specific than any of them — and building it yourself costs the hour you were going to spend on the account.
The hour is the thing to price. One rebuilt-by-hand view a week, at the hour it costs your most expensive person, is most of a working week over a quarter — and that is only the ones that get built.
The more expensive ones are the questions nobody asks because the answer would take an afternoon. That is how an account ends up run on the four views that shipped with the tool.
A view that is still true on Thursday.
Describe the cut you want — the platforms, the window, the breakdown, the metric you judge on — and get the view rather than a form to configure one. What gets built stays wired to the data, so sharing it with a client does not turn it into a screenshot that is wrong by the end of the week.
One thing worth knowing before you send it: Audience Network is 22% of spend and 4% of revenue on this account. It will be the loudest thing on the chart.
Audience Network: the loudest thing on the chart.
Some things you want once. Some you want every week.
A view you ask for is a one-off. A standing job is the same request, made permanent: the report that rebuilds itself before the Monday call, or an agent watching one specific thing that speaks up only when it moves. You set what it watches and when it should bother you; the rest of the time it stays quiet.
The client cut you rebuild every Monday, produced before the call instead of during it — same shape each week, on current data, so the comparison to last week is real rather than reassembled.
Set one on the metric you check obsessively — the branded search share, the one campaign that carries the quarter, a placement you do not trust. It watches only that, and stays silent while nothing changes.
A watcher that reports every day trains you to ignore it. These are built to say nothing until the thing they watch actually moves, which is what makes the message worth opening when it comes.
A plan is only worth reading if it shows where the numbers came from.
Every media plan is a stack of forecasts, and almost none of them say what they were forecast from. A cell reading ₺1,400 CPA is either last quarter's campaign or somebody's optimism, and the deck does not tell you which.
Adgent drafts the plan as data instead: budget split, flights, line items, and a cost range for each — with the source campaigns and the window printed under every range. Where the account has no history, it writes no number at all and says so.
- A budget split, agreed in a meeting nobody minuted
- A CPA per line, keyed in from memory of last quarter
- Every market carries an estimate, including the one you have never run
- Assumptions live in the planner's head, and leave when they do
Reviewable only by someone who already knows the account as well as the person who wrote it.
- Every cost range names its source campaigns and window. You can open them and check.
- The market with no history gets no number. It gets a two-to-four-week test instead, stated as such.
- The measurement caveat is in the plan, not discovered in the QBR.
- It arrives as a Draft with open questions attached — nothing is applied to any account.
Reviewable by anyone, in the ten minutes before the call.
I can still give it budget, but I will not attach a cost estimate to it, because there is nothing here to ground one in. Do you want it planned as a test flight, or held back until Norvik proves the season?
One caveat I would not bury: your conversion action carries a value proxy, and a funnel step is dropping before confirmation — so the CPA figures are directional until that is fixed. Nothing is applied. It sits as a Draft until you approve it.
The gap is stated before the plan, not after it.
Every range names its basis
A cost range is written as the campaigns it came from and the window they were read over — not as a figure with a source that lives in someone's head. You can open those campaigns and disagree with the read, which is the only kind of forecast worth reviewing.
No history means no number
A market the account has never run in gets budget and a test window, and no estimate at all. The blank is the finding. Filling it with a plausible figure is how a plan starts lying in the first row and keeps the tone for the rest of the page.
Approval is per line, not per plan
You can take the two Norvik lines and leave the Dalmere test in draft until the opening date is confirmed. A plan is not a single yes — and producing it touches no campaign, no budget and no setting.
The plan is built from the connected account's own Meta and Google Ads history and nothing else. There is no pooled benchmark under it and no learning carried across from another advertiser — which is also why the empty line stays empty: there is no other account's Dalmere to borrow a number from.
A plan with no blank in it is a plan that is guessing.
Built from the connected account’s own history and nothing else. There is no pooled benchmark underneath and no learning carried across from another advertiser — which is also why the empty line stays empty.
- 0history for the new market, so no estimate is offered
- 6line items allocated to the exact total
- pausedis the state every build arrives in
Built complete. Then held, until you approve it.
Structure, budget, targeting, copy and the creative slots — drafted whole from what you described, prefilled from what this account has actually proven rather than from a template. What you get back is a specification you can read line by line, not a half-configured campaign waiting for twenty more clicks.
Meta's own guidance puts the floor at 50 events in 7 days. [developers.meta.com] A sales campaign optimizing on 4 purchases a month has nothing to learn from. It will spend the ₺3,500 and stay in learning.
Say which and I will draft it. It arrives paused either way.
Every choice carries the reason it was made, including the ones it declined.
The bid strategy it proposes is the one proven in this account. The keyword variants are ones that have run. Where it picks something second-best it says why — the ideal option was not available in this ad set.
A missing creative stops the build where you can still fix it, rather than failing after approval. The same applies to a conversion event that cannot carry value: you are told before, not after.
Approval creates the campaign in a paused state. Turning it on is a second, separate decision — and like every other write, it lands in the ledger with the state it replaced.
Building something is not the same as doing it.
A drafted plan or campaign is an artifact, not an action. It sits there, fully specified, until you approve it — and when you do, it goes through the same gates as every other change: shown with its before-state, labeled reversible or not, and logged.
Ask for a campaign built to a target the account has never reached, or a plan for a market with no history behind it, and you get pushback with the account's own numbers attached — before anything is launched. Building on request does not mean building whatever is requested.
It is the same chat where the problem was found.
The point of building from chat is that you never leave the place you were working. The verdict names the problem, you ask for the thing that shows it, and the fix applies from the same message.
Tell us the thing you keep rebuilding by hand.
The weekly cut nobody has automated, the client slide that takes an hour, the quarterly plan that costs a planner two days. Describe it in a sentence and we will build it on your data.
- Live dashboards and standing reports, from one message
- Plans with every range showing its basis
- Nothing reaches an account without your approval
The thing you described, running on your own numbers — plus how long it took, which is the part most people do not believe.
Thanks — we’ve got it.
We’ll be in touch within a couple of working days.