Reliance on word of mouth
It lands on the owner / operations manager first, well before it shows up in any number.
Home and property services / Core trades
Operloom designs and builds the connected system a plumber runs on: the website, the CRM, the booking and follow up and the reporting, configured as one and handed over documented.
What earns the work is reviews, photographs of finished work and turning up when you said you would. What loses it is a system that cannot keep up with the interest it creates.
Primary conversion: Quote request, call or booked visit
01Local service
Discovery for a plumber runs through local search, map listings, trade directories and repeat customers. The channels below are the ones that follow from that, and nothing is included because it is fashionable.
The foundations: crawlability, speed, structure and the markup that describes what this business is
Service and service area pages targeted to high intent local searches
Core Google Business Profile, maps, service categories, photos and review programme
Usually eligible when the business serves customers in person at a real location or service area
Answering what a customer needs to know before they will make contact
Before and after work, project proof and local trust content
Local search campaigns for priority services and urgent needs
Automated review requests after completed jobs
Campaign pages built from the same components, so they are fast to ship and consistent to measure
02Local service
Before any of this is a technology question, it is an operating question. These are the conditions a plumber works inside, and the ones the build has to answer.
It lands on the owner / operations manager first, well before it shows up in any number.
Left alone it becomes a reporting problem too: the record of what happened gets assembled afterwards, from memory.
Because quoting from site between jobs, where the first tradesperson to reply usually gets the work, this one compounds rather than staying still.
Fixing it is rarely a tooling decision. It is a question of where the work is supposed to stop and who picks it up next.
None of this is unusual for a plumber, which is exactly why it goes unaddressed for so long.
03Local service
Written as it actually happens rather than as a funnel diagram. The steps that matter are the handovers.
A customer finds the business through local search, map listings, trade directories and repeat customers.
They send an quote request. The form asks the questions that decide whether it can be scoped, and nothing else.
The quote request is routed and qualified against the criteria that actually predict a good job.
An estimate goes out with the scope written down, and its status is visible without anyone chasing it.
A visit is committed to a real slot, with the buffers and the preparation the work genuinely needs.
The job is delivered. What happened is recorded against the customer, not in a separate note.
An invoice is raised from the same record, so what was agreed and what was billed cannot drift apart.
Payment is taken online, and its status is on the record rather than in somebody inbox.
A review request goes out at the point the customer is most likely to mean it.
04Local service
Quoting, invoicing and payment are built as one path rather than three tools, because the gaps between them are where revenue goes missing.
A customer asks for pricing with enough detail attached to answer properly.
Approval is recorded against the scope it approved.
Where a deposit is how the work is committed, it is taken at that point.
Raised from the agreed scope, not retyped from it.
Without a phone call, and reconciled automatically.
Available to the customer rather than requested from you.
Visible on the record, so chasing is informed.
05Local service
Scheduling for a plumber is where most of the avoidable loss sits. survey, estimate or service visit scheduling with geographic buffers.
Read from the real calendar, so double booking is not possible rather than unlikely.
Preparation and turnaround built into the slot, because a visit is not only the time with the customer.
The questions that decide whether the slot is right, asked before it is taken.
On the interval this kind of work needs, each one carrying a reschedule link.
A customer can move a visit without a phone call, which is how you find out early.
A clear policy applied consistently, with the slot released for rebooking.
To the right person and the right location, using rules rather than judgement.
Handled properly wherever the work crosses them.
06Local service
The CRM holds leads, customers, properties, jobs, estimates, stages and follow up tasks. Configured around how the work is actually run, rather than around the default pipeline the platform ships with.
No duplicates, and no separate spreadsheet holding the version people actually trust.
The stages a customer actually moves through here, named the way the team already names them.
Every open job has an owner, a stage and a date. Anything without all three is a fault.
Attribution written to the record once, then left alone.
Somebody is responsible for every open job, and the system knows who.
Tasks that appear on the right day for the right person, and chase when they do not happen.
The measures a plumber is run on, drawn from the same records the team works in.
Who can see and change what, decided deliberately rather than by whoever set the account up.
07Local service
What the site has to do here is specific: local lead generation and quote website, structured so a customer can get from arriving to quote request, call or booked visit without a detour.
08Local service
These are the workflows that carry the repeatable parts of a job. Every one of them has a human review point, because the useful automations are the ones people trust.
09Local service
Email only works when it arrives. Authentication and list hygiene come before anything creative, because a message in spam is worse than no message.
10Local service
Every one of these already exists in some form, usually as a tool somebody chose alone. The build is mostly about the lines between them.
Where a customer first finds the business.
The pages a customer reads before deciding to make contact.
Qualifying questions asked once, at the point of enquiry.
Every customer, every job and who owns it.
Real availability for a job, with the preparation time it needs.
Estimates and invoices raised from the agreed scope.
Payment taken and reconciled against the record.
Operational and lifecycle messages that arrive and are logged.
The rules that move work between systems, with human review where it matters.
What a customer can see and do without contacting anyone.
Campaigns tracked through to the record they produced.
The measures a plumber is actually run on.
Who is told, when, and what they are expected to do about it.
11Local service
Not every business needs every capability, and pretending otherwise is how implementations get expensive. This is the mix a plumber typically needs, split by how load bearing each part is.
CRM setup and data model supports plumber businesses by helping to generate qualified local enquiries
Pipeline and lifecycle design supports plumber businesses by helping to generate qualified local enquiries
Lead routing, scoring and follow up supports plumber businesses by helping to generate qualified local enquiries
Website build or redesign supports plumber businesses by helping to generate qualified local enquiries
Service and landing pages supports plumber businesses by helping to generate qualified local enquiries
Technical and on page SEO supports plumber businesses by helping to generate qualified local enquiries
Local SEO and Google Business Profile supports plumber businesses by helping to generate qualified local enquiries
Brand identity system supports plumber businesses by helping to generate qualified local enquiries
Booking and appointment system supports plumber businesses by helping to generate qualified local enquiries
Online payments and deposits supports plumber businesses by helping to generate qualified local enquiries
Quotes, estimates and invoicing supports plumber businesses by helping to generate qualified local enquiries
Email infrastructure and deliverability supports plumber businesses by helping to generate qualified local enquiries
Workflow automation supports plumber businesses by helping to generate qualified local enquiries
Analytics and conversion tracking supports plumber businesses by helping to generate qualified local enquiries
Reviews and reputation management supports plumber businesses by helping to generate qualified local enquiries
Security, privacy and maintenance supports plumber businesses by helping to generate qualified local enquiries
12Local service
Better systems do not guarantee a commercial result, and nobody should promise one. What they do is remove specific failure points. These are the ones that matter for a plumber, and the measures that would show whether the change worked.
Asking the qualifying questions at the point of enquiry, so the job is scoped before anyone spends time on it.
Measure: CallsMaking the second job as deliberate as the first, rather than leaving it to whoever remembers.
Measure: FormsBeing findable for the terms a customer actually uses, rather than the ones the business uses internally.
Measure: QuotesCutting the gap between an quote request arriving and a person answering it, which is usually the single largest lever.
Measure: Booked jobsGiving customers the confirmations, reminders and status information they would otherwise have to ask for.
Measure: Win rateTaking the repeatable parts of the job out of somebody's head and putting them into a workflow that runs whether or not it is a busy week.
Measure: Job value and source13Local service
Reporting is built around the decisions the business actually makes. For a plumber that is a short list, which is the point.
Reviewed alongside the stage it depends on, not in isolation.
Measured from the record rather than reconstructed at month end.
Tracked as a trend, because a single period rarely means anything.
Defined once and written down, so it means the same thing next quarter.
Measured from the record rather than reconstructed at month end.
Broken down by source, so the number leads somewhere.
14Local service
A short audit of the platforms, the data in them and the points where an quote request stalls.
The operating model on paper first: stages, ownership, definitions and the measures that will judge it.
Built in the order that gets a plumber value soonest, not the order that is tidiest to build.
Connections built with retry, logging and a defined failure path, so a break is visible rather than silent.
Everything written down, because a system only one person understands is a risk rather than an asset.
Instrumented against calls, forms and quotes, with the definitions agreed first.
A review cadence with a short list of changes, run against the same measures each time.
15Local service
Concrete deliverables, not projected commercial results. What each one achieves depends on how it is used after handover.
16Local service
Recommended starting scope
Local Service Growth
A starting scope rather than a fixed package. The plan page sets out who it is for, the core deliverables, the modules, the integrations and the measures.
Core measures
Scope varies with what already exists, so we do not publish a figure. Tell us what you have and you will get a scoped proposal with the assumptions written down.
17Local service
The categories this operating model usually has to connect. Naming a category is not a claim of partnership, certification or reseller status.
18Local service
Licensing, insurance, safety and service area accuracy where applicable.
That is a factual summary of the areas that tend to apply, not advice. Requirements vary by jurisdiction and change. We build to what your advisers confirm applies, and we implement it properly: consent capture, retention, access control, audit trails and secure handling.
19Local service
Often, yes, and it usually makes the project smaller. A maintainable site is better connected than replaced: quote request capture that carries its source, tracking that survives, and a clean handover into the CRM. The CRM question is whether it can hold leads, customers, properties, jobs, estimates, stages and follow up tasks without being fought. If it can, we configure it properly. If it cannot, we say so and explain what migrating would actually cost you in time and disruption.
Carefully, and within our lane. Licensing, insurance, safety and service area accuracy where applicable. We build to what your advisers tell us applies: consent capture, retention rules, access control, audit trails and secure handling. We implement requirements. We do not interpret them for you, and we will say so rather than guess.
The scope starts from how this kind of business runs rather than from a package. In practice that means local lead generation and quote website, a CRM holding leads, customers, properties, jobs, estimates, stages and follow up tasks, and the booking and follow up around it. The nearest starting point in our catalogue is Local Service Growth, which is a scope to argue with rather than a fixed list.
Availability comes from the real calendar, not a copy of it, so a job cannot be booked into a slot that is already gone. Survey, estimate or service visit scheduling with geographic buffers. Every booking writes back to the customer record, so the diary and the pipeline are the same story.
It depends on how much already exists and how clean it is. A build is sequenced so that something useful goes live early rather than everything landing at once: the CRM and quote request capture first, because that is where work is lost today, then the site, then the automation, then reporting. We give a timeline after a scoping conversation, not before one.
It should, because the phone is part of the system rather than an exception to it. Calls get tracked to the source that produced them, missed calls raise a task instead of vanishing, and a quote can be sent from site rather than at eleven at night. Local visibility and review flow are what keep the phone ringing in the first place.
Less than most people expect, but not nothing. Access to the platforms, a decision maker who can settle scope questions in the same week they are asked, and someone who knows how the work really runs, which is rarely the same as how it is written down. Content and assets where you have them. We write what you do not.
You get the documentation, the workflow map and the training, because the point is that you own it. Ongoing support is a separate arrangement rather than an assumption: some businesses take a maintenance and improvement retainer, others take the handover and run it themselves. Both are fine, and we will tell you which one we think fits.
Bring the version of the process that actually happens rather than the documented one. That is the one worth designing against.