Name the missing behavior
Watch the task in practice. If staff simply copy approved information between tools that already fit the work, an integration may be enough. If they need different calculations, approvals or ways to act on records, investigate what a custom interface would add.
Consider a quote process. Sending form details into a CRM is primarily a connection. Guiding a customer through measurements, validating combinations and preparing a staff-reviewed estimate may require custom behavior. Start with that distinction before discussing tools.
Check what the existing tools can do
Confirm what the current platforms can do, which interfaces they provide and who controls access. An existing feature may solve the problem with configuration. A supported integration can be easier to maintain than a custom connection that depends on undocumented behavior.
Also examine the limits. A system may accept a new contact but not the product context or assignment the team needs. Test the receiving record and its next action before treating the connector as a solution.
Compare the work of maintaining each option
An integration still needs ownership, error handling and review when an external service changes. Custom software adds responsibility for its interface, permissions and release process. Neither is maintenance-free.
Compare the recurring work as well as the initial build. Who will update field mappings, handle an expired connection or investigate a failed estimate? A lower initial cost can become expensive if every ordinary exception requires a developer to intervene.
Combine approaches where they fit
A hybrid approach is often practical: a small custom form or workspace uses existing customer and project systems behind it. This can give people the interaction they need without creating another authoritative customer database.
Define the first release around one task and its exceptions. An estimator might support one product category and send a reviewed result to the existing CRM. A portal might begin with file collection and status visibility while billing stays in the established system.
- Use configuration when the platform already fits the task.
- Use integration when the main gap is a reliable handoff.
- Use custom development when the workflow needs new behavior.
- Name the record owner when combining approaches.
Test an ordinary case and an exception
Ask for a demonstration using an ordinary case, an incomplete request and an unavailable destination. Inspect the final record, the user’s explanation and the recovery path. A screen recording of the successful case cannot show whether the system is operable.
Make the decision on the fit of the workflow, the dependencies and the team’s ability to maintain it. Document what remains manual in the first release. Give any remaining manual step a named owner and include it in the demonstration.
