Skip to content

[Service 004]

Business process automation

Removing the step someone repeats every day (the copy, the paste, the export, the Friday report) and making the system do it, with failures that page a human instead of passing quietly.

Typical timeline
3–6 weeks
Engagement
Project or retainer
Where
Los Angeles + remote

[You probably need this if]

  • 01Someone spends part of every day copying data from one tool into another
  • 02A weekly report is assembled by hand from exports
  • 03Mistakes are found by customers rather than by the system
  • 04Your Zapier or Make bill has become a line item people ask about

[What you get]

  • Process audit and cost estimate
  • Automation build
  • Monitoring and alerting
  • Runbook and handover

[What it looks like]

Before → after

  • Orders re-keyed into the fulfilment system every morning

    Orders flow in automatically; only exceptions need a person

  • Invoices typed into QuickBooks from emailed PDFs

    PDFs read, matched to the vendor and drafted for approval

  • Monday report built from five exports

    Report published on schedule, refusing to send if the data looks wrong

[Common tools on these projects]

Integrates with

All integrations →
  • Shopify
  • QuickBooks
  • Google Sheets
  • SlackSlack
  • Gmail
  • Zapier
  • Make

[What happens after you email]

How it works

  1. 0130 min, free

    Call

    You describe what is slow. I ask where the time actually goes. If I am not the right fit, I say so on the call.

  2. 021–2 weeks

    Audit

    I map how the business runs, the tools and the manual steps between them, and put a time and dollar cost on each. You get a written plan whether or not we continue.

  3. 033–12 weeks

    Build

    Fixed scope, weekly updates, working software early. You see it running on your own data before it is finished.

  4. 04Ongoing, optional

    Hand over

    Documentation, a recorded walkthrough, and access to everything. Retainer support if you want it; not required.

[Process automation]

Questions

What should I automate first?

The step with the highest hours multiplied by frequency, that follows a rule someone could write down. If the rule needs judgement every time, it is a tool problem, not an automation problem.

What happens when an automation fails?

It stops and tells someone in Slack, email or a queue, with enough context to fix it. Silent failure is the most expensive kind, so it is designed out from the start.

Will my team need to learn new software?

Usually not. The best automation is invisible: the work simply stops arriving. Where a person needs to approve something, it shows up in a tool they already use.

[Further reading]

Automation2 min read

What your manual work is really costing you

A simple way to put a dollar figure on the copying, pasting and re-typing your team does every week, and how to decide what to automate first.

Integrations2 min read

Zapier vs a custom integration: when to switch

No-code automation is the right answer surprisingly often. Here are the specific signs that you have outgrown it, and what a custom integration actually changes.

Tell me what is slow.

A 30-minute call, no charge. You will leave with a clearer picture of the problem whether or not we work together.

Booking projects for Q4 2026