# Business process automation services for operations teams

> Business process automation (BPA) replaces the manual hand-offs in a multi-step process, like client onboarding or purchase approvals, with rule-based workflows that move data between your tools. We map the process, automate it in n8n, Make, Zapier or Power Automate, and document every workflow. A first process takes 4 to 6 weeks and costs $5,000 to $12,000; larger programs run to $40,000.

- Page: https://methodcrew.com/services/business-process-automation
- Last updated: 2026-10-28
- Publisher: [The Method Crew](https://methodcrew.com/)
- Service: Business process automation
- Category: Automation

We take one process that crosses several tools and several people, such as onboarding a client or closing the month, and rebuild it so the hand-offs happen on their own. Rules first. A model only where rules run out.

## Key facts

- Price: $5,000 to $40,000 per project. A process audit plus the first automated process runs $5,000 to $12,000. Programs covering several processes run $15,000 to $40,000. Platform fees are paid by you directly.
- Timeline: 4 to 12 weeks
- Typical tools: n8n, Make, Zapier, Microsoft Power Automate, Airtable, Google Workspace, Microsoft 365, Slack, Postgres, Retool
- Change requests: $175 an hour, quoted in writing first
- Model and tool usage: billed to your own accounts at cost, no markup
- Ownership: code, workflows, prompts, accounts and data belong to you

## Who it is for

- COOs and operations managers at companies with 10 to 500 staff
- Finance teams closing the month with spreadsheets, email threads and manual reconciliations
- Service firms where onboarding one new client touches 5 or more tools
- Companies running dozens of Zaps or scenarios that nobody fully understands any more

## Signals you need it

- **The process lives in one person's head.** Onboarding, approvals or month-end only run smoothly when a particular person is in. Their vacation becomes everyone's backlog.
- **Status checks happen by message.** People ask in Slack or email whether something was sent, signed or paid, because no system shows it.
- **The same record is typed 3 times.** A new customer gets entered into the CRM, the billing tool and the project tracker by hand, with small differences each time.
- **Automations with no owner.** Zaps and scenarios were built by someone who has since left. When one fails, you find out from a customer.

## What we hand over

- **Current-state process map.** Every step, owner, tool and wait time in the process as it runs today, drawn from interviews and a sample of real cases, with the bottlenecks marked.
- **Ranked automation backlog.** The hand-offs worth automating, each with estimated hours saved per month, build cost and risk, so you can fund them in order.
- **Production workflows.** The automations in n8n, Make, Zapier or Power Automate on your accounts, each with error alerts, retries and a named owner.
- **Workflow register.** One table listing every automation: its trigger, the systems it touches, its owner and where its logs live. It is how you avoid a second generation of orphaned Zaps.
- **Runbook and handover training.** Plain-language steps for pausing, fixing and changing each workflow, and a training session for the staff who will own them.

## How the engagement runs

1. **Map** (1 to 2 weeks): We interview the people in the process, follow a few real cases from start to finish and measure the wait between steps. You get the current-state map, the ranked backlog and the confirmed scope for the first build.
2. **Prove** (1 week): We automate the riskiest hand-off first, usually the one touching the oldest system, and run it on live cases with a person checking every output. That shows early whether the APIs behave the way their documentation claims.
3. **Build** (2 to 8 weeks): We build the remaining workflows in order of value, with logging, alerts and exception paths for each. Every week ends with a demo on real data, and old and new run side by side for a week before go-live.
4. **Run** (Monthly, optional): On a care plan we monitor every run, fix failures before your team notices and work down the backlog. If you prefer to own it fully, we hand over the register and runbook and stay on call.

Every engagement follows [The Method](https://methodcrew.com/approach): Map, Prove, Build, Run.

## What is business process automation, and do you need it or AI automation?

Business process automation means rebuilding a multi-step process so data and tasks move between people and tools on their own, using rules. A signed proposal in PandaDoc creates the client in Xero, opens a project in Asana, adds a Slack channel and sends the welcome email. Nobody copies anything. Each step either happens automatically or lands in one person's queue with everything they need to act.

The work is mostly rules because most of a business process is predictable. The client name is the client name. An invoice over $10,000 needs a director's approval. A contract is signed or it is not.

A quick test for which service fits:

- Every input arrives in a structured form (fields, dropdowns, records) and every decision can be written as a condition. You need BPA.
- Some steps require reading free text or documents, such as working out what a customer email is asking for. You need BPA with 1 or 2 model steps, which is our [AI automation service](https://methodcrew.com/services/ai-automation).
- The process does not exist yet, or nobody agrees how it should run. You need a decision before any automation, and an [AI readiness audit](https://methodcrew.com/services/ai-readiness-audit) is the cheaper place to start.

We default to rules wherever they work. They cost less to run, behave the same way every time and are easier for your own team to change after handover.

## Which process should you automate first?

The one that scores best on 5 tests. The process behind the loudest complaint is often a poor first pick, because loud usually means contested.

| Test | Good sign | Warning sign |
|---|---|---|
| Volume | Runs 20 or more times a week | Runs a few times a quarter |
| Stability | Same steps for the last 6 months | Being redesigned |
| Rules | Decisions can be written as conditions | Depends on case-by-case judgment |
| Systems | Tools have documented APIs | Key data sits in a desktop app or on paper |
| Ownership | One manager owns the outcome | Three teams share it |

During Map we score each candidate from 1 to 5 on every test and weight the result by the hours it consumes each month. The top of that list is usually less glamorous than people expect: purchase order approvals, new-starter setup, chasing unsigned documents, moving a won deal into delivery. Those processes are frequent and well understood, which is exactly why they automate cleanly and pay back.

A process that scores well on everything except Systems is still a candidate. The build just costs more, because we may need a workaround such as a scheduled export, an email parser or, rarely, a screen bot. We would rather tell you that in week 1 than discover it in week 5.

## What is the difference between BPA and RPA?

BPA connects systems through their APIs and redesigns the process around them. Robotic process automation (RPA) uses software robots that click through screens the way a person would. Both have a place, and they fail in different ways.

| | BPA | RPA | AI automation |
|---|---|---|---|
| How it connects | APIs, webhooks, databases | Screen clicks and keystrokes | APIs plus a language model step |
| Typical tools | n8n, Make, Zapier, Power Automate | UiPath, Power Automate Desktop, Automation Anywhere | n8n or code calling OpenAI or Anthropic models |
| Breaks when | A vendor changes an API version | A button moves on screen | Inputs drift away from the test set |
| Best for | Modern cloud tools | Legacy desktop systems with no API | Email, documents, free text |
| Running cost | Low | Medium, often licensed per bot | Low to medium, usage-based |

We build BPA first and use RPA only when a system has no API and cannot be replaced soon: an old ERP, a government portal, a bank's desktop client. Screen bots need more maintenance because any interface update can stop them, so we price a care plan alongside any RPA work.

If you already run UiPath or Power Automate Desktop bots, we can audit them and replace the fragile ones with API integrations where the vendor now offers an API. That swap can also retire a bot license.

## What does business process automation cost, and what changes the price?

A process audit plus the first automated process costs $5,000 to $12,000 and takes 4 to 6 weeks. A program covering several linked processes, such as quote-to-cash or hire-to-onboard, costs $15,000 to $40,000 over 8 to 12 weeks. Both come as a fixed price, in writing, before work starts.

The price moves with:

- The number of systems. Each one adds authentication, field mapping and testing. Two cloud tools sit at the low end; 6, including an on-premise ERP, sit at the top.
- Exception paths. The happy path is a fraction of the work. Rejections, partial approvals, refunds and cancellations take the rest.
- Data quality. If customer records disagree between the CRM and the billing tool, someone has to decide which one wins, and sometimes the records need cleaning first.
- Audit needs. Finance processes often need a full log of who approved what and when.

You pay platform fees directly, on your own accounts. That usually means an n8n Cloud, Make or Zapier subscription, or a small server for self-hosted n8n. We size the plan to your volume so you are not paying for headroom you will never use. Changes after handover are billed by the hour, or come under a monthly [automation care plan](https://methodcrew.com/services/automation-care-plans).

## What happens when a workflow breaks, and what is not included?

Every workflow we build alerts a named person when it fails, with the record that caused it and a link to the log. In n8n that alert runs from an [error workflow](https://docs.n8n.io/flow-logic/error-handling/), which starts whenever another workflow's run fails. Temporary errors, like a rate limit or a timeout, retry on their own with growing waits. Permanent errors, like a missing required field, stop and wait for a person, so nothing ends up half-written into one system and missing from another. The runbook lists each alert and its fix.

Most failures start outside the workflow: a vendor changes an API, someone renames a CRM field, a password expires. We keep credentials in one place and check field names on every run, which turns silent breakage into a clear alert. Your team handles the common fixes after training.

Not included in a BPA project:

- Licenses for the automation platform or the business tools it connects.
- Replacing your core systems. If the CRM itself is the problem we will say so, but a migration is a separate project.
- Processes that need a policy decision first. We can run that conversation during Map. We cannot automate a disagreement.
- Customer-facing apps or portals. We do not build consumer apps.

If the process is mostly people reading documents and typing what they see, start with [intelligent document processing](https://methodcrew.com/services/intelligent-document-processing).

## What changes for your team

- Each step of onboarding, approvals or month-end starts as soon as the previous one finishes
- A record is entered once and copied to every system that needs it
- Managers can see where each case sits without asking anyone
- Every automation has a named owner, a log and an alert when it fails
- Process knowledge lives in a written runbook, so a vacation no longer stalls the work

## Tools we work with

n8n, Make, Zapier, Microsoft Power Automate, Airtable, Google Workspace, Microsoft 365, Slack, Postgres, Retool

## What it costs

$5,000 to $40,000 per project. A process audit plus the first automated process runs $5,000 to $12,000. Programs covering several processes run $15,000 to $40,000. Platform fees are paid by you directly.

- Change requests: $175 an hour, quoted before work starts
- Model and tool usage: billed at cost, no markup

All 20 price bands: https://methodcrew.com/pricing

## Blueprints that use this service

- [Weekly ops report automation](https://methodcrew.com/blueprints/weekly-ops-report): built in 3 to 6 weeks, $8,000 to $20,000 per project.
- [Invoice processing pipeline](https://methodcrew.com/blueprints/invoice-processing-pipeline): built in 6 to 9 weeks, $15,000 to $35,000 per project.

## Common questions

### What are examples of business processes that can be automated?

Client onboarding, purchase order approvals, new-starter setup, contract chasing, invoice approval routing, moving won deals into delivery and month-end checklists are the common ones. Each has a clear trigger, predictable steps and several tools involved. Our Map phase produces a ranked list of the candidates in your business, with hours saved and build cost for each, so you can fund them in order.

### Do we need to change our software to automate the business?

Usually not. Most cloud software has an API, so we automate around the tools you already use. We recommend a change only when a tool blocks the process, for example a spreadsheet acting as a database that 6 people edit at once. In that case we move the data into Airtable or Postgres and keep the views your team knows where we can.

### Which platform do you build on: n8n, Make, Zapier or Power Automate?

The one that fits your volume, your IT policies and whoever maintains it. Zapier is easiest for non-technical owners. Make handles branching logic well at lower cost. n8n can be self-hosted, which suits data-sensitive teams and high volumes. Power Automate makes sense if you run on Microsoft 365. The proposal states the reasoning, so the choice is on paper.

### How long does a business automation project take?

A first process takes 4 to 6 weeks: 1 to 2 weeks of mapping, a week proving the hardest hand-off, then 2 to 3 weeks of build and side-by-side running. A program covering several processes takes 8 to 12 weeks. The most common delay is waiting for system access, so we ask for it in week 1.

### Who owns the workflows when you are done?

You do. Everything runs on your accounts from day one: the automation platform, the credentials, the logs and any code. At handover you get the workflow register, the runbook and training for the people who will own each workflow. There is no license from us and nothing to switch off if you stop working with us.

### Can you fix automations someone else built?

Yes. We start with an inventory of every Zap, scenario or flow: what it touches, when it last ran and whether anyone still needs it. Some can be deleted, some need repair and a few should be rebuilt properly. The inventory is a short fixed-fee piece of work, and you keep the register even if you stop there.

### Is business process automation worth it for a company of 20 people?

It can be, if a process runs often enough. A 20-person agency onboarding 8 clients a month across 6 tools spends real hours copying and chasing. A first automated process at $5,000 to $12,000 has to win back enough of those hours within a year to make sense. We work that out in Map and say plainly if it does not.

## Related services

- [AI automation](https://methodcrew.com/services/ai-automation): Workflows where a language model reads and sorts, and your existing systems do the rest. $4,000 to $35,000 per project.
- [n8n, Make, Zapier and API integrations](https://methodcrew.com/services/workflow-integrations): Records moved between your CRM, inbox and finance tools without CSV exports. $1,500 to $20,000 per project.
- [Automation care plans](https://methodcrew.com/services/automation-care-plans): Monitoring, fixes and small changes for the automations you rely on. $1,500 to $6,000 per month.

## Further reading

### Guides

- [AI agents vs workflow automation vs chatbots: how to pick](https://methodcrew.com/insights/ai-agents-vs-automation-vs-chatbots)
- [n8n vs Make vs Zapier: choosing an automation platform in 2026](https://methodcrew.com/insights/n8n-vs-make-vs-zapier)

### Terms explained

- [Intelligent document processing (IDP)](https://methodcrew.com/glossary/intelligent-document-processing): Intelligent document processing uses OCR and AI models to read documents such as invoices, contracts and forms, extract the fields you need, check them and post them into your systems.

## Next step

Request a 30-minute scoping call: https://methodcrew.com/contact. Or email contact@methodcrew.com.