Check four things first.
- Frequency: does the task repeat often enough?
- Rules: can you explain the input, decisions and completion?
- Exceptions: who reviews cases outside the normal path?
- Access: do the tool, plan and account allow the integration?
A worked example with visible assumptions.
Illustrative example: 40 records a week × 5 minutes per record = 200 minutes of repeated work a week. If 30% still needs human review, the remaining potential reduction is 140 minutes, or about 2.3 hours a week. These are planning assumptions, not results from an LH project.
Replace the figures with a sample of real work. Include correction, review and maintenance time. Fewer manual steps do not automatically mean more sales or lower payroll costs.
Compare costs with a reasonable value.
Include build fees, tool subscriptions, API usage, notifications, monitoring and support. Compare those with time that could be redirected and problems that could be reduced, using your own data.
LH’s automation package starts at a standard RM5,000 build fee. The workflow, integrations and exception handling determine the quotation. The 30% offer for the first five customers requires availability confirmation.
Define acceptance before building.
Test normal input, incomplete data, duplicate submissions, a disconnected service and cases requiring a person. Explain how the owner learns that something failed and how work resumes.
For booking, decisions include a slot already being taken, confirmation and cancellation. The Ain’s Little Cells project note describes a workflow you can explore on the real website.