Choose a process, not a collection of tools
Copying an enquiry into a second system, chasing missing details and assembling the same report every week are candidates for improvement. The first step is to observe the work from start to finish. Sometimes the best change is removing a duplicate form or agreeing who updates a record.
Write down the trigger, information required, action and exception. “When an enquiry arrives, create a task for the right person” is a clearer starting point than “automate sales”. It also makes it easier to establish whether the change worked.
Make the boundaries explicit
| Question | Example answer to agree |
|---|---|
| What starts it? | A completed, valid enquiry form, rather than every keystroke. |
| Which record is authoritative? | The enquiry record owns contact details; staff can correct them there. |
| What happens once? | Create one follow-up task, even if the form is submitted twice. |
| When must a person decide? | An ambiguous request goes to a review list rather than an automatic quote. |
| How is failure noticed? | A named person sees failed tasks and can retry them safely. |
These are illustrative requirements. Your rules may differ, particularly where the action affects money, availability or a customer’s access.
Use the smallest intervention that fixes the handover
A built-in workflow in an existing tool may be enough. Where two systems can exchange data, an integration can remove retyping. A bespoke tool becomes relevant when the workflow has important rules or shared information that the current products cannot represent.
Read what an API integration needs to get right before assuming two systems can be connected. Available endpoints, permission levels, export limits and subscription terms affect feasibility. An API logo on a supplier’s website does not establish that it supports the particular action you need.
Our custom software service covers operational dashboards and workflow tooling when a tailored application is justified.
Keep a human route through exceptions
A customer can change their mind halfway through a process. An email address can be wrong. An external service can be unavailable. Decide how staff pause an automation, correct the input and resume work without sending duplicate messages or losing the original request.
- Keep a useful activity history showing the action, outcome and reason for failure.
- Separate a successful internal action from a successful notification; an email problem should not erase the underlying request.
- Limit access to the records needed for the task, and remove access when it is no longer required.
- Give the process a named owner who understands the business rule and can review exceptions.
Measure saved work honestly
Count the current effort before the change: how often the task happens, how long it takes and how frequently somebody has to correct it. After a trial, compare completed work and exception-handling time. A workflow that saves typing but creates a large manual review queue may not be an improvement.
For example, a task taking ten minutes on twenty occasions represents 200 minutes of handling time. That is an illustration, not a promise of savings. Subtract the time still needed for checks, corrections and maintenance when judging value.
Separate website care from operational development
If the need is ongoing website monitoring, visibility and optimisation, Sitewell is the related service to explore. If the work requires a new internal tool or substantial changes to business logic, discuss it with Digizu. Existing lead follow-up guidance may help when the problem is responding consistently to new enquiries.
Map an admin problem with us
Bring one process that is taking too much time, the systems it touches and the exceptions staff currently resolve. We can work out whether automation is the appropriate next step.