Your Client Wants Automation. Which Task Should You Leave Manual?
Choose a useful first automation by separating repeatable administration from decisions about suitability, price and customer commitments.

“Could we automate this whole process?” is an understandable request from a busy client. It is also a broad starting point for a proposal.
Before choosing modules, separate the repeatable administrative actions from the decisions that still need the client’s judgement. That boundary gives you a smaller project to explain and a clearer result to check.
Walk through one real situation
Imagine a fictional virtual assistant reviewing a service business’s enquiry routine. Information arrives, someone assesses suitability, a price is discussed and a booking is confirmed.
Some steps may follow a stable rule: record the request, check whether essential fields are present and prepare an internal task. Other steps may depend on capacity, unusual requirements or an agreement with the customer.
Ask the client to explain an awkward recent example. Where did they depart from the normal routine? What information made the decision different? A process that looks repetitive from the outside may contain a judgement the diagram has not yet captured.
Write the boundary into the proposal
A practical first scope might end at an internal task ready for review. State what starts the workflow, what it produces, who checks it and which customer-facing actions remain outside the build.
Avoid promising an end-to-end system when you have only agreed a data-transfer step. The client should be able to distinguish the administrative improvement from the decisions they still own.
Also agree what happens when the rule cannot decide. A visible review case is a legitimate outcome. It should say who receives the question and what information they need to resolve it.
Choose a testable first step
Prefer a bounded task with recognisable inputs and an observable finish. “Improve customer management” is difficult to test. “Prepare one internal review task for a complete, previously unseen enquiry” gives you something specific to inspect.
Rehearse it with fictional examples before involving live client actions. Include an incomplete request and a repeat submission. Check whether the result preserves the agreed boundary rather than making an automatic commitment on the client’s behalf.
Tool permissions should follow the actual authorised task. A practice project is not a reason to collect unrelated information or pass personal passwords between people.
Let the client see what remains human
Show the route on a small process map. Mark the review decision clearly and ask the client to explain it back in their own words. If they expect an automated price agreement while you expect a manual review, resolve the mismatch before building.
A useful automation proposal makes responsibility easier to understand. You can extend the routine after the first step has been tested and the next decision is clear. The first delivery does not need to pretend that every part of the business follows the same rule.
Keep working on this question
Explore our build an automation another person can understand guide, or read The Workflow Works on Your Laptop. Can a Colleague Run It?.
For a structured learning option, see the Office Automation with Matze product overview.
Explore the course contents and current price. Affiliate link: Superstore may earn a commission if you buy. Review the format and requirements before purchasing.




Discussion 1