What a Workflow Automation Diagnostic Includes (and What It Doesn't)
One hour, one job, a written answer.
A workflow automation diagnostic is a one-hour working session on one job your team does by hand. At the end you get a straight answer on whether it's worth building, and a one-page scope with a fixed price, in writing, within two business days.
Who's on the call
You, or whoever approves the spend, and the person who does the job now. Screens shared. The walk-through is the product, so if that person can't make it, we move the call.
What happens in the hour
- The sweep. We list the three to five jobs your team does by hand and pick one: the one that eats the most hours, or causes the most expensive mistakes, and already lives in software. The rest go on a list for later, out loud.
- The walk-through. The person who does the job runs it on two or three real examples while I time it. I note every system, every copy and paste, and every exception. "What happens when the email has no phone number?"
- The access check. Which accounts the build touches, who owns them, who has admin access, and whether you'd have to buy any license.
- The verdict. I say it plainly before we hang up.
The three possible verdicts
- Build it. The job is worth automating. You get the fixed number in writing.
- Fix the process first. The job lives in one person's head, or it's done differently every time. Nothing can be built on that yet. The scope page lists what to write down first. That's a real outcome, and it's what the diagnostic was for.
- Too small. The honest build isn't worth what it would cost you. I'll tell you.
What you get
One page, within two business days: the job, the person who does it, the measured baseline, the systems involved, what you provide and by when, the fixed price, the delivery date, what's not included, and the list of other jobs for later.
What I need from you beforehand
- Three to five recent real examples of the job: the actual emails, files or records.
- The list of systems it touches.
- The person who does it, on the call.
What it doesn't include
- One job only. A review of the whole company is a separate quote and doesn't ride in on the diagnostic.
- No final price on the call. The fixed price comes in writing so you can read it twice.
- Nothing built or fixed live.
- Regulated data. Health records, financial accounts and legal matters add setup and review work. I scope that before you sign anything.
It's paid, and it comes off the build
The diagnostic is a paid hour. If you go ahead with the build, it's credited in full. The build runs in your own accounts, which is what makes "you own it" true. Go-live means it's running on your live work and the person who used to do the job by hand is using it after training. Delivered isn't the same thing.
After that there's an optional month-to-month care plan: 30 days' notice, up to two hours of changes a month, and a one-page report each month.
About the Author
Anthony Pinto
Naval Academy graduate, former submarine officer, and founder of Veteran Vectors, a NaVOBA-certified Service-Disabled Veteran-Owned Business Enterprise and Disability:IN-certified DOBE. Anthony runs personalized LinkedIn outreach for small businesses, booking qualified sales calls through a script written for each named prospect, then builds the follow-up systems to run the pipeline. Every post here is grounded in hands-on client work.
Which job eats the most hours?
Book a free 30-minute call. Tell me the one job someone on your team does by hand every week, and I'll tell you whether it's worth a paid diagnostic. That fee comes off the build.
Book a Call