Recognise the problem before buying the software
Imagine a hypothetical decorating business. One request arrives through Facebook, another by phone and a third through the website. A quote is sent, but the reminder to follow it up stays in somebody’s head. A customer calls again and the person answering cannot find the previous conversation.
That is an information and responsibility problem. A CRM can help if the business agrees how enquiries are recorded, who owns them and when the next action is due. Simply buying software will not establish those habits.
If you receive only occasional enquiries and already record them reliably in one place, a well-maintained spreadsheet and calendar may be sufficient initially. Consider a CRM when follow-up is being missed, several people share the work or the time spent reconstructing customer history is becoming a regular frustration.
Understand contacts, opportunities and tasks
A contact represents the person or business. An opportunity represents a possible piece of work. A task records an action somebody needs to complete. Keeping those concepts separate prevents a repeat customer being treated as an entirely new person every time they enquire.
For example, one contact could request a website this month and a booking connection later. Those can be separate opportunities with different scopes and decisions. Their shared contact record can retain the relevant history without mixing the value or status of the two jobs.
A pipeline shows where an opportunity stands. It is a working view, not a substitute for notes or a contract. A task such as “Call about the quote on Tuesday” is clearer than leaving the opportunity in “Contacting” indefinitely.
Start with stages that mean something
A practical starting pipeline could be: New enquiry, Contacting, Discovery booked, Quote preparation, Quote sent, and Accepted awaiting the agreed payment. Keep a separate way to record that somebody declined or is not ready.
Define each stage in a sentence. “Discovery booked” should mean a real appointment has been arranged, not that you intend to call. “Quote sent” should mean the customer actually received a proposal. A “Won” label should follow your documented acceptance and payment gate, rather than a hopeful conversation.
Service delivery may then need a separate view for onboarding, work in progress, review and completion. This keeps sales follow-up from becoming a confusing mixture of prospects and active jobs. Use only the stages the team will maintain; a complicated board that nobody trusts is not an improvement.
Capture enough information for the next conversation
Useful enquiry details might include name, preferred contact route, business or job type, a brief description, timing and the source of the enquiry. Ask which information is essential now and which can wait until discovery.
After a conversation, record the problem, the agreed next step, the owner and the due date. If a customer mentions a competitor’s website they like, note the URL and what they find useful about it. If a quote depends on another person supplying information, record who is waiting for what.
Keep private information proportionate and use an appropriate secure channel for sensitive documents. Avoid turning free-text notes into a store of passwords or confidential customer records. Agree who may view, change and export information, and what happens when a staff member leaves.
Connect the website without losing the human step
A form can create or update a contact, open an opportunity and notify the owner. But that connection must be tested through the actual form and destination. An integration switch showing “connected” is not proof that the right details reach the right pipeline.
Use an authorised fictional enquiry to check the field mapping, owner, stage and alert. Test the same person enquiring twice so you understand duplicate handling. If they book a call separately, check whether the existing opportunity advances or an unnecessary second opportunity appears.
A phone reminder does not place a call by itself. An appointment record does not guarantee availability if the business has not chosen and maintained its calendar arrangements. Define what the system does and what a person must do.
Choose software around daily use and total cost
Ask the person who handles enquiries to try the mobile view, find a contact, add a note and set a task. Check the supported connections to your existing website, email, calendars and quoting tools. Confirm what is included in the actual account tier rather than relying on a feature list.
Budget for setup, ongoing management, seats, platform costs and message or phone usage where applicable. A managed CRM has ongoing responsibilities: checking failed workflows, handling user changes and keeping the process understood. See Vemblo’s CRM and automation options and pricing guide for our scoped arrangements.
Before importing real records, agree access, recovery, retention and a practical exit/export route. A short demonstration cannot establish that a system is secure, that a migration is complete or that every connection works.
A simple weekly CRM review
- Does every open enquiry have an owner?
- Is the next action clear, with a useful due date?
- Are appointments genuinely booked and notes available?
- Which quotes need a decision or a follow-up?
- Are old opportunities still active for a reason?
- Are failed connections or duplicate records being investigated?
- Which enquiry sources led to conversations and accepted work?
Review the process with the team before adding more automation. Start by making the work visible, then automate a repetitive step once its rules are clear. Our business automation guide explains how to choose and test those steps without losing control.
Further reading
External references checked on 1 November 2026. Provider guidance may change.