If your tools work individually but staff keep copying data between them, investigate an integration first. If the tools cannot represent how the work happens, a different application or a custom system may be needed.
Buying another platform before mapping the process can leave you with one more place to maintain the same information. Start with a real task, such as an enquiry becoming an order.
Map one task from beginning to end
Write down who starts it, where the information comes from, who approves it and how the next person knows it is ready. Include exceptions: a customer changes an address, an order is cancelled or a required document is missing.
For each field, identify the source of truth. If the CRM and store both hold a customer’s address, decide which can update it and when. Connecting systems without that agreement can spread conflicting information faster.
Choose the smallest change that covers the workflow
| Situation | Option to investigate |
|---|---|
| The tools work, but data is copied manually | Integration between existing systems |
| A common workflow is missing | Configure a ready-made application |
| Customers or partners need a shared process with specific rules | Custom software or a portal |
| Nobody agrees how work should happen | Define the process before building |
Two different project examples
For Podbase, product data and variants reach the Webflow website from an internal system. The need was to connect existing tools.
Rentclub required a platform connecting car dealers, customers and banks, with applications and staff workflows. That scope called for shared business software. These are different problems; the existence of spreadsheets alone does not decide which solution fits.
What an integration quote should cover
- Which records and fields are transferred, and in which direction.
- Whether updates happen immediately or on a schedule.
- How duplicates, missing fields and conflicting edits are handled.
- What happens when a provider is unavailable.
- Who receives an error notification and can retry the task.
- Who maintains the connection when either system changes.
A successful demonstration with one record is not enough. Test changes, cancellations and interrupted transfers as well. Check what access and subscription level the providers require before committing to a solution.
How to decide whether the work is worthwhile
Record the current task volume, time spent and recurring errors. Compare that with the build and maintenance effort. Use your own figures; there is no universal number of saved hours that makes every integration worthwhile.
Start with one complete workflow and agree what improvement you will measure. For wider ownership and permissions problems, read when to replace spreadsheets. For implementation options, see business software and integrations.
Tell me what you’re considering. I’ll help you weigh the options.
I build websites and business software, and help teams make product and technology decisions.
