SERVICES

Four kinds of work, one underlying problem

Every project below comes from the same place: a business that grew, added a tool for each new problem, and ended up with systems that don’t speak to each other.

NEW BUILDS
MOST COMMON

Build the automation

A process runs on someone’s memory and copy-paste. I map it, scope it, and build the system that runs it instead — against your real data, not a demo account.

  • Zapier, Make and n8n builds, including multi-branch logic and routers
  • Google Apps Script for work no visual tool reaches
  • Custom Zapier apps built with the CLI or the Builder
  • Error handling and monitoring included, not quoted separately
CUSTOM API WORK
WHERE OTHERS STOP

Connect what has no connector

Most automation people stop where the native module stops. If your system has an API, I’ll connect to it directly — and if it doesn’t have one, I’ll tell you on the first call rather than three weeks in.

  • REST APIs with no existing module: Pylon, Fishbowl, Beds24, IsolarCloud, Drchrono, Acuity
  • Payloads that arrive in the wrong shape — JSON to CSV, nested arrays, undocumented formats
  • Pagination across thousands of records, rate limiting, retry logic
  • Fuzzy matching where the data doesn’t line up cleanly
RESCUE WORK
USUALLY URGENT

Fix what someone else left behind

An automation worked for three months, then quietly stopped. Nobody noticed until a customer complained. I find out why, fix it, and make sure the next failure announces itself.

  • Diagnosing silent failures and logic errors
  • Rebuilding fragile scenarios so they survive a field change
  • Adding the error handling that should have been there
  • Documenting what’s actually running, often for the first time
ONGOING
RETAINER

Keep it running

For businesses where automations are load-bearing. I watch what’s running, fix what breaks, and build the next thing as it comes up. Two of my current clients have been on this arrangement since 2023.

  • Monitoring, with failures flagged rather than found later
  • Fixes when a platform changes something underneath you
  • New builds as the business changes
  • Priority response
WAYS TO WORK

Three ways to start

Every engagement is scoped against one number worth moving. No open-ended hourly billing unless you specifically want it.

Automation audit

$250
one-off, delivered in a week

I map your current process, identify what’s worth automating and what isn’t, and give you a costed plan you can take anywhere — including to someone else.

  • Full process map
  • Prioritised opportunity list
  • Costed build plan

Fixed-scope build

From $600
priced per project, not per hour

One workflow, scoped and priced up front. You know the cost before anything starts, and it doesn’t change if it takes me longer than I expected.

  • Fixed price, fixed scope
  • Error handling and monitoring
  • Documentation and handover
  • 30 days of support after launch

Monthly retainer

From $900/mo
for teams running on automation

For businesses where a broken automation means a broken day. Monitoring, fixes and new builds, with priority response.

  • Monitoring and fixes
  • Ongoing new builds
  • Priority response

What’s the slowest thing your team does every week?

Send me one paragraph describing it. I’ll tell you what it would take to automate — or tell you honestly that it isn’t worth it.

Book a 30-minute call