To the agency owner reading this,
The daily ads work, done. The judgement stays yours.
Finds it. Fixes it. Proves it.
Ad account management software for agencies. It reads every connected Meta and Google Ads account through the day, flags what is drifting, and proposes the fix with the evidence. Then it executes only what your team approves, change by change or through a rule your team switched on. Every change is logged, and a budget or status change can be undone.
Free for 14 days, then 290 USD/month. Card required, cancel anytime.
- Approval-gated
- Dry-run mode
- Append-only ledger
- Each client's data kept apart
Meta and Google Ads today. TikTok is built and waits on TikTok's approval of our app; nobody can connect a TikTok account until then.
1 · EnclosedA working demo with invented data. Nothing here touches an ad account. Try it: press Approve.
A working demo of the Adspenta Inbox, with invented figures. One proposal for Northwind Dental on Meta: reduce the daily budget on Always-on Prospecting from €220.00 to €160.00 a day, because spend is 10% ahead of the month's plan with 10 days left. Pressing Approve does not send it: the change shows Not sent yet, with a take-back window, 20 seconds here and 5 minutes in the product, and Take back cancels it. When the window runs out it is sent to Meta and shows as confirmed once Meta reports the new value.
Campaign: Always-on Prospecting
Reduce the daily budget on Always-on Prospecting
Because spend is 10% ahead of the month's plan with 10 days left. Left as it is, the month ends at €6,600.00, €600.00 over plan.
- Month plan
- €6,000.00
- Day
- 20 of 30
- Even pace to date
- €4,000.00
- Spent to date
- €4,400.00 (+10%)
What to expectAt €160.00 a day the month ends at €6,000.00, on plan. Measured at +7 and +14 days against this account's own baseline.
Waiting for you
Meta reports €160.00/day. Due: +7 day check · +14 day check
When you approve, it waits 5 minutes so it can be taken back, then it is sent to Meta. In this demo the wait is 20 seconds.
- Approve → Not sent yet, with 5 minutes to take it back
- → Sent to Meta and confirmed
- → measured at +7 and +14 days.
Ledgerappend-only
- This morningProposal raised · reduce daily budget €220.00 → €160.00
Read, notice, propose, approve, verify. Every day, on every account.
The five steps a good media buyer runs each morning, run through the day on every client account, and written down. The long version is on how it works.
Finds it.
Reads every account every day and notices what drifted. Steps 1 and 2
Fixes it.
Proposes the exact change with the reason, and sends it only after a yes. Steps 3 and 4
Proves it.
Reads the change back from the platform, then checks the account again at +7 and +14 days. Step 5
1Read
Every account. Every day.
Through the day Adspenta reads every connected Meta and Google Ads account: campaigns, budgets, delivery, spend, cost per result, creative performance.
2Notice
It notices what a good buyer would.
It compares each account with its own recent history and the plan you set: spend running ahead of plan, cost per result drifting, an ad wearing out, a budget that will not spend.
3Propose
It proposes the fix, with the reason.
A finding becomes a proposal card: the exact change, the numbers before and after, the evidence it was drawn from. Nothing is hidden behind a score.
4Approve
Nothing happens without a yes. And you can still say no.
A person approves, or does not, unless your team has put that kind of change on that account on Act, and then the rule it switched on says the yes. After a yes there is a take-back window, in which one click puts the old value back before anything is written to the platform. The service default is five minutes; your agency can set its own, or none, in Settings.
Approve, or take it back. Five minutes by default, your call.
5Verify
Verified. Logged. Reversible.
The change is written, then read back from the platform to confirm it landed. The result goes into an append-only ledger: approved, executed, verified, by whom, at what second. Seven and fourteen days later the account is read again and compared with its own baseline: improved, worse, no change, or not enough data to say.
There is no edit button for it. Not for you, and not for us.
And what it will not do
It does not pick your offers or decide your strategy, and it drafts ad text only when someone asks, for a person to check. It watches the operational surface: budgets, delivery, pacing, structure. The judgement stays where it belongs.
Rules you can read. AI that only explains.
The part that touches money is ordinary, testable code. The language model is kept on the other side of that line, where the worst it can do is write a bad sentence.
What the code does
Finds what is drifting, computes the exact change, keeps inside the limits you set, writes it to the platform and checks it landed. The same every time it runs.
What the AI does
- Answers questions about an account in plain English, citing the figures it used.
- Explains why a detector fired, for a client who is not a media buyer.
- Drafts the weekly client update, which a human edits and sends.
- Raises a proposal card for a person to look at, the same card the rules produce.
It never executes a change, never moves a budget, and never approves anything on your behalf.
Four locks between a proposal and your client's money.
Built in dry-run first. Live is a switch you flip, per account, on purpose.
Service mode
Dry run computes and logs the change without sending it. One switch for the whole service, held by us; the service starts here.
Live writes, per account
Even with the service live, each account stays proposals-only until someone on your side turns it on.
Limits
Limits on how much one approval can move, how often, and how many times a day.
Halt
One switch stops new changes being sent, on every account, from the moment it is pressed. Anything a platform has already accepted stays, and a campaign already being created may finish, paused. It stays stopped until a person turns it back on.
And after every yes, the take-back window.
One login for your team. One clean view for each client.
Each client's data is kept from your other clients, in the database itself. Our own console shows your account names, budgets and spend, and your most recent Ledger lines, which can name a campaign. To see more, for support, we open your own screens read-only, and every screen we open is in your access log. How the separation is enforced is written out on the security page.
Manage multiple ad accounts in one portfolio
Every account you run, in one list, with the ones that need a decision at the top.
Client logins
Give a client a login for their own accounts only. They see the findings, the changes, the reports and any support thread about those accounts, and they cannot approve. They can stop changes to their own accounts with their own halt switch, and ask AI Chat a few questions a day about them.
A weekly PDF the client can read
What changed, why, and what it did, in sentences rather than a dashboard export.
Our access is logged and shown to you
To answer a support question an operator can open your own screens read-only, for a limited time, and every screen opened is logged and shown to you.
We have no customer logos yet. Here is what we can show instead.
Structural proof, checkable today. Names and numbers from clients will go here when there are clients to name.
2,726
Automated backend tests, all passing in release 2.35, and 1,159 more for the screens
7
Review rounds, the latest on 8 Oct 2026, every finding reproduced
Every read
By the operator is logged
Built in the open. The changelog of what shipped and when is dated and honest, including the rounds where the audit found something.
Adspenta is a prototype in daily use. Our own agency account runs on it, advertising Adspenta itself, and the first outside agency is trialling it. The company is being registered in Romania.
Three things we got wrong, from the changelog
Each one is still on the changelog, corrected in place and dated, where you can check it.
-
Prototype 2, 8 Sep 2026 · corrected 24 Sep 2026
We called a review independent.
The entry said it was done by people who do not work for us. We could not stand behind that description, so it is gone; what the review found is as it was.
Fixed 24 Sep 2026: the word is gone from the entry.
What we learned: a sentence we cannot prove does not stay on the site. Read the entry
-
2.5 to 2.8, 11 to 14 Sep 2026 · corrected 24 Sep 2026
A failed backup told nobody.
For the first nights our backups ran, a failed nightly backup alerted nobody: that half of the job had no way to send an alert.
Fixed 15 Sep 2026: a failed backup now raises an alert. Since 19 Sep our console also flags a night with no record.
What we learned: silence is not the same as fine. Read the entry
-
2.2, 9 Sep 2026 · corrected 24 Sep 2026
We described a switch as yours when it was ours.
The changelog said the dry-run switch was per platform and owned by the customer. It is one switch for the whole service, held by us, and every flip is written to our access log. The switches you hold are each account's live writes, and the halt.
Fixed 24 Sep 2026: the entry now says whose switch it is.
What we learned: when the page and the product disagree, the page is corrected in public, with a date. Read the entry
One plan, per agency. 14 days free, then 290 USD a month.
Adspenta
Not a percentage of ad spend. The bill does not move when a client’s budget does.
290 USD
per agency, per month, billed monthly
Up to 40 connected ad accounts, Meta and Google
Start 14-day free trialFree for 14 days, then 290 USD/month. Card required, cancel anytime.
What is included
- Every connected account read every day
- Fixes suggested with the reason
- Nothing changes without a yes, or a rule your team switched on
- A 5-minute take-back window, and a read-back before anything is called confirmed
- Every change checked again at +7 and +14 days
- One halt switch for every account
Prices exclude VAT. Full detail and the questions people ask on the pricing page.
What agencies ask before they connect an account.
Can it manage both Meta and Google Ads accounts?
Yes. Adspenta reads Meta and Google Ads accounts through the official APIs, runs the same checks on both, raises proposals for both, and live writes reach both. TikTok is built and waits on TikTok's approval of our app; nobody can connect a TikTok account until then.
Can it build new campaigns?
Yes, on Meta and on Google Ads, where every type Google lets a tool create can be built here: Search, Performance Max, Demand Gen, Shopping, Display and App. The campaign is planned in one place and checked before anything is created. Every campaign is created paused, so turning it on is the one step that starts delivery, and that step is approved and recorded like any other change.
Does it change budgets automatically?
Not unless your team tells it to. By default every change waits for a person, and nothing is sent without a recorded approval. An owner or admin can put one kind of change on one account on Act; from then on the system approves changes of that kind there itself, inside the same limits and take-back window, and records each one as approved by that rule. If those changes stop working, it steps itself back to asking first.
How is this different from Bïrch (formerly Revealbot) or Madgicx rules?
Rule-based tools do what you configured. You write a condition, it fires, it acts. That works well for the cases you already thought of, and it is silent on the ones you did not.
Adspenta runs its detectors against every account's own recent history, so a problem gets raised whether or not you wrote a rule for it, and it stops at a proposal unless you have put that kind of change on Act. You get the reasoning and the numbers on the card, then you decide.
How many ad accounts can one agency connect?
Up to 40 on the plan; if you run more, write to us before you start. A connected account is one ad account on one platform, so a client running both Meta and Google is two.
The price is per agency per month: 290 USD after a 14-day free trial. It is not a percentage of ad spend, and it does not change when a client's budget does.
Can a client see their own account without seeing the others?
Yes. A client login shows only that client's own accounts: the findings, changes, reports and any support thread about them. It cannot approve anything. It can stop changes to its own accounts with its own halt switch, and ask AI Chat a few questions a day about them.
The separation is enforced in the database itself. The security page explains it in full.
Proposals, not surprises.
Connect one account in dry run and watch it work for a week before anything is live. The first 14 days are free.
Free for 14 days, then 290 USD/month. Card required, cancel anytime.
MarkWrite to hello@adspenta.com. It reaches the people building Adspenta, not a ticket queue.