People sometimes confuse our free call with an audit. The call is a quick check: is this worth automating, and roughly what would it cost? The audit is the first week of any project, and it’s where most of the useful work happens.

What we do in that week

We sit with the people who run the process today, usually over two or three screen-share sessions, and write down every step. That includes the exceptions people forget to mention, like the client who pays by bank transfer or the spreadsheet tab only one person is allowed to edit.

We also pull numbers where we can. How many times a month does this run? How long does each run take a person? How often does it go wrong, and what does fixing it cost?

What you get at the end

A written spec of the process as it works today and as it would work automated, a list of the tools and permissions involved, and a fixed price for the build. If the numbers don’t justify building it, the spec says that too.

About one in five audits ends there. That’s a fine outcome. You still walk away with documentation for a process that probably never had any.

What it costs

The mapping week is included in every build price. If you only want the audit, it’s a flat $1,800, credited against the build if you go ahead within 60 days.

How to prepare

Pick one process, not five. Find the person who does it most often and book an hour of their time. Have admin access to the main tools ready, or know who has it. That’s all we need to start.