You know your clients. The strain begins when somebody else needs to help: which conversation did you promise to return to, which organisation is paying, and what can your assistant safely see? A larger contact list will not answer those questions on its own.
For a Manchester coaching and consulting practice, a useful CRM—customer relationship management system—should make the next piece of work understandable. Keep the person, the commercial conversation and the follow-up task connected without making every private coaching note part of the sales record.
Gbeya brings contact notes, tags, assigned ownership, follow-up tasks and opportunities into its workspace CRM. Begin with those practical jobs. Before putting sensitive material into a shared record, verify the exact permissions your coach and assistant will use. A record being inside a workspace is not the same as a confidential note being restricted to one colleague.
Can your assistant act without guessing?
Choose one test or appropriately sanitised client record and answer these questions without opening a private conversation elsewhere.
- Who is this person, and what is their role in the engagement?
- What is the next agreed action, who owns it and when is it due?
- Which details does this operator need, and which should remain restricted?
- Is this a prospective deal, an agreed commitment or a confirmed payment?
- Can you correct or export the necessary history without silently changing its meaning?
If an answer depends on your memory, repair that part of the workflow before importing a larger list.
This is an operational diagnostic, not a certification of permissions, privacy compliance or export completeness.
Step 1
Person and role
Who is involved and why the relationship exists.
Step 2
Operational context
The brief factual history needed to do the next piece of work.
Step 3
Owned next task
A named person, a clear action and a due date.
Step 4
Opportunity and payment
Track the commercial conversation; check received payment separately.
Link these records around the relationship. Keep sensitive coaching notes within a separately verified access boundary.
1. Give each person a record you can recognise
Start with the person you are actually communicating with. An executive, their assistant and the person approving the budget may belong to the same organisation while needing different conversations. Keep their roles clear in a short, factual note rather than assuming that a company name describes the relationship.
Use the email address the person has confirmed for this engagement and record why the relationship exists. If a client changes employers, review the existing record before creating another one. A matching name is not enough to combine two histories, and two email addresses do not automatically mean two different people.
- Why this matters
- Identity decisions determine which notes, tasks and opportunities appear together. A mistaken combination can expose context to the wrong person; unnecessary duplication can split a promised follow-up.
- Work through the example
- Suppose your client asks you to contact their new work address. Confirm the change through an appropriate existing channel, identify the old record and check linked work before making the change. Record the date and reason in the working history.
- When the approach changes
- If two colleagues share an administrative inbox, do not treat the inbox as proof that they are one person. Establish a supported way to distinguish their roles before importing their histories.
- Your decision
- Test email changes and duplicate handling with non-customer examples first. Do not promise an automatic or reversible merge until that specific workflow is verified.
2. Keep operational context useful and private detail separate
Your assistant may need to know that a programme review is due and that the client prefers an afternoon call. They may not need the personal discussion behind the review. Write the operational next step directly rather than copying a session transcript into a general note.
The UK regulator’s data-minimisation guidance links the information you keep to its purpose. Its accuracy guidance also distinguishes recorded opinions from established facts. For this workflow, date your professional interpretation, identify it as an interpretation and record what would change it. The regulator marks this guidance as under review, so check the current wording for your circumstances.
- Why this matters
- A shorter record is not automatically a better record. It needs enough context to support the task, while leaving out detail that has no justified role in that task.
- Work through the example
- Write “Send the agreed programme-review options by Thursday” rather than a speculative account of why the client has become quiet. Keep any necessary coaching reflection in a location with the right access and retention arrangements.
- When the approach changes
- A safeguarding, contractual or professional requirement may justify more detailed records. Decide that requirement deliberately; this page is not a universal retention schedule or legal assessment.
- Your decision
- Before adding a field or note, identify its purpose, who needs it and the review or deletion rule. Verify note visibility using the actual staff roles.
3. Turn a promised follow-up into an owned task
A note can preserve context without assigning responsibility. Give the next action a named owner and a date, then write the task in terms of something that can be completed. “Check client” is vague; “Send the two agreed review dates” tells the assistant what you mean.
Keep the task connected to the contact so that the person doing it can read the relevant context. If you take the work back, make the handover explicit. The point is not to populate a busy board; it is to prevent two people from assuming the other person will act.
- Why this matters
- Ownership answers who is responsible; a due date answers when the work needs attention. Neither establishes that a message was delivered or that a client accepted it.
- Work through the example
- Suppose you agree to send options on Thursday. Your assistant prepares them on Wednesday, you review them, and the task is completed after the agreed action actually happens. Record a failed send as unresolved rather than treating preparation as delivery.
- When the approach changes
- For a solo practice, a light weekly list may be enough. Add handover steps only where another person or a meaningful risk makes them useful.
- Your decision
- Use one accountable owner per next action, with a clear completion condition and an explicit reassignment when responsibility changes.
4. Separate relationship status from this particular opportunity
A returning client can be discussing a new consulting project while remaining a client of your existing practice. The person’s relationship stage and the new project’s deal stage answer different questions. Moving one should not erase what you already know about the other.
Likewise, a commercial agreement and a recorded payment are different events. Keep the opportunity value, the agreed scope and the payment record separate. If you work in more than one currency, review values by currency unless you have an explicit conversion method; adding unlike amounts produces a number that cannot explain the business.
- Why this matters
- The contact holds the continuing relationship; the opportunity describes one possible piece of work. Payment evidence belongs to the financial record rather than a manually chosen sales label.
- Work through the example
- A client who already bought coaching asks about a £3,000 leadership workshop. Track the workshop as a separate opportunity. An accepted proposal does not mean the £3,000 has arrived, and an older paid booking is not payment for this new workshop.
- When the approach changes
- A very small practice with one offer may not need a deal for every routine repeat booking. Use opportunities for decisions that require qualification, scope or follow-up.
- Your decision
- Require a specific payment record before describing an opportunity as collected revenue. Preserve the client relationship when a separate proposal is declined.
5. Rehearse a real handover before moving the whole practice
Choose a small set of ordinary situations: an active coaching client, a new enquiry, a declined proposal and somebody who should not receive marketing. Walk through the next task for each. Use test records, not genuine confidential session content, while you check access.
Ask the assistant to explain what they would do from the record without a separate verbal briefing. If the explanation is wrong, improve the record or the workflow before adding more fields. Review the export and correction process as well as the attractive contact screen; your working history needs a way to remain understandable over time.
- Why this matters
- A handover is a practical test of whether the information supports the work. It reveals missing context and permissions that a populated dashboard can hide.
- Work through the example
- Give the assistant a test contact with a dated follow-up and a separate restricted-note requirement. Confirm that they can complete the operational task without seeing information outside their role. If the current permissions cannot support that boundary, change the design before real use.
- When the approach changes
- A fully shared partnership may agree a different visibility model. That does not remove the need to document it and test that access behaves as agreed.
- Your decision
- Expand only after identity, visibility, follow-up and export checks pass for your actual roles. Record any missing control as a specific implementation requirement.
Useful context is more valuable than a larger record
The case for a shared record is practical: another person can understand the next task without asking you to reconstruct the relationship. That is an operating goal, not a claim that a CRM automatically improves revenue.
Professional coaching standards emphasise confidential handling of records, including work done by support personnel. That changes the design question from “Can the team see everything?” to “What does this person need for this task?” The standard applies within its professional scope and does not certify a software product.
An academic study of 288 Taiwanese IT-service firms reported relationships between CRM adoption, customisation capability and effectiveness, with strategic alignment relevant to the relationship. It is useful context for evaluating fit; its abstract does not establish what a small Manchester coaching practice will earn or save.
Our recommendation is therefore narrow: build a record around the decisions your team makes, and test the handover. Add information when it makes those decisions more reliable. Remove duplication and unnecessary detail when they make the record harder to use.
High confidence in separating identities, tasks, commercial status and payment evidence. The benefit for your own practice remains something to measure.
Before relying on the workflow, demonstrate what each staff role can see, how duplicate records are corrected and what the export contains. Review currencies separately unless a defined conversion method is in place.
Plan the first working sample
Start with twelve records, not the entire address book
Suppose you choose twelve test or appropriately sanitised records representing the work your assistant will handle. Allow five minutes per record to check identity, ownership and the next action, then thirty minutes to rehearse access and a handover.
12 × 5 minutes + 30 minutes = 90 minutes of planned review time.
These are planning inputs, not measured savings. A complicated history or unresolved access model can take longer; a simple practice may need fewer examples.
Keep the sample small enough to inspect carefully and varied enough to reveal different responsibilities.
Assumptions worth checking
A complete CRM contains every conversation.
It contains the context needed for its purpose. Sensitive detail needs an appropriate access model, and a copied conversation may be less useful than a clear agreed action.
An experienced assistant can infer the next step.
Experience does not reveal an agreement that was never recorded. Write the commitment, owner and date so that a reliable handover does not depend on guesswork.
A client label proves that this new project has been paid.
The relationship can be established while a new opportunity remains unpaid. Check the actual order or payment for that particular commitment.
Your next 30 days
Days 1–7
Define the minimum useful record
List the decisions your assistant makes and the information each requires. Agree note boundaries and one set of stage definitions.
Ready for the next step: Every proposed field has a purpose and an access decision.
Days 8–14
Rehearse with a small sample
Run the twelve-record example with test or properly sanitised information. Check duplicate identity, assignment and task completion.
Ready for the next step: Both operators can explain the next step from the same record.
Days 15–21
Check the difficult cases
Verify role visibility, corrections, exports, suppressed contacts and separate deal/payment states. Log missing controls for implementation.
Ready for the next step: The workflow handles these cases without hidden manual assumptions.
Days 22–30
Adopt and review
Move the approved subset, keep a clear correction route and review unresolved tasks each week. Compare missed or ambiguous handovers with your own baseline.
Ready for the next step: The working record supports the actual job and the team knows how to correct it.
Questions before you proceed
Does a CRM replace confidential coaching notes?
Not automatically. First decide what belongs in the operational record and what needs a more restricted location. Verify the actual staff permissions before storing sensitive detail.
Can one client have more than one opportunity?
A continuing relationship and a particular proposed engagement are distinct. Gbeya’s opportunity model links deals to a contact; test the exact workflow you will use for parallel engagements.
Should I put every person from an old spreadsheet into the CRM?
Review purpose, accuracy and communication status first. A larger import is not evidence that the records are appropriate or usable. Consent and suppression require separate checks.
Can I assume two matching names are duplicates?
No. Confirm identity and linked work before combining anything. A common name or shared inbox is not sufficient evidence, and reversible merge behaviour must be verified.
Does moving a deal to Won confirm a payment?
No. A sales-stage change records a commercial status. Confirm payment through the relevant financial record before counting collected revenue.
How do I know the CRM is helping?
Measure a workflow you care about: unresolved handovers, tasks without owners or time spent reconstructing context. Use your own before-and-after records, with the same definitions and period.
Sources and further reading
Prepared by Gbeya · Sources reviewed 30 October 2026.