One end-to-end process
For example: a website enquiry arrives, is checked against existing contacts, receives an owner and gets its first follow-up task. The whole sales department is not one workflow.
Workflow Audit · $2,000 fixed
One process, a clear picture of the work and a practical recommendation. Before you spend money on a build, find out whether automation is the right answer—and what a worthwhile version would need to do.
A standalone paid deliverable. The introductory fit call is free.
You may know that enquiries sit too long, client setup needs too much chasing or staff keep copying the same details. The audit examines the cause, the exceptions and the cost of changing it.
It is useful when several fixes look plausible, the baseline is unclear or you want a second look before committing to software. It is less useful when there is no recurring process, no owner or no access to examples of the work.
For example: a website enquiry arrives, is checked against existing contacts, receives an owner and gets its first follow-up task. The whole sales department is not one workflow.
Examine the tools involved in that boundary, their existing capabilities and the places people move information between them.
Speak with the process owner and relevant colleague, review suitable examples, then walk through the findings and the recommendation.
Additional workflows, systems or interview requirements are scoped separately. The audit does not include production changes, a finished automation or a full security assessment.
The steps, owners, inputs, handoffs and exception paths within the agreed boundary.
What is known about volume, active working time, waiting and rework—and where the evidence is too weak for a firm estimate.
The relevant native features and integrations, so a custom build is compared with a simpler configuration.
Options ordered by practical value, effort, dependencies and risk, including changes you can make without new automation.
A transparent model of time, review effort and running costs, alongside decisions requiring a person’s approval.
A recommended boundary, dependencies and acceptance criteria—or a reasoned recommendation not to build.
The planning window is ten business days after the agreed inputs are available. Your proposal confirms the start, dependencies and readout date; it is not an instant report generated from a website address.
Interview the people involved and follow suitable examples through the current process. Mark assumptions and missing data.
Check existing software, sketch the viable changes and model their costs, review work and operational risks.
Walk through the findings, answer questions and agree what would need to be true before a build should proceed.
Plan for roughly two to four combined hours across the process owner and relevant colleagues, plus preparation of suitable examples. This is a planning allowance; the proposal confirms the actual ask.
Useful inputs include approximate monthly volume, current process notes, software names and a small set of synthetic or properly redacted examples. If the records are incomplete, say so. I will separate observations from assumptions rather than create a precise-looking baseline.
Do not send passwords, confidential customer files or sensitive records through the website or ordinary email. Any system access or restricted data review needs an agreed method first.
The model starts with manual touch time and subtracts the work that remains: checks, exceptions, review and maintenance. Software and support costs also count.
A time estimate only becomes a business benefit when your team can use that capacity productively or reduce a real cost. I keep assumed capacity value separate from observed cash savings. A long payback can be a reason to reduce the scope, use a native feature or leave an idea alone.
The audit is priced in USD for the scope above. The proposal confirms taxes, payment terms, timing and any additional scope before work starts.
There is no obligation to buy implementation from me and no automatic audit credit against a future build. You can use the deliverable to make an internal decision or brief another provider under the agreed usage terms.
The free 20-minute call establishes the problem and fit. It does not include detailed analysis. The paid audit includes interviews, review, a documented map, options, economics and a readout.
Yes, if there is enough access to understand the process. Missing or unreliable data is identified explicitly. The next recommendation may be to measure the work before paying for implementation.
Not by default. Documentation, a walkthrough or read-only access may be enough. Any additional access is discussed for the specific scope and should be limited to what is needed.
Use synthetic or appropriately redacted examples wherever they can answer the question. If confidential information is necessary, agree the handling and confidentiality terms before sharing it.
No. It is a diagnostic and planning deliverable. A build is separately scoped and priced after the recommendation is understood.
Yes. The deliverable is meant to make the next decision clear, including the workflow boundary and acceptance criteria. Its use and any underlying intellectual property are addressed in the audit agreement.
We’ll decide whether the focused audit fits the problem before you commit to paid work.
Free 20-minute fit call. Audit: $2,000 for the defined scope.