Email Marketing
CRM setup that your team actually uses
A well-set-up CRM shows you every lead, where it came from and what should happen next. We configure your CRM with a pipeline that mirrors how you sell, segmentation that keeps messages relevant, and workflows that stop leads slipping through.
Who it is for: Businesses tracking leads in inboxes and spreadsheets, or paying for a CRM that nobody trusts because the data inside it is a mess.
Everything in this service
- Pipeline stages that mirror how you actually sell
- Lead capture connected from forms, ads and email
- Source tracking, so you know which marketing produces customers
- Segmentation by behaviour, value and lifecycle stage
- Task and follow-up workflows for the sales team
- Data cleanup and migration from your current mess
What to expect
- Every lead visible, owned and followed up
- Marketing judged by which sources become customers
- One system of record your team trusts
How crm setup actually works
Decide the data model before you choose the tool
Most failed CRM projects were tool decisions made before anyone had agreed what they were recording. The questions that need answering first are basic and rarely written down. What counts as a lead. What is the difference between a lead and an opportunity in your business. Do you sell to individuals, to companies, or to individuals within companies, because that changes the shape of everything. Does one customer have several ongoing pieces of work at once. What do you need to know about a customer that a generic system will not have a field for.
The answers give you a structure: the records you keep, how they relate, and the small set of fields that genuinely drive decisions. Small is the operative word. A field earns its place if someone acts on it, reports on it, or segments by it. Fields added because they might be interesting one day are the reason CRMs fill with blanks, and a form with thirty optional fields will be completed badly or skipped entirely.
Getting this right first means the tool becomes a straightforward choice rather than a gamble. It also means migration is possible later, because you know what you are moving. Choosing a platform first and shaping the business around its defaults is how teams end up with a pipeline that fits nobody and a set of statuses that no two people interpret the same way.
- Define lead, opportunity and customer in your own terms first
- Decide whether you sell to people, companies or both
- Keep only fields someone acts on, reports on or segments by
- Optional fields fill with blanks and undermine trust in the data
- Structure first makes tool choice and later migration far easier
Lifecycle stages that mean something
Pipeline stages are where CRMs most often drift into fiction. The usual fault is stages named after what your team is doing rather than what the customer has done. Contacted, following up and nurturing all describe your activity and can be true for months without anything changing. They also mean whatever the person updating the record wants them to mean.
Stages defined by customer actions are unambiguous and produce useful forecasts. Enquiry received. Qualified against agreed criteria. Meeting held. Proposal sent. Verbally agreed. Won or lost. Anyone can tell which stage a deal is in without a discussion, and movement between stages reflects real progress. Attach entry and exit criteria to each one, in a sentence, so nobody has to guess.
Keep the number small. Seven stages is usually plenty and many businesses need five. Every extra stage adds a judgment call and a chance for records to sit in the wrong place. Add a defined set of lost reasons too, because knowing that a third of losses are on price and a third are timing is more useful than any other report the CRM will produce, and it is free if the field is a short list rather than a text box.
- Name stages after customer actions, not your activity
- Give every stage written entry and exit criteria
- Five to seven stages is usually enough
- Use a fixed list of lost reasons, not free text
- Stages that require interpretation produce forecasts nobody trusts
Routing, ownership and response time
The most valuable thing a CRM does for many businesses is make sure a new enquiry has an owner within minutes rather than sitting in a shared inbox while everyone assumes someone else has it. Speed of first response is one of the strongest predictors of whether an enquiry converts, and it is almost entirely a process problem.
Routing rules should be explicit: who gets what, based on service, territory, size or source, and what happens when that person is unavailable. Every record has one owner, because shared ownership means nobody feels responsible. Every owner has a next action with a date, since a lead with no next step is a lead that will be forgotten. And there should be an escalation path so an untouched enquiry surfaces to someone else rather than quietly ageing.
The reporting that follows is where the argument between marketing and sales usually gets settled. Time to first contact, number of attempts before giving up, and conversion by owner and by source turn opinions into observations. It is worth agreeing in advance what those numbers will be used for. Used to improve the process, they are extremely valuable. Used to blame individuals, they guarantee the CRM stops being updated honestly, which is a far more expensive outcome.
- Assign every new enquiry an owner automatically, within minutes
- One owner per record, always
- Every open record needs a next action with a date
- Escalate untouched enquiries rather than letting them age
- Use the reporting to fix process, not to blame people
Hygiene, duplicates and the slow rot
CRM data degrades continuously. People change jobs and email addresses, companies are acquired or renamed, and the same person enters your system three times through a form, an event list and a manual entry with a slightly different spelling. Left alone, a database becomes something the team works around rather than from, and once trust is gone it is very hard to restore.
Prevention beats cleanup. Validate at the point of entry, so obviously wrong email addresses and phone numbers are caught immediately. Use consistent formats for names, phone numbers and company names, ideally enforced rather than requested. Check for existing records before creating new ones. Prefer selection lists over free text for anything you will report on, because free text produces six spellings of the same answer and no usable report.
Then run maintenance on a schedule. Merge duplicates, mark bounced addresses so they stop being emailed, archive records with no activity for years rather than deleting them, and review the fields that have quietly fallen out of use. This works when one person owns data quality with time allocated for it. It fails when it is everyone responsibility in principle and nobody in practice.
- Validate at entry, it is cheaper than cleaning up later
- Check for existing records before creating a new one
- Use selection lists over free text for anything reportable
- Merge duplicates and retire bounced addresses on a schedule
- Give data quality a named owner with allocated time
Adoption is the actual deliverable
A perfectly configured CRM that the team avoids is worth nothing. Adoption is not a training issue at the end of the project, it is the thing the project is for, and it is won or lost in how the system fits the working day.
People avoid a CRM for consistent reasons. It takes longer than the old method. It asks for information they do not have at that moment. It duplicates something they already typed elsewhere. It shows them nothing useful in return. Or it feels like surveillance rather than support. Each of those has a fix. Fewer required fields. Automatic capture from email, calendar and forms so less is typed. Views that give a person their own day rather than a management report. And being straightforward about what is measured and why.
The rollout matters too. Involve the people who will use it while the pipeline is being designed, since they know how the sale actually works. Start with a smaller system than you think you need and add once the routine is established, because it is far easier to add a field than to remove one people have got used to ignoring. Train on the daily routine rather than the feature list. And have the team commit to using it as the only record, because a CRM that runs in parallel with a spreadsheet is a CRM in the process of being abandoned.
- Design with the people who will use it, not for them
- Reduce typing with automatic capture from email and forms
- Give each user a view that helps their day, not a management report
- Launch smaller than feels right, then add
- A parallel spreadsheet means the CRM is already losing
Connecting the CRM to the rest of the business
A CRM earns its keep when it is the single place someone can look to understand a customer. That means connecting it to the systems where customer activity actually happens: website forms, email marketing, advertising platforms, the checkout or booking system, invoicing, and support.
The connection worth prioritising is source tracking, because without it marketing spend is judged on enquiry volume rather than on revenue. Capturing where a lead came from, and carrying that through to won business, is what allows you to say which channel produces customers rather than which produces the most form fills. Those are frequently different, and the difference usually changes where budget goes.
Two cautions. Keep the direction of data clear, so each system has one authoritative source for each piece of information and you do not end up with two versions fighting each other. And be deliberate about what you sync, because pushing everything everywhere creates copies of customer data in places nobody has thought about. Connect what serves a decision or an action, document what flows where, and leave the rest alone.
- Connect forms, email, ads, checkout, invoicing and support
- Prioritise source tracking through to won revenue
- Give every piece of data one authoritative system
- Sync what serves a decision, not everything available
- Document what flows where, for your own review later
Migrating from spreadsheets and inboxes without losing anything
Most CRM projects are migrations rather than fresh starts, and the existing data is usually spread across a spreadsheet, several inboxes, someone phone, and a previous system nobody has logged into for a year. The migration is where projects lose weeks and confidence, and a clear method prevents that.
Take stock first: where the records are, how many, and how good. Then decide what actually moves. A five-year-old list of unqualified enquiries is not an asset, and importing it means starting your new system with a large volume of dead weight and email addresses that will bounce. Moving active customers, live opportunities and genuinely engaged contacts is usually the right scope, with the remainder archived somewhere accessible rather than imported.
Clean before importing, not after, because a bad import creates thousands of records to fix by hand. Standardise formats, deduplicate, and map old fields to new ones deliberately rather than accepting a default match. Import a small sample first and check it carefully, then run the full load. Keep the original files untouched as a fallback. And set a hard date after which the old method stops being used, because two systems running in parallel is how migrations quietly fail.
- Inventory every place records currently live
- Move active data, archive the rest rather than importing it
- Clean and deduplicate before the import, never after
- Test with a small sample before the full load
- Set a firm cut-off date for the old system
A clear path, step by step
- 01
Map how you sell
Your real sales process, drawn out first, so the CRM fits it rather than fighting it.
- 02
Configure and connect
Pipeline, fields, sources and integrations set up, existing data cleaned and imported.
- 03
Automate the follow-up
Assignments, reminders and lifecycle workflows, so no lead sits untouched.
- 04
Train and embed
Your team trained on a simple daily routine, because an unused CRM is worthless.
Why choose us for this
We configure around your sales process, not a template
Adoption is the deliverable: we train until the team uses it
Independent advice on which CRM fits your size and budget
Common questions
Which CRM should a small business use?
One your team will actually open daily. For most small teams that means a simple, affordable tool over an enterprise suite. We recommend based on your process, team size and the tools it must connect to, and we have no reseller ties.
We have a CRM but nobody uses it. Can you fix that?
Usually, yes. Non-use almost always means bad setup: too many fields, a pipeline that fits nobody, dirty data. We strip it back to what the team needs, clean the data and rebuild the routine around it.
Explore related work
Want this for your business?
Book a free visibility call and I will tell you honestly whether I can help.
How this is delivered
One person leads every project. Where a job genuinely needs a specialist, I bring in people I have worked with before and manage them, so you get one point of contact and one invoice rather than three suppliers blaming each other.
- You talk to the person responsible for the work, not an account manager
- Specialists are briefed and managed by me, and their work is checked before it reaches you
- One contract, one invoice, one place to chase