Short answer: a first process can be live in 30 days when the business chooses one high-value workflow, assigns a process owner, configures only the essential control points and measures adoption from day one.
Choose one process, not a transformation programme
Start where work is repeated, cross-functional and visibly costly: overdue customer follow-up, a procurement approval queue, missing inspection evidence, a service exception or an asset incident. Avoid a process that is still being redesigned every week.
Days 1–5: map the real work
Run a short working session with the people who receive, complete and manage the work. Identify the trigger, the current owner at each stage, the evidence required, decision points, exceptions and the definition of completion. Map what really happens, not just what the policy says.
Days 6–12: design the minimum operating model
- Define the case record and links to the relevant ERP or system record.
- Set workflow stages and one accountable owner for each next action.
- Specify the minimum evidence and approval checks.
- Configure simple reminders and one escalation condition.
- Agree the management measures to review each week.
Days 13–20: configure, test and refine
Use a small group of real but controlled cases. Test normal routes, missing evidence, reassignment, overdue work and closure. Make the reason for each rule visible so people understand what the system is doing.
Days 21–30: go live and learn
Launch with a named operational owner, a short user guide and a daily review of early exceptions. Keep the first version focused. Improve the process from real evidence rather than trying to predict every future variation before launch.
What success looks like after 30 days
- Every new item receives a visible owner.
- Teams can see the next action and missing evidence without chasing status.
- Managers can see overdue work and bottlenecks.
- The team has a measured baseline and a clear improvement backlog.
Questions leaders ask
Do we need to replace our ERP first?
No. The ERP remains the system of record. Intelliflow manages the work, owners, evidence and exceptions around the relevant records.
What if our process is not standard?
Start with shared control points and configure the variations that matter. A first process should prove a repeatable operating model, not force every edge case into day one.
See how the platform works · explore solutions · bring us your first process.
Related reading
- Business Process Automation for Multi-Site Operations
- Business Process Automation for Multi-Site Operations
About this guide
Written by the Intelliflow Editorial Team and published 31 July 2026. The timing is a practical implementation target, not a guarantee; actual work depends on process complexity, data, integrations and customer readiness.
Sources and further reading
- ISO 9000 quality-management principles for process and continual-improvement context.