Notes
Notes on Business Automation
What can be handed to software, what it costs, and where automation makes things worse rather than better - whether you are three people or three hundred.
- 7 min read
When your domain expires, everything attached to it stops
When a domain expires, the registrar must switch it off before deleting it, and the notice goes to a mailbox on that same domain. What ICANN's policy says, what stops with the name, and what the clocks look like after.
- 18 min read
The tax clock and the subscription clock disagree
US federal rules want the records behind a tax return kept for three years, sometimes seven, sometimes indefinitely. Eleven help centres, read on one day: how far back your accounting, payment and chat tools let you reach, and what happens when you stop paying.
- 10 min read
What 99.9% uptime promises, and what you get when it is missed
A 99.9% uptime SLA allows 43 minutes down a month. Miss it and the remedy is the value of three days of subscription, claimed within 30 days, only for outages that meet the contract's definition.
- 7 min read
The PDF your invoicing tool sends has an end date as an invoice
Under the EU definition that Germany already applies, an invoice between businesses has to be issued in a structured format. A plain PDF stays valid there until 31 December 2026, or 2027 for smaller issuers. Plus what six invoicing tools send by default.
- 15 min read
The customer paid, and the money can sit on hold for 21 days
A payment can land in your account and sit on hold for up to 21 days, or 180 in a dispute, on criteria the processor is not obliged to disclose. What the US PayPal agreement says, and which of your processes it breaks.
- 7 min read
20% off which price? The law says the lowest of the previous 30 days
Under the EU lowest-price-in-30-days rule a discount on goods sold to EU consumers is counted from the lowest price of the 30 days before the sale, and the court has said so. Your shop's compare-at field stores one number and no history.
- 7 min read
Delete a Google Workspace user, and their data has twenty days left
Deleting a Google Workspace user frees a licence and starts a 20-day clock on mail, files, calendars and the automations signed in as that person. What the admin pages say, and which option Google names instead.
- 7 min read
Your automation said no. The customer can ask for a person
When software alone takes a decision that matters to a person, the GDPR gives them a right to human intervention, to be heard and to contest it. Fraud rules and auto-declines come with a built-in no; the route back to a person is a setting, and in most tools an unset one.
- 7 min read
The AI voice that calls your customers is a robocall
Under the TCPA an AI voice call to a customer is a robocall, the FCC confirmed in 2024. The tools ask for a number and a script; the law asks for the customer's consent first. US federal rules only.
- 18 min read
The spreadsheet stops being a database before you notice
The published ceiling is ten million cells, and it is not the one your business will hit. What arrives first, what the vendors say happens then, and who gets told.
- 19 min read
Void and delete are not the same thing in your books
One action, two traces in the ledger. The button that looks reversible is the permanent one, and the systems connected to your books are told about only one of the two.
- 19 min read
The payment failed, and the retries started without you
A subscription card payment declines and a two-week schedule starts running. Some of those attempts never happen at all, and the counter goes up anyway.
- 17 min read
The model behind your assistant gets switched off
The date is published months in advance, in a table nobody in your business reads. What happens on the day, and why the risk is a different answer rather than an outage.
- 15 min read
The conversation you rely on will be deleted
Hidden at ninety days, deleted at a year, and nothing to restore afterwards. What the platforms actually say about the thread your agreements live in.
- 17 min read
Certificates now expire sooner than the reminder you set
Since March 2026 a certificate can last at most 200 days, and the schedule keeps shortening. Whether that is your problem at all depends on one thing.
- 17 min read
A chargeback gives you one reply and somebody else's deadline
The money is taken before you hear about it, the clock belongs to the card network rather than to you, and you get a single submission. What the rulebooks actually say.
- 14 min read
Your supplier had the breach. The notification is yours to write
EU law gives a controller 72 hours from becoming aware of a personal data breach. It gives the processor who tells you no deadline at all. What twelve vendor contracts actually promise, and what went wrong in four documented cases.
- 15 min read
The bot has to say it is a bot
Since 2 August 2026 the EU AI Act has required chatbots and other AI systems that talk to people to say what they are. The chat tools small businesses actually run mostly have no such setting, one ships it switched off, and two vendors give opposite advice in the same field.
- 12 min read
Who your review automation decides not to ask
The two-step flow that sends happy customers to Google and unhappy ones to a private form is a shipped feature. The FTC's rule leaves it unbanned. Google, Trustpilot and G2, where the reviews land, ban it by name.
- 19 min read
The version your app runs on has an expiry date
When the version your integration is pinned to expires, nothing errors. The answers start arriving from a different version instead, and nobody is told.
- 14 min read
Anyone on the internet can knock on your webhook
The address your automation listens on is public, and on the tools most small businesses use, nothing checks who called. What the vendors themselves say about it.
- 18 min read
Access that expires on its own, and nobody is at fault
Nobody left, nobody changed a password, and the connection between two of your tools stopped anyway. The vendors publish these clocks. None of them puts the date on yours.
- 11 min read
Your reply on WhatsApp has a 24-hour deadline
Meta gives a business 24 hours from the customer's last message or call to answer freely. After that, only pre-approved templates go through. What starts the clock, and what does not restart it.
- 15 min read
The number you text from has to be registered
In the US, texts to customers are blocked unless the sending number belongs to an approved campaign. Why the failure looks random, why blocked messages are still billed, and what to check.
- 12 min read
The sending limit that does not reset at midnight
Your mailbox counts recipients over a rolling 24 hours, not per calendar day. What that means the morning after you hit the limit, and why fifteen emails can be enough to trigger it.
- 11 min read
The meeting is in your calendar, the client was never told
Booking software can create a calendar event with the client on it and send them nothing at all. What the documentation says about invitations, and why silence is not guaranteed either.
- 13 min read
Why your emails stopped reaching the inbox
Mailbox providers raised what they require of senders, and the bottom rung applies to everyone. Why password resets break before newsletters do, and how to read the bounce that already names the cause.
- 4 min read
Your automation does not know what time it is for the customer
US rules put marketing calls and texts inside an 8am–9pm window measured at the recipient's location. Most workflows do not store where the recipient is, which makes compliance a data problem before it is a legal one.
- 4 min read
One sale, three exchange rates, and none of them agree
You invoiced 30 EUR and 33 USD arrived, but your books expected 36. The gap is not an error — it is which moment each system locked a rate. What to reconcile and what to stop chasing.
- 4 min read
The attachment never arrived, and the error said timeout
File-handling limits are the least dramatic thing an automation platform documents and one of the most common reasons a document quietly does not reach the other side. The numbers, the misleading error, and what to do instead.
- 4 min read
Your automation switched itself off
Platforms disable workflows that keep failing — one vendor at 95% errors over seven days. That is a sensible rule with an awkward consequence: the thing that was watching your process is now the thing that stopped.
- 4 min read
You renamed a column. The automation stopped seeing it.
Tidying a spreadsheet header is not filed as a change to anything, yet it can silently detach a live workflow from its data. Why it happens, what it looks like afterwards, and how to make your own edits safe.
- 5 min read
The refund button does not have an undo
A refund takes one click, cannot be reversed, and quietly changes your stock and your fees at the same time. What to check before the click, and what to build around automated refunds.
- 4 min read
The cancellation arrived before the payment
Platforms do not promise to deliver events in the order they happened, and small-business workflows are usually built as if they did. What breaks, and the one design change that fixes most of it.
- 4 min read
Nothing is being sent, and nothing is broken
Email platforms suspend sending automatically when a campaign crosses thresholds they do not publish. Your automation keeps running, the API keeps answering, and no customer hears from you. How to notice within an hour.
- 4 min read
You deleted it here. It is still there.
Automation platforms copy records forward and have no reverse gear, so deletions never travel. The result is a business where removing something takes as many actions as there are systems — and nobody knows the number.
- 4 min read
A customer asks you to delete their data. Where is it?
Deleting a contact from your CRM is the easy part. The copies your automations made are the hard part, and one platform will not let you delete in bulk at all. A practical route through it.
- 6 min read
When automated invoices quietly stop charging tax
Automated invoicing and tax: how a billing system decides where your customer is, why a zero in the tax line is not the same as no tax due, and the setting that switches itself off.
- 5 min read
The automation handles most of it. Who handles the rest?
Automation covers the ordinary cases and leaves the awkward ones. Where those land, why the platform may discard them by default, and how to make the leftovers a list somebody works through.
- 5 min read
Admin rights will not let you fix it: who can actually repair an automation
Why the most senior person in the account can be unable to repair a broken step. How permissions on workflows and permissions on connections differ, and what to arrange before something breaks.
- 6 min read
The vendor changed something and your automation stopped
When a platform changes its API or moves a feature between plans: why the warning existed and you never saw it, how deprecation schedules actually work, and what to put in place before the next one.
- 5 min read
Moving your automations to another tool: what does not come with them
Switching automation platforms means rebuilding rather than transferring. What has to be redone by hand, the incoming addresses that change, and how to price the move honestly.
- 5 min read
If the data goes, is anyone keeping a copy? Probably not the platform
Cloud platforms are resilient, which is not the same as backed up. What vendors document about restoring your data, which deletions are permanent, and the smallest backup habit worth having.
- 5 min read
What you actually take with you when you leave a platform
Exporting your data before leaving a tool: what a full account export contains, what it quietly leaves behind, and why the parts that cannot be exported are the ones that took longest to build.
- 5 min read
When the alerts stop being read: automation notifications you can live with
Automation error notifications default to one email per failure, and the usual response is to switch them off. What the sensible middle looks like, and who should be receiving them.
- 5 min read
The person who built your automations has gone. What now?
When the contractor or employee who set everything up leaves: what a platform can and cannot transfer, why the account tier decides your options, and the order to work in.
- 5 min read
The test button is not a rehearsal: testing automation without emailing real customers
Testing an automation safely: why the test button sends real messages and creates real records, what a green test does and does not prove, and how to rehearse without touching a customer.
- 5 min read
Your busiest week is when the automation gives up
Why automations break at seasonal peaks: daily quotas versus burst limits, what a 429 does to the rest of your queue, and what to check before the rush rather than during it.
- 5 min read
Where did this email address come from? Proving consent, one contact at a time
Automated sending assumes consent that somebody obtained months ago. What a signup actually records, the two timestamps that tell you how a contact joined, and how to answer the question per person.
- 5 min read
The records your automation cannot use, and the ones it half-uses
Before automating, the state of your data decides what happens. Why a missing required field stops loudly while an invalid one passes quietly, and which fields are worth fixing first.
- 7 min read
One customer, two records: where duplicates come from and what they cost
Duplicate customer records after a sync or import: which field each system uses to recognise a person, why some duplicates can never be merged, and how to clean up without losing history.
- 8 min read
Two calendars, one slot: why syncing does not stop double bookings
Double booked across two calendars: why real-time sync still leaves gaps, the settings that quietly exclude a calendar from conflict checks, and what to do when both clients are already booked.
- 6 min read
Did the automation pay for itself? Hours saved is the wrong answer
How to tell whether an automation paid for itself: why saved hours rarely become money in a small business, the four ways they actually can, and what to measure instead.
- 5 min read
What happens to customer data you paste into an AI tool
Putting client information into AI tools: what two vendors actually document about training and retention, why the paid tier is a different product legally, and a rule of thumb that survives policy changes.
- 6 min read
The order was cancelled after the invoice went out
What happens when an order is cancelled after the invoice has been sent: why the paperwork cannot simply be deleted, how a credit note can mark an invoice paid without any money, and where two systems stop agreeing.
- 9 min read
Your client is in another time zone. Whose 9am is in the reminder?
Appointment reminders in the wrong time zone: whose clock the message speaks in, the three ways booking tools get it wrong, and the four weeks a year when the gap moves.
- 17 min read
Orders stopped arriving, and the other end stopped calling
Orders stopped syncing because the webhook stopped working: what Shopify, Stripe, Square and WooCommerce do after failed deliveries, and what you can recover.
- 17 min read
The orders your sales report does not know you made
Orders not showing in sales reports are usually the off-checkout ones: drafts, deposits, bank transfers. What Shopify, WooCommerce, Square and Stripe count.
- 16 min read
How long your automation keeps its history, and what disappears
Automation run history retention is counted in weeks on Zapier, Make, n8n and Power Automate. What gets deleted, what survives, and what to export.
- 17 min read
When the other app says slow down, what happens to the records
Your automation stopped syncing, too many requests hit the other app. What Zapier, Make and Power Automate do next, and which switch to flip.
- 16 min read
Why your 8am automation runs at 7am after the clocks change
Automation running at the wrong time after daylight saving: which clock your schedule really follows, what four vendors document, and the fixes that hold.
- 15 min read
What happens to your automations when the plan runs out
Hit your automation plan limit and one platform holds the work for 60 days, one switches every scenario off at once, and two do not publish what happens.
- 6 min read
Your automation told a customer something untrue. Who answers for it?
When an automated message gives a customer wrong information, the business is answerable for it — a tribunal has said so plainly. What that means for your bot, your templates and your autoresponder.
- 10 min read
When two systems write the same field, whose value wins
Sync tools rarely say which system owns which field. When two of them can write the same value, one quietly overwrites the other and nothing records that it happened.
- 9 min read
When no-code is right, and when it stops being changeable
No-code automation is the correct answer far more often than developers admit. The failure mode is not volume, it is the day changing one rule means opening five screens.
- 9 min read
Work out when your marketplace money actually lands
Every channel pays on a different delay, and the published schedule is not the number you can plan with. The two dates you need are already in your own exports.
- 8 min read
How to keep track of every automation your business runs
Every automation platform records how a workflow changed. None of them records why it exists, who owns it, or what breaks if it stops. Five fields fix that.
- 11 min read
What happens when an automation runs the same job twice
When an automation fails and tries again, the retry can repeat the action: a second invoice, a second charge, a second parcel. What the tools do by default, and what to ask for.
- 8 min read
The second sales channel, not order volume, breaks fulfilment
Manual order fulfilment survives far more orders than people expect. What it does not survive is a second place to sell, and the maths of why is not obvious.
- 16 min read
How to reconcile marketplace payouts without a connector
Your marketplace pays net, so the deposit matches no number in any report. The method that works when A2X and Link My Books do not cover your channel.
- 11 min read
When a new account breaks your bookkeeping automation
A client edits the chart of accounts and the expense app stops matching. Nothing errors until month end, and Xero does not record the change at all.
- 9 min read
Agree what "done" means before you pay for software
The expensive requirements are not hidden. They are so obvious to you that saying them out loud never occurs to you, and that is where the budget goes.
- 17 min read
Six checks before you pay a supplier invoice, and when to automate
Duplicate and erroneous payments run 0.8% to 2% of what a business pays out. The six checks that catch them, and the volume where automation earns its keep.
- 5 min read
What you should get when an automation is handed over to you
A handover is complete when someone else can run, fix and change the thing without calling the person who built it. Here is the list to ask for before the final invoice.
- 7 min read
Whose accounts does your automation actually run on?
Most small-business automations run on one person's login. What happens when that person leaves, changes a password or turns on two-factor - and how to set access up so it does not matter.
- 6 min read
When a supplier changes their bank details, who checks?
BEC losses hit $3.05bn in 2025, and 86% went out by wire or ACH. Accounting software will not warn you that a supplier's bank account changed - here is the control that does.
- 13 min read
Where to start automating a business that already works
Where to start automating a small business that already runs: the order to work in, what has to exist before software helps, and how to change things safely.
- 6 min read
Getting invoice data out of PDFs: what actually works
Vendors advertise 99% extraction accuracy. What that figure means, why your results will differ, and how to work out whether automating your invoice entry is worth it at your volume.
- 6 min read
AI receptionist or a person: how to compare them honestly
The statistics used to sell AI receptionists come from the companies selling them. Here is how to work out what missed calls cost you, and what each option really covers.
- 17 min read
Why automations fail silently, and how to make them speak up
Why automations fail silently: a green tick means the workflow ran, not that it worked. What Zapier, Make and n8n do by default, and how to design around it.
- 6 min read
How to automate chasing overdue invoices without annoying clients
Small businesses wait 28.8 days to get paid and 59% carry invoices overdue by a month. What to automate in the chase, and what to keep human.
- 9 min read
What automation costs a small business, and why quotes differ
What you pay for when you automate a process: software, build and upkeep, why quotes differ so much, and how to work out whether it is worth it.
- 8 min read
Automating appointment reminders: the settings that cut no-shows
Your booking tool already sends reminders. Which settings do the work - timing, a reply that means something, a card on file - and where a reminder cannot help at all.
- 6 min read
When not to automate a process, and how to tell in advance
Most of the money lost on automation goes into processes that should never have been automated. Five tests to run before you spend anything.