Industry guide · Field Service Management

The Late-Night Lockout Calls You Are Not Answering, and the Jobs They Cost You

The short answer

A focused first release, typically an AI phone agent that answers after-hours lockout calls and books the job, ships for $50k to $120k in 10 to 16 weeks in Digital Heroes delivery experience. A full dispatch, quoting, and invoicing platform runs $150k to $350k phased over 6 to 12 months. Most locksmith owners start with the after-hours agent because the calls it captures begin paying for the build inside the first busy month.

The 9pm call you let ring out is tomorrow's lost job

Picture the owner of a six-truck mobile locksmith shop. It is a Tuesday. Her dispatcher, Marco, spent the morning on the phone with a property manager who wanted a rekey quote on eleven units, then burned forty minutes chasing three techs across town because the job board is a dry-erase whiteboard next to the coffee machine. The shop runs on Housecall Pro for invoicing and a lot of loose texting. It mostly holds together. Until the phones go quiet at 6pm.

That night a college kid locked out of his apartment calls the main line at 9:47pm. It rings four times and drops to a voicemail box that Marco clears at 7am. By then the kid has called the next locksmith on the Google map, paid $165 for a fifteen-minute open, and left that guy a five-star review. The owner never sees the call. It does not show up as a lost job in any report, because it was never a job. It was just a ring nobody answered.

Multiply that by the three or four after-hours calls the line drops every week, add the two commercial estimates sitting unread in the inbox and the follow-ups nobody made, and you have the real leak. It is not measured in bad months or angry reviews. It is measured in hours of unpaid phone tag and in jobs that quietly went to whoever picked up.

Problem: the phone stops being answered at 6pm. The lockouts do not stop.

Lockouts keep no business hours. A stranded driver at midnight, a landlord locked out on a Sunday, a bar manager who snapped a key in the back door at 1am: these are the highest-intent, highest-margin calls a locksmith gets, and they land when nobody is at the desk. The shop's answer today is voicemail or a $1.50-a-minute answering service that reads a script, cannot quote a lockout, and cannot see which tech is on call.

Housecall Pro and Jobber will sell you an online booking form. A person in a parking garage with 9% battery is not filling out a form. That is the gap the off-the-shelf tools cannot close: they assume the customer comes to a screen, when the customer is dialing a phone in a panic.

A custom build puts an AI voice agent on the main line the moment it goes after-hours. It answers in two rings, asks the three questions that route a locksmith job (residential or commercial, vehicle or building, exact location), checks the job against your service area and on-call rotation, quotes a price band, and books it. Then it texts the on-call tech the address with a one-tap accept and writes the whole thing into Housecall Pro as a booked job before the customer hangs up. The 9:47pm call becomes a dispatched ticket instead of a 7am regret.

Problem: the eleven-unit rekey quote is still in the inbox three days later

The property manager Marco quoted wanted eleven units rekeyed plus a small master key system. That estimate is worth more than a week of lockouts. It went out once, as a PDF, and nobody touched it again. By Friday the manager has three quotes and picks the one whose salesperson called back. Yours was not it.

Housecall Pro can fire one automated reminder. It does not know that a $4,000 commercial rekey deserves a different chase than a $90 house call, it never references the actual units or the master key detail, and it never escalates the big ones to a human. Estimates rot on a timer.

A custom follow-up engine watches every unaccepted estimate over a threshold you set. It sends timed, plainly written follow-ups that name the real job (the eleven units, the master key system, the day you walked the property), spaced the way a good closer would space them. When a high-value quote goes cold, it drafts a message and drops it on the owner's phone to send with one tap. It also tags why quotes stall, so you learn which prices and property types close and which never do.

Problem: your best tech finishes eight jobs a day and asks for zero reviews

The kid from the parking-lot lockout gave his five stars to a competitor. Your tech, who rekeyed a storefront and cut four keys that same night, asked for nothing, because he was already driving to the next call. Reviews are how the next stranded customer picks a locksmith off the map, and your crew is too busy to chase them.

