What are the first 10 steps to build a GTM playbook for a locksmith services operator in 2027?

The revenue problem being solved

A locksmith services operator does not usually lose money because the work is bad. It loses money in the ninety seconds between a customer's problem and someone answering the phone, and again in the gap between a job being finished and the money being collected. Most independent shops running two to six vans are effectively three separate businesses stapled together — emergency roadside and residential lockouts, scheduled residential and commercial rekeys and hardware installs, and recurring commercial or property-management contracts — and each of those has a completely different sales motion, margin profile, and buying trigger. Building a go-to-market playbook is the act of separating those three businesses on paper so each one can be measured, priced, and staffed on its own terms.

The specific revenue leaks are predictable and they show up in the same order at nearly every shop. First is unanswered inbound. Emergency lockout demand is non-deferrable: a customer standing next to a locked car will call three to five listings and hire whoever answers and gives a firm ETA. A missed call is not a delayed sale, it is a permanently lost one, and it takes the review that would have come with it. Second is quote drift — techs pricing in the driveway from memory, so the same deadbolt install goes out at wildly different numbers depending on who took the job and what mood the day was in. Third is the unbilled add-on: the tech opens the car, notices two worn cylinders and a strike plate that has been chiseled out, and says nothing because nobody ever told them that mentioning it is part of the job. Fourth is the uncaptured commercial relationship — the property manager who called once for an eviction rekey and was never contacted again, when that single account might have been worth a standing rekey schedule across forty units.

Quantify the leak before designing anything, because the playbook's whole job is to close a specific gap and you cannot claim a win against a number you never wrote down. Pull ninety days of call logs from whatever phone system is in use and count three things: total inbound calls, calls answered inside twenty seconds, and calls that converted to a dispatched job. Then pull the invoice history and compute average ticket by service type, not in aggregate — aggregate average ticket is the single most misleading number in this trade because a $45 car opening and a $1,400 commercial hardware job average into a figure that describes no actual job. Then count how many customers appear more than once in twenty-four months. That repeat rate is the honest measure of whether there is a business here or just a sequence of strangers.

The output of this diagnostic is one sentence you will test everything against: revenue equals answered calls times booking rate times average ticket by mix times repeat rate. Every one of the ten steps that follows moves exactly one of those four terms. If a proposed tactic does not move one of them, it does not belong in the playbook. That constraint is what keeps a go-to-market document from turning into a wish list, and it is why the operator — not a consultant, not a marketing vendor — has to own the numbers before anyone writes a word of strategy.

Root-cause map

Before sequencing the ten steps, map where the money actually goes missing. The value of this map is that it separates causes that live in operations from causes that live in demand generation. Operators consistently misdiagnose a dispatch problem as a marketing problem, buy more leads, and make the dispatch problem worse — more calls into a system that already cannot answer them produces more bad reviews, which lowers the map ranking that the extra leads were bought to compensate for.

Read the map right to left when you are deciding what to build first. The three convergence points — intake and coverage, pricing and enablement, data spine and follow-up — are the natural work packages, and they should be attacked in that order because each one feeds the next. There is no point building a review-request engine before you have a customer record to attach the request to, and there is no point buying lead volume before someone reliably answers the phone.

Two root causes deserve special attention because they are the ones operators most often argue about. The first is after-hours coverage. Emergency lockout volume skews heavily toward evenings, nights, and weekends, and a shop that only answers between eight and five has structurally conceded the highest-urgency, highest-willingness-to-pay segment of its market. The second is the absence of a customer record. A great many shops still run on a paper invoice book or a text thread, which means the residential customer who paid for a rekey in March is unreachable in November when they need a smart lock installed. Neither of these is a marketing problem and neither is solved by spending more on ads.

The first ten steps in order

Here is the sequence itself. Treat each step as a deliverable with a named owner and a date, not a theme. A locksmith services operator running this properly should expect roughly eight to twelve weeks from first step to a functioning playbook, with the first four steps compressible into two weeks if the owner clears their calendar.

