The 3 automations every founder should build first

Most founders don't have an automation problem. They have a repetition problem that has been allowed to grow for two years.

The work looks small in isolation: copying a name from an enquiry form into a spreadsheet, sending a "just checking in" message, confirming an appointment, telling a client where their order is. Each takes two minutes. Together they take your week, and they take it in fragments — the worst possible way to lose time.

The instinct is to automate whatever is annoying. That's the wrong filter. Automate what is repetitive, rule-based and revenue-adjacent. Three workflows meet that test in almost every small business.

1. Lead capture and follow-up

This is the automation with the shortest payback period, because the money is already at the door.

The typical failure is not laziness. It's latency. An enquiry arrives at 9pm, sits in an inbox, and gets a reply at 2pm the next day — by which time the prospect has messaged two competitors. Speed of first response is one of the few conversion levers you can change this week without changing anything about your offer.

What the workflow looks like:

1. 1Every enquiry route — website form, WhatsApp, Instagram DM, phone log — writes into one place. One place, not four.
2. 2An immediate acknowledgement goes out with a real answer: what happens next, when, and a link to book time.
3. 3The lead is tagged by source and by intent, so you can see later which channel actually produces buyers.
4. 4A short follow-up sequence runs if the lead doesn't respond — three touches over ten days, then a clean stop.
5. 5Anything that gets a reply drops out of automation and lands on a human.

Build this when you're getting more than about five enquiries a week, or whenever you notice you're replying from memory rather than from a list.

2. Booking and reminders

Scheduling is pure administrative friction. It creates no value and consumes attention on both sides.

Replace the back-and-forth with a booking link that reflects your real availability, buffers between calls, and asks two or three qualifying questions at the point of booking. Those questions matter more than the calendar. "What are you trying to solve?" and "What's your timeline?" turn a slot into a briefed conversation.

Then add reminders — one 24 hours before, one an hour before. No-shows on booked calls typically fall sharply once reminders exist, and the recovered hours are the most expensive hours you have.

A detail people miss: automate the aftermath too. A short recap, the agreed next step, and a proposal or resource link sent automatically after the call keeps momentum without depending on your energy at 6pm.

3. Customer and internal status communication

Most complaints are not about the work. They are about not knowing what's happening.

Every business has status moments — order received, work started, draft ready, delivery scheduled, invoice due. Each one is a message someone currently writes by hand, or forgets to write at all. These are perfect automation candidates because the trigger is unambiguous and the content is near-identical each time.

Do the same internally. When a deal is marked won, the onboarding checklist should create itself and land with an owner. When an invoice passes fourteen days, someone should be told before it becomes an awkward conversation.

Written well, these messages don't feel robotic. They feel like a business that is paying attention.

How to sequence the work

• Week one: consolidate enquiries into one system and turn on instant acknowledgement.
• Week two: add the booking link, the qualifying questions and the reminders.
• Week three: map your five most common status moments and automate the three clearest.
• Week four: review what actually fired, what annoyed people, and delete anything that added noise.

Two rules that keep automation honest

Automate the process, not the relationship. Anything that requires judgment, negotiation or empathy stays human. Automation should hand a well-prepared human a well-prepared conversation.

Never automate a broken process. If your follow-up sequence is vague, automating it just means you're vague at scale. Write the messages you'd be happy to receive, then let the system send them.

The point

None of this is exotic. It's lead follow-up, scheduling and status communication — the three things a founder does badly not through incompetence but through volume. Build them once, and you buy back the fragmented hours that were preventing you from doing the work only you can do.