GeekThangs Start a Project
Automations

We do the same thing by hand every week.

Somebody on your team spends hours every week on a job that never changes.

  • The repeat job runs on its own, in the background
  • Your team keeps the judgment. The copying and chasing stops
  • It tells you when it runs, and loudly when it does not
Get a Free Analysis See an Example
A tradesperson in a workshop, checking a laptop between jobs
A close-up of hands typing into a spreadsheet on a laptop

Nobody chose these jobs. They just accreted.

Every business accumulates these. Copying the same figures from one place into another, sending the same reminder, rebuilding the same list, updating a schedule in three places because three places have to agree.

They are rarely on anyone's job description. Someone absorbed them, and now the business quietly spends a person's afternoon on them every week.

The useful question is which one costs the most and breaks the least when a machine does it.

A calendar that used to be built by hand.

A yoga studio we build for still prints a class calendar for the wall every month. Somebody used to rebuild it by hand in a document editor. Now the schedule lives in one place, and the month sheet, the week cards and the website all come out of it.

  • Before The month was rebuilt by hand in a document editor. Text overlapped its own boxes, the legend drifted, and a class that changed had to be found and fixed in every place it appeared.
  • After One schedule file. It makes the printable month, a card for each week, and the listings on the website, so the wall and the site cannot say different things.
  • What it costs to run Nothing, and no one has to remember. Next month's sheet is generated from the same file the moment the schedule changes.

See the Calendar Automation, With a Sample You Can Run

The shape of the ones we get asked for.

Automations run inside your own accounts, so unlike a website there is no address to send you to. Sketched out instead: what starts it, what runs, and what you get back.

  1. A quote request comes in
    1. Reads what they asked for
    2. Prices it off your list
    3. Writes the quote
    It is in their inbox, and logged in yours
  2. A client says yes
    1. Makes the folder
    2. Raises the invoice
    3. Sends the welcome note
    The job is open and nobody typed the same name four times
  3. The month ends
    1. Pulls the numbers
    2. Builds the report
    3. Checks it against last month
    It is waiting for you on the first, already written

Yours would be built from your own tools and your own handoffs.

Why the boring middle should not be a person's job

The judgment in these jobs is real, and it stays with your team. What does not need a person is the copying, the reminding, and the keeping-things-in-sync.

Take that part away and the work still happens. Nobody has to hold it in their head, and nobody's afternoon disappears into it.

  • The repeat job, handled

    Intake, quoting, follow-up, the report you rebuild every month. The parts of the week that run the same way twice.

  • Wired into what you use

    It plugs into the tools you already have rather than replacing them, so nothing new has to be learned.

  • Loud when it fails

    Something that silently stops is worse than something you do by hand. It tells you when it did not run, and it tells us.

  • You keep the override

    Every rule is yours to change or switch off. Nothing goes out under your name without a rule you set.

Ready to hand off the job you do every week?

Get a Free Analysis

What comes with an automation

  • The handoffs that eat the week

    Intake, quoting, follow-up, the monthly report. We start with the biggest one, so the difference shows in the first week.

  • Built on your tools

    Wired into what you already use, not a new platform to migrate to and learn.

  • It reports itself

    It tells you when it ran, and it tells you loudly when it did not, so nothing fails in silence.

  • Written down in plain words

    What it does is written in plain language, so the next person can read it and nothing lives only in one head.

From bottleneck to background

Four steps, from a job done by hand to one that runs on its own.

We time one real week

Not what the process is supposed to be. What actually happens, and how many minutes each handoff costs.

A monthly report open on a laptop and a second monitor, generated automatically

Why hand it to GeekThangs

The judgment stays yours

We automate the copying and the chasing, never the decisions your team makes.

You approve it until you trust it

It drafts, you send, and nothing goes out unwatched on day one.

Nothing fails in silence

It tells you when it did not run, and it tells us too.

We start where it hurts

The biggest, most repetitive handoff goes first, so the difference shows in the first week.

Written for the next person

What it does is in plain language, so it never lives only in one person's head.

Questions worth asking first

What should we automate first?

The job that costs the most time and breaks the least when a machine does it. We time one real week to find it rather than guessing.

Will it replace anyone?

It replaces the copying and the chasing, not the judgment. Your team keeps the decisions. The typing stops being their job.

What if it breaks?

It tells you when it did not run, and it tells us. Something that fails silently is worse than something you do by hand, so it is built to fail loudly.

Do we have to switch tools?

No. Most of this is wiring together things you already use. It is usually the smallest project we do, because it rarely needs anything new built.

What if our process keeps changing?

Then the first job is writing it down, and that is a conversation rather than a build. Automation needs a decision you make the same way twice.

Before you automate anything

What we would want to know before handing a weekly job to a machine.

Tell us what you do twice.

Name the job you type into two places, or the follow-up that depends on somebody remembering. That is usually where the first one lives.