Development Agency
Contact Sign in Get a project quote

Service

Locksmith website development

For owners and dispatchers of locksmith businesses who need a website and back office built around the dispatch of mobile engineers, the record of who was let into what, and the commercial clients whose keys and locks you look after.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

A locksmith business lives on the dispatch moment.

  • Someone is locked out at a flat door at seven in the evening; the call comes to whichever mobile is on, the dispatcher rings round three engineers to find who is nearest, and the customer waits with no idea whether anyone is coming.
  • The engineer who takes it writes the address on his hand.
  • When he arrives there is the question every locksmith faces: is this person entitled to be let in?
  • He checks a driving licence and a utility bill, and the record of that check is his memory of it.
  • Six months later a letting agent asks who authorised entry to a flat and the business has nothing written down.

Where it gets harder

Commercial work has a different failure.

  • A business client with twelve doors on a suited system expects the locksmith to know which cylinder is on which door, how many keys were cut and who holds them.
  • That knowledge lives in the head of one engineer who has been there for years.
  • Maintenance contracts renew by habit rather than by a system, survey reports are a word-processor file saved under the wrong client name, and the price list by job category exists as a laminated card in each van, with each van's card a slightly different version.

Scope of the service

What the build covers

A custom locksmith build covers the trade core shared with other local services:

  • Service area by postcode district or radius
  • A request form with photos of the door or lock
  • Job records moving through enquired Quoted, booked, in progress, complete and invoiced
  • Engineer scheduling with travel buffers for planned work
  • Quotes and invoices with line items and deposits approved online
  • Job photos before and after
  • Review requests at completion

The locksmith-specific layer is where the work is. Emergency dispatch gives the dispatcher a live map of engineer status, on a job, free or off shift, so an incoming entry call is offered to the nearest free engineer and the customer receives a message showing the engineer is on the way with an estimated arrival the engineer sets from the van. An identity verification record is completed before any entry job is started: which documents were seen, the relationship to the property declared, a photograph of the authority where your procedure requires it, and the engineer's confirmation, all stored against the job. For business clients, a key and lock register records each door, cylinder, keying and the keys issued and to whom. Security survey reports are produced from a structured template you supply. Recurring maintenance contracts for commercial clients hold the sites covered, the visit schedule and the renewal date. A price list by job category, with every figure entered by you, drives quick quoting from the van.

Deliberately out of scope

  • Vehicle telematics hardware, accounting and payroll, and any judgement about whether a verification is sufficient, which remains the engineer's and the business's own procedure

When the scope grows

Scoping scenario

A locksmith with four mobile engineers, two on an evening rota, handles twenty entry jobs a week and holds registers for thirty commercial clients including two property managers with suited systems across many buildings. A one-van locksmith doing mostly daytime lock changes.

That needs

  • The request form
  • A diary, verification records and invoicing
  • The scope document names which build is being made

Deliverables

What you receive

  • Discovery notes from a walk-through of an emergency entry job and a commercial key register visit
  • A scope document naming each dispatch and job stage, the verification record fields and what stays outside the system
  • Design of the dispatch map, the verification record on the engineer phone, the key register and the survey report
  • The build, deployed to your hosting or hosting we manage
  • Migration of customer, contract and key register records from spreadsheets or an existing app where relevant
  • Training for the dispatcher, the engineers and the owner, with a written guide
  • Handover material and ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access to your current call log, price card, verification procedure, survey template and the list of engineers and shifts, with one named contact.

    Project stage: Onboarding

  2. Planning

    Discovery with the owner and the dispatcher; the dispatch flow, the verification record, the register model and the contract rules are agreed in the scope document.

    Project stage: Planning

  3. Design

    Clickable designs of the dispatch map, the engineer phone screens for accepting a job and completing verification, and the key register for a multi-door site.

    Project stage: Design

  4. Development

    Requests, jobs and price list first; then dispatch and live status; then verification records; then registers, surveys and contracts.

    Project stage: Development

  5. Client review

    Your engineers run a test fortnight with live dispatch alongside the phone round, including evening work, and check every verification record against your procedure.

    Project stage: Client review

  6. Revisions

    Findings are corrected and re-checked against the scope document and the verification fields you specified.

    Project stage: Revisions

  7. Ready for launch

    Registers and contracts imported, on-the-way messages tested against numbers you control, price list loaded, launch list signed.

    Project stage: Ready for launch

  8. Delivered

    Dispatch runs through the system; hosting and maintenance continue under their own agreement if chosen.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Card payment providers for payment at the door and invoice settlement
  • SMS providers for on-the-way messages and arrival updates set by the engineer
  • Mapping services for engineer position, nearest-free dispatch and travel estimates
  • Accounting software for invoices, contract billing and payments
  • Calendar feeds for planned work on engineer phones
  • Key-cutting and cylinder supplier catalogues for register part references

How we would approach it

Worked example

Concept demo

A four-engineer locksmith with an evening rota and property-manager clients

The situation

A locksmith was dispatching by ringing round engineers and had no written record of the identity checks made before entry jobs.

Why it is a custom build

The verification record gating the job status is what makes this a custom build; dispatch apps move jobs along without asking who was let in and on what basis.

The scope we would propose

  • A dispatch screen showing each engineer as free, on a job or off shift from their phone status, with an incoming entry call offered to the nearest free engineer and the customer messaged once accepted
  • A verification record that must be completed on the engineer's phone before the job can be marked in progress, with the documents seen and the declared relationship to the property
  • Key and lock registers for two property managers holding every door and cylinder across their buildings
  • Maintenance contracts with a visit schedule and renewal reminders

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of mobile engineers and whether an evening or night rota is run
  • Live dispatch with map positions and the mapping provider involved
  • Verification record fields and any photo or signature capture your procedure needs
  • Number of commercial clients with key and lock registers and their size
  • Security survey templates to lay out and the report output
  • Maintenance contracts, visit schedules and renewal billing
  • Price list complexity by job category and how quotes are built from it
  • Hosting choice: your own hosting or ours

Start from a package

Locksmith business package

Live dispatch to the nearest free engineer, on-the-way messages, identity verification recorded before entry, key and lock registers for business clients, survey reports and maintenance contracts.

Custom build
View the package

FAQ

Frequently asked questions

How do you decide between a custom build and the package?

If your dispatch, verification and register needs fit the way the locksmith business package works with configuration, we quote for the package and say so. Custom work is the honest route when dispatch must follow a particular rota logic, when a property manager wants their own view of registers, or when the verification procedure needs fields beyond the standard record. Discovery is where we tell you which.

Does the system decide whether someone is entitled to entry?

No. The verification record captures what your engineer saw and what the customer declared, following the procedure you define. The decision remains the engineer's and the business's own; the system makes sure it is recorded and cannot be skipped.

Are the arrival times promised to customers?

The estimate shown to a customer is set by your engineer from the van when accepting the job, and updated by them. It is your business's own estimate from your own dispatch data; neither the system nor we promise response times.

Can commercial clients see their own key register?

If scoped, yes. A client login can show the doors, cylinders and keys issued for their sites and request a visit, without seeing any other client's data.

Who owns the system afterwards?

You do. Source code and data, including verification records and registers, are handed over at delivery. Hosting and maintenance are optional and separately agreed.

Get a project quote for locksmith software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences