Pipeline Design
Part of CRM for relationship-led businesses
Keeping service relationships separate from new-business deals
Separate service obligations from sales deals while sharing the customer context each team needs.
Keep service obligations and new-business deals as separate work under the same customer relationship. A service item needs a response or resolution owner; a deal needs a purchase decision and sales outcome. Connect them where one affects the other, but do not use a deal stage for an unresolved customer problem.
Give each kind of work its own outcome
An account can show the continuing relationship. A ticket or case can track a request or problem; a project may track agreed delivery work.
An opportunity tracks a proposed new purchase. A task assigns an action within any of these processes. The available record types depend on the CRM and any separate service system.
For example, a customer might report a fault while discussing an upgrade. The fault remains service work even if it shapes the upgrade discussion. The upgrade becomes an opportunity when there is a distinct potential purchase. Link the relevant records or references so sales can see the unresolved issue and service can see a commercial promise that affects its work.
| Question | Service work | New-business deal |
|---|---|---|
| What finishes it? | A response, resolution, transfer or other agreed service outcome | A won or lost purchase decision |
| Who acts now? | The service owner or receiving specialist | The deal owner or next sales participant |
| Which date matters? | The promised response or service review | The customer decision or sales review |
These are operating distinctions; a CRM does not enforce them without the relevant process and setup.
Service Work vs New-Business Deal: Key Differences
- What finishes it?
- A response, resolution, transfer or other agreed service outcome
- Who acts now?
- The service owner or receiving specialist
- Which date matters?
- The promised response or service review
- What finishes it?
- A won or lost purchase decision
- Who acts now?
- The deal owner or next sales participant
- Which date matters?
- The customer decision or sales review
Pass the context that affects action
Give sales the service item’s reference, current owner, status and customer-facing commitment when those facts affect a proposal. Give service colleagues the approved scope or promise that affects their work. If a complaint concerns the proposed scope, identify who will answer it and whether the proposal must wait.
The account owner need not own every service item. When a deal is won, confirm that the receiving team accepted any required delivery hand-off; a won stage alone does not show that operational work began. Keep the service item’s status and owner independent of the deal’s outcome.
Check the available structure
HubSpot documents associations among companies, contacts, deals and tickets. Its help desk is documented for Service Hub Professional and Enterprise; eligible users can create tickets with a ticket pipeline and status and associate a company or contacts. Seats and permissions affect access to particular help desk features.
Pipedrive’s Projects feature supports post-sale delivery work linked to customer and deal context. It is included on Premium and higher plans and is a paid per-user add-on on Lite and Growth. Neither example establishes that a particular organisation’s service process has been configured.
Check what each team can find with its normal access. HubSpot may associate some activities automatically, depending on their type, logging route and existing associations. Seeing an activity on an account does not establish that it appears on the intended ticket or deal.
CRM Setup Checklist: Separating Service from Sales
- Confirm CRM supports tickets, deals, projects and tasksVerify HubSpot Service Hub Professional/Enterprise or Pipedrive Premium+ access
- Ensure service items are not tracked as dealsAvoid using deal stages for unresolved issues; use tickets or cases instead
- Link records where needed, but maintain independenceUse references or associations to connect service and sales work without merging outcomes
- Review team access levels and permissionsEnsure service and sales teams see only what they need—no over-access to unrelated records
Review a difficult customer case
Consider a customer with an open complaint, a pending renewal and a proposed upgrade. The service owner should be able to find the complaint and promised response. The deal owner should be able to see which purchase is affected. Closing one item should leave the others with their own status, owner and next action.
If staff use deals to track routine support requests or close deals to signal service resolution, clarify the record and hand-off rules. The connected customer view should preserve each item’s distinct outcome.
Handling a Customer with Multiple Interactions
- Identify open complaintService owner tracks issue via ticket; status and commitment remain visible
- Track pending renewal and upgrade proposalDeal owner manages opportunity independently; scope linked to service context
- Share relevant context across teamsSales receives service item reference and status; service sees commercial promise
- Close one item without affecting othersEach record retains its own status, owner and next action—no cross-contamination
