Every Automation Has a Bill Behind It: Keep a Register
An operations lead at a 40 person company inherited an automation platform. It had grown one workflow at a time for two years, and nobody had ever cleaned it up. When they finally made a list, it came to 23 credentials and 9 paid subscriptions behind it.
The workflows ran fine. The problem was the pile of accounts. Finance kept getting surprised by renewals for tools nobody remembered buying. Then the CFO asked which ones could be cancelled. "I couldn't answer for half of them."
Every business that has been automating for a while has a version of this. AI adds to it fast, because every agent and every connector brings its own key and its own bill.
How the pile builds
Each workflow starts as a sensible fix. Someone needs a scraper, an enrichment tool or an AI model, signs up on a card, and connects it. The workflow works, so nobody looks at it again.
Two years later the costs are spread across cards and invoices, the keys are shared between workflows, and the person who set up half of them has moved on. One builder described finding a tool that charged $50 a month to check whether email addresses still worked. Nobody had looked at its report in six months.
The same gap shows up outside automation. Owners describe business pages and domains set up on an employee's personal email, then lost when that person left. A manufacturer spent four months loading recipes into production software, then could not afford the next price rise and had no export ready.
What a register holds
The fix is boring and it works. One table, kept current, with a row for every tool, account and key the business runs on. Builders who had cleaned up the same mess agreed on the columns:
- what it does and which workflows use it - who owns it, by name - what it costs and when it renews - the last time it ran - how to get your data out
The owner column matters most. It is the first of our ten guardrails, named ownership, and the reason we argued in Every AI Tool Needs a Named Owner that rollouts drift without one. A tool with no owner has nobody to say whether it can go.
How to cut safely
Builders who had been through the cleanup shared a rule worth copying: "disable workflows, never credentials." Several workflows can share one key, so switching off a key breaks all of them at once. Switching off a workflow only quiets that one.
Disable anything without an owner or a recent run for two weeks before cancelling it. Watch who complains. One builder warned that a quarterly report can look dead for months and still matter, so check the next scheduled use before revoking anything. Then cancel the subscriptions, which is where the money is.
For new work, set one rule. Nothing gets connected unless it goes in the register first, with an owner and a company email behind it. The same discipline applies to agents, which need their own row and their own limits, as we set out in A Green Light Proves Nothing.
How to tell if you have the problem
Ask your finance lead for every software charge from the last year. Ask your operations lead for every tool the workflows call. If the two lists do not match, or nobody can say who owns half of either, you have the problem.
Who does this work
Keeping the register is part of fractional AI leadership. In the first month we put a named owner against every system in a register and make the build-versus-buy call for each capability. Then we review it monthly, so the CFO's question always has an answer. Where the same data feeds many tools, the Digital Brain wires it once into a layer you own, so tools can come and go without taking your data with them.