Field service CRM

Custom field service CRM software, built around your dispatch and your jobs

A field service CRM has one job: get a request from the phone or the website to the right technician, with the right information, and turn the finished work into a paid invoice. We build that system around how your office and crews already work — instead of reshaping the business around a SaaS template.

  • Typical timeline8 – 12 weeks
  • IntegrationsQuickBooks, RingCentral, Google
  • OwnershipYour code, your data

Scope

What a field service CRM can include

The modules every service company needs, plus the ones only your process needs.

01

Calls & requests to jobs

Phone calls, web forms and marketplace leads open a customer record and become a job without retyping.

02

Dispatch board

Jobs by technician, day, zone and skill. Drag to reschedule; the technician sees the change immediately.

03

Technician mobile app

Today’s route, job notes, checklists, photos, on-site estimates and signatures, with offline mode for basements and rural sites.

04

Estimates, invoices & payments

Line-item estimates, approvals, invoices and card payments, synced with QuickBooks Online.

05

Service agreements

Recurring maintenance plans that generate visits and reminders on schedule.

06

Owner dashboard

Jobs booked, completed and invoiced, revenue per technician and unpaid invoices on one screen.

In detail

What “field service CRM” actually means

A sales CRM tracks deals. A field service CRM tracks work that happens at a customer’s address: who called, what they need, who goes there, when, with which parts, what was done, what it cost and whether it was paid. The center of the system is the job, not the deal — which is why Salesforce or HubSpot need heavy add-ons to do it, and why platforms such as ServiceTitan, Jobber and Housecall Pro exist.

Those platforms are good products. They also assume a standard residential workflow. Companies that run commercial contracts, multi-trade jobs, construction-style projects, unusual dispatch rules or their own pricing logic end up keeping part of the work in spreadsheets next to the platform. That gap is where a custom field service CRM pays off.

Signs you have outgrown your current tool

  • The dispatcher keeps a separate spreadsheet or whiteboard because the schedule view does not match how you assign work.
  • Office staff copy customer details between the phone system, the CRM and QuickBooks by hand.
  • Technicians text photos to a manager instead of attaching them to the job.
  • You pay for modules and seats you never use while the one workflow you need is “on the roadmap”.
  • Reports that matter to you — margin per job type, callbacks per technician — are built in Excel at month end.

How we build it

We start with one to two weeks of discovery: we sit with the dispatcher, a technician and the person who invoices, and map how a job actually moves today. You receive a written specification and milestone schedule — yours to keep even if you build elsewhere. Then we build in two-week iterations with a demo every Friday, starting with the job record and the dispatch board, because everything else hangs off them.

Integrations are planned up front, not bolted on: telephony (we have shipped RingCentral integrations; Twilio works the same way), QuickBooks Online for customers and invoices, Google Calendar and Gmail, and lead marketplaces such as Thumbtack. The technician app is built with React Native from the same backend, so office and field always see the same data.

Custom vs ServiceTitan, Jobber or Housecall Pro

QuestionSaaS platformCustom field service CRM
Time to startDays8–12 weeks for the core system
Fit to your processYou adapt to the productThe product follows your process
Cost modelPer user, every month, rising with headcountBuild once, then support you size yourself
Ownership of code and dataVendor’sYours
Best forStandard residential service, fast startNon-standard workflows, integrations, long-term control

If your process is standard, stay on a platform — we say that on calls too. If it is not, read ServiceTitan vs custom software, the total cost of ownership worksheet and the field service CRM features checklist.

Trades we build for

HVAC and plumbing, electrical, roofing, cleaning, landscaping, pest control, appliance repair, garage doors, fireplace and chimney, glass and glazing, and general contracting. See HVAC & plumbing, construction and the field service CRM case study.

Comparing with Jobber and ServiceTitan

If you run on Jobber today, read Jobber vs a custom CRM for an honest look at when to stay and when to build. For larger trades companies, see ServiceTitan vs custom software.

Related work

Systems like this we have built

Client names are withheld under confidentiality agreements. See all case studies →

Delivery

How the project runs

The same four phases on every project. Only their length changes with scope.

1. Discovery · 1–2 weeks

Interviews with the people who will use the system, a map of the current process, a written specification and an estimate. The documents are yours even if you build elsewhere.

2. Architecture · 1–2 weeks

Data model, integrations, infrastructure and a milestone schedule. This is where the scope and launch date are fixed in writing.

3. Build · two-week iterations

A working demo every Friday and a staging environment you can open at any time. Changes in scope are agreed before they are built.

4. Launch & support · ongoing

Deployment, handover, documentation and training, then a support arrangement sized to the business.

Engagement

How we work together

After a short call and a 1–2 week discovery you receive a written specification and a milestone schedule — before any build starts.

NDA before the first call, US and EU contracts, and the code, accounts and data belong to you from the first commit. How we work →

Get a quote
Fixed scope
Scope and launch date fixed in writing after discovery. Best for a defined system or MVP.
Dedicated team
Senior engineers embedded in your product, working in your tools and rituals. Best for long-running products.
Time & materials
Flexible scope with weekly reporting. Best for evolving requirements and support.

FAQ

Questions we are asked most

What is the difference between a field service CRM and a regular CRM?

A regular CRM is built around deals and contacts. A field service CRM is built around jobs at a customer address: scheduling, dispatch, technicians, parts, on-site estimates, invoices and recurring service.

How long does it take to build a custom field service CRM?

The core system — requests, jobs, dispatch, estimates, invoices and QuickBooks sync — usually takes 8–12 weeks. A technician mobile app adds roughly four weeks, often in parallel.

Can we keep ServiceTitan or Jobber while you build?

Yes. Most clients run both for a short period, migrate data in stages and switch once the team is comfortable. Sometimes integrating the existing platform is the better answer, and we will say so.

Does the technician app work offline?

It can. Offline mode for job details, checklists and photos is a common requirement and is planned in the data model from the start.

Can you move our data from our current software or spreadsheets?

Yes. Customers, jobs, documents and history are migrated in stages during the build, so the office keeps working during the switch.

Do we own the system and the data?

Yes. Repositories, cloud accounts and data are created in your name from the first commit. There is no per-seat subscription and no lock-in.

Contact

Talk to the people who will build it

Describe what you need in two minutes. We reply within one business day and send a written scope and timeline after a short call.

Other services

Industries

Company

Guides

Get a quote