The review prompt inside most field tools blasts a generic request at everyone on the same schedule, or it never gets switched on at all. It fires while the customer is still annoyed, or a week later when the relief has worn off.

A custom flow triggers on the invoice being paid, at the moment the customer is standing back inside their house or car and grateful. It names the tech and the job, sends happy customers to your Google profile, and routes anyone who sounds unhappy to a private inbox so the owner hears it before the internet does. Reviews stop being something a tired tech has to remember and become something the job produces on its own.

Problem: two trucks cross town while a third sits three blocks from the next call

At 2pm the whiteboard says truck three is free, but truck three carries the automotive gear and the next job is a commercial safe. So the dispatcher sends truck one across the city, past a rekey it could have knocked out on the way, and when a lockout comes in there is no clean slot for it. The day becomes a map of wasted miles.

The schedule board in ServiceTitan or Jobber shows you appointments. It does not know a lockout is urgent and a scheduled rekey is not, it does not know which truck carries automotive tools versus safe tools, and it will happily double-book the one tech who can open a safe.

A custom dispatch brain holds in real time what lives in Marco's head: each tech's location, the gear on each truck, the urgency of each job, and the gaps in the day. It slots an emergency lockout into the nearest capable truck's dead time without bumping the paid commercial install, and re-sequences the route so nobody drives past a job they could have done. That is billable hours pulled out of thin air, every day.

Problem: six years of jobs in your CRM (Customer Relationship Management) that nobody has ever asked a question

Every locksmith on Housecall Pro or ServiceTitan is sitting on a mine nobody has dug: years of customers, quotes, and closed jobs. The property manager who bought one rekey in 2022 and was never called again. The commercial accounts on a natural re-key cycle. The July spike in car lockouts. It is all in the database, and the canned dashboard shows none of it.

Off-the-shelf reporting gives you revenue by month and a job count. It cannot tell you which dormant accounts are worth a call this week or which price points on which job types actually close.

A custom build reads that history and turns it into work. It surfaces the property managers who bought once and vanished, flags the commercial accounts due for a re-key cycle, and feeds those names straight into the follow-up engine and the dispatch plan. The jobs you already earned become the cheapest pipeline you will ever run, because you paid to win those customers once already.

What this costs, honestly

These bands come from Digital Heroes delivery experience across more than 2,000 projects, not a rate card. A focused first release, usually the after-hours AI phone agent that answers and books lockouts, typically runs $50k to $120k and ships in 10 to 16 weeks. A full operations platform that also owns dispatch, quoting, follow-up, and invoicing runs $150k to $350k, phased over 6 to 12 months so you are live on the phone agent long before the rest is done.

What pushes a locksmith build toward the top of the band is specific to this trade. A shop running automotive, residential, commercial, and safe work needs four sets of dispatch rules and gear logic, not one. The voice agent has to hold up on genuinely bad audio, because your callers are outdoors, stressed, and often inside a concrete parking structure. Deep two-way sync with the Housecall Pro or ServiceTitan API, multiple locations, and real on-call rotation and SLA logic all add build. A single-trade, single-location shop lands near the floor.

When Housecall Pro is genuinely enough, and when it is not

If you run one or two trucks, do not build anything. ServiceTitan, Jobber, and Housecall Pro are good products, and at that size the invoicing, scheduling, and reminders they give you are plenty. Spending six figures to save Marco an hour a day does not pay back when there is no Marco.

The signals that it is time to build, or to layer AI on the CRM you already have, are concrete. You are missing or turning away after-hours calls. You run multiple crews and dispatch lives on a whiteboard. You have thousands of past customers nobody markets to. Your quotes close below where they should because nobody chases them. You are a private-equity-backed rollup trying to run five acquired shops on four different tools. The position: in almost every one of those cases, do not rip out Housecall Pro. Keep it as the system of record and build the phone agent, the follow-up engine, and the dispatch brain against its API. Replace the tool only when it physically cannot hold your data, not because it feels dated.

