What happened overnight?
This is an illustrative scenario, not a customer account. The people and the company are invented; every event in it maps to a real mechanism on ftes.ai, named as it happens.
The company is an online retailer with a growth lead and an outside media buyer on a reduced retainer. The Performance Ads FTE, connected to the ad account with a dedicated account whose spending permission is capped at the platform, monitored the live campaigns against the caps and the success criteria in each campaign's brief. Two campaigns diverged: one is well inside its criteria, one is not. The FTE proposed moving part of the underperforming campaign's remaining budget to the other, within the overall cap, with the evidence attached. It also finished the brief for a new campaign the lead outlined last week, from the campaign brief template, and queued the launch for approval.
It changed nothing. Budget shifts and launches are on the Asks list at every autonomy level.
What does the growth lead see?
The morning brief, first person: spend against the cap, the proposed shift with its evidence, the launch waiting, the campaigns' status against their briefs, and the role's own token spend, which is separate from the ad spend and small beside it. The lead reads the shift proposal: the performance data for both campaigns over the period, the criteria from the briefs, and the amount proposed, which stays inside the cap. The lead approves it, and the FTE makes the change in the ad platform through its scoped account, logged.
The lead also reads the attribution section, which shows two figures: what the ad platform claims and what the analytics tool records, side by side, with the note that neither is the truth and the platform does not blend them.
How does the launch approval go?
The launch brief in the Approvals tab follows the template: objective, audience, creative from the approved set, budget with its cap, dates, success criteria the FTE will report against, and what it will do if the criteria are missed, which is propose a pause rather than pause. The lead reads it against the seasonal plan, sends it back once because the audience overlaps a campaign the media buyer is running, a rules reason that will add a line to the remit about the buyer's campaigns, and approves the revised brief an hour later. The FTE launches the campaign through the platform within the cap and logs it.
The guardrails piece in the library lists what the FTE can and cannot do in an ad account; the launch is the clearest example of gated.
- Shift: proposed with evidence, approved inside the cap, made through the platform
- Launch: brief from the template, sent back once, approved, launched within the cap
- Never: raising a cap, launching unapproved, blending attribution
What about the media buyer?
The buyer's retainer now covers the campaigns that need craft: the seasonal creative concept and the audience strategy. The buyer reads the FTE's daily report in the workspace as a viewer, sees the two attribution figures rather than one, and uses the FTE's monitoring to spend their hours on the creative rather than on checking spend. The remit line the send-back added means the FTE will flag audience overlap with the buyer's campaigns before proposing a launch. The buyer and the FTE are not competing; the FTE runs the daily loop the buyer never wanted to.
The comparison of a media buyer FTE with an agency in the library sets out the division.
What does the lead do with the afternoon?
Reads the Performance tab: spend against caps per campaign, results against each brief's criteria, the days the account was actually touched, the dual attribution, and the unmeasured list, which states that incrementality is not measured because no holdout was run. Decides to run a holdout next quarter so that the question can be answered honestly. Reads the FTE's proposed missions for the seasonal push and approves one as an objective with a target subset, a deadline, and progress tracking, rather than as a separate campaign primitive.
Then does the work only a person does: negotiates the seasonal creative budget with the finance lead, using the record.
What does the record show at the end of the day?
The audit trail: the shift proposal, its evidence, the approval, the change in the platform; the launch brief, the send-back with its reason, the approval, the launch; the attribution report with both sources; the objective approved. The Performance tab: everything against the caps and the briefs. At the monthly review the lead will read results against each brief's criteria, the cost of the role's tokens separate from the ad spend, and decide whether any class, probably budget shifts under a threshold, has earned the Promotion Standard's consideration. Launches never will.
The library's piece on how a Performance Ads FTE works describes each mechanism outside the story; the campaign brief template is the one the launch followed.