Marketing operations gets asked two questions about AI that most stacks cannot answer: what did we actually run, and what did it cost. When generation happens in personal chat windows, the honest answer is a shrug — there is no workspace record, no per-run cost, and no way to attribute output to a person or a campaign.
HeadshotMarketing treats an AI run the way it treats any other governed action. Executing a tool creates a record before the work starts, moves it through its lifecycle to completed or failed, and stores the input, the output, the token count derived from the actual text, the wall-clock duration, and the computed cost. A failed run is not discarded — it is stored with its error message and the time it burned. The tool's own usage counter increments on success, so a registry of tools doubles as a picture of what the team actually reaches for.
The console makes that ledger legible rather than burying it in a table. Three cards at the top show available tools, generations this month, and tokens this month — all derived from real execution rows scoped to the current calendar month, not a lifetime counter. Under the tool grid, a recent-generations feed shows each run's prompt and output with a relative timestamp, and every result can be copied or saved as a draft. The generation panel's footer reports the duration and token count of the run you just made, so the cost of a habit is visible at the moment you form it.
Because drafts saved from a generation carry an ai-generated tag plus the tool, provider, and model in their metadata, the trail does not end at the ledger. Months later it is still possible to ask which assets in the content library started as AI output and which run produced them.
The honest gap: metering and enforcement are not the same thing. Every run is measured, but the AI execution mutation does not yet carry a platform quota directive, so there is no gateway-enforced ceiling on AI spend the way there is on active campaigns, contacts, landing pages, and connected social accounts. Wiring AI generation into that same quota system — with a per-workspace budget and a hard stop — is committed work, not a shipped claim.
This is an illustrative pre-launch scenario, not a customer story.
Do it yourself
Watch AI usage accumulate as real, inspectable records: month-scoped generation and token counts, a per-run duration and cost, a full execution feed, and an ai-generated tag on everything that came out of it.
Open Content → AI Tools and read the three cards at the top: available tools, generations this month, and tokens this month.
You should see: Workspace AI usage for the current calendar month is visible immediately, derived from real execution records rather than a lifetime counter.
Ready to make this your story?
