Signal, rule, action, record.
When a team keeps repeating the same message, the same reminder and the same approval, that repetition is a process waiting to be written down. Writing it down is most of the work.
The four parts
Something happens: an order arrives, a stage completes, a payment falls due, a document lands. The system notices rather than a person noticing.
Your existing informal logic, written down — who should act, what happens next, how long before it escalates. Configuration rather than code, so it can change without us.
The task, notification, approval or update happens. Where it touches money or a customer commitment, it is proposed and a person confirms.
What fired, when, to whom and what they did. The part that makes the process auditable instead of merely faster.
Questions people actually ask
Where should we start?
Do we need to replace our existing systems first?
What if our process is not written down anywhere?
Related
Tell us what wastes the most time.
Fifteen minutes is usually enough to know whether it's worth building. If it isn't, we'll say so.