Business process automation

Business process automation services that move routine work between your systems without retyping

We map one repeated process, then automate its routine steps and route the odd cases to a named person.

Scope your first workflow
Trusted by the world's fastest-growing brands

Where automation starts

Write the process down before any tool is switched on

Business process automation services begin with three questions about the work as it runs today: who touches each step, how many minutes it takes, and which cases need a person. Software comes after the answers.

Process inventorySampleSample Piedmont Supply Co.Charlotte, NCProcessRunsMinHoursVendor invoice approval4201284Order entry from email3001050New vendor setup12408Month-end sales report13606Total148

Map it

We follow one process from the first trigger to the last record: an invoice arriving, an order request, a new vendor. We write each step, the person who does it and the system it lives in. A step nobody can describe cannot be automated safely, so gaps in the map get settled with your team first.

Count it

We time the steps with the people who do them and multiply by how often the process runs. That gives hours a month for each process and a ranking. The workflow that eats the most hours goes first, and the price in the scope is set against the hours it can return.

Keep a person in it

Some cases need judgment: an invoice with no purchase order, an order for a product you stopped selling. We write the rule that sends those to a named person, with the facts already attached. The automation handles the routine cases and hands over the rest.

Two ways to automate

Start from the process, or start from a platform

Both routes end with software moving data between systems. They differ in what gets decided before the first flow is built, and in who is left holding the documentation.

Platform first, many flows at onceYou pick a tool, then buildProcess first, one workflow at a timeWe map, then build
First decisionWhich automation platform and plan to buyWhich process runs most often and costs the most hours
ScopeSeveral small flows built as ideas come upOne workflow, written down and priced
Odd casesFound as each flow runsRules send them to a named person with the details attached
Your timeLearning the tool on top of the normal workloadA few sessions to walk the steps, then approvals
What is left behindThe flows themselves, plus the builder’s notesProcess map, rule list, hours estimate and a run log
Which route fits?

A single repeated task between two apps suits a platform and an afternoon. A process that crosses email, an accounting system and three people’s inboxes repays the mapping, because the expensive mistakes sit in the handoffs.

What the sources say

Six published rules we design the automation around

Each comes from a tax agency’s guidance or a vendor’s own documentation, with the source and the date we read it underneath. They shape what an automation must store and how it should fail.

  1. RecordsRetention periods

    The IRS sets three years as the default period to keep business tax records, with longer periods in named cases.

    The IRS lists 6 years when more than 25% of gross income was left out and 7 years for a bad debt deduction or a worthless securities loss. An invoice workflow therefore keeps the original document and its approval trail where your bookkeeper can find them. Your accountant sets the exact period.

  2. Employment taxFour years

    The IRS says to keep employment tax records for at least 4 years after the tax is due or paid, whichever is later.

    Onboarding and payroll workflows create records of that kind: forms collected, dates, approvals. We store them in a folder structure your company controls, named by employee and year.

  3. Other usersBeyond tax

    The IRS tells businesses to keep records for non-tax purposes until they have checked what insurers, creditors or others need.

    A purchase approval log may matter to a lender, and a signed vendor agreement to an insurer. During the process map we ask who else relies on each document, so the automation keeps the copy and the trail those readers expect.

  4. Vendor forms$2,000 line

    The IRS instructions for Forms 1099-MISC and 1099-NEC say to enter nonemployee compensation of $2,000 or more for payments made in 2026 and later.

    A vendor-setup workflow can ask for the tax form when a vendor is added and total each vendor’s payments from the accounting system, so the list is ready for your accountant. We build the collection and the running total. The filing decision stays with your accountant.

  5. Failure handlingError workflow

    In n8n, a failed run can start a separate error workflow, and that workflow must begin with the Error Trigger node.

    The docs say one error workflow can serve several workflows, for example to send an alert by email or chat. The Stop and Error node lets a workflow fail on purpose when a result looks wrong. We use both so a bad invoice raises an alert.

  6. ReplaysTask usage

    Zapier can replay a failed run, and replaying an entire run counts the steps that already succeeded toward task usage again.

    Autoreplay is offered on the Professional, Team and Enterprise plans and does not replay safely halted runs. So we place the risky step, the one that writes to your books, behind a check, and size the plan with replays in mind.

