CRM for relationship-led businesses

A relationship-led business needs to see its continuing customer relationship and the separate work within it. Give each potential purchase, service request and follow-up its own owner and outcome so colleagues can act without treating every conversation as a new deal.

Set the customer boundary

If an existing customer discusses a purchase for one site while reporting an unresolved service issue, keep the opportunity and service request as separate work items linked to the same customer context.

Give each item a distinct purpose

These are working distinctions, not a requirement for four separate products. Create another opportunity when a customer has a separate purchase decision that can have its own outcome.

Update the existing opportunity when a conversation changes the proposal already under discussion. Keep a service issue visible to its responder even while sales discusses new work with the same customer.

HubSpot documents associations among company, contact, deal and ticket records. Descriptive association labels require a Professional or Enterprise subscription. Pipedrive can link activities to people, organisations and deals.

Its Projects feature supports work after a sale, but it is not a substitute for deciding how an active service request will be owned. Projects is included on Premium and higher plans and is a paid per-user add-on on Lite and Growth.

Key CRM Features by Platform (Australia Focus)

Preserve context without merging work

A long relationship may continue while one purchase decision pauses or ends. Record a genuine waiting reason and review point on the opportunity. Closing that opportunity should leave the customer account and any service work intact.

Place an observation on the account when it applies to the wider relationship. Put a proposal change on the relevant opportunity, and a service commitment on the service item. Check where activities appear before relying on automatic links: HubSpot's rules depend on the activity and how it was logged.

If an introduction leads to new work, record it against that enquiry or opportunity when known. A later opportunity for the same customer may have a different referrer. Keep an unconfirmed source marked as unconfirmed.

Link related work without combining it

In HubSpot, associations work in both directions and can link different record types or records of the same type. For example, a service ticket can be associated with the contacts involved in a complaint and with a deal those contacts are also discussing.

Use those links to make relevant history findable, not to imply that every person or activity belongs to every item. A contact may be associated with more than one company, and a ticket may relate to a deal, but each work item should still retain its own purpose and owner. Before adding a link, ask whether the connection will help someone understand or act on that item.

Activities need particular care because appearing on one timeline does not guarantee they appear on every related record. In HubSpot, one-to-one emails, meetings, notes and calls are eligible for automatic association, but the records must already be associated when the activity is created or logged. Check the relevant timelines after logging important customer context.

HubSpot's default rules can associate a company activity with its five most recent associated open deals, or a contact activity with their primary company and five most recent associated open deals. These are defaults, not a guarantee that every relevant item will receive the activity. Manually associate an activity when the people who need its context would otherwise miss it.

Keep response work distinct from delivery work

Keep post-sale delivery work, such as onboarding or implementation, separate from an active service request that needs a response. Assign each item its own owner.

Check a customer story

Consider an existing customer with an open service issue, a proposal for one site and a later introduction to another team. A sales colleague and a service colleague should each be able to find their work, its owner and the context needed to act. Closing one deal should leave the other work visible. If information repeatedly lands on the wrong record, clarify the record rule before adding fields.

A practical check is to follow one real interaction through the records. Find the customer relationship, the specific purchase decision or service request, and the activity that explains the latest commitment. Confirm each item has a clear owner and the activity is visible where the next person needs it.

Pipedrive activities can be linked to projects as well as people, organisations, leads and deals, so a delivery activity can sit with the project it advances.