Step one — define the three ICPs and pick a lead segment. Write one page each for the emergency consumer, the scheduled residential or small-commercial buyer, and the recurring commercial account. For each, capture the trigger event, who decides, how fast they decide, what they will pay, and where they search. The emergency consumer decides in under two minutes on a phone map result. The property manager decides in a week against a rate sheet, often with a purchasing rule requiring a certificate of insurance and sometimes a W-9 on file. Pick one segment to lead with. Most operators should lead with recurring commercial, because emergency volume is already coming in and commercial is the segment that compounds — but that choice belongs to the operator and should be made explicitly, not by default.

Step two — write the offer set. Convert the service list into named, bounded offers a customer can say yes to: car lockout, house lockout, residential rekey per cylinder, deadbolt supply and install, master key system design, safe opening, access control service, and a commercial rekey program. For each offer, write what is included, what is explicitly excluded, the typical duration, and the parts required. Vague scope is what produces driveway renegotiation, and driveway renegotiation is what produces one-star reviews.

Step three — build the price book. Per offer, set a service call or trip fee, a labor rate or flat rate, and part prices with a stated markup band. Publish after-hours, weekend, and holiday multipliers as explicit line items rather than letting techs improvise a surcharge. Set the minimum ticket deliberately: it should cover drive time, vehicle cost, and the tech's loaded hourly rate with margin, and in most markets that means the minimum is meaningfully higher than the advertised trip fee — which is exactly why the trip fee must be disclosed on the phone as a trip fee, not as a total. Undisclosed surcharges are the single fastest way to earn a chargeback and a complaint.

Step four — draw the coverage map and the ETA promise. Draw a primary radius you can reach inside a defined window, a secondary radius that costs a stated surcharge, and a hard boundary you decline. Attach a real ETA promise to each ring and staff to it. An operator who promises thirty minutes and arrives in seventy has manufactured a bad review out of a job they completed competently. The ETA promise is a product feature and should be treated as one.

Step five — choose the channel mix. For emergency demand, the map listing is the whole game: a verified business profile with accurate hours, service areas, categories, photos of real vans and real technicians, and a steady flow of recent reviews. For scheduled residential, add a site with a page per service and per city served. For commercial, the motion is outbound and relational — property management firms, general contractors, facilities managers at schools and clinics, apartment complexes, and self-storage operators. Assign a weekly outbound quota in the low tens of contacts rather than a vague intention to network.

Step six — fix intake. Decide who answers, in what window, and what they say. Write a fifteen-line call script that captures name, callback number, address, vehicle or door type, the actual problem, and payment method, then gives a firm ETA and a firm price range. Route after-hours to a rotating on-call tech or an answering service briefed on the price book. Track speed-to-answer and booking rate weekly. This is the highest-leverage step in the entire playbook and it costs almost nothing.

Step seven — set the dispatch SLA and the job record. Every job gets an ID, an assigned tech, a promised window, a status, and a close-out with photos and a signature. Whether that lives in field service software or a disciplined shared spreadsheet matters less than the discipline itself, though software pays for itself quickly once you exceed two vans. The rule is that no job exists without a record and no record closes without a payment status.

Step eight — enable the technicians. Techs are the entire sales force in this business and they are usually the least equipped. Give each one the price book on their phone, three specific upsell prompts tied to what they will physically see on site — worn cylinders, a chiseled strike plate, an unrekeyed lock after a tenant turnover — a card-present payment method, and a two-line review request script. Then tie a modest commission, commonly in the single-digit-percentage range, to add-on revenue specifically rather than to total ticket, so the incentive rewards noticing rather than upcharging.

Step nine — build the review and follow-up engine. Ask for the review at the moment of relief, on site, before leaving. Send a follow-up message the same day with a direct link. Then schedule the second touch: a residential rekey customer hears from you at eleven months about hardware and smart locks; a commercial account gets a quarterly check-in tied to their turnover cycle. This step is what converts the transaction stream into a book of business.

Step ten — run the weekly revenue review. One hour, same time each week, five numbers on one page: calls, answer rate, booking rate, average ticket by service line, and repeat rate. Compare against the baseline from the diagnostic. Change exactly one variable per week and write down what you changed. The playbook is not the document — the playbook is this meeting, and the document is just what it reads from.

Benchmarks and ranges to plan against

Benchmarks in this trade vary enormously by market density, licensing regime, and service mix, so treat every number below as a planning band to be replaced by your own measured baseline within one quarter. The point of a band is to tell you whether you are in a normal range or badly off, not to give you a target to hit.

