Notes

How to tell a claim worth trusting from one that sounds good

Five notes went up on my feed this week, and when I lined them up they were all running the same test. Not on automation as such. On claims — the ones on my own site, and the ones you will hear from anybody selling you anything in this space.

The test is simple to say. A claim that is specific enough to turn out wrong is worth more than one that is too smooth to check. The smooth one costs nothing to make, which is exactly why it tells you nothing.

Here is the week, one claim at a time.

A page about a town

I have five town pages on my site: Annapolis, Edgewater, Severna Park, Crofton and Glen Burnie.

Most local pages on the internet are one template with the town name swapped in. Skim one and you cannot tell it apart from a page somebody actually wrote. The tell is not the design. A generated page cannot afford to be specific, because anything specific might be wrong, so it stays vague about everywhere it names.

The Severna Park page names a road, names a group of businesses up there that have already solved this without me, and tells them the page is not for them. All three could be wrong. That is what makes them worth writing, and it is the first thing to look for on anyone's local page, mine included.

A trigger

Every automation example on my site starts with an event, not a task. A call you cannot answer. A form or work order arrives.

That distinction does a lot of work. Ask an owner when their follow-up actually goes out and the honest answer is often "when I remember to." That is not a trigger. It is a person, and the person is already busy. If you cannot name the moment a job should start, there is nothing to build on yet — and that is worth knowing before you pay anyone.

An estimate

A savings number is only as good as the assumptions underneath it. The planner on my site puts them on the screen instead of burying them: $32 an hour as a loaded staff cost, the automation absorbing about 65% of the task, and 50 working weeks a year. Change any one of them and the answer moves.

So the number is not the finding. The assumptions are. It is an estimate, not a quote for your books, and if the answer looks wrong for your business it probably is. Before you trust anybody's estimate, ask to see what it is made of.

Something that keeps running

One local business website I looked at this week had been taken over. Open the home page and you got a gambling site. I doubt the owner knows.

That is the risk with anything you set up and stop looking at: it keeps running whether it is doing what you meant or not, and an automation is no different. So the useful question is not only what it does. It is how you would find out it stopped doing it, and how you would switch it off. My FAQ puts that in writing: test cases, exceptions and manual checks are agreed before handoff, and the handoff instructions tell you how to pause a workflow.

A timeline

The last one is the claim everybody asks for first: how long will it take?

Mine is written down. A single automation is usually ready in about a week. Larger workflows typically take two to three weeks. And the sentence after that is the one worth reading: access to your tools and review of sample inputs are checked when we agree the schedule.

Two of the things a schedule depends on are in your hands, not the builder's — getting them into your tools, and showing them what the real inputs look like. A timeline with no conditions attached is not a faster promise. It just has not been checked yet.

What the five have in common

Each one is a claim that names its own conditions. The town page names a road. The trigger names an event. The estimate names its three numbers. The handoff names how you switch it off. The timeline names what it is waiting on.

None of that makes a claim true. It makes it checkable, which is the most you can ask of anyone before you have worked with them. A vendor who gives you a number with nothing underneath it has not made a stronger promise than one who shows the working. They have made one you cannot test until after you have paid.

If you want to see the conditions written down in one place, the FAQ has them, and the free consult is fifteen minutes with one task you would like to stop doing by hand.

tech-d-enterprises.com/faq

← 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.