How to choose a developer for locksmith software

Ask whether they will ride along on a truck for a day before they write a line of code. A developer who has never watched a tech pick a lock at 11pm or seen a dispatcher juggle the whiteboard will build something that demos well and dies in the field. This is the best filter you have.

Make them prove the AI phone agent on a deliberately bad call before you sign. A clean demo in a quiet office proves nothing. Your real callers are panicked, outdoors, and down to half a bar in a garage, and that is the only test that counts.

Confirm they can work against the Housecall Pro or ServiceTitan API and its rate limits, not just stand up a new island that forces your office to enter every job twice. Integration is the unglamorous part, and it is where most of these projects quietly fail.

Settle ownership in writing before the project starts. You own the source code, the customer data, the phone number, and the trained voice agent, full stop. Ask a candidate directly what happens to all of it the day you walk away, and listen to how fast they answer.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. Mordor Intelligence sizes the field service management market at USD 6.26 billion in 2026, forecasting USD 9.87 billion by 2031 at a 9.54% CAGR, confirming sustained double-digit-adjacent demand for FSM software. Source: Mordor Intelligence (2026) →
  2. ServiceTitan's KPI guide cites an average first-time fix rate near 80% (90% ideal) and describes strong technician-utilization rates as falling in the 60-80% band, with average travel time typically 30-60 minutes depending on service-area size. Source: ServiceTitan (2026) →
  3. 88% of organizations are concerned about employee retention, and providing learning opportunities is respondents' #1 retention strategy; career progress is cited as people's top motivation to learn, yet only 36% of organizations qualify as 'career development champions.'. Source: LinkedIn Learning (2025) →
  4. Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
Rohan Malhotra · Enterprise Software Consultant

Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.

Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.

FAQ

Frequently asked questions

