Agentic Back Office Series #8: Approval Design and Delegation Depth

The lazy debate is whether humans should be in the loop. Back-office work needs a better vocabulary. Some decisions deserve pre-approval. Some deserve post-review. Some deserve sampling. Some can run under thresholds. Some should stop at a recommendation. Some should never be delegated because the consequence is too sensitive or

Agentic Back Office Series #7: System-of-Record Discipline for Agentic Operations

The risk in agentic back office is that agents will be useful in the wrong place. They will reconcile and coordinate just well enough that teams trust the agent workspace more than the systems of record. This creates a shadow operating layer. Back-office functions already struggle with truth. Vendor data

Agentic Back Office Series #6: Compliance Evidence and Admin Workflows

Compliance work is a strong agentic back-office candidate because much of it is recurring evidence work. The company needs proof that controls exist, access is reviewed, vendors are assessed, policies are acknowledged, incidents are handled, logs are retained, and exceptions are documented. The work is repetitive, detail-heavy, and expensive when

Agentic Back Office Series #5: People Ops Without Policy Chaos

People ops is the place to be most careful. Finance mistakes create reconciliation work. Procurement mistakes create spend and vendor risk. Legal mistakes create obligations. HR mistakes can affect trust, fairness, privacy, employment outcomes, and a person's relationship with the company. The agentic back office must not treat

Agentic Back Office Series #4: Legal Ops and Contract Playbooks

Legal ops is not just a support function for lawyers. It is the system that determines how legal work enters, gets classified, gathers facts, follows playbooks, routes exceptions, and turns into a signed obligation. That makes it one of the highest-leverage agentic back-office candidates. The contract intake moment is usually

Agentic Back Office Series #3: Procurement Intake and Vendor Governance

Procurement begins badly in many companies because intake is messy. Someone wants to buy a tool, renew a vendor, add seats, sign a statement of work, or bypass a slow process. The request arrives with half the information procurement, security, finance, legal, and the budget owner need. Then the real

Agentic Back Office Series #2: Finance Ops as the First Killer Use Case

Finance is the best place to start because the work already has a language of evidence. Approvals, invoices, purchase orders, vendors, budgets, entities, journal entries, close tasks, collections, revenue recognition, accruals, and reimbursement policies all depend on records that must reconcile. The team is not just answering requests. It is

Agentic Back Office Series #1: The Back Office Moves From Ticket Queues to Operational Loops

Back-office teams are buried in requests. A vendor needs review. A manager needs an HR answer. Finance needs context for an invoice exception. Legal needs to know whether a contract clause is standard. Compliance needs proof that a control ran. None of this looks strategic from the outside, but it
You've successfully subscribed to Antoine Buteau
Great! Next, complete checkout to get full access to all premium content.
Welcome back! You've successfully signed in.
Unable to sign you in. Please try again.
Success! Your account is fully activated, you now have access to all content.
Error! Stripe checkout failed.
Success! Your billing info is updated.
Error! Billing info update failed.