custom automations

The thing you do every week stops needing you.

If you do it more than once a week and it follows rules, it can probably be automated. Below is what we have actually built. It is a starting point, not a catalogue, so the more useful move is to tell us the part of your week you resent and let us tell you honestly whether it is worth automating.

01 · paperwork

The documents that have to happen and that nobody wants to be the one doing.

  • Invoices raised and sent without anyone opening a template
  • Quotes and proposals generated the moment a form comes in
  • A contract or PDF turned into a plain summary with the dates that matter pulled out
  • Forms built, and what people put in them landing where you actually look
  • Documents filed and named correctly the second they arrive
02 · time

The things that go wrong quietly because a date passed and nobody was watching.

  • A schedule emailed to you, read, and put on your calendar without you touching it
  • Renewals, expiries and logins that warn you before they lapse instead of after
  • Booking and availability kept in sync across the tools that disagree with each other
  • Recurring work that starts itself instead of waiting to be remembered
03 · customers

The follow-through that happens on your good weeks and slides on your busy ones.

  • Outreach that finds who fits, researches them, and drafts the first message
  • Follow-up that keeps going after the first no reply
  • Review requests that go out after a job closes, at the moment people actually answer
  • Onboarding that creates the folders, accounts and kickoff docs on signature
04 · information

The answers that exist already, just not anywhere you can reach quickly.

  • Reporting that builds and sends itself on a schedule
  • Weekly numbers pulled out of several tools into one place, without anyone assembling them
  • Meeting notes turned into action items and follow-up drafts before you leave the call
  • Inbox and message routing, so the right thing reaches the right person
  • Data moved between two tools that were never going to integrate
the big one

One place you talk to, instead of nine you check.

The version of this we get asked about most is not one automation, it is the layer above them. Everything you run reports into one or two channels you already have open, and you give it instructions the same way you would text a person, in a sentence, without opening anything.

We run one. Adam texts a sentence about a shift he just picked up, and his calendar and the booking availability on this website both update, with a confirmation step in between so nothing gets written that he did not agree to. It is the same pattern underneath, pointed at whatever your business actually runs on.

It’s all running. How do you know it’s working?

Everything on this page runs out of sight, which is the point and also the problem, so the next door is the one that puts it on a screen. Builds are priced on the call, because the cost is almost entirely how tangled the system we are plugging into is. Keeping them alive afterwards is from $1,000/mo, and it is not optional, since an automation nobody maintains is one that stops quietly and lets you find out from the thing that did not happen.