Notes

Decide it first: six small decisions that come before any tool

This week's notes looked like six different subjects: software settings, hiring help, refunds, web enquiries, automation tools and voicemail. Read together, they make one point. In each case the useful work happens before any tool is touched. Somebody has to decide something first, and when nobody has, no tool makes up for it.

What the software you already pay for can do

Before you pay anyone to automate a job, open the settings of the tools you already pay for. A lot of small-business software can do more than it is being used for. The enquiry form may already be able to file each request into a client list. The booking tool may already send the reminder. Nobody switched it on, because it was set up in a hurry and nobody looked again.

So read the feature list first. Sometimes the job turns out to be half done. I make the same check before I build anything: we check what your current software already does.

tech-d-enterprises.com/services

What you will have in hand after the first step

Before you hire anyone to help with automation, look at what their first step is. Some start with a paid audit, some with a free call, some publish a price for a first build. Any of the three can be the right start for you.

The question that sorts them is the same: what will I have in hand when this step is over? A written plan I could act on myself? A clear yes or no on one task? Something that already runs? If nobody can say, ask before you book. My own first step is a free 15-minute call about one task, and nothing is installed, signed or paid for during the call.

tech-d-enterprises.com/appointments

What your refund policy actually says

A customer asks for a refund, and the reply gets written while you are still working out what your answer is. One of the prompts in my free library is for that email: "Draft a polite, empathetic refund response that acknowledges the issue, explains policy in friendly language, and offers a next step."

Run it and look at the middle. If you cannot say what goes in "explains policy", the prompt has not failed. It has found the real gap: there is no written policy yet. Write that down first, in a few plain sentences. Then the AI has something true to explain, and every customer gets the same answer.

tech-d-enterprises.com/free-prompt-guide

What you need to know before you call back

A website enquiry comes in that says, in full: "Interested. Please call." So the first call goes on finding out what they need, what they have already tried and how soon they want it. That is fine at a desk. It is a lot to do between other work, and a lot to hold in your head until you can ring back.

The part of Front Desk I would look at first is not the chat window the visitor sees. It is what lands in your inbox: every answer they gave, in their words, so you do not open the call asking what they do. Worth checking first: your last five web enquiries. How many told you what the person actually needed?

tech-d-enterprises.com/front-desk

Which job the tool is for

Zapier, Make or Power Automate? It is one of the questions on my FAQ page, and the honest answer is shorter than people expect. They are the plumbing between your calendar, your forms and your inbox, and they are all fine. The tool matters far less than picking the right job to point it at.

The wrong job on the best tool is still the wrong job. The right one is usually small and dull: the follow-up nobody has time for, the form that came in on a Saturday, a weekly report someone retypes. If you cannot name that job in one sentence yet, comparing tools can wait.

tech-d-enterprises.com/faq

When you really call people back

A lot of outgoing voicemail greetings say "leave a message and we'll get back to you" and stop there. They do not say when, or where to look in the meantime. There is a prompt in the same library for this: "Write a professional voicemail script (20–30 sec) that gives clear next steps and points to online resources."

The useful part is the brief, not the wording. Before you paste it in, decide when you really call people back, and the one page a caller should look at while they wait. If you cannot answer the first one, that is the thing to fix, and no script will fix it for you.

tech-d-enterprises.com/free-prompt-guide

The decision comes first

None of these six starts with buying anything. Each one starts with a sentence you can write today: what my tools already do, what I want from a first step, what my policy is, what I need from an enquiry, which job I would hand over, and when I call people back.

If you do one thing this week, pick the one you could not answer and write that sentence down. If what you end up with is a repeat job that ought to run on its own, the readiness checklist on my site works the same way. It is five checks, and each unchecked item is something to clarify before a build.

tech-d-enterprises.com/ai-readiness-checklist

← All notes

Want this kind of thing running in your business?

I build one workflow at a time, on the tools you already use. Flat fee from $495, about a week to build.