Book a call

Automations · from $1,500

Stop doing the same job by hand.

I connect your apps in Make or Zapier so repetitive work runs without you copying information between them. From $1,500 CAD, including testing, error handling and a documented handover.

The photooff a phoneThe flowMAKE · 9 STEPSPostedinstagramThe branded cardrendered
  1. The photooff a phone
    Waiting
  2. The flowMAKE · 9 STEPS
    Waiting
  3. The branded cardrendered
    Waiting
  4. Postedinstagram
    Waiting

Swipe the diagram →

Idle. Waiting on the next photo.
$1,500CAD, where a flow starts
4in every build · testing, errors, docs, handover
2platforms · Make or Zapier
1account it lives in · yours

Built to keep running

An automation that fails silently just gives you another job to check. I build in retries and alerts so you know when something needs attention. That work, and the documentation to hand it over, are part of the quote.

Proof

DomCast used to post to Instagram by hand.

DomCast Metals is a casting shop in Windsor, Ontario, running since 1938. Somebody there used to photograph a finished part, crop it, drop it into a template, write the caption, and post it. Now a flow does all of that. Nobody opens the app.

Before

Photo off a phone, cropped by hand, dropped into a template, captioned, posted. Ten or fifteen minutes, whenever somebody remembered.

After

The flow preps the photo, renders the branded card, and posts it. Somebody approves the caption and that's the whole job.

The heavier one runs inside their shipment system.

Runningdomcast metalsThe log it writes while it runs.
domcast · shipmentsThe DomCast shipment management dashboard I built, showing shipment stats and recent orders
run logpacking slip → bill of lading
A packing slip gets scanned, OCR reads it, and the Bill of Lading writes itself instead of somebody retyping it. That one is too big to live in Make, so it got built into the system DomCast opens every morning. This screen is a recreation and the numbers on it are made up. The DomCast case study has the rest of that build. Click through the demo →

What's included

What a build includes.

Every automation I quote ships with all four. A flow with no error handling isn't finished, it works until something upstream changes and then it stops without telling anyone.

  1. Testing

    01 / 04

    I run the flow against your real data before it touches anything live, including the rows that break things.

  2. Error handling

    02 / 04

    Retries where a retry makes sense, and an alert to both of us when it stops running, so you hear about it the same day.

  3. Documentation

    03 / 04

    A plain page that says what runs, when, what it touches, and what to check first if it stops.

  4. Handover

    04 / 04

    The scenario lives in your Make or Zapier account under your login. You own it and you can hand it to anyone.

The money

What it costs.

Automations start at $1,500 CAD. I quote it fixed before I start, you pay 50% up front, 25% at the halfway point, and 25% once it's running, and changes after that are hourly. Most single flows land at the from-price. What pushes it up is how many apps are in the chain and whether one of them has a bad API.

the job you redoONE FLOWfrom $1,500it runs itselfapps in the chaina bad API
  1. the job you redo
  2. ONE FLOWfrom $1,500
  3. it runs itself
$1,500, where it startsmost single flows land here
50%up front
25%at the halfway point
25%once it's running

It's also the cheapest way to find out what working with me is like. $1,500 and a couple of weeks tells you how I scope a job and how I write it down, before you hand me anything bigger. The rest of the model is on the pricing page.

When the automation outgrows Make.

There's a point where a flow stops being enough. You want a screen somebody can look at, roles, and a record of who changed what. Make can be bent into that and it turns into something nobody can hand over. That's the point where it becomes a system, and those start at $7,500.

Straight answers

Common questions.

  • 01

    Can't I build this myself in Make?

    Maybe, and I'll tell you on the call if you can. A lot of what people ask me about is two modules and an afternoon, and I'd rather say that than take $1,500 for it. My Make.com consultant page lays out where the line sits.

    "I'd rather say that than take $1,500 for it"

    the short answer
  • 02

    Is $1,500 worth it for one automation?

    Work out how long the job takes and how often you do it. If it's twenty minutes a month it's not worth $1,500. If it's a couple of hours every week and has been for a year, it probably is. I'm not going to make up an ROI number for you.

    "I'm not going to make up an ROI number for you"

    the short answer
  • 03

    What if it breaks at 2am?

    You get an alert and so do I, because that's in every build. APIs change and accounts get disconnected, so flows break eventually. Fixes are billed hourly, the documentation says what to check first, and you have my email, cole@flxw.ca.

    "You get an alert and so do I"

    the short answer

Start here

What are you doing by hand?

Free, 30 minutes. Tell me the job you keep doing by hand, how long it takes and how often you do it, and you leave with a scope and a fixed price in writing.

Book a call

Or email cole@flxw.ca with the steps you repeat every week and the apps they run through.