Business process automation guide
What business processes should you automate first?
Automate frequent, repeatable processes with clear rules, usable data and mistakes you can detect and recover from. Lead routing, CRM updates and routine handovers are often good starting points when ownership and exceptions are already understood. Choose one bounded process, measure the current work and prove the result before expanding.
Where to start
Find the recurring handover that gets stuck.
Short answer
A good first automation has an obvious trigger, a defined output and an owner who can explain what should happen when something goes wrong.
Start with the work people describe as “every time a request arrives, I copy this, check that and remind someone”. Look for repeated administration around a business outcome: an enquiry assigned, a record updated or a handover completed.
Define the boundary before choosing a tool. “Automate Sales” is too broad. “Turn a valid demo request into an assigned CRM lead and follow-up task” is specific enough to map, test and measure. This is the starting point for business process automation.
Write down for each candidate
- Trigger and expected output
- Inputs and the system that owns each field
- Manual steps, handovers and waiting time
- Frequency and active handling time
- Known exceptions and who resolves them
- Process owner and the result you want to improve
Remove unnecessary steps before automating the remaining ones.
Selection criteria
Compare value and readiness separately.
Use this lightweight scorecard to compare your own shortlist. Give each criterion 0, 1 or 2 using the anchors below. Add the three value ratings for a value score out of 6, and the three readiness ratings for a readiness score out of 6. These are discussion aids, not industry benchmarks or an ROI prediction.
| Criterion | Score 0 → 1 → 2 |
|---|---|
| Value: frequency | Occasional → recurring → frequent enough to create a queue or repeated daily work. |
| Value: manual effort | Little repeatable handling → some repeated work → substantial copying, checking or preparation. Use observed handling time. |
| Value: delays and rework | Little operational friction → recurring delays or corrections → a clear bottleneck affecting the next step. |
| Readiness: process clarity | Rules or ownership unclear → main path known, exceptions need work → stable steps, owner and exception routes agreed. |
| Readiness: data quality | Missing or conflicting inputs → fixable gaps → required data and reliable record identifiers available. |
| Readiness: connectivity | Access unproven → integration needs investigation → supported access and required actions verified in the systems involved. |
High value with high readiness is a strong pilot candidate. High value with low readiness needs preparation. A high score never overrides an unacceptable failure risk.
Risk gate
Check the cost of being wrong before you rank.
Short answer
Keep a candidate out of the first pilot if errors could cause serious harm, nobody can monitor it or there is no safe way to recover.
For every candidate, ask what an incorrect action would do. Creating a duplicate task and making an irreversible customer or hiring decision have very different consequences. Separate the low-risk administrative steps from decisions that need human judgement.
Agree which data can be processed, who may access it, which system is authoritative and how long operational logs are needed. If those answers are unclear, resolve them before connecting the systems.
A pilot needs a clear answer to each
- Who owns the process and checks failures?
- Can bad input be rejected before a downstream action?
- Can an incorrect action be corrected or held for review?
- What happens with missing data, duplicates and conflicting records?
- How do we pause the workflow and continue manually?
Unclear ownership, unstable rules and inaccessible data are reasons to prepare the process first.
Practical examples
Which processes are useful first candidates?
These are illustrative options, not claims about client results. Their priority depends on your volume, data and failure risk. A small, well-defined handover can be a better first project than an entire customer journey.
| Process | Start here when… |
|---|---|
| Lead routing and follow-up tasks | Form data, ownership rules and the next Sales action are clear. Send incomplete or unmatched requests to a visible review queue. |
| CRM administration | A trusted source supplies the fields and record matching is reliable. Start with a narrow update; review ambiguous matches instead of automatically merging records. |
| Marketing handovers | Entry, audience, suppression and stop conditions are explicit. Begin with an internal task or notification before adding automated customer messages. |
| Customer onboarding coordination | The trigger, checklist and owners are stable. Create tasks and reminders while keeping approvals and unusual requests with people. |
| Recurring reporting inputs | Source fields and metric definitions are agreed. Automate collection and consistency checks before automating interpretation. |
| Email or document intake | Inputs vary but the required output can be checked. Pilot extraction and review before allowing consequential writes or sending responses. |
Prioritisation in practice
Turn a shortlist into one manageable pilot.
Compare candidates against the same business objective. If the objective is more consistent enquiry follow-up, a reliable lead handover is more directly relevant than an unrelated reporting task.
01Map and simplify
Observe actual examples, including exceptions. Remove duplicate entry and unnecessary approvals. Define one trigger and one completed outcome.
02Apply the risk gate
Resolve ownership, access and recovery questions. Keep consequential decisions outside the first automatic path.
03Score value and readiness
Use the six criteria above and record the evidence behind each rating. Treat unknowns as investigation work, not optimistic scores.
04Compare total effort
Include implementation, data cleanup, testing, review, licences, API or model usage and ongoing maintenance. Prefer the smaller dependency chain when two candidates offer similar value.
05Choose a narrow first release
For example, validate one form, match the CRM record, assign an owner and create a task. Add document interpretation or wider journeys only after this path is reliable.
A frequent form-to-task handover with clean data would usually precede a complex document process with unresolved matching rules. That is an illustrative ranking, not a universal order.
Rules, AI and people
Choose the approach for each step.
Short answer
Use rules for known conditions and system actions, AI for interpretation that cannot be captured reliably by those rules, and people for consequential judgement and unresolved exceptions.
Field validation, record lookup, ownership and status changes usually belong in explicit workflow logic. AI may help extract details from a varied document, classify a free-text request or prepare a summary. Its output still needs checking.
A customer-facing message or sensitive decision may need approval even when the preparation is automated. Do not treat an AI confidence score as proof of correctness. The guide on AI vs rule-based automation explains this split in more detail.
If the input is already structured and the rules are known, the workflow may not need AI at all.
Illustrative workflow for a free-text request
Illustrative pattern, steps 1 to 5
- 01 · TriggerA request arrives
- 02 · AIExtract or classify only the unstructured information
- 03 · RulesValidate fields and look up the existing CRM record
- 04 · HumanReview ambiguous or consequential cases
- 05 · RulesCreate the approved next action and record the outcome
Case evidence · Optimile & Mobiflow
Make incoming demand actionable for Sales.
For Optimile and Mobiflow, the published case describes a HubSpot foundation with structured companies, contacts and deals, and separate sales pipelines for the two brands. Incoming website requests create a contact and lead, use round-robin assignment and create a Sales follow-up task.
The lesson for prioritisation is the handover: start where incoming demand needs a clear owner and next action. The case also shows why CRM structure and Sales adoption matter before adding more automation. It does not establish a quantified time saving or conversion uplift.
The documented website-to-Sales handover
- 01 · WebsiteRequest submitted
- 02 · HubSpotContact and lead created
- 03 · HubSpotRound-robin assignment
- 04 · HubSpotFollow-up task created
- 05 · SalesFollow-up
Case evidence · Logi-technic
Prepare complex information, then validate the next action.
Flo, the workflow built for Logi-technic, connects agency emails and supported CVs with AI-assisted extraction and assessment, prepared follow-up and Salesforce/Connexys registration. It uses n8n to coordinate the systems and checks around the interpretation steps.
The case describes existing-record lookups, validation of agency replies and routes for incomplete or conflicting information. AI supports the assessment; it does not make the hiring decision.
This is a useful example of combining interpretation with controlled execution, rather than a template to copy as an entire first pilot. For a comparable process, start with one intake or preparation step and establish review and validation before extending the workflow.
The documented Flo process
- 01 · CollectQueue incoming agency proposals
- 02 · ExtractStructure email and supported CV information
- 03 · AssessPrepare a profile recommendation and explanation
- 04 · PrepareCheck Salesforce and prepare the appropriate reply draft
- 05 · RegisterValidate agency replies and connect the relevant Salesforce records
Tool selection
Use the existing systems where they fit.
The process should decide the architecture. If the required steps can be managed clearly inside HubSpot or Salesforce, start by assessing that option. Check the capabilities, permissions and subscription available in the actual account before promising a particular workflow.
n8n is useful when the process crosses CRM, email, documents and APIs and needs orchestration between them. It does not remove the need for reliable access, validation and exception handling. Avoid adding an integration layer when the existing system can handle the bounded process adequately.
Use CRM automation for consistent records and follow-up, marketing automation for defined journeys and handovers, and AI workflows when a step genuinely requires interpretation.
Choose the smallest setup that the process and its failure paths require.
Pilot and measurement
Prove the workflow before expanding it.
Record a baseline over a period that includes normal work and known exceptions. Compare like-for-like cases after the pilot. Measure the remaining manual work as well as the steps that disappeared.
01Record the current work
Track eligible case volume, active handling time, elapsed time until the next action, errors or rework and the share needing exceptions.
02Set acceptance criteria
Agree the expected output, allowed automatic actions, review owner and conditions for stopping the pilot. Choose targets from your own baseline rather than a generic ROI claim.
03Test ordinary and failure paths
Use representative examples: missing fields, duplicate events, existing records, conflicting data, an unavailable API and unexpected documents. Check that retrying does not repeat an action unintentionally.
04Run with appropriate supervision
Start with a limited scope and review outputs. Keep failures visible, document manual recovery and confirm that the responsible team can use the result.
05Compare, adjust and expand
Review completion, quality, remaining handling time and operating costs. Expand only when the current process works and the next addition has a clear purpose.
Estimated time released = eligible cases × observed handling time removed, minus review and recovery time. This is a planning estimate, not guaranteed capacity or cash savings.
Questions about getting started
Choosing your first automation, answered briefly
- What is the best business process to automate first?
- Start with a frequent, bounded process that has clear rules, reliable inputs, an accountable owner and a recoverable failure path. Lead routing or routine CRM administration can fit, but the right choice depends on the actual manual work and data.
- How do I prioritise automation opportunities?
- Apply the risk gate first. Then compare value from frequency, manual effort and operational friction with readiness from process clarity, data quality and connectivity. Among similarly valuable candidates, prefer the one with fewer dependencies and a manageable maintenance burden.
- Should I fix a process before automating it?
- Yes. Clarify ownership, remove unnecessary steps and agree the rules and exceptions first. Automation can otherwise preserve duplicate work and repeat the same errors faster.
- Do I need AI for business process automation?
- No. Known conditions, record lookups and field mappings usually need rules. AI is useful when a step must interpret varied language or documents, and its output can be checked before it is used. See AI vs rule-based automation.
- Can I start with HubSpot or Salesforce instead of n8n?
- Yes, when the process fits the features and access available in your CRM. Consider n8n when coordination across other systems or custom integration logic is needed. Choose after mapping the process and checking the actual account capabilities.
- Which processes should wait?
- Processes with unstable rules, unclear ownership, poor data or unproven system access need preparation. Irreversible or sensitive decisions should not become automatic simply because the surrounding administration can be automated.
- How do I measure whether an automation is useful?
- Compare eligible volume, remaining handling time, time until the next action, errors and exception work against the baseline. Include implementation and operating costs. Hours released are not automatically cash savings or additional revenue.
- Can VNCK help choose a first automation in Belgium?
- VNCK works from Willebroek, Belgium. I help teams map the work between CRM, marketing, email, documents and APIs, then choose and build a controlled workflow around the systems they use. Read about business process automation or discuss your process.
Your first automation
Start with one process your team can explain.
Bring a recurring task, the systems involved and a few real examples. I can help map the handovers, challenge unnecessary steps and choose a manageable first workflow.