Automation with a signature

There’s a version of automation that feels like good hospitality. The invoice arrives on time, the confirmation email lands instantly, the file is named correctly without anyone touching it. Nobody misses the human here, because no human was ever adding anything. The machine took over a chore, and everyone’s day got slightly better.

Then there’s the other version. The birthday email from a company you bought socks from once. A “just checking in” sequence that checks in on nothing. That condolence-adjacent message with your first name mail-merged into it at a jaunty angle. Somewhere behind each of these, a person decided that the appearance of care could be manufactured at scale, and the recipient can always tell.

Same technology. Opposite effects. The difference isn’t the tooling, it’s what got automated: a task, or a relationship.

We’ve started using a simple sorting rule in our own shop, and it travels well. Automate the repeatable. Sign the meaningful.

Automate the repeatable

Anything you’d do identically a hundred times in a row is a candidate. Scheduling, backups, deploys, reminders, formatting, the seventeen little handoffs that move a project from one stage to the next. These deserve automation, aggressively, because doing them by hand isn’t craft. It’s friction wearing craft’s jacket. Every hour a machine reclaims from that pile is an hour that can go somewhere judgment actually lives.

No client has ever felt less loved because our invoices send themselves. The chore was never the relationship.

Sign the meaningful

But some moments are load-bearing. Delivering hard news. Explaining why we’d cut a feature the client loves. The first email after a project stumbles, and the last one after it ships. Praise, when it’s specific. Apology, always. These can’t be automated, not because the software fails at the words, but because the point of the words is that someone spent themselves on you. A generated apology is a contradiction in terms.

The cost is the content.

Think of it the way you’d think of a signature on a print. The press did the reproducible work, and nobody’s embarrassed about that. The signature marks the part that couldn’t have come from anyone else, and its whole value is that it doesn’t scale.

The lights on, nobody home

The failure mode of the moment isn’t too much automation. It’s automation without a signature anywhere in the building, companies becoming smooth, frictionless surfaces that answer instantly and mean nothing, until customers realize they haven’t encountered a decision, an opinion, or a person in months. Efficiency, pushed past a certain line, stops reading as competence and starts reading as absence. The lights are on. Nobody appears to be home.

And absence has a price that never shows up on the dashboard that celebrated the time savings, because the customers it costs you don’t complain on the way out, they just quietly stop feeling anything about you at all.

So we draw the line one way, every time: machines do the lifting, people do the meaning. Let the pipeline assemble the deliverable, and have a human write the note that accompanies it. The scheduler can book the call, so long as somebody shows up to it unscripted. Use every generator you like on the first draft, then make sure the final draft has fingerprints.

Where the human touch stays visible matters more than how much of it remains. A single genuinely written sentence at the top of an automated report changes how the whole report is received. One real voice memo outweighs a month of triggered emails. Customers aren’t auditing your stack. They’re checking, half-consciously, for one thing only: is anyone actually here?

Automate until the chores are gone. Then sign your name where it counts, in ink, in person, in sentences no template suggested.

The machines are welcome to the lifting. The signature stays ours.