CRM and automation: track prospects, quotes and follow-ups

• Find an enquiry’s source and history
• Assign follow-ups to the right person
• Measure response times and sales, from contact to customer

The need often appears before choosing software: several people call the same prospect, nobody knows whether a quote was sent, or management counts sales manually. We start with these concrete situations to map an enquiry’s route from arrival to conclusion. At every stage, someone should know what to do and be able to find the necessary information.

The first deliverable is a map of the intended process: contact sources, sales stages, progression criteria and permitted actions. A support request does not follow the same path as an annual contract. Mixing them in a single ‘prospects’ column makes indicators difficult to interpret.

A CRM can complement WordPress, Shopify, another CMS or a bespoke application. It does not automatically replace the public website, its editorial pages or its SEO. A CMS migration addresses a different decision, which we can handle within the same project if necessary.

The right solution depends on user numbers, sales stages, access rights and software already paid for. We first examine what your environment can do. Native automation may be enough to transfer a form; it will be less suitable for several databases with conflicting rules. The choice includes export options and the cost of functions actually needed.

On a small screen, scroll the table horizontally.

HubSpot, Pipedrive, Zoho, Odoo or an existing solution can be considered according to suitability. This list describes technical possibilities; it implies no partnership or certification claimed by Gloria. Actual compatibility is checked during scoping.

Consider a fictional renovation company. Its enquiries come from the form, phone calls and referrals. The salesperson receives an address, project type and sometimes photographs. The problem is not collecting more data: it is finding the record, checking the service area and organising the next step without losing context.

The proposed journey creates or finds a record, retains the known source and places it at the ‘need to confirm’ stage. A rule can suggest an owner based on the area. After the salesperson validates it, the enquiry moves to ‘visit to arrange’, then ‘quote sent’. Every open opportunity has a next-action date. An out-of-scope enquiry receives a separate status instead of inflating the opportunity count.

Automation prepares tasks and transfers information. The professional remains responsible for the diagnosis, price and commitments made to the customer. Before enabling an external follow-up, we approve its text, trigger, exclusions and stopping rule when a reply arrives. This scenario is a demonstration, not a client reference or a result already achieved.

‘Follow up quotes’ is not precise enough to automate. A prospect may have replied by phone, requested more time or declined the project. The scenario below extends the fictional renovation-company example: it shows the information to retain and the decision left to the salesperson.

The opportunity record shows an owner and a next action

Illustrative record R-024: bathroom renovation, visit completed, quote version 2 sent, owner ‘assigned salesperson’, next action ‘check for a reply before calling’. The sending date, last interaction and timeframe agreed with the prospect are separate fields. A new quote replaces the previous one in tracking; it does not trigger a second series of reminders.

On a small screen, scroll the table horizontally.

An unrecorded call can make follow-up inappropriate: the process must account for it

A connector does not know what was said on a phone unconnected to the CRM. The procedure therefore explains how to record a call, a reply received elsewhere or a postponement request. In this scenario, follow-up is initially an internal task requiring human approval. Any automatic sending requires additional scoping: approved copy, permitted channel, exclusions, stopping rules and delivery checks. Automations remain capable of being disabled.

Testing sends the same enquiry twice, changes the quote, records a reply before the due date and interrupts the connection. The report must allow the team to find one opportunity, the correct version and the reason a task was cancelled or blocked. History retains actions useful for diagnosis without unnecessarily copying confidential documents.

If this workflow is included in the quote, deliverables comprise the rule sheet, fields to complete, test scenarios and recovery procedure. CRM licences, integrations and maintenance are identified separately. The benefit is checked by tracking quotes without a next action and the time spent finding their status, then the actual sales decisions obtained.

Contact migration is prepared using a representative sample. We identify essential fields, obsolete data and possible links between a person, company and opportunity. A shared email address is not always enough to identify a customer; an uncertain match must be reviewable before merging.

