A won deal and a completed job mean different things
Sales marks an opportunity as won. Operations still needs to arrange delivery, assign people, handle changes and confirm completion. If everyone shares one status field, “complete” can mean a signed agreement to one team and finished work to another. Adding more stages to the sales pipeline may obscure both meanings.
Give the work a distinct identity when it has its own dates, permissions, history or completion rules. One customer can have several jobs; one job can require several visits. That calls for linked records that preserve those relationships. Those records may still live inside the CRM. A separate lifecycle does not automatically require a separate application.
Here, an operational platform means software in which people assign, perform and verify work, such as installations, fulfilment or service delivery. It might be a CRM extension, a packaged application, an ERP module or custom software. Start with the work you need to represent, then choose where it belongs.
Check what your existing products can actually do
CRM products can support more than contacts and sales opportunities. HubSpot, for example, documents custom objects with their own properties, pipelines and links to other records. Availability and limits depend on the subscription, and managing those objects requires the appropriate permissions. Check the documented capabilities of your actual account before treating a missing screen as a reason to build.
Also test a ready-made operational product. Microsoft documents work orders, scheduling, mobile tools and inventory capabilities in Dynamics 365 Field Service. Its work orders and bookings have separate lifecycles. Products like this may already represent the work your team is trying to squeeze into a deal record.
Ask the supplier to show the whole task using representative data and the intended user roles. Being able to add a field is only part of the test. The team must be able to find the next action, apply the right rule and recover when the normal sequence changes. Include licences, configuration, integrations, administration and ongoing support in the comparison.
A hypothetical installer: one sale, several pieces of work
Imagine an equipment installer wins an agreement covering two customer sites. The first site needs one visit; the second needs an initial visit and a later inspection. A technician finishes at the first site while a missing part delays the second. The customer account is unchanged and the sale remains won, but delivery is only partly complete.
For this example, keep the account and agreed commercial scope in the CRM, with a linked work order for each site and separate visit records. Operations owns scheduling and delivery status. The inventory system remains responsible for stock movements, and the finance system for invoices. This is a proposed division of responsibility to test, not a mandatory software architecture.
Sales needs a useful summary, such as “one site complete, one awaiting a part”, with a link to the work. It does not need another independently editable copy of every visit. Operations needs enough customer context to do the job without changing the agreed price by accident.
Use these cases in the product demonstration
| Case | What the system must represent | Evidence to ask for |
|---|---|---|
| One agreement covers two sites | Separate work at each site, linked to the same customer and agreement. | Open each work order from the customer record without duplicating the customer. |
| One visit is complete, another is delayed | Visit status, site-level completion and overall delivery remain distinguishable. | The summary shows unfinished work and identifies the person responsible for the next action. |
| A technician records a result | The technician can update assigned work but cannot change the commercial terms. | Sign in as that role: the permitted result should save, and a commercial-term change should be rejected. |
| An accepted job changes | A revised scope has an approver and a visible effect on the affected work. | Change the quantity and show who approves it, which tasks change and what history remains. |
| A delivery update reaches the CRM late | The customer view identifies when its information was last updated. | Show the delay, the responsible operator and how a corrected summary reaches the CRM. |
Choose the option your team can operate
Extend the CRM when its supported records, workflows and permissions handle the exercise clearly, and your administrators can maintain the configuration. Keeping work in one product may reduce the number of handovers, but custom rules still need an owner and checks when they change.
Use a packaged operational application when its core model already fits the work. Test configuration and integration before committing to custom development. If finance, stock or purchasing already works in an ERP, first examine its relevant modules and supported connections. Recreating those functions in a new platform adds responsibilities that may have little to do with the gap you need to close.
Consider a focused custom layer when an essential part of the workflow remains awkward or unsupported after those checks. Name the exact gap: perhaps a distinctive allocation rule, an approval spanning several systems, or a task interface that existing tools cannot adequately support. Specify the smallest complete workflow to build and who will maintain it. “We want one screen” is not enough to justify replacing the systems behind it.
Agree which system may change each fact
For every shared record, write down where it is created, who may change it and which value wins if two systems disagree. In the installer example, a corrected site address might belong to operations while an account billing address belongs to finance. A single label such as “customer address” would hide that distinction.
Keep stable links between the customer, agreement, work orders and visits. Decide which summaries should be copied to the CRM, how current they must be and where a failed update is investigated. These rules matter whether the connection uses a packaged connector or custom code. The integration article below covers the reliability questions in more detail.
Leave the evaluation with a specific decision
Bring a sales owner, an operations owner and the person who administers the existing software to the same demonstration. Use a representative completed job and an exception, with sensitive information removed. Record what the product demonstrated, what needs configuration and what remains an unproven promise.
The output should name where each record will live, who can update it, which work remains manual and what the first implementation includes. If a critical case is unresolved, test that case before committing to a broader build. A useful boundary lets each team work with a clear view of the customer and a reliable account of what still needs doing.
Sources and further reading
Define where your operational work belongs.
Bring one delivery workflow, the systems involved and the exceptions that cause extra work. We can help define what fits your existing tools and what needs a focused extension.
Discuss your operational workflow


