← The BriefTeamwork
The budget change nobody approved
AI can spot a budget shift in seconds. The hard part is deciding who signs off, what they see and how to undo it. Here is the approval setup we recommend.
Most teams don’t lose money because an AI made a bad call. They lose it because a good call went live without anyone owning it, and afterwards nobody can say who moved the budget, or why.
AdsOS is built around one rule: Friday AI can analyse, suggest and draft, but a person approves every change before anything reaches Meta, Google Ads or TikTok. That rule only works if approving is fast. This is the setup we recommend.
Three kinds of budget change
- Shift Move spend between campaigns that share a goal. Small, frequent and easy to reverse, so one editor can approve it.
- Scale Raise a daily budget beyond the plan. On Business and Agency plans, ask for a second approver.
- Pause Stop delivery on a campaign that is burning spend. Approve it quickly, then review the reason the next morning.
What the approver should see
An approval is only as good as the context behind it. Every suggestion in AdsOS shows the rule that fired, the two weeks of results it read and the exact campaign version under review. If someone edits the campaign after that, the approval no longer applies.
“Approve the version you reviewed, not the one that changed while you were at lunch.”
AdsOS product team
Who approves what
| Change | Approved by | Undo window |
|---|---|---|
| Shift between campaigns | One editor | 7 days |
| Raise a daily budget | Editor + second approver | 7 days |
| Pause delivery | One editor | 7 days |
If a platform refuses partway through, AdsOS rolls the change back instead of leaving half of it live. Every decision lands in the activity log with the person, the time and the change, and each applied change is measured a week later, so the next approval starts from evidence.
AdsOS Team
The people building AdsOS: product, engineering and the specialists who help teams launch their first approved campaigns.
