CRM & ERP Implementation
One system the whole team actually uses — instead of five they half-use.
Picking, setting up, and moving into a single system that runs the business — with honest advice about which one you need, and whether you need one at all.
No obligation. No jargon. Plain English.
Sound familiar?
- The answer to a customer question depends on who picks up the phone.
- Your customer list lives in a spreadsheet, an inbox, a phone, and a notebook — and none of them agree.
- Someone sold you a system, you paid for it for a year, and the team quietly went back to the spreadsheet.
- You can't tell how much work is in the pipeline without asking three people and adding it up yourself.
Do we actually need one of these?
Maybe not, and that is a real answer rather than a polite one.
A CRM — the customer relationship management system that remembers every customer and every conversation — earns its place when the business has outgrown one person’s memory. The usual signs are concrete. Two people give a customer two different answers. A quote goes out and nobody follows up because it was never anywhere except an inbox. You cannot see what is in the pipeline without asking around. Someone leaves and takes half the client history with them.
If none of that is happening, a well-kept spreadsheet that the whole team actually uses is a perfectly respectable operating system for a small business, and we will say so. The worst outcome here is not staying on the spreadsheet. It is paying for a platform, half-adopting it, and ending up with two versions of the truth.
Which system should we pick?
The simplest one that covers the next few years.
There is a ladder. At the bottom sit all-in-one small-business platforms — GoHighLevel is a common one — which bundle contacts, pipeline, messaging, and follow-up into a single subscription that works reasonably well the day you turn it on. In the middle sit platforms like HubSpot, which start small and scale up as you do. At the top sit enterprise systems like Salesforce and full ERP platforms — enterprise resource planning, meaning one system that runs operations, inventory, purchasing, and finance alongside customers.
The enterprise tools are not bad. They are built for organizations with dedicated administrators and a budget for configuration, and a small team that buys one generally pays for a great deal of capability it never switches on. We recommend the tool that fits the business, and we are happy for that to be the cheap one. Choosing well is mostly about being honest regarding how much complexity you will realistically maintain.
Why do these projects fail?
Adoption, nearly every time. Not the software.
A system fails when using it is slower than working around it. Too many mandatory fields, stages that use vendor vocabulary instead of yours, no clear moment when the old way ends. So we cut the required fields to what genuinely needs to be there, name the stages the way your team already names them, train in short bursts on the handful of daily tasks that matter, and set a cutover date that everyone knows about in advance.
The second failure mode is a bad migration. Spreadsheets accumulate years of shorthand — the same customer entered three ways, dead accounts, notes in a column nobody can explain. That gets cleaned and de-duplicated properly, loaded into a test copy first so you can look at your own data before it counts, and anything ambiguous gets flagged for a person rather than guessed at. Migrations are messy work and we would rather do them slowly than confidently.
Who owns it at the end?
You do, completely. Accounts in your name, billed to you, with you holding administrator access from day one. Your data stays exportable. The configuration, the field definitions, and the reasoning behind both get written down and handed over.
We are a new firm and we say that plainly, so the only thing we can offer instead of a long client list is a setup that does not trap you. If you decide next year that someone else should run this, everything they need is documented and nothing needs our permission.
What's included?
Done-for-you. We build it, connect it to what you already use, and stay until it's running the way you'd run it yourself.
- A short discovery that decides whether you need a CRM — customer relationship management, the system that remembers every customer and every conversation — or whether your current setup is genuinely fine
- Honest platform selection: the simpler, cheaper tool where it fits, and an ERP-class platform — enterprise resource planning, one system tying operations, inventory, and finance together — only where the business really needs one
- Configuration around how you already sell and deliver, rather than the vendor's default demo setup
- Data migration from spreadsheets, inboxes, and whatever the last system was — cleaned, de-duplicated, and checked before it goes live
- Staff training in short sessions, aimed at the handful of things each person actually does daily
- An adoption plan with a defined cutover date, so the old spreadsheet stops being an option
- Written documentation of how the system is set up and why, in your accounts, under your ownership
How does it work under the hood?
The short version: real, named mechanisms doing specific jobs — no magic. Open this up if you're the skeptic, or if you have a technical friend who's going to ask.
Show me how it actually works
The tool matters far less than the setup, and less again than whether people use it. A CRM — the customer relationship management system that holds every customer, quote, job, and conversation in one place — only pays for itself when it becomes the single source of truth. A half-adopted one is worse than a spreadsheet everyone actually uses, because now you have two records of reality and no way to tell which is current. So the first question we ask is not which platform, it is whether the business is ready to commit to one place. If the honest answer is no, we say so, and we'd rather talk you out of it than bill for it.
Platform selection is where most of the money gets wasted. There is a real ladder here. At the simpler end sit all-in-one platforms built for small businesses — GoHighLevel is a common example — which bundle the customer list, pipeline, messaging, and follow-up into one subscription with sensible defaults. In the middle sit platforms like HubSpot, which grow with you and integrate widely. At the far end sit enterprise systems like Salesforce, and full ERP-class platforms — enterprise resource planning, meaning one system that ties operations, inventory, purchasing, and finance together rather than just customers. Enterprise tools are excellent and genuinely necessary for some businesses. They are also configurable to the point of being a project rather than a purchase, and a small team that buys one usually ends up paying for capability it will never turn on. Our default recommendation for a small business is the simplest platform that covers the next few years, not the one with the most impressive feature list.
Configuration is the part that decides adoption. A platform out of the box models a generic business, and your pipeline stages, job types, and required fields are not generic. We map how work actually moves — first contact, quote, scheduled, delivered, invoiced, follow-up — and build the stages to match the words your team already uses. Then we cut. Every required field is a small tax on the person entering data, and a system with forty mandatory fields gets filled in with junk. We keep the required set short enough that entering a record honestly is faster than working around it.
Migration is messy, and anyone who tells you otherwise has not done one. Spreadsheets carry years of accumulated human shorthand: the same customer spelled three ways, phone numbers in four formats, notes in a spare column nobody remembers adding, records for businesses that shut down years ago. We extract, standardize, and de-duplicate against a defined match key — usually phone and email — then load into a test environment first so you can look at your own data in the new system before it is real. Some records will not survive the trip cleanly, and we flag those for a human decision instead of guessing. The old spreadsheet gets archived, read-only, rather than deleted; nobody should have to trust a migration on faith.
Adoption is the hard part, and it is mostly not technical. Training happens in short sessions focused on the five things a given person does every day, not a tour of the whole platform. There is a named cutover date after which the old system is no longer where work gets recorded, because a soft transition with no deadline reliably becomes a permanent dual-entry burden. And the accounts are yours from the first day — signed up in your name, billed to you, with you as administrator. We document the configuration, the field definitions, and the reasoning, so another competent person could take it over. If we disappeared, you would still own your system, your data, and the instructions.
What's the return?
We measure every engagement in the same three currencies — dollars, customers, and hours of your day. Here's what this one pays back.
Quotes stop being forgotten and jobs stop being invoiced twice, because everyone is working from the same record.
Dollars
Nobody falls through the gap between the first call and the signed job, since the next step lives in the system rather than in someone's memory.
Customers
The weekly ritual of reconciling three lists to work out where things stand stops being a job anyone has to do.
Hours of your day
What changes, in practice?
One ordinary moment in your week, before and after. Illustrative, not a client case study.
Before
A six-person commercial cleaning company. Quotes live in the owner's sent folder, the customer list is a spreadsheet somebody last tidied in spring, and scheduling is a whiteboard photographed each Monday. When a client calls asking why last month's extra visit was not on the invoice, three people search three different places and nobody finds it.
After
Every client, contract, site, and past visit sits in one system the team opens each morning. The extra visit was logged against the site when it happened, so the answer takes twenty seconds. New staff are useful in their first week because the information is in the system rather than in the owner's head.
Questions owners ask us
We bought a CRM before and nobody used it. Why would this go differently?
Because the failure was almost certainly setup and adoption, not the software. Systems get abandoned when they demand more data entry than they give back, when the fields do not match how the team talks, and when there is no date after which the old way stops. We fix all three deliberately — short required fields, your language on the stages, and a real cutover — and if we do not think your team will commit, we will tell you before you buy anything.
Do we need Salesforce?
Probably not. It is genuinely powerful and some businesses need exactly that, but for a small team it is usually a configuration project rather than a purchase, and you end up paying for capability you never switch on. We would rather put you on the simplest platform that covers the next few years and leave you room to move up later than sell you the biggest name.
What happens to everything in our spreadsheets?
It gets cleaned, de-duplicated, and loaded into a test environment so you can inspect your own data in the new system before anything goes live. Records that cannot be resolved cleanly get flagged for a human decision rather than guessed at. The original spreadsheets get archived read-only, not deleted.
How disrupted will we be during the switch?
There is a real dip, and we plan around it rather than pretending it away. Migration and configuration happen in the background, training runs in short sessions, and the cutover is scheduled for a quieter stretch of your calendar. The honest expectation is a slower fortnight, not a lost quarter — and if your busy season is coming, we would rather wait.
If we stop working with you, are we locked in?
No. The accounts are created in your name and billed to you, with you as administrator. Your data is exportable, the configuration is documented, and the reasoning is written down. You are a customer of the platform, not of us — walking away should cost you nothing but the conversation.
Who does this work best for?
It fits most businesses that sell time or appointments — but here's where it pays back fastest.