The mapping document explains where contact details, notes, statuses, dates and attachments will go. It also specifies what will not be migrated. Retaining a complete history can take more work than importing a contact list: export limitations and the destination software’s capabilities are therefore checked before commitment.

We plan a backup, trial import, volume checks and verification of authorised or anonymised real records. Priority rules are written down: which system is authoritative for an address, status or amount? Correcting a field must not be undone by the next exchange between systems.

Initial workflows often concern incoming enquiries, task creation, stage changes or transfer of an approved record. For each, we describe the trigger, conditions, action and stopping cases. A cancelled appointment must not keep generating reminders; a form submitted twice must not create two identical opportunities.

Depending on the need, we use the software’s functions, an automation platform or a custom API connection. Important exchanges have error monitoring and a recovery procedure. The owner must be able to know that a transfer failed rather than discover weeks later that an enquiry disappeared.

Access is limited to necessary data. Test and production environments are separated where tools allow; private keys remain on the server. Commercial messages, data processing and retention periods are scoped for your context. Installing a connector does not, by itself, make the entire organisation compliant.

Before deployment, we record a baseline over a representative period: time to first response, proportion of enquiries with an owner and next action, data-entry time, records without updates and conversion of relevant opportunities into customers. Definitions remain identical after launch. Comparing a quiet month with a seasonal peak without adjustment would produce a misleading conclusion.

Illustrative calculation: 200 monthly records each require four minutes of re-entry. Reducing this to one minute would free up ten hours per month. Time spent checking, handling exceptions and administering the system must be deducted from this potential gain. A freed-up hour is available capacity; it becomes a financial saving only if it genuinely reduces an expense or enables additional useful work.

To assess return on investment, we compare observable gains with configuration, training, licence and maintenance costs over the same period. The dashboard distinguishes observed gains from assumptions. An increase in sales also depends on the offer, demand and sales work; it is not automatically attributed to the CRM.

Acceptance testing follows working situations: a new enquiry, an existing contact, a change of owner, a lost opportunity, a reopened record and a departing user. We also test a missing field, a duplicate and an interrupted connection. A successful demonstration is not enough if nobody knows how to recover a blocked record.

You receive operating rules, an access list, field mappings and a guide to routine operations. The people concerned check screens using their own tasks: finding information, preparing a reminder, exporting an authorised list and viewing their indicators. Problems found during this trial are corrected before wider rollout.

Launch can start with one group or a single workflow. Acceptance criteria, the approver and conditions for returning to the previous setup are fixed in advance. After handover, we specify who administers users, changes rules and monitors alerts, with optional maintenance defined in the quote.

To price your project, we need to know your tools, user numbers, data volume and two or three representative journeys. Complexity comes from rules, historical-data quality, permissions and integrations. The number of screens or contacts therefore does not fully describe the work required.

The quote distinguishes analysis, configuration, data migration, automations, testing and onboarding. It identifies software subscriptions and possible variable costs: automation operations, storage, messages or APIs. Accounts and exit terms are agreed so you can recover your data and documentation.

The website starting prices of €290, €590 and €990 excluding VAT concern standard scopes; they do not include a bespoke CRM deployment. You continue to register, pay for and renew the domain, with initial connection available from Gloria. Hosting and maintenance are defined separately. Describe your current sales process to scope a measurable first phase.

Do we need to change our CRM to automate?

Not necessarily. We first check its functions and exchange capabilities. An existing tool can be simplified and connected to the website. Changing becomes appropriate if significant limitations cannot reasonably be resolved.

Can we start with a single automation?

Yes. Transferring website enquiries with an owner and a next action often makes a concrete first phase. It allows data, usage and measurement to be tested before expanding the scope.

Are all follow-ups sent automatically?

We choose the level of automation with you. Some messages remain drafts or tasks to approve. Planned sending must have stopping rules, exclusions and an identified owner.

Who owns the licences and data?

Account holders, administration rights and export options are specified in the quote. Licences remain subject to the software publisher’s terms. Handover includes the agreed documentation and access.