When is it worth analysing your processes?
You do not need to know which tool to buy or what to automate. It is enough to see a recurring problem that makes work harder. For example:
- The same data is entered several times — from a message into a spreadsheet, then into the sales system.
- Cases wait despite your team’s efforts — information, a decision or a clear handover is missing.
- Corrections take too much time — errors in orders, quotations or documents resurface at later stages.
- You do not know where to start — departments report different needs, and it is hard to judge which change will bring the greatest benefit.
We examine the actual work, from the first message or document to completion. We can start with order processing, quotations and job costing or purchase invoice checks.
What do you receive after process analysis?
You receive a report with a process map and recommendations. We discuss it with you to help select the first step. It includes:
- A map of the current process. Activities, responsible people and systems, highlighting where work stops or needs correcting.
- An assessment of the problem’s scale. Case volumes, working time and common errors. We distinguish measured data from estimates.
- Improvement proposals and priorities. A comparison of options, from existing tool settings and working practices to integrations or a new solution.
- A cost-benefit assessment. Expected results, implementation and running costs, and the assumptions used in the calculations.
- A plan for the first improvement. Scope, responsibilities for people and systems, and how to check the result. If implementation is recommended, we also describe how to handle unusual cases.
We may recommend an existing feature, a change to working practices or postponing investment. The report helps you decide what to do and whether implementation is needed.
Illustrative extract from a process map — fictional data
This extract covers order intake at a trading company, from the customer’s message to order confirmation.
| Step | Who and which system | Output | Where work stops or returns |
|---|---|---|---|
| 1. Receive the order | Customer service, email | Message and attachments assigned to the customer | A missing order number makes resubmissions hard to identify |
| 2. Match products | Customer service, ERP and product-reference spreadsheet | Lines linked to product records | The customer’s description matches several variants; clarification is needed |
| 3. Prepare the order | Customer service, ERP | Draft with quantities, units and prices | An unclear pack-to-item conversion needs checking |
| 4. Check availability and lead time | Sales, ERP; purchasing or production if stock is short | Information about a possible fulfilment date | Some stock is reserved; replenishment timing needs confirmation |
| 5. Confirm to the customer | Customer service, email | Confirmation of quantity, price and timing sent | Changes to quantity or timing return to the ERP check |
We add measurements or estimates of working time, waiting time and exception frequency. These help determine which stage to improve first. This extract illustrates how a process is described; it is not the result of a client analysis.
How much does process analysis cost?
We match the scope to the problem you want to solve. Prices and timescales are indicative; we agree the exact price before work starts.
Single-process analysis helps when you know which part needs improvement, such as order intake. It includes a process map, a cost-benefit assessment and a change plan.
An area review covers 2–3 related processes, such as the journey from a quotation request to an order. It helps assess dependencies, set priorities and select the first improvement.
| Option | Price excluding VAT and timescale |
|---|---|
| Single-process analysis | £730–£1,160 2–3 weeks |
| Area review | £1,160–£1,740 3–5 weeks |
Analysis is more than a list of automation ideas. We measure or estimate the number of cases and handling time, estimate the payback and design a solution that takes account of your company’s systems and data. After the analysis, you know what implementation may cost and whether it pays off. If you commission implementation within 30 days, we deduct the full analysis price from the implementation price.
The first implementation after a review can cover one selected process.
How do process analysis and mapping work?
- We agree the scope. We discuss the problem, its consequences and the expected result. We select one process or several related processes, then agree the scope and price.
- We learn how daily work happens. We talk to the people doing it, work through example cases and examine documents and systems. We include situations needing further clarification or decisions.
- We compare options and discuss recommendations. We show what is worth changing, what conditions must be met and what results are possible. We discuss costs, sequencing and questions relevant to your decision.
The timescale mainly depends on how quickly we can speak to the people doing the work and gather sample documents.
Illustrative situation: order processing
An order arrives by email. An employee checks products and prices, then enters the data. Analysis shows how long each stage takes and where waiting occurs.
50 orders a day at 5 minutes each, over 21 working days, represent 87.5 hours a month. Analysis identifies the share spent on data entry, checking information and handling exceptions. Only then do we estimate how much work can be reduced.
If retyping takes the most time, automation may help. If product identification causes delays, names, references and records need organising first. The cause determines the improvement. This is an illustrative situation, not a client project.
Who carries out the analysis?
DO IT GLOBAL carries out the analysis. Your project has one lead who knows the agreed requirements and can lead subsequent implementation. Recommendations account for working practices, system capabilities and change costs. During implementation, we connect solutions to ERP systems, databases, email and business applications.
Our analysis draws on over 20 years of IT experience in requirements analysis, system design, programming and implementation. Learn more about DO IT GLOBAL’s experience.
How do we assess whether a change is worthwhile?
We compare current work with how it could look after improvement. We include processing time, corrections, waiting, implementation and maintenance costs. Where precise data is unavailable, we provide a range and explain what it depends on.
Time recovered lets your team handle other tasks or more cases. Financial savings arise, for example, from reduced overtime or avoiding additional recruitment. We assess these benefits separately to avoid counting the same result twice.
What happens after the analysis?
The decision is yours. You can use the recommendations yourself or commission implementation. If you choose to work with us, we prepare a proposal with scope, price and outcome checks. After launch, we can also provide maintenance and further development.