Your size · 41–75 person teams · Locksmith
Multiple locations and governance needs: for locksmith companies at this size, a second location inside the same legal company is included, the crew is never a seat count, and what is still being built says so in plain words.
41–75
The pressure
Location sprawl
A second shop should not mean a second system. Locations inside the same legal company ride the same company record at no extra charge: same book, same board grammar, one bill.
The fleet question
Trucks with GPS are Later on the roadmap. Fleet connectivity is posted at $20 a device before it ships. Until then, the board already answers where the work is.
Procurement wants a contract
Security documentation is reviewable before rollout, and contracted terms are a conversation with a person, not a quote generator. Month-to-month stays the default.
The work
01
Emergency lockouts
Routed to the nearest truck with an ETA the customer can see: the minutes that decide who gets the job.
02
Commercial access
Recurring inspections, SLA terms, and renewals for the accounts that pay every month, with the work documented per site.
03
Automotive
VIN and ownership verified before dispatch, and the documentation kept on the job record.
Turned on at this size
Everything below is in the one $99 subscription. Where a module is still being built, it wears the roadmap’s own word instead of a promise.
Locations
The second shop on the same record. Included inside the same legal company.
Owner reports
Both locations, one read. Spreadsheet out.
Security
Row-level tenant isolation; cards held by the processor.
FleetLater
Connected trucks, $20 / device, posted ahead.
APIs and webhooksLater
Ordinary calls at $0. Public keys after Core is live; the developer surface deepens Later.
Multi-companyLater
Franchise and group oversight on top of Core.
The old way
Instant dispatch or no job
A lockout customer on the curb does not wait for a call back.
Key codes in spreadsheets
Security-sensitive records in a shared file are a liability, not a system.
Commercial wants proof
Access-control clients expect documented work and scheduled reports, not an invoice and a wave.
The stage decision
The company. Both locations run the same book and the same board: governance as a shared record, not a policy binder.
Asked at this size
What does Thorbis cost a locksmith shop this size?
$99 per company per month, unlimited people, every module included as it releases. Plus metered usage. $15 included each month. The size changes; the bill does not.
Can this really run a 75-person, multi-location operation?
The operating loop, the board, the field app, and multi-location records: yes, today, with unlimited people. Fleet, deeper APIs, and multi-company franchise control are Later on the roadmap, in the roadmap’s own words. We will not sell those early.
Do we have to pay per seat at this size?
No. Seventy-five people costs what seven does: $99 for the company, every location inside it included, and metered usage at posted rates. Headcount is not a pricing event.
What about contracts, security review, and procurement?
The security page documents tenant isolation and payment handling for review before rollout, and contracted terms are a conversation. Email the context and a person responds within a business day.
Locksmith at every size
41–75 person teams, other trades
Start
$99 / company. Plus metered usage. $15 included each month. Grow into the next stage without migrating out of this one.
Coming from a suite? We’ll extract your records.
Rather talk first? Email the team.
