Seven small-business tasks you can automate today

Choose one repeated task with a clear owner and a low-cost failure. Record one week of current work, then test with sample data.

• Tasks 1–5: Use built-in product features. Availability still depends on the account and plan.
• Tasks 6–7: Use Power Automate between Microsoft services. Check licenses, connector access and organization settings.

These examples do not require a separate third-party automation service.[1][3][8][11]

For your own list, score weekly frequency and pain from 1 to 3. Score the harm of a wrong action from 1 to 3. Start with a high-frequency, high-pain task that has low harm. If harm is high, add a human approval and a rollback plan. The score is a decision aid, not a prediction of savings.

Workflow: Google Form submission → response row in Sheets → alert to the owner.

1. Create: Ask for name, contact method, request category and a short description. State the expected reply time.
2. Connect: In Responses, link a Google Sheet and enable new-response email notifications.
3. Test: Submit a request yourself. Check the row and alert, then add separate owner and status columns.

• Human review: A staff member decides whether to quote or accept the work.
• Data access: Restrict the form and sheet separately. Do not collect card numbers, identity documents or passwords.
• If it fails: Compare response counts with rows and the alert inbox. Use the form response view and contact the customer manually.

Measure: Requests still without an owner after one business day.[1][2][15]

Workflow: Customer selects an available time → Calendar creates the booking.

1. Set up: On a computer, use a personal Google Account or eligible Workspace account. Create a 30-minute appointment schedule.
2. Configure: Set working hours, time zone, location, title, booking window and notice period. Collect only the details needed to prepare.
3. Test: Book with a second account. Check the confirmation and calendar event, then cancel the test.

• Before sharing: The owner checks holidays, exceptions and meeting details. Tentative or unaccepted events may not block availability. A booking is not a job quote.
• If no times appear: Check dates, time zone, conflicts and minimum notice. Compare bookings with confirmations.
• Account limits: Personal accounts and Business Starter have one booking page. Some options need another eligible subscription.

Measure: Bookings completed without scheduling emails, and any double bookings.[3][4][5]

Workflow: Matching email → label or folder checked by an assigned person. This example uses Gmail; Outlook rules vary by version.

1. Choose: Open a supplier statement. Select More → Filter messages like these and confirm the exact sender.
2. Start small: Apply a label such as Supplier statements. Do not delete, forward or skip the inbox.
3. Test: Send matching and non-matching messages. Confirm only the intended message gets the label.

• Owner review: Approve the criteria first. Review any later archive or delete rule separately. Do not route invoices to a personal mailbox.
• If it fails: Restore misplaced messages, narrow the rule and check the label and inbox daily for a week.
• Keep checking: A sender address does not prove an invoice is authentic. Review urgent mail yourself.

Measure: Correct labels and false matches.[6][7]

Workflow: Recurring billing date → draft invoice in Zoho Books. Use this only for agreed, predictable recurring charges.

1. Choose draft mode: Enable recurring invoices if needed. Select Create Invoices as Draft in the preferences.
2. Create one profile: Use the signed agreement: customer, item, amount, interval, tax treatment and end date if applicable.
3. Test: Check the next invoice date. Compare the first draft with the agreement before sending.

• Human review: For every draft, check the customer, period, price, tax and recipient.
• If terms change: Update or stop the profile before its next run. Correct inaccurate drafts and record missing invoices.
• Plan and payment: Check current availability and fees. Draft mode does not charge the customer. Automatic send or charge needs a separate decision and any required authorization.

Measure: Expected invoices versus generated drafts after each billing date.[8][9][10]

Workflow: Weekly calendar alert → billing owner reviews unpaid invoices. The reminder goes to your team, not the customer.

1. Create: Set a recurring event, alert and backup owner.
2. Link: Use the restricted invoice system, not a public sheet of customer balances.
3. Review: Check due dates, recorded payments, disputed invoices and contact details before sending a polite message.

• Human review: A payment may need reconciliation or have arrived elsewhere. Resolve disputed or corrected invoices before a reminder.
• If it fails: Check calendar ownership, notifications and the next event. Use a manual reminder until fixed.

Measure: Overdue invoices reviewed and reminders sent in error. An email notification is not proof of payment.[8][9]

Workflow: SharePoint request → manager’s decision → notice to the requester. Approval does not place an order or pay a supplier.

1. Create: Restrict a list with requester, item, reason, estimated cost and approver fields.
2. Connect: In Power Automate, use the SharePoint item-created trigger and Start and wait for an approval.
3. Route: Map the details and approver. Add an outcome condition and approval/rejection notices. Test both branches with dummy requests.

• Human review: The manager decides before purchase. Check purchasing limits and define a manual route for absent approvers. Exclude identity documents and bank details.
• If it fails: Inspect run history, trigger, connection, approver address and failed action. Reconcile outcomes before retrying to avoid duplicate notices.
• Access: Check connector permissions and data policies. Premium connectors may need extra licenses.

Workflow: Teams Updates submission → Power Automate posts a short message to the chosen channel.

1. Create: Ask for completed work, next action, blocker and owner in an Updates request.
2. Connect: Use the Updates trigger for that request. Add the Teams action to post in a chat or channel and map the fields.
3. Test: Submit a dummy update. Check the intended channel and flow run history.

• Owner review: Check the request, audience and mapped fields before activation. Exclude passwords, customer details and confidential terms. Add an approval action if review is needed.
• If it fails: Check the selected request, connection, channel permissions and run history. Send the update manually until repaired.
• Access: Confirm product and connector licensing in your organization’s account.

Measure: Missing updates and time spent chasing status.[16][13]

Count all requests, including those received outside the form. Record exceptions, duplicate entries, corrections, and customer complaints. Compare similar weeks and note changes in staffing or volume. Measure elapsed time and hands-on time separately if time matters to you. Do not claim a time saving until your own records support it.

AUTOMATION WORKSHEET
Task and owner: __________________________
Trigger and input: ________________________
Expected action: __________________________
Human approval before: ____________________
Baseline count and period: ________________
Success measure and target: _______________
Test cases, including a bad input: _________
Access and data needed: ___________________
Failure signal and backup owner: __________
Manual recovery steps: ____________________
Review date and decision: _________________