Start with one real example
Take a recent quotation that became an installation or delivery. Ask which details were retyped, where an approval was lost and how a later service request found its history. These gaps help determine whether you need Sales, Trade, Field or a combination.
Name the owner of each record
A connection is more reliable when one system is authoritative for each record. Agree ownership before adding automation, and test what happens when a record changes, a sync fails or a customer returns an item.
Follow one quotation into the next team’s work
Use a representative example with a named customer, an accepted scope and a promised date. In a solar business, the handoff needs the survey, design, materials and installation plan. In trading, it needs the order lines, available quantities and delivery status. In service, it needs the site, work order, technician and evidence requirements. Record the exact information the receiving team needs before choosing an automation.
Define what completion means
A delivered line, a signed handover and a completed service visit are different business events. Decide which evidence closes each step and which role can approve it. Then test one exception: a partial delivery, unused materials returned from site, or a visit that needs another appointment. Keep financial review connected to the source record so a draft invoice does not silently become an approved payment.
Prepare a useful demonstration brief
Bring synthetic sample records, the roles involved, your current tools and the exception you want to resolve. Ask to see the record before and after the handoff, who can make a change and where the history remains. Use AI to explain the available context or prepare a draft, then review the sources and confirm as an authorized person. The linked guides help you explore the product combination and rollout sequence.