Compare work your team already repeats
An exporter or manufacturer can begin automation in sales, support, finance or operations. Start with repeated work: copying inquiry details, finding specifications, entering invoice fields or compiling order milestones. For each task, identify the source material, processing steps, final result and responsible person.
The following are workflow illustrations using fictional data, not client results. Imagine a company comparing three tasks:
- Sales inquiry preparation: use customer emails and current product files to organize models, quantities and open questions. Produce a draft; sales staff confirm prices and lead times.
- Finance document checks: use invoices and purchase orders to match references and compare fields. Produce a discrepancy list; finance staff verify differences and decide on approval.
- Order-status reporting: use order sheets and confirmed updates to group milestones. Produce follow-up tasks; coordinators check missing or conflicting messages.
Compare source availability, field consistency, result checks and exception ownership. A high inquiry volume does not automatically make sales the best starting point. If the product catalog is outdated but purchase records are reliable and finance can supply reference answers, document comparison may be the better first pilot.
Record one complete task as it happens today
Follow a task through the current process. Include source searches, waiting, corrections and handoffs, as well as data entry. A quickly generated inquiry draft still creates work if a salesperson must verify every sentence; count that review time.
Choose normal, incomplete, duplicate and conflicting examples. An inquiry may lack a destination, an invoice may have no matching purchase order, an update may arrive late, or two product files may disagree. Record who resolved each case, which source they used and what they corrected. Leave unconfirmed fields open instead of filling them with guesses.
This record becomes the baseline and later acceptance material. Use consistent definitions before and after. If volume, sample difficulty or staffing changes, record the difference instead of attributing every change to automation.
Give the first pilot a clear finish line
Consider a fictional X20 inquiry asking about packaging and lead time for 1,000 units. One testable scope extracts the model, quantity, questions and source references, then prepares a review draft. Missing destination and unsupported lead time appear as open items.
The pilot can end when a salesperson receives the record, draft and follow-up task. The salesperson still decides on the external quote and sending. This scope tests retrieval and result quality. A wider company plan can still cover customer records, order tracking, support lookups and finance handoffs in later stages.
Define the pause points too. Who resolves conflicting sources? What happens when a connection fails? How does rejected output return to the existing process? Agree on those paths alongside the normal steps.
Write acceptance checks before building
Acceptance should describe observable behavior. For inquiry preparation, check:
- The model, quantity and customer questions match the original email.
- Product details cite a current source, and missing information stays unresolved.
- Duplicate messages are identified without duplicate follow-up tasks.
- Drafts wait for an authorized reviewer, and rejection prevents sending.
- After an interruption, completed steps can be checked before recovery.
Keep some examples out of development and use them for final acceptance. Record the full preparation, review and correction time, plus exceptions still handled manually. Passing a few ideal examples demonstrates those examples, not every possible business case.
Prepare a one-page discussion brief
A finished technical specification is not necessary. Use one recent sanitized task to answer six questions:
- Current steps: who receives the material, checks which sources and hands it to whom?
- Inputs: which inbox, spreadsheet, document or business system supplies the current version?
- Output: do you need a structured record, reply draft, discrepancy table or follow-up list?
- Human decisions: who confirms quotes, lead times, accounting entries, payments or external sending?
- Exceptions: are fields missing, records duplicated, versions conflicting or permissions unavailable?
- Ownership: who accepts the result, receives failures and maintains the sources?
For integration discussions, name the tools and access owners. Do not send passwords, keys or sensitive customer records.
Use the result to plan the next stage
Review the pilot and baseline with its actual users. Include corrections, source maintenance, failure handling and provider costs before deciding to continue, revise or pause. If a critical source is unreliable, improve that foundation first.
When expanding, reuse confirmed field definitions and review responsibilities, but assess each new system’s access, exceptions and acceptance separately. Handover should explain operation, stopping, recovery and ownership, with maintenance scope documented. A pilot tests the design and working relationship; a company-wide plan still connects sales, support, finance and operations in stages.