Service

CRM and sales systems

The system of record for revenue: where leads land, how they are routed, what happens next, and whether anyone can see the truth of the pipeline.

Most CRM problems are not tool problems. They are the result of a system configured to mirror an aspirational sales process rather than the one the team actually runs, with the predictable consequence that people stop updating it and the pipeline report becomes fiction. The fix is rarely a different product.

We design the process first, configure the tool to match it, automate the parts that are pure administration, and make sure the reporting reflects something a director can act on.

Why this is worth doing properly

The value of a CRM is entirely dependent on data discipline, and data discipline is a design problem. Every required field a salesperson cannot answer at that stage is a field that will be filled with nonsense or left blank, and a handful of those is enough to make every downstream report untrustworthy.

The second issue is fragmentation. A business will typically have leads arriving from a website form, a paid campaign, a phone call, a WhatsApp message and a conference badge scan, each landing somewhere different. Consolidating those into one pipeline with source attribution intact is usually worth more than any feature of the CRM itself.

Marketing attribution also lives or dies here. If closed revenue is never written back against the original source, then every channel decision is being made on ad platform self-reporting, which systematically double-counts. The CRM is the only place the honest number can exist.

Where this work usually goes wrong

Configuring for the process you wish you had

A nine-stage pipeline in a business that really has four stages will be worked around within a month. Model what people actually do, then improve it deliberately rather than by fiat.

Too many required fields

Every mandatory field is a tax on the person entering it and a source of garbage data when it is unanswerable. Require the few that reporting genuinely depends on and make the rest optional.

No routing rules

Leads that arrive without an owner sit unworked. Assignment should be automatic and time-bound, with escalation when nobody touches a record, because speed to first contact is one of the few consistently reliable predictors of conversion.

Migrating dirty data

Importing a decade of duplicated, half-populated records into a new system reproduces the old problem in a more expensive tool. Deduplicate and decide what is worth carrying before the migration, not after.

Reporting nobody trusts

Once a pipeline report has been visibly wrong twice, people revert to spreadsheets and the CRM becomes an expensive contact list. Trust is recovered by making the data entry burden small enough that the records stay accurate.

What this covers

CRM strategy and consulting
What the system needs to do, which process it should encode, and whether you need a new tool at all.
Custom CRM development
A bespoke system where an off-the-shelf product genuinely cannot fit the process, which is less often than vendors imply.
CRM setup and configuration
Pipelines, stages, fields, permissions and automation configured against the agreed process.
GoHighLevel implementation
Full build including funnels, calendars, pipelines, automation and sub-accounts for agencies and multi-location businesses.
Customer database management
Deduplication, enrichment, field hygiene and a defined owner for data quality.
Lead capture systems
Every inbound path — forms, calls, chat, WhatsApp, events — writing into one place with source intact.
Sales pipeline development
Stage definitions with entry and exit criteria that a manager can apply consistently.
Lead assignment and routing
Automatic ownership by territory, product or round-robin, with time-bound escalation.
Automated sales follow-ups
Sequenced follow-up that continues until someone replies or the sequence exits, rather than depending on memory.
Appointment booking systems
Calendar booking connected to real availability, with reminders and no-show handling.
Quote and proposal automation
Generated documents from CRM data, so pricing is consistent and version confusion disappears.
Customer onboarding workflows
The handover from sale to delivery, automated so nothing depends on an internal email being read.
CRM integration with websites and advertising
Forms and ad platforms connected both ways, including offline conversion feedback for optimisation.
Existing CRM migration
Moving from one system to another with deduplication, field mapping and a verified record count.
CRM dashboards and reporting
Pipeline, conversion by stage, source attribution and forecast accuracy in one place.
Sales-process optimisation
Finding the stage where deals actually stall and changing something specific about it.

How the work runs

Delivery sequence The delivery sequence for crm & sales systems, in order. Each phase is described below. 01 Map the realprocess 02 Design stages andfields 03 Consolidate leadcapture 04 Automate theadministration 05 Migrate and verify 06 Train and handover
The delivery sequence for crm & sales systems, in order. Each phase is described below.
  1. Map the real process

    Sit with the salespeople and record what actually happens between an enquiry and a signature, including the parts that are not supposed to happen. This is the artefact everything else is configured against.

  2. Design stages and fields

    Stage definitions with objective entry criteria, and the minimum field set that reporting requires. Every proposed required field has to justify itself against the cost of collecting it.

  3. Consolidate lead capture

    Every inbound route wired into the CRM with source and campaign preserved, so attribution is possible and nothing arrives in a personal inbox.

  4. Automate the administration

    Assignment, follow-up sequences, reminders, quote generation and onboarding handoffs. The target is removing clerical work, not removing judgement.

  5. Migrate and verify

    Deduplicate, map fields, import, and then verify record counts and spot-check values against the source. A migration is not finished when the import completes.

  6. Train and hand over

    Documentation and working sessions with the people who use it daily. A system nobody was trained on is a system that will be worked around.

What you receive

You probably need this if

What we build and work with

We are not tied to a vendor. The right CRM depends on your process, your budget and who administers it after we leave.

