Carry the customer relationship beyond the sale.
The next team needs the customer, agreed scope and delivery owner—not another round of questions. ORQESTRA’s CRM design connects that handover to the opportunity.
CRM integration is in development. The examples show the intended customer view and handover; connected sales workflows are not yet available for production use.
From Northwind’s won opportunity to delivery.
A salesperson has won Northwind’s onboarding work. Follow the shared customer into the pipeline and handover to see which record identifies the account, what was agreed and who takes responsibility next.
Illustrative workflow. The customer stays the same as you move through Sales, Finance and Work.
Northwind Traders
Enterprise Record · ORQ-CUST-1042
One customer identity connects each view. Source access still applies.
A win becomes an accountable handover.
The proposed sequence, from the starting event to the confirmed result.
Qualify the opportunity
Capture the customer, owner, decision-makers, value and next action in the sales pipeline.
Explore the capability.
The planned CRM experience connects pipeline activity to a shared customer identity. Its focus is the handover from a commercial commitment to the people responsible for delivery and billing.
Identify the customer once
Link company and contact records to the same Enterprise Record. A trading name or email address can help a match, but ambiguous records need review before they feed another system.
A customer may also be a supplier. Those roles belong to the same business identity; separate contacts retain their own records.
Connected information.
Clear responsibility.
The target design links information across these systems. Each retains responsibility for its own transactions or content.
Define the first
working scope.
Scope one process before committing to a rollout. Agree these requirements and verify the workflow with the people who will use it.
Our implementation approach- Define the sales event that starts a handover.
- Agree customer matching and ownership rules.
- Map the finance and delivery context the team needs.
- Validate access for sales, service and account owners.
Before you connect the work.
Can we keep our existing CRM?
That requires an integration assessment. CRM-XT is the planned CRM engine. Bring the records, permissions and actions your existing CRM needs to support.
Can one customer have accounts in several companies?
The data model separates a shared customer identity from company-specific financial accounts. A multi-company workflow must verify each mapping and preserve company and currency context.
How should conflicting customer details be resolved?
The planned stewardship process compares source evidence and applies field ownership rules. Possible duplicates require review; matching and conflict resolution are not yet available as a production workflow.
What does delivery need to know when a deal is won?
Describe the process, systems and decision-makers involved. Use the enquiry to identify scope, dependencies and what must be demonstrated before use.