Your size · 41–75 person teams · Appliance repair
Multiple locations and governance needs: for appliance-repair 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
Warranty service
Diagnose, verify coverage, order the part, complete the repair, submit the claim, reconcile the payment. One workflow, not six spreadsheets.
02
COD repairs
Diagnose, quote from the book, collect at the door. The customer is not waiting on a mailed invoice.
03
Parts flow
Parts arrive at the depot, get logged, get assigned to the job, and move to the truck, so the truck actually has them.
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
Warranty details are scattered
Coverage dates, claim numbers, and billing rules across spreadsheets and inboxes turn paid work into rejected claims.
“I thought it was on the truck”
A part in the wrong place is a second visit the customer remembers.
The first visit doesn’t fix it
Without the model’s diagnostic history, the tech arrives to look instead of to repair.
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 appliance-repair 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.
Appliance repair 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.
