Surveyor CRM: what a small practice actually needs
What surveyor CRM software should do, why general-purpose tools such as Salesforce leave gaps, and what a small surveying practice should ask on a demo.
What is a CRM?
CRM stands for customer relationship management. In plain terms it is a database of the people and organisations you deal with. Every contact, quote and job is attached to the right record. Around that sit the tools that act on those records. They include reminders to follow up, templates for the emails and documents you send, and a board showing which job is at which stage.
The point of one, if it is set up well, is that nobody has to remember anything. The system knows the client rang on Tuesday, the quote went out on Wednesday, and nobody has chased it.
The term comes from sales software. The best-known products, Salesforce and HubSpot, were built to help sales teams move leads towards a sale, and they are very good at that. The trouble starts when a surveying practice tries to run on one, because a survey instruction is not a sale. The sale is the easy part, and the work begins after it.
Most surveying practices do not have a CRM at all. They have a spreadsheet of jobs, an inbox where the quotes went out, and a shared drive with the reports in it. Someone keeps the calendar in Outlook, and an accounts package knows about invoices but nothing else. Each part works on its own, and the practice runs on the gaps between them.
A surveyor CRM is the thing that closes those gaps. Its job is not managing relationships. It is managing jobs, along with the client, the property, the terms and the report that hang off each one. So before comparing products, it helps to be clear about what the job actually is.
What a job needs, in the order it happens
Broadly speaking, every practice we talk to runs a job slightly differently, but the same six stages keep coming up. Yours might have more or fewer, in this order or another one. The list below is the usual shape.
- Enquiry. Someone asks for a price. It arrives by phone, web form, email or a panel instruction, and it has to be recorded before it is forgotten.
- Quote, or quotes. A fee, a survey type and a set of assumptions go back to the client. Often it is more than one. A client who is not sure whether they need a Level 2 or a Level 3 wants a couple of options, with enough detail to make the right choice. If they do not respond, someone has to remember to chase.
- Terms of engagement. The client accepts, and the terms for that survey type go out and come back signed. RICS expects this before the inspection. Since March 2026 the terms also have to tell the client if AI is used in producing the work.
- Booking. A date, a surveyor, access arrangements, and everything the surveyor needs on the day.
- Inspect and report. The site visit, and then the writing. Before the writing starts, someone pulls together what the report needs from the job, the property and the notes from site. Then the report is written, checked and delivered.
- Invoice and payment. Raised, sent, paid and reconciled, with the chasing in between.
Firms differ in the order and the detail. Some send terms before the quote is accepted, and some take payment at booking. Some invoice on delivery, and some add a site-notes stage or a second review before anything goes out. All of those are fine.
What breaks is when the stages live in separate systems. Nobody can see a job whole, and the handoffs between systems are where things get dropped. It is the quote that was never followed up, the terms that never came back, or the two surveyors booked for the same Tuesday.
Why a general-purpose CRM falls short
It is tempting to buy Salesforce or HubSpot because everyone has heard of them, and the entry prices look modest. Salesforce’s own UK pricing in September 2026 lists Starter Suite at £20, Pro Suite at £80 and Core at £156 per user per month, billed annually. Because that is per user, every surveyor and every member of office staff needs a licence. The comparison a small practice should make is not with the sticker price, but with what has to happen next.
A general-purpose CRM is built for the quote and for tracking the opportunity. Some will hold a status against it, and some will record a payment. Everything else in the client’s journey, from the terms to the booking to the report, happens in whatever process the firm has built around it. The CRM runs separately from all of that, and knows nothing about it.
| General-purpose CRM (Salesforce, HubSpot) | Practice software built for surveyors | |
|---|---|---|
| Designed for | Sales teams moving leads to a closed sale | The whole instruction, from enquiry to payment |
| Pipeline stages | Lead, qualified, proposal, closed won | Enquiry, quote, terms, booking, inspect and report, invoice and payment, in the order your firm works |
| Terms of engagement | Not managed natively. You build your own process outside the CRM, or pay for custom development | Held per survey type, sent and tracked |
| Reports | A file attachment at best | Job data pulled together for the report, then the report stored, checked and delivered |
| Conflict checks | Custom development | Built in, against your whole history |
| Insights and reporting | Sales dashboards, custom views and exports | Dashboards built around the numbers a practice watches, plus exports |
| Set-up | Configured by a consultant or a partner, typically weeks and a separate bill | Set up with you at onboarding, past jobs imported free |
| Pricing | Per user, every seat the same price | Surveyor seats and support seats priced differently, because they do different jobs |
| Vocabulary | Accounts, opportunities, deals | Clients, properties, jobs, reports |
The pattern is the same whichever big-name CRM you pick. They are excellent at what they are for. A practice, though, does not need a tool that is brilliant at winning the instruction and blank about the seven weeks that follow.
Every gap in the table has to be filled with customisation. That means either a consultant’s invoice, or a member of staff who becomes the firm’s unofficial systems administrator. Both are costs the sticker price hides. Both put the practice back where it started, running on a system that was designed for something else.
What to look for
One record per job, and everything hangs off it. The client, the property, the quote, the terms, the booking, the report and the invoice should all be reachable from the job. The job should be reachable from any of them. If you have to search three places to answer “what is happening with the Smiths’ Level 3”, the tool has not solved the problem.
Conflict checks that use your history. A conflict of interest is easy to spot if you remember the property or the client. It is not easy after five years and two thousand jobs. The check should run against the whole back catalogue, which means the tool has to import your past jobs rather than start collecting from the day you switch.
Quotes you can see at a glance. Every quote should carry a status. The ones that have gone quiet are then visible to whoever is chasing that week, rather than buried in a sent folder. Automatic follow-ups are a nice extra. The visibility is what stops enquiries dying.
Terms held per survey type. Level 2, Level 3, a valuation and a schedule of condition each have their own terms. The tool should hold them, send the right one, and record when it came back.
A calendar the whole team sees. Who is where, on which job, with what access arrangements. If the calendar is one person’s Outlook, the practice stops when they are on holiday.
Report handling that respects how you write. Some firms write in Word, some use a report writer, and some dictate. The practice tool should pull together what the report needs from the job, then store, version and deliver the report whatever produced it. It should also give you a way to check the report before it goes out.
Insights that matter to a practice. Any CRM will give you a dashboard and an export. The question is whether it can show jobs by survey type, time from booking to delivery, or fee income by surveyor, without someone building the view first. Exports should still be there for anything it does not show.
Data you can leave with. Everything you put in should come out again, in full, in a usable format. A tool that makes leaving hard is charging you a fee it does not show on the pricing page.
What a regulated firm needs underneath
The features above are the visible part. Under them sit the things a RICS-regulated firm has to be able to demonstrate whether anyone asks or not.
- Where the data is. Client and property data for UK jobs should be hosted in the UK, or at least in a jurisdiction with UK GDPR adequacy. The vendor should say which.
- Who can see what. Named logins, not shared ones. A support person who books jobs should not necessarily see fee levels or sign off reports.
- An audit trail. Who changed what and when, on the job and on the report. Complaints usually surface months after completion, and the record is what defends the firm.
- A data processing agreement. The vendor is your processor. If they cannot show you a DPA and a sub-processor list without being asked twice, keep looking.
- A record of AI use. The RICS professional standard on responsible use of AI has been in force since 9 March 2026. If a tool uses AI anywhere in producing or checking work, the firm has to have assessed the tool and recorded the risks. It also has to keep a named surveyor’s decision on each output. A tool that helps with that record is worth more than one that pretends AI is not involved.
Questions to ask on a demo
- Show me one job from enquiry to payment. How many screens was that?
- What does the conflict check actually check, and what does it run against once my past jobs are imported?
- What can I see about the practice at a glance, and what can I export?
- Where is my data hosted, and can I have your DPA and sub-processor list now?
- How can I export my data, and am I locked in with you?
- What does the tool do with AI, and what record does it keep of it?
- What is the notice period, and is there a setup fee?
Where SCORE fits
SCORE is practice software built around the stages above, in whatever order your firm runs them, with more or fewer as you need. It is built in modules. A sole practitioner runs the parts that matter to them, and a ten-surveyor firm switches on the rest. If your practice has a stage we have not thought of, tell us, because the aim is simple. We want to be the best system for any surveying practice, however you run yours.
It is hosted in the UK and keeps an audit trail on every job and report. Your history is imported free as part of onboarding, and you can export it all at any time. Its dashboards show the numbers a practice watches, and the exports are there for anything else. Quality control is one of its modules. You write the report however you write it today, then run the built-in quality checks on it before it is issued, with your sign-off on every one. SCORE pulls the job data together for the report now. Managing report templates, and pre-filling the bulk of a template for the surveyor to finish, is on the roadmap.
It is also in early beta with a small group of firms. We would rather show you than tell you, so the questions above are the ones to bring to a demo.
We are keen to talk to surveyors and support teams as we go, because the mission only works if the software fits every kind of practice. If there is something you need that we do not do yet, tell us, and we will see whether we can build it with you.
SCORE is not approved, endorsed or affiliated with RICS.