The scope

What the automation work produces

Six parts of one automated workflow. Each is a piece of working setup in your accounts plus the document that explains it.

Process map · invoices4 exception typesInvoice arrivesVendor · Shared mailboxDuplicateMatched to the POBookkeeper · AccountingPO mismatchVendor checkedBookkeeper · Approved listNot listedApprovedBuyer, controller or owner · EmailBill enteredBookkeeper · Accounting

The process map

We walk the process with the people who run it and draw each step, its owner and its system. A distributor’s invoice path runs from the shared mailbox to the bill in the accounting system. You receive: a one-page process map with the odd cases marked.

Hours sheet · invoicesEstimate56hours a month returnedToday84 hAfter28 h336 clean × 2 min11.2 h84 exceptions × 12 min16.8 h

The hours sheet

We time each step and multiply by how often it runs, then estimate the hours the first workflow would return. That estimate sets the price. You receive: an hours sheet showing today’s hours, the estimate after automation and the working behind both.

Invoice workflowSwitched onEmail to the invoices mailboxTriggerSave the PDF, read the fieldsActionSend to the approverHandoffVendorAmountPO numberPDF

Triggers and handoffs

We build what starts the workflow and what each step passes along: an email arrives, a form is submitted, a record changes status. Each handoff carries the data the next person needs. You receive: a rule list naming each trigger, action and destination, switched on in your accounts.

Invoice fieldsTo a personPDFVendorVendor AOn the approved listInvoice numberINV-20418Not a duplicatePO numberPO-7731Found in accountingAmount$2,480.00PO total is $2,310.00Original kept in the Invoices folder

Reading and checking documents

Where a step starts from a PDF or an email, we set up the reading of fields such as vendor, amount and purchase order number, then check them against your records. You receive: a field list with the check applied to each one and a folder holding the originals.

Approval limits2 waitingBuyerUnder $1,000Controller$1,000 to $5,000OwnerOver $5,000Exception queueVendor A · $2,480.00ControllerAmount differs from the POVendor C · $7,150.00OwnerVendor not on the approved list

Approvals and exceptions

We write the approval limits as rules, such as who signs under $1,000 and who signs over $5,000. Cases that break a rule go to a named person with the details attached. You receive: an approval matrix and a queue of exceptions in the tool your team already opens.

Run logSample month420receivedApproved, no edits336Sent to a person84No matching PO41Amount differs29Vendor not listed9Duplicate number5

The run log and alerts

The workflow records what it did, what it sent to a person and why, and alerts a named person when a run fails. A shared sheet or table holds the record. You receive: the run log, the alert rules and a short guide to reading both.

How it runs

From process map to a workflow you can audit

Your sign-off comes first on the scope, then on each stage in turn, and each stage hands you a document for your files. The samples below follow a fictional distributor, Sample Piedmont Supply Co.

process-inventory.csv

Process inventory

Sample · Sample Piedmont Supply Co., Charlotte, NC
ProcessRuns a monthMinutes eachHours a month
Vendor invoice approval4201284
Order entry from email3001050
New vendor setup12408
Month-end sales report13606
Total148
Invoice approval takes 84 of the 148 hours, so it is the first workflow to scope. Minutes are the staff’s own estimates, checked against a sample of ten items.

Our stack

Tools that carry the data between systems

Each of these can move or read records for a workflow. We pick one for its job and build it in an account you own.

Zapier
Why Zapier

Zapier connects thousands of apps through short chains of triggers and actions.

How we use it

We use it for handoffs of a few steps, such as a new row in a sheet creating a task and sending a notice. You hold the account.

IntegrationsSpeedNo-code
ZapierYes
MakeYes
NativeSome
ManualNo

Questions

Business process automation services, answered

Start here

See the hours and the price for your first workflow

Tell us which process eats the most hours. The written scope that comes back carries the hours estimate and the price, and you read both before deciding.