01The test that separates a good candidate from a bad one
A process is ready to automate when you can describe it in one page and someone new on the team could follow that page and get the same result a trained person would. If two experienced staff would handle the same request differently, or if the rules changed last month and might change again next month, automating it just locks in whichever version you happened to write down, and the exceptions pile up as broken tickets instead of saved time. Repeatable and well-defined beats important and vague every time this decision gets made.
- A process is ready when it fits on one page and a newcomer could follow it
- If two staff members would handle it differently, it is not ready yet
- Rules that change monthly get locked in wrong, not automated well
02What usually comes first, in what order
Booking confirmations and reminders are the most common starting point because the rule almost never changes: a slot is booked or it is not. Order and payment confirmations come next, since a Stripe webhook or an e-Factura submission either succeeds or fails and both outcomes have one correct response. Invoicing and late-payment reminders follow once the numbers behind them are reliable. Review requests and content scheduling usually come last, not because they matter less, but because a bad early automation on the money-facing processes above costs more to leave broken.
- Booking confirmations and reminders first, because the rule almost never changes
- Order and payment confirmations next, since each has one correct response
- Review requests and content usually last, not least important, just lower cost of delay
One job model instead of three separate improvised ones
ATP Spedition runs three logistics lines at once: last-mile courier, moving, and freight, each with its own rules, before PROOF48 built it a single system. Rather than automating each line's existing habits separately, the map came first: one job model that could represent all three, then dispatch, offline-first driver apps, proof of delivery and e-Factura built on top of that shared model. Automating the wrong starting point there would have meant three incompatible systems instead of one that actually holds.
See the build: ATP SpeditionQuestions, answered
What if I am not sure which process to automate first?
That is normal, and it is what the mapping day at the start of an automation project is for. We watch what actually repeats rather than asking you to guess from a blank page.
Can automation handle a process that still has exceptions?
Yes, as long as the exceptions are defined too. What breaks is an automation built on a rule nobody wrote down, so the exception cases were never actually decided in the first place.
Where PROOF48 fits
Automate what repeats with a rule you could write on one page, starting with bookings and order confirmations before reviews and content. AUTOMATE, at 2,997 EUR a month, includes two custom automations mapped to what your business actually repeats, not a generic template.
Cosmin Tiu · Founder, PROOF48
Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.