Short answer: Your ERP, CRM and accounting system aren't going anywhere. What changes is who sits in front of them. The copying, checking and re-keying moves to AI agents that work through the system directly, and your people spend their time approving the exceptions. The system matters more than ever; your team just opens it less.
This is for owners of Canadian companies with 50 to 500 people who keep hearing that AI will make their software obsolete, and wonder whether to hold off on the next upgrade.
Isn't AI supposed to replace business software?
For most of this year the market story was a "SaaS apocalypse": AI agents would do the work, so nobody would need the software. Robin Brohl, who spent years at Constellation Software, put the better reading in one line: "SaaS doesn't disappear. It disappears into the workflow."
His point is that software shifts from an application people open to a capability other things call. Screens give way to APIs. People stop typing commands and start overseeing.
The system of record survives because it holds the truth: the customer list, the inventory count, the general ledger. An agent needs one authoritative place to read from and write to. Rebuilding that place is the expensive, risky part of any software change, and AI does nothing to make it cheaper.
What does "headless" mean for my business?
Headless means the system keeps running and keeps the records, but nobody has to open a screen for routine work. The agent works through the system's API. People open it for exceptions and for reports.
| The work | Today | With agents |
|---|---|---|
| Customer order by email | Someone re-keys it into the ERP | The agent enters it and flags anything odd |
| Supplier invoice | Matched to the PO by hand | The agent matches it; a person approves the mismatches |
| Month-end | Reconciliation takes days | The agent reconciles daily; a person reviews the breaks |
| Quote | Pulled together from three screens | The agent drafts it; the salesperson approves |
The person's job moves from doing the entry to deciding the exceptions. That is a better use of someone who knows your customers and suppliers.
What should I do now?
- Keep your system of record, and keep it in charge. Don't buy a new app to sit beside it. If your team needs a screen, it should be a report inside the system they already use.
- Give agents their own access, and log everything. An agent gets its own login with only the permissions it needs. Every change it makes is recorded where your controller can see it.
- Design the approval step with care. This is where most projects go wrong. People either approve everything without reading, or give up and go back to doing it by hand. When Anthropic studied its own coding tool, users approved about 93% of permission prompts, and paid less attention as the prompts piled up. So ask people to approve exceptions, not every entry. Show the reason and the source document. Keep the volume low enough that someone actually reads.
- Ask your vendor what agent access will cost. Some vendors now charge separately when agents use the API, and the limits can be tight. SaaStr was quoted up to $240,000 a year for agent access to one system, and another vendor's API limits cut their agent off after 10 to 20 minutes a day. Before you build, ask three questions: what are the API limits, what does a call cost, and does an agent need a paid seat?
One more thing for your next renewal: most business software is priced per seat. As fewer people log in and more work runs through the API, expect vendors to move toward usage or outcome pricing. Negotiate with that in mind.
How do we build agents this way?
This is how we work, written down in the Agent Forge Way:
- We work inside your system of record. You never log into anything of ours (rule 09).
- Agents update your system directly, with permissions you control, and every update is logged (rule 04).
- Each agent runs in shadow first, then handles exceptions, then goes live (rule 06).
- Approvals come through the channels your team already uses, like email or Teams (rule 07).
If one workflow in your business runs through one or two people and holds everything else up, book a 30-minute call. No deck, just the work that piles up.