# Consultants CRM | Practical customer journeys | 121 > Follow a practical consultants CRM journey from first enquiry to an owned decision, with clear professional limits and useful review measures. For consultants, the useful unit of work is a considered commercial conversation rather than a volume lead. This journey follows context, qualification, professional judgement and an explicit next commitment. Consider this practical starting point: a referral email that describes a broad business problem but leaves budget, urgency and decision authority unclear. A configured CRM can keep the contact, context, owner and next action together, while the business still decides whether the consultant is qualified to help, has capacity and should progress to a paid piece of work. ## A visible commercial conversation from start to finish Fictional Northbank Advisory example. It demonstrates an operating pattern for consultants, not a customer result, professional recommendation or promise that every capability is included. ## Capabilities explained ### Companies Groups people and related information around an organisation rather than treating every person in isolation. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Helps business-to-business teams see contacts in the context of the company they work for. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Contacts Stores a person or lead with contact details, activity, ownership and related records. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Gives a team one place to understand who a customer is and what has happened. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Appointments Stores scheduled customer interactions with time, attendee, owner, status and related contact context. **How it works:** Applies configured availability, booking rules and connected-calendar settings to eligible appointments. **Why a business would use it:** Makes booked work visible alongside the customer conversation and follow-up. **Limitations:** Sync, meeting-link and resource behaviour varies by calendar type and external provider. **Human responsibility:** Staff must handle exceptions, incorrect availability and bookings that need judgement. ### Opportunities Represents a potential sale or deal linked to a contact, value, owner and pipeline position. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Shows which customer conversations are active commercial work rather than general contacts. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ### Estimates Prepares an amount for customer review before it becomes an approved billing or document process. **How it works:** Uses configured products, merchant connections and checkout rules for an eligible payment or order journey. **Why a business would use it:** Provides a controlled step between a sales conversation and a formal charge. **Limitations:** Provider fees, tax treatment, disputes, settlement and feature eligibility remain separate responsibilities. **Human responsibility:** A responsible person must approve prices and terms and resolve refunds, disputes and fulfilment exceptions. ### Documents and contracts Builds or uploads documents, collects signatures, tracks status and can include supported payment steps. **How it works:** Uses configured products, merchant connections and checkout rules for an eligible payment or order journey. **Why a business would use it:** Keeps the agreement, signers and payment journey together for operational follow-up. **Limitations:** Provider fees, tax treatment, disputes, settlement and feature eligibility remain separate responsibilities. **Human responsibility:** A responsible person must approve prices and terms and resolve refunds, disputes and fulfilment exceptions. ## What consultants actually need the CRM to hold Northbank Advisory is a fictional example used to make the workflow concrete. The aim is not to reproduce a sector package, but to show the minimum useful context for a team that needs preserve context from the first introduction through discovery, proposal and agreed follow-up. ### The customer situation Imagine a referral email that describes a broad business problem but leaves budget, urgency and decision authority unclear. Northbank Advisory records the customer’s own account before interpreting it. For this consultants team, that prevents a short message from becoming a confident but unsupported category, price or promise. ### The working record The useful record contains organisation, sponsor, referral source, problem statement, meeting notes, decision date, proposal status and next action. At Northbank Advisory, those fields must help a person respond, decide or understand the next handover; extra detail collected merely because a field exists adds risk and maintenance. ### The ownership question Northbank Advisory names the principal consultant or another responsible colleague against the next action. The Northbank Advisory shared view is useful only when the team can tell who must act, by when, and what happens if that person is unavailable. ### The decision that stays human A person decides whether the consultant is qualified to help, has capacity and should progress to a paid piece of work. On this consultants journey, CRM presents records, reminders and history without turning incomplete information or silence into approval. ## Move the consultants conversation without losing context A workable starting journey for Northbank Advisory is Referred → Discovery needed → Qualified brief → Proposal with client → Decision recorded. For consultants, each change should mean something observable to the team and customer rather than acting as a decorative pipeline label. ### 1. Capture referred For Northbank Advisory, capture starts with the source, the customer’s words and enough contact detail to reply. The first response should set a realistic expectation and ask only for information needed now; it should not imply that whether the consultant is qualified to help, has capacity and should progress to a paid piece of work is resolved. ### 2. Establish discovery needed Northbank Advisory asks the owner to check duplication and fill the smallest important gaps. Preserve context from the first introduction through discovery, proposal and agreed follow-up becomes the operating goal, rather than sending every consultants enquiry through one sequence regardless of context. ### 3. Record qualified brief At Northbank Advisory, the team records the human decision, its basis and the promised next action. If information is missing, the request names it and its reviewer; if work should stop, a clear reason is more useful than leaving this consultants record open indefinitely. ### 4. Complete proposal with client and decision recorded For Northbank Advisory, later stages preserve the customer commitment, operational handover and outcome. Its consultants team closes or defers work deliberately, records why, and gives future follow-up a date and purpose instead of keeping an undifferentiated list of old leads. ## How Northbank Advisory could use the pattern in a normal week This example uses fictional people and activity. It demonstrates how a configured CRM might support a consultants team while keeping account availability, detailed configuration and service scope subject to agreement. ### The first response Northbank Advisory receives the initial enquiry described above. The record is assigned to the principal consultant, the customer receives an acknowledgement that matches the actual response process, and the owner sees the missing information and a dated action rather than a vague notification. ### The awkward case The same week, a request outside the consultant’s competence or one involving a conflict that needs discussion before any sales activity. At Northbank Advisory, the ordinary sequence pauses while a person reviews the context and records the decision. For this consultants workflow, the failure route matters because automation should expose exceptions rather than quietly continuing. ### The handover evidence At each handover, Northbank Advisory keeps the source, time, owner, status change and next commitment. Northbank Advisory attachments or sensitive details remain only where the approved design permits them. A completed consultants task proves that an action was recorded, not that the underlying judgement was correct. ### The weekly view The team reviews referrals awaiting acknowledgement, discovery calls without a written outcome, proposals without a decision date and work declined by reason. For consultants, those measures prompt investigation rather than promise performance. They help Northbank Advisory only when stages are updated consistently, exceptions remain visible and someone corrects stale or misleading records. ## Keep the consultants workflow useful after launch The safest consultants design is modest: a small number of meaningful fields, an owner, an observable next action and a review rhythm. Northbank Advisory would test the ordinary path and the exception path before relying on either. ### Professional and operational boundary A workflow may remind and route work, but professional judgement, conflicts, scope, advice and acceptance remain with the consultant. ### Exception handling A request outside the consultant’s competence or one involving a conflict that needs discussion before any sales activity should be visible to a named person. Northbank Advisory needs a stop, escalation or manual route so that delay, missing data or unusual circumstances do not produce an inappropriate automatic message. ### Access, data and communication Use the minimum information required for this consultants journey. Confirm Northbank Advisory roles, channel consent, retention, export access and connected suppliers in the customer’s own account. Keep sensitive or formal consultants records in the approved system for their purpose rather than copying them into CRM notes. ### Review rhythm Northbank Advisory reviews the workflow twice weekly, because long gaps between discovery and proposal are easy to overlook. The Northbank Advisory review checks a representative journey, stale records, failed actions, user access and whether fields still support a real decision. Any material consultants change should be tested before it reaches ordinary customer communication. ## Frequently asked questions ### What is the most useful first CRM workflow for consultants? For consultants, start with one common enquiry from capture to a recorded outcome: Referred → Discovery needed → Qualified brief → Proposal with client → Decision recorded. Keep Northbank Advisory’s first version narrow enough that the team can name the owner, test exceptions and see where a customer is waiting. ### What should consultants avoid automating? A workflow may remind and route work, but professional judgement, conflicts, scope, advice and acceptance remain with the consultant. Consultants should also avoid automatic follow-up where consent, urgency, safety, suitability, a complaint or a vulnerable person needs a considered response. ### Which information belongs in a consultants CRM record? Use information that supports the current relationship and next action: organisation, sponsor, referral source, problem statement, meeting notes, decision date, proposal status and next action. At Northbank Advisory, detailed or sensitive information is not collected simply because a custom field exists, and an authoritative professional or operational record is not duplicated without a defined reason. ### How should a consultants team know the workflow is working? Review referrals awaiting acknowledgement, discovery calls without a written outcome, proposals without a decision date and work declined by reason. Then inspect examples behind the figures. For consultants, a dashboard can expose patterns but cannot prove service quality, causation or correct professional judgement without reliable data and human review. ## Related CRM pages - [/crm/solutions](https://121.direct/crm/solutions) - [/crm/demo](https://121.direct/crm/demo) - [/crm/features/appointments](https://121.direct/crm/features/appointments) - [/crm/features/sales-pipelines](https://121.direct/crm/features/sales-pipelines) - [/crm/guides/crm-ownership-model](https://121.direct/crm/guides/crm-ownership-model) - [/crm/solutions/coaches](https://121.direct/crm/solutions/coaches) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.