Start automating a process that happens often, follows clear rules and has an owner who can fix exceptions. Lead routing, invoice reminders and routine handoffs are good candidates when their source data is reliable. Use a standard platform for a simple connection; consider a custom workflow when important permissions, integrations or reporting do not fit the platform.
TL;DR
- Start with a frequent, rule-based workflow that has a clear owner and a safe way to handle errors.
- In the hypothetical invoice example, 400 cases a month free about 43 hours after review; the modeled monthly benefit is $1,080 after support and software costs.
- At that benefit, the example's $3,600 setup pays back in about 3.3 months; released staff capacity becomes cash savings only if spending actually falls.
- Use a simple platform for standard low-risk connections; consider a custom workflow when important rules, permissions or integrations do not fit.
- Microsoft lists Power Automate Premium at $15 per user per month, paid yearly; unattended Process is $150 per bot per month, paid yearly.
- Keep people responsible for payment disputes, unusual approvals and other decisions where an incorrect action has a serious cost.
- Process management defines and improves the whole workflow; automation handles selected tasks within it.
The examples below show what starts each workflow, what the system can do and where a person remains responsible. Hapy sells business systems and automation, so compare our service with the simpler options using the same cost and scope assumptions.
Which processes are worth automating?
Start with work that occurs often enough to matter and has an observable outcome. A daily lead handoff with a known owner is a better first pilot than a rare contract decision with unclear rules. For each example, check the data source and define what happens when the system cannot complete the task.
| Workflow | Trigger and automated action | Human decision or exception |
|---|---|---|
| Lead intake | A form creates a customer record, checks duplicates and assigns an owner. | Review strategic leads, missing details and disputed matches. |
| Quote approval | A discount request is routed with its value and margin. | Approve unusual commercial terms and delivery commitments. |
| Customer onboarding | A signed agreement creates kickoff tasks and requests assets. | Resolve missing access and explain unusual project risks. |
| Support triage | A request is categorized and routed to the relevant queue. | Handle billing disputes, security reports and sensitive replies. |
| Invoice follow-up | An overdue, unpaid invoice creates a reminder draft. | Check disputes, recent payments and relationship-sensitive cases. |
| Recurring reporting | A scheduled refresh gathers approved metrics into a report. | Investigate changes and decide what the figures mean. |
| Inventory alerts | Stock crosses an agreed threshold and alerts purchasing. | Adjust for supplier delays, substitutions or changing demand. |
| Document review | An uploaded document is classified and missing fields are flagged. | Interpret legal terms and approve exceptions. |
| Quality checks | A release candidate collects test results and missing approvals. | Accept remaining business risk before release. |
| Team handoffs | Completion of one step creates the next assigned task. | Resolve competing priorities and ambiguous blockers. |
| Renewal reminders | A renewal window creates an account review task. | Negotiate terms and discuss customer concerns. |
| Management dashboards | Workflow events update agreed measures and exception counts. | Interpret trends and change targets or operating rules. |
The broader business process automation guide explains the category. When the workflow itself needs redesign, start with the process-management example below before automating a task.
Process management example: supplier invoice approval
Business process management (BPM) defines, measures and improves how the whole process works; automation performs or coordinates selected tasks inside it. APQC’s comparison makes that distinction: software can speed up a step, but the process still needs decisions, measures and ownership.
Consider a hypothetical company whose supplier invoices wait in a shared inbox. Finance wants to reduce the time from receipt to a decision without paying the same invoice twice. The team first maps the workflow and measures elapsed time and exceptions. Only then does it choose which handoffs to automate.
| Step | Process owner and rule | Useful automation | Exception |
|---|---|---|---|
| Receive | Finance records the supplier, invoice number and amount. | Create a tracked record from the inbox. | Missing or unreadable fields go to a person. |
| Match | Finance compares the invoice with the purchase order and delivery record. | Flag a match or a possible duplicate. | Route mismatches and duplicates for investigation. |
| Approve | The authorized manager decides on the specific amount and terms. | Route the approval request and record the decision. | Changed terms require review again. |
| Pay and reconcile | Finance controls payment and verifies the result. | Update the record after the payment system confirms it. | A failed or uncertain response stays open for reconciliation; it must not create a second payment. |
Track time in each queue, the share needing rework and unresolved exceptions before and after the pilot. An automated reminder might reduce a handoff delay, but it cannot fix a missing approval owner or bad supplier data. This is a supplier-payment process; the overdue customer-invoice reminder below is a different workflow.
Invoice follow-up: protect against stale data
A reminder can save time, but only if the system checks payment status before it sends anything. Start by preparing drafts for finance staff; route disputed invoices and missing payment information to a person. Once the records are reliable and the owner can stop or correct a wrong message, automate the low-risk cases. Keep a record of each reminder alongside the invoice.
Lead routing: make the handoff visible
A form can create a CRM record, check whether the contact already exists and assign the lead by region or service. Route incomplete records to a named person instead of silently discarding them. A team should still review important accounts and correct a bad match; routing is not the same as deciding whether a customer is worth serving.
Quote approvals: automate the packet, not the decision
Collect the proposed price, margin, scope and delivery capacity in one request, then route it to the right approver. A rule can send a routine discount to a sales manager; it should not decide that unusual payment terms or delivery risks are acceptable. Record who approved the exception and which version of the quote they saw.
How much can one workflow save?
In this hypothetical US invoice-reminder pilot, a team handles 400 cases per month. It currently spends eight minutes on each case. The proposed system prepares reminders, but staff still spend ten hours a month reviewing exceptions. Assume a loaded staff cost of $30 per hour, a $20 monthly software allowance and four hours of monthly support at $50 per hour. The implementation costs $3,600. These are planning assumptions, not measured results or a quote.
| Monthly calculation | Result |
|---|---|
| Current work: 400 × 8 minutes | 53.3 hours |
| Less review and exception work | 10 hours |
| Capacity released | 43.3 hours |
| Capacity value: 43.3 hours × $30 | About $1,300 |
| Less software and support: $20 + $200 | $220 |
| Modeled monthly benefit | $1,080 |
| Setup payback: $3,600 ÷ $1,080 | About 3.3 months |
The $1,300 values time that staff can use elsewhere. It is not automatically cash saved: payroll falls only if the business can actually reduce paid hours or avoid a planned hire. The model excludes tax, financing and any wider revenue effect. If exceptions double to 20 hours, the modeled benefit falls to $780 a month and payback rises to about 4.6 months. This is why an exception path and a measurement period matter as much as the number of automated cases.
Should you use rules, AI or a person?
Use rules for structured inputs and clear thresholds. Use AI to help interpret varied text or documents when a person can review uncertain results. Keep consequential decisions with the responsible person. A hybrid workflow might extract a supplier name from an invoice, then use a rule to check the amount and route an uncertain match to finance.