How much does custom locksmith software cost for a shop with six trucks?
A focused first release, like an after-hours AI phone agent, typically runs $50k to $120k and ships in 10 to 16 weeks in Digital Heroes delivery experience. A full platform covering dispatch, quoting, follow-up, and invoicing runs $150k to $350k phased over 6 to 12 months. A six-truck shop usually starts with the phone agent and adds modules as they pay for themselves.
Can an AI really answer our phones and book a lockout at 2am?
Yes. A voice agent can pick up in two rings, ask whether the job is residential or commercial and vehicle or building, confirm the location against your service area, quote a price band, and book the job into your CRM, then text the on-call tech the address with a one-tap accept. The hard part is not the booking, it is making it sound right for a stressed caller in a parking garage, which is why you test it on bad audio before you sign.
Do we have to replace Housecall Pro, or does this sit on top of it?
In most cases it sits on top. Housecall Pro stays your system of record, and the phone agent, follow-up engine, and dispatch logic are built against its API and write jobs straight back into it. You only replace the CRM if it genuinely cannot hold your data or hits limits you cannot work around.
How is this different from what ServiceTitan or Jobber already do?
ServiceTitan and Jobber give you scheduling, invoicing, an online booking form, and generic reminders. They do not answer a live 2am lockout call, chase a $4,000 commercial estimate the way a salesperson would, or route an emergency job to the one truck carrying the right gear. Custom work adds the pieces those tools leave on the table and connects them to the data you already have.
How long before the after-hours phone agent is actually taking calls?
A focused first release with the phone agent typically ships in 10 to 16 weeks. The first few weeks go to mapping your service area, on-call rotation, and pricing logic, then testing the agent on real recorded call conditions. You go live on the phone agent well before a larger platform is finished.
What happens to our years of customer and job data when we migrate?
It stays, and it becomes an asset instead of dead weight. A proper build reads your existing Housecall Pro or ServiceTitan history, keeps it intact, and mines it for dormant accounts, re-key cycles, and pricing patterns. In most cases you are not migrating off the CRM at all, just building on top of it.
Who owns the code and the AI agent if we stop working with the developer?
You should own all of it: the source code, the customer data, the phone number, and the trained voice agent. Settle this in writing before the project starts. If a developer hesitates on ownership or wants to keep the phone number or the agent, treat that as a warning.
What results should we expect in the first few months?
The clearest early wins are after-hours calls that now get answered and booked instead of going to voicemail, and commercial estimates that get chased instead of rotting. You should also see reviews rise as requests fire automatically at job close. Dispatch and data-mining gains come as those modules ship, since they depend on more of the platform being in place.
Is it worth it for a smaller shop, or only for multi-location operations?
If you run one or two trucks, stay on Housecall Pro or Jobber; custom software will not pay back at that size. It becomes worth it once you have multiple crews, you are missing after-hours calls, dispatch is a whiteboard, or you are consolidating several shops as a rollup. The trigger is operational pain measured in hours and missed jobs, not the number of locations by itself.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
How much would it cost to build something like ServiceTitan just for my company?
A true ServiceTitan clone would cost millions and you do not need one, because companies that bring this request to Digital Heroes typically use 20 to 30 percent of its features. Building that slice, shaped to your exact dispatch board and technician day, runs $80,000 to $200,000 depending on offline requirements and integrations. The field service builds that succeed copy a workflow, not a product.
How big a team does it take to build field service management software?
The standard Digital Heroes team for a field service build is five to six people: a project lead, a designer, two or three developers split across the mobile app and backend, and a QA tester who works on real devices in real signal conditions. Bigger is not better; experience with offline sync is. The riskier pattern is the opposite, a single developer quoting the entire system alone.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
We're outgrowing Jobber. Should we move up to ServiceTitan or build our own?
Move to ServiceTitan if the problem is missing features on a standard residential trades workflow, because migrating between products is far cheaper than building. Build custom when the problem is fit: multi-day commercial jobs, subcontractor crews, or pricing rules that neither Jobber's Grow plan (about $199 per month billed annually, up to 15 users) nor ServiceTitan models cleanly. In Digital Heroes scoping calls, about half the teams asking this question turn out to need an integration or add-on rather than a new platform, so name the exact workflow gap before committing either way.
How much does it cost to build custom field service management software for a small business?
For a company running 5 to 25 technicians, a focused first version with scheduling, dispatch, a technician mobile app, and invoicing typically runs $40,000 to $80,000 in Digital Heroes delivery experience. A full platform with offline mode, a customer portal, GPS tracking, and accounting sync lands between $90,000 and $180,000. The two biggest cost drivers are offline sync depth and integration count, so pin both down in scoping and the quote holds.
How does custom field service software work when technicians have no cell signal?
Properly built field software stores the technician's entire day on the device, including job details, forms, photos, signatures, and parts, then syncs automatically when signal returns. The hard engineering is conflict resolution: deciding what happens when a dispatcher reassigns a job while the technician is working it offline. That logic has to be designed before the build starts, because retrofitting offline into an app that assumed a connection is close to a rewrite.
Will custom field service software scale if we grow from 10 technicians to 100?
Yes, when it is architected for growth from day one, and scale is where custom wins because cost per technician falls as you add crews instead of rising with every seat license. The real scaling work is operational: multi-branch dispatch, role permissions, and roll-up reporting, which usually arrives as a phase two costing 30 to 50 percent of the original build. State your three-year headcount plan in the first scoping call so the data model supports branch two before branch two exists.
Keep reading
let's build

Build something worth launching.

A plan, a team, a timeline, within 24 hours. No decks, no discovery calls. Tell us what you're building and we'll come back with a real scope and a real number.

message us directly · we reply within one business day

mission briefing

Monthly dispatch

Playbooks, real build costs, and what we're shipping. One email a month. No fluff.

visit us

New York HQ

1140 Broadway, Suite 704 · New York, NY 10001

Get directions
Online now

Hey there 👋 How can we help you today?