On intake, the operative standard is that emergency callers hire whoever answers. Aim to answer effectively every call during posted hours and to have a live-answer path after hours. If your answered-call rate is well under ninety percent, no amount of additional lead spend will help — you are already paying for demand you cannot serve. Booking rate on answered emergency calls should be high, because the caller has already decided to buy something and is only shopping price and ETA. If a large share of your answered calls do not convert, the cause is almost always one of three things: your price disclosure is confusing, your ETA is uncompetitive, or the person answering does not have authority to commit to a window.

On service mix, plan for wide dispersion in ticket size. Simple consumer lockouts sit at the low end, residential rekeys scale with cylinder count, hardware supply and install jobs carry both labor and a parts margin, and commercial master key or access control work sits an order of magnitude above the consumer work. Because of that dispersion, revenue per van is driven far more by mix than by job count. Two vans running mostly commercial can out-earn four running mostly lockouts, on less fuel and fewer hours. This is precisely why step one asks you to pick a lead segment.

On parts, set a markup band and hold to it rather than pricing part by part. Hardware markup in the trades commonly runs meaningfully above cost to cover carrying inventory on the van, warranty exposure, and the fact that the customer is buying same-hour availability, not the part itself. Write the band into the price book so a tech never has to invent it.

On capacity, do the arithmetic before you promise anything. A van running an eight-hour day with an average of thirty to forty-five minutes of drive time between jobs in a mid-density metro realistically completes a handful of jobs, not a dozen. Multiply realistic jobs per day by average ticket by working days to get van revenue capacity, then compare to the fully loaded cost of that van — technician wages and payroll burden, vehicle payment or depreciation, fuel, insurance, tools, and inventory. If the capacity number does not clear the cost number with room for overhead and profit, the fix is mix or price, not more hours.

On marketing efficiency, the discipline is to measure cost per booked job rather than cost per lead or cost per click. A channel that delivers cheap clicks and expensive booked jobs is worse than an expensive channel that books reliably. Track it per channel, per month, and kill anything whose cost per booked job approaches your average gross profit per job. On the local map listing, treat review recency and volume as the primary lever — a steady weekly trickle of recent reviews consistently outperforms an old pile of them.

On the commercial motion, expect a long, unglamorous ramp. Property managers and facilities buyers change vendors when their current vendor fails them, which means your job is to be the known alternative at the moment of failure. Plan on multiple touches over months per account, plan on producing a certificate of insurance and a signed rate sheet on request, and plan on the first job being small and evaluative. The payoff is that a single property management firm can generate more predictable annual revenue than an entire quarter of walk-up emergency work, and it books during business hours.

Trade-offs and alternatives worth deciding explicitly

Every one of the ten steps has a cheaper version and an expensive version, and the wrong choice is usually the one made implicitly. Name the trade-off, decide it, and write the decision down.

Answering service versus in-house intake. An answering service gives you twenty-four-hour coverage without paying someone to sit awake, but the operator answering has no price book in their head and no authority, so booking rate drops and quote accuracy suffers. In-house or on-call rotation preserves quality but burns your best technician's sleep. The practical middle is an answering service that is trained on your top eight offers and given explicit authority to quote a range and commit to a window, with a compensating audit: listen to five recorded calls a week.

Flat-rate versus time-and-materials pricing. Flat rate is faster to quote on the phone, easier for a tech to defend, and converts better on emergency work — at the cost of margin on the jobs that turn out ugly. Time-and-materials protects margin on complex commercial work but invites disputes on consumer jobs. Most operators land on flat rate for the consumer catalog and time-and-materials for commercial projects and access control, which is a legitimate answer as long as the boundary is written down.

Emergency-led versus commercial-led go-to-market. Emergency work pays today, requires no relationship, and scales with ad spend and map ranking — but it is unpredictable, review-fragile, price-shopped, and competes against aggressive national lead brokers. Commercial work is slower to win, requires insurance documentation and net terms, and ties up working capital in receivables — but it is schedulable, higher margin, and it compounds. You do not have to pick one forever, but you have to pick which one gets the operator's own calendar time this quarter, because that is the scarce resource.

