What I mean when I say workflow

“Workflow” is one of those words that shows up in every demo. I use it anyway, because I mean something small.

A workflow is a job you already do more than once. It has a start (someone emails, a ticket comes in, Friday hits), a middle (you look something up, you write, you send), and a done (it’s on the calendar, in the folder, or out the door).

If you can’t name those three, it isn’t a workflow yet. It’s a pile.

One job, not “AI on everything”

Owners tell me they want help with all of it. That’s how you buy four tools and still type the same reply. Pick one job. Invoice follow-up. Appointment reminders. A first pass on a quote. Write the steps as you do them today — on paper if you want.

Then ask: which step is slow because it’s typing, searching, or copying — not because it needs your judgment? That’s the only place a tool might help. The judgment stays with you. The copying might not.

A sentence is enough

You don’t need a diagram with swimlanes. You need a sentence: “When X happens, we do Y, then Z.” If that sentence is true next Tuesday without you standing there, you’ve got something. If it only works when you remember, it’s still just you.

I start here on purpose. Platforms change names. A clear job doesn’t.