| Approach | Suitable work | Failure to plan for |
|---|---|---|
| Rules | Route a lead by a known region or send a renewal task. | Missing or outdated fields send work to the wrong owner. |
| AI-assisted | Suggest a category for a support message or extract invoice fields. | An incorrect result looks convincing and needs review. |
| Human-led with assistance | Review a contract change or approve a disputed payment. | An automated draft is mistaken for an approved decision. |
Do not add AI to a workflow that a simple rule can handle. If the system can send money, change access or make a customer commitment, set an approval boundary and give the owner a way to pause the workflow.
What will the software and help cost?
For a straightforward connection, try an existing platform before commissioning a custom system. As checked November 12, 2026, Microsoft lists Power Automate Premium at $15 per user per month, paid yearly, for cloud and attended desktop flows. Its Process plan lists $150 per bot per month, paid yearly, for unattended automation. Those are different licenses; confirm connector, usage and account needs for the actual workflow. Your implementation and staff time are additional.
Hapy’s Business Systems & Automation page lists $4,999 per month for agreed work connecting tools, building dashboards and improving workflows. That is a broader service than one platform license, and its scope and capacity must be agreed. For the hypothetical single invoice workflow above, a $4,999 monthly service would exceed the modeled $1,300 monthly value of released time. Choose it only if the agreed wider work has enough value beyond that one workflow; otherwise a smaller platform-based pilot is the more proportionate starting point.
Custom work becomes more useful when several systems need shared permissions, unusual business rules, an audit trail or a dedicated operational interface. Include setup, hosting, monitoring, incident response and future rule changes in its cost. The automation strategy guide helps select the workflow before choosing a tool.
How do you make a pilot safe to expand?
Name one owner and a backup. Map the trigger, source data, expected output and exception path. Record the current volume, hands-on time and errors, then compare those with the same measures during a small pilot. If payment status is stale or nobody can recover a failure, keep the action in review rather than sending it automatically.

For the invoice example, the next decision is clear: proceed if the team can keep payment data current and expects enough repeat volume to justify the setup. Start with draft reminders if either assumption is uncertain. Once the owner can explain the errors and the actual cost, use that evidence to decide whether to expand to another workflow.