HubSpot
Strong where marketing and sales need to share one record and reporting matters more than deep customisation.
GoHighLevel
Efficient for agencies, multi-location and service businesses that need funnels, calendars, SMS and pipelines in one subscription.
Pipedrive
A good fit where the requirement is genuinely sales pipeline management without a marketing suite attached.
Custom build on PostgreSQL and FastAPI
Where the process is genuinely unusual and licence costs at seat volume exceed the cost of building.
Zapier and n8n
Integration glue between the CRM and everything else, with n8n self-hosted where data residency matters.
Calendar and booking integration
Availability, routing and reminders wired to the calendars people actually keep.
Offline conversion APIs
Closed revenue fed back to Google and Meta so ad optimisation targets money rather than form fills.

What changes once this is in place

One pipeline, one truth
Every lead source lands in the same system with attribution intact, so the pipeline report stops being contested.
Nothing sits unworked
Automatic assignment with time-bound escalation, which usually produces the single largest conversion improvement available.
Less administration per deal
Quotes, reminders and onboarding handoffs generated rather than typed, returning selling time to salespeople.
Marketing spend judged on revenue
Closed-won data written back to the ad platforms, ending the reliance on platform self-reported conversions.
A system your team will actually use
Field requirements kept to what reporting genuinely needs, which is what keeps the data trustworthy.

How this differs by market

The work is the same craft everywhere. What changes is the law, the language and the buying culture — and those change enough to matter.

European Union

A CRM is a processing system under the GDPR, which means a lawful basis for each contact, a defined retention period, and the ability to fulfil access and erasure requests without a manual hunt through five systems. Where the vendor stores data outside the EU, transfer mechanisms need documenting rather than assuming.

Nordics

Data residency questions come up more often here than elsewhere in Europe, and several supervisory authorities have been active on transfers. Where residency is a genuine blocker, a self-hosted CRM or an EU-region deployment is the practical answer and should be scoped at selection rather than discovered at procurement.

United States and Canada

State privacy laws create consumer rights to access and delete that the CRM has to be able to serve. Canada’s CASL means consent status must be a first-class field on the record, since mailing a contact without documented consent carries real penalties.

United Arab Emirates

The federal PDPL applies to mainland entities, while DIFC and ADGM have their own regimes for companies established there. WhatsApp is a primary sales channel for much of the region, so a CRM that cannot log WhatsApp conversations against the contact record is missing most of the sales history.

Not legal advice. Regulatory summaries on this site describe how we scope and build, and are current to our latest review. Verify the operative text with qualified counsel in the relevant jurisdiction before relying on it.

How we know it worked

The measures that matter are speed to first contact, conversion rate between defined stages, and forecast accuracy against actual closed revenue. All three are properties of the process, and all three become measurable only once the data is trustworthy.

We capture a baseline for each before configuration changes, because the most common false claim in CRM work is that a new system improved conversion when what actually changed was how conversion was counted.

Forecast accuracy is the honest long-term measure, and it takes two or three quarters to read. We would rather report it late and correctly than early and flatteringly.

Estimates are labelled as estimates. Any figure on this site that describes a range is a planning estimate with its assumptions stated, not a measured client outcome. We do not publish client results without the client's permission and a date.

Questions

Do we need a custom CRM?

Usually not. Off-the-shelf products cover most processes, and a custom build means you own the maintenance forever. It is justified when licence costs at your seat count exceed build cost, or when the process is genuinely unusual — and we will tell you when it is not.

What does it cost?

Configuration projects are quoted fixed against a defined scope. Custom development is quoted per phase. Software licences are paid by you directly to the vendor; we do not resell them at a markup.

How long does a migration take?

Typically four to eight weeks for a mid-sized business, with most of the time spent on data cleaning rather than on the technical move. Dirty source data is the usual reason these overrun.

Will our team actually use it?

Only if the entry burden is proportionate. That is a design decision we make deliberately, and it is why we push back on long required-field lists during configuration rather than after adoption fails.

Can you integrate the CRM with our website and ads?

Yes, and we would treat that as part of the scope rather than an extra. A CRM that is not connected to lead capture and ad platforms is doing half its job.

What happens if we stop working with you?

The system is registered to your organisation, the data is exportable, and the configuration is documented. Nothing is held in an agency account.

Related services

Sectors where this is usually the lead engagement

These are the industries where this discipline is typically the first thing a client buys rather than something added later. The link goes to a page written for that sector specifically, with a paragraph on this service and on every other one.

It appears on all thirty sector pages, because every one of them carries a paragraph on all twenty-two services. This list names only the sectors where it tends to lead.

Where we deliver this

This service is delivered across the European Union, the Nordic countries, North America and the United Arab Emirates. The craft does not change; the law, the language and the buying culture do. Consent regimes, invoicing mandates and payment conventions differ enough between markets that a campaign or a system built for one frequently cannot be used unchanged in another.

Each country page sets out what actually differs there and what it means for scope — all 32 countries and 10 cities are listed here. A few of the markets we work in most:

Start a conversation

Tell us what you are trying to change and we will tell you whether this is the right service for it — including when it is not.

Get in touch

Tell us what you are trying to change

Describe the problem rather than the service — the two frequently differ, and working out which is which is the useful part of a first conversation. We reply within one working day, and if it is outside what we do well you will hear that in the reply rather than after a call.

We use what you send to reply to you. Nothing else, and no list.

WhatsApp