Back to BlogWorkflow Integration

How Office Teams at Growing Companies Automate Approvals Across Email, Slack, and ERP Systems

BB
BrightBots
··6 min read

Every growing company hits the same wall. You've got purchase requests piling up in someone's inbox, expense approvals getting lost in Slack threads, and a finance team manually rekeying approved data into your ERP system. What started as a manageable process when you had 20 people becomes a genuine operational bottleneck at 60. According to research from McKinsey, knowledge workers spend an average of 19% of their working week just searching for information and chasing approvals — that's nearly one full day, every week, per person. The good news is that AI automation can now sit between your existing tools and handle the entire approval workflow for you, without anyone needing to rebuild your systems from scratch.

Why Approval Workflows Break Down as You Scale

The root problem isn't that your team is disorganised — it's that your tools weren't designed to talk to each other. Someone submits a purchase request via email. A manager approves it verbally in Slack. Finance then waits for a formal confirmation before updating the ERP. At every handoff, there's an opportunity for delay, confusion, or a dropped ball.

The manual glue work between these systems is surprisingly costly. A mid-sized consultancy with 75 staff, processing roughly 200 approval requests per month, can easily spend 40 hours of collective staff time just routing, chasing, and reconciling those requests. At an average blended cost of £40 per hour, that's £1,600 a month — or nearly £20,000 a year — in pure administrative overhead. And that figure doesn't account for the delayed purchases that slow down project delivery, or the frustrated employees who chase approvals three times before giving up.

The frustration compounds because each tool does its job in isolation. Your ERP holds the financial truth. Your email holds the paper trail. Your Slack holds the actual conversation where decisions get made. None of them update each other automatically, so your team becomes the integration layer — and humans are expensive, inconsistent integrations.

What an AI Automation Layer Actually Does

An AI automation layer — sometimes called an AI agent or workflow orchestrator — sits between your existing tools without replacing them. Think of it as a smart coordinator that watches for triggers, routes information to the right people, collects responses, and updates your systems automatically.

Here's what a modern approval workflow looks like when it's automated. An employee submits a purchase request through a simple form or even a Slack message. The AI agent immediately checks the request against predefined rules: is it under the budget threshold for auto-approval? Does it require one sign-off or two? It then routes the request to the correct approver — via Slack, email, or both — with a single-click approve or reject button. Once a decision is made, the agent logs the outcome in your ERP, notifies the requester, and archives the thread. The entire loop closes in minutes rather than days.

Crucially, the AI agent also handles exceptions intelligently. If an approver hasn't responded within 24 hours, it sends an automated nudge. If a request falls outside the usual parameters, it escalates automatically to a senior stakeholder. Nothing falls through the cracks because the system — not a person — is responsible for following up.

Tools like Make (formerly Integromat), Zapier, and more advanced platforms like Workato or Tray.io can build these workflows without any coding. They connect to most major ERPs (SAP, NetSuite, Xero), communication tools (Slack, Microsoft Teams, Gmail, Outlook), and form tools (Typeform, Google Forms, Jotform) out of the box.

A Real Example: How a UK-Based Marketing Agency Cut Approval Time by 80%

Archer & Field, a 55-person integrated marketing agency in Manchester, was struggling with a purchase approval process that averaged 3.2 days end-to-end. Project managers were cc'ing finance on email chains, approvals were being given verbally in Slack with no audit trail, and the accounts team was spending six hours every Friday manually updating NetSuite with approved POs.

They worked with an automation agency to build a connected workflow using Make, Slack, and NetSuite. The new process works like this: a project manager submits a purchase request through a short Typeform linked in Slack. The automation checks the amount — anything under £500 is auto-approved and logged to NetSuite instantly. Anything above routes to the department head via a Slack message with embedded approve/reject buttons. Once approved, the automation creates the PO in NetSuite, emails the supplier, and posts a confirmation in the project's Slack channel.

The results within 60 days were significant. Average approval time dropped from 3.2 days to under 14 hours. The Friday manual reconciliation session was eliminated entirely, saving the accounts team six hours a week. Error rates on PO data entry dropped to near zero because humans were no longer rekeying information. Across the year, the agency estimated they recovered roughly £28,000 in staff time previously consumed by approval admin.

How to Get Started Without Overhauling Your Systems

The biggest misconception about workflow automation is that it requires an IT project. It doesn't. You can automate your approval workflow in stages, starting with the highest-friction process and expanding from there.

Start with a single workflow. Pick the approval process that causes the most pain — expense requests, purchase orders, content sign-offs, or client proposals. Map out every step on a whiteboard, including who needs to approve, under what conditions, and what happens after. You'll quickly see where the delays live.

Identify your trigger and your destination. Every automated workflow has a starting point (someone submits a form, sends an email, posts in Slack) and an end point (a record is updated in your ERP, a notification is sent, a document is filed). If you can describe those two points clearly, an automation platform can connect them.

Choose a platform that matches your tools. If your team lives in Microsoft Teams and uses Dynamics 365, Microsoft Power Automate is the natural fit. If you're a Slack-first organisation using Xero or NetSuite, Make or Zapier will connect cleanly. Most platforms offer pre-built templates for common approval workflows, meaning you're not starting from scratch.

Build in an audit trail from day one. One of the biggest wins of automated approvals isn't just speed — it's visibility. Every request, decision, and timestamp gets logged automatically. When your auditors ask for a record of all approved POs over £5,000 in Q3, you can produce it in seconds rather than hours.

Expect the initial setup of a single workflow to take one to two weeks. After that, adding new workflows becomes significantly faster because the integrations are already in place.

Conclusion

The gap between a manual approval process and an automated one isn't measured just in time — it's measured in decisions that got delayed, projects that slipped, and talented people spending their Friday afternoons chasing paper trails. For growing companies, automating the glue work between email, Slack, and your ERP is one of the highest-return operational improvements available. You don't need to rebuild your tech stack or hire a developer. You need to connect what you already have, add a smart layer between them, and let the system do the chasing.

Want to automate your business?

We build custom AI agents and maintain them for you. Get a free audit to see exactly where automation can help.

Get Your Free AI Audit