Choose one recurring bottleneck
Start with a process you can describe and measure, such as copying contact details, preparing an intake or tracking proposal status. Record how often it occurs, how long it takes and where mistakes arise. A useful first project has a clear start, a responsible person and an observable result. Automating an unclear process usually preserves the confusion.
Separate proposals from confirmed actions
A draft quotation is not a sent quotation. A preferred date is not a confirmed appointment, and a payment request is not a received payment. Define the evidence and approval required for each transition. In an illustrative enquiry workflow, the request is recorded, a person checks the scope, a proposal is prepared and delivery planning follows confirmed acceptance.
Check integrations and exception handling
An integration depends on the application's interfaces, permissions and available functions. Choose the source of truth for customer details, document versions and status. Keep a stable reference so retries do not create duplicate records. Decide what happens when a connection fails, information is missing or a customer changes the request. Make the exception visible to the responsible person.
Prepare for teams and customers across borders
For a European workflow, clarify communication language, time zones, date formats, currencies and responsibility for follow-up. Confirm access by role and the information each participant needs. Start with a bounded pilot, review normal cases and exceptions, and compare the result with the initial process before extending it to more teams or markets.
Prepare your enquiry
- The repetitive process and its current owner
- Applications used and available connection options
- Required inputs, records and approval points
- Known exceptions and duplicate-record risks
- Current processing time and the outcome to improve
Questions before you start
Can everything run automatically?
Not every decision should be automatic. Agree which routine steps can run under rules and which actions need review, especially when scope, money or external communication changes.
Can my existing tools be connected?
Provide their names and the required workflow. Compatibility, access and any subscription requirements must be checked before an integration is confirmed. Do not send passwords in the enquiry form.
How are savings established?
Measure comparable work before and after implementation: handling time, repeated entry, correction work and outstanding requests. A demo or a projected saving is not evidence of a realised result.
Turn a requirement into a result you can verify
An example to discuss
A new enquiry needs to reach the right team member. Discuss which details are required, who owns the case and when follow-up is due. Start with one clearly defined process before involving more systems.
What should be checked before handover?
Define the input, expected output and responsible person. Test duplicate enquiries, missing information and an unavailable integration. Agree when a person must intervene and which external actions need prior approval.