Buying leads versus owning the channel. Lead brokers and national dispatch networks deliver volume immediately and take a large share of the ticket, and critically the customer relationship stays with the broker, so nothing compounds. Owning your map listing and site is slower and requires sustained review generation, but every job adds to an asset you keep. A defensible pattern is to use bought leads to fill genuine capacity gaps while explicitly capping them as a percentage of total jobs, and to treat that percentage falling over time as a success metric.

Software versus spreadsheets. Field service software gives you scheduling, dispatch, job records, invoicing, and payment in one place, and it removes the entire class of failures where a job exists only in someone's memory. It costs a per-technician monthly fee and takes a few weeks to configure properly. Below two vans, a rigorous shared spreadsheet with a job ID column genuinely works. Above two vans, the coordination cost of the spreadsheet exceeds the software cost — the failure mode is not that the spreadsheet is wrong, it is that nobody updates it during a busy Friday.

Technician commission versus flat wage. Commission on add-ons increases average ticket, and it also increases the risk that a tech recommends work that was not needed — which in a trade already fighting a public reputation problem around bait pricing is an existential risk, not a nuisance. If you pay commission, pay it on add-ons rather than total ticket, cap it, and audit a sample of jobs where an add-on was sold. Flat wage with a team-level quality bonus is the conservative alternative and is entirely defensible for an operator whose differentiation is trust.

Speed versus radius. Widening your service radius increases addressable demand and destroys your ETA promise simultaneously. It is almost always better to dominate a tight radius with a fast, reliable window than to be mediocre across a metro. Expand the radius only when a second van makes the promise keepable, not when the map looks empty.

Rollout plan and the first ninety days

Sequencing matters more than completeness. Build in the order that makes the next step possible, and resist the temptation to start with the marketing, which is the fun part and the one that fails hardest when the operational steps behind it are missing.

Note that step five, the channel mix, deliberately lands in weeks seven and eight rather than week one. That ordering is the whole argument of this playbook: you turn up demand only after intake, pricing, and dispatch can absorb it. An operator who buys visibility in week one converts a fixable operations problem into a permanent reputation problem, because the reviews from those mishandled jobs outlive the campaign by years.

Staffing the rollout is straightforward at small scale. The operator personally owns steps one through four — segment choice, offers, pricing, and coverage are ownership decisions and cannot be delegated to a marketing vendor without the playbook drifting away from the economics. The office manager or lead dispatcher owns steps six and seven. The senior technician owns step eight, because tech enablement written by someone who has never picked a lock at eleven at night will be ignored. Steps five and nine can be supported by an outside vendor, but only against the price book and ICP definitions the operator produced.

Watch for three predictable failure modes in the first ninety days. The first is price-book erosion: within a month, techs quietly return to driveway pricing because a customer pushed back and nobody backed them up. Catch it by sampling invoices weekly against the book and by publicly supporting the tech the first time a customer complains about a correctly applied surcharge. The second is intake regression, where after-hours routing silently breaks — the on-call phone dies, the answering service changes staff — and nobody notices for weeks because unanswered calls generate no artifact. Test it yourself: call your own after-hours line every week from an unknown number and time the answer. The third is measurement drift, where the weekly review stops happening once the numbers get uncomfortable. That meeting is the playbook's immune system; if it lapses, everything else decays within a quarter.

The success condition at day ninety is not a revenue number, because ninety days is too short to move an annual figure honestly. It is this: you can state your answer rate, your booking rate, your average ticket by service line, and your repeat rate from memory, and each has moved in the right direction against a written baseline. An operator who can do that has a real go-to-market system. An operator with a beautiful document and no baseline has a brochure.

Related questions

How long before a locksmith GTM playbook shows revenue impact?

Intake fixes show up within two to four weeks because they act on demand that is already arriving. Pricing changes show in average ticket within a month. Commercial account development and review-driven map ranking realistically take one to two quarters to move revenue meaningfully.

Should a two-van shop bother with a written playbook?

Yes, and more than a ten-van shop needs to. At two vans the owner is the system, so every process lives in one head and dies with one bad week. Writing down pricing, intake, and coverage is what makes a third van possible without chaos.

What is the single highest-leverage step to do first?

Fixing intake — answering every call with a firm ETA and a firm price range. It costs almost nothing, acts on demand you are already paying to generate, and every other step downstream depends on having a booked job to work with.

How do you price after-hours emergency work without looking predatory?

Publish the multiplier as an explicit line item, disclose the trip fee and the price range on the phone before dispatch, and have the technician restate the total before starting work. Surprise is what customers punish, not the surcharge itself.

Do you need field service software to run this?

Not below two vans, where a disciplined shared spreadsheet with a job ID column works. Above two vans the coordination cost exceeds the software cost, mostly because spreadsheets stop getting updated during exactly the busy days that matter most.

FAQ

How many service lines should a locksmith operator run at once?

Three is the practical ceiling for a small shop: emergency consumer, scheduled residential and light commercial, and recurring commercial contracts. Each has a distinct sales motion, and running more than three means none of them gets a real price book, a real intake script, or a real owner. If you are adding a fourth line such as automotive key programming or access control, treat it as a deliberate business decision with its own equipment budget, technician training plan, and margin target rather than as an extension of the existing catalog.

What belongs in the playbook document itself versus in a system?

The document holds decisions: ICP definitions, the offer set with inclusions and exclusions, the price book with surcharge rules, coverage rings and ETA promises, the intake script, the dispatch SLA, the technician enablement kit, and the weekly review agenda. The systems hold state: job records, customer history, invoices, payments, review requests. Keeping decisions in a document and state in a system prevents the common failure where the playbook becomes a stale copy of yesterday's schedule and nobody trusts it.

How do you get commercial accounts to switch vendors?

They switch when the incumbent fails — a missed emergency, a lockout during a tenant turnover, a rekey that took three days. Your job is to be the known alternative at that moment, which means periodic low-friction contact, having your certificate of insurance and rate sheet ready to send the same day, and accepting a small evaluative first job without complaint. Expect several touches over months per account, and expect the win to arrive suddenly after a long quiet stretch.

Should the price book be published on the website?

Publish ranges and the trip fee, not exact totals for every scenario. Ranges pre-qualify callers, reduce phone haggling, and build trust in a trade with a well-documented reputation problem around undisclosed pricing. Exact totals invite disputes when site conditions differ from what the customer described. The rule of thumb is that anything you would state on the phone before dispatch belongs on the site.

How do you keep technicians from freelancing on price?

Put the price book on their phone, make it the only sanctioned source, sample invoices against it weekly, and back the technician publicly the first time a customer challenges a correctly applied charge. Freelancing is nearly always a symptom of an unsupported technician rather than a dishonest one — they deviate because the book had no answer for the situation in front of them, so treat every deviation as a gap in the book until proven otherwise.

What metrics should be reviewed every single week?

Five: total inbound calls, percentage answered live, percentage of answered calls booked, average ticket broken out by service line, and repeat customer rate. Review them at the same time each week against the written baseline, change one variable at a time, and record the change. Anything beyond these five is a diagnostic you pull when one of the five moves unexpectedly, not a standing agenda item.

Sources

• https://www.sba.gov/business-guide/manage-your-business/market-price-your-product — SBA guidance on pricing and market positioning for small service businesses
• https://www.bls.gov/ooh/installation-maintenance-and-repair/locksmiths-and-safe-repairers.htm — Bureau of Labor Statistics occupational data on locksmiths and safe repairers
• https://www.consumer.ftc.gov/articles/hiring-locksmith — FTC consumer guidance on locksmith hiring, disclosure, and pricing complaints
• https://support.google.com/business/answer/3038177 — Google Business Profile requirements for service-area businesses
• https://www.bbb.org/all/scamstudies/locksmith_scams — Better Business Bureau research on locksmith pricing and disclosure practices
• https://www.aloa.org/ — Associated Locksmiths of America, licensing, certification, and industry standards
• https://www.irs.gov/businesses/small-businesses-self-employed — IRS small business guidance on recordkeeping, W-9s, and contractor documentation
• https://www.sba.gov/business-guide/manage-your-business/get-business-insurance — SBA guidance on business insurance and certificates of insurance for commercial contracts

Related on PULSE

• [How do you build a pricing book for a field service operator?](/knowledge.html)
• [What does a dispatch SLA look like for a multi-van service business?](/knowledge.html)
• [How do you win recurring property-management accounts as a trades operator?](/knowledge.html)
• [What is the right technician commission structure for add-on revenue?](/knowledge.html)
• [How do you measure cost per booked job across local service channels?](/knowledge.html)