Your size · 41–75 person teams
Scale without the enterprise implementation.
Multi-location companies buy governance. Here 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 person teams
Two locations
Included inside the same legal company.
71 people
Owners, office, every truck. $0 each.
The bill
Posted before anything runs. No quote to decode.
The software bill
$99 / month
The pressure
What breaks at this size.
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.
41–75 person teams
The owner can’t see every job. The record can.
At this size the company runs on its systems, and the systems run on one record.
Turned on at this size
The modules that earn their place.
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 rhythm
Daily, weekly, monthly.
01
Daily
Each location runs its own board. Nobody merges spreadsheets to know what happened.
02
Weekly
The cross-location read: closed, open, unpaid, by shop, by crew, in one place.
03
Monthly
The company view for leadership, out to a spreadsheet, without a BI project in the way.
A day at this size
One working day, on the record.
6:15
Two boards open
Jasper and the second shop dispatch independently, on the same system, under the same book.
9:30
The transfer
A crew crosses town to cover the other location’s emergency. One record; nothing re-entered.
12:00
The standard holds
Both shops quote the repipe from the same book. The company’s price, not the branch’s guess.
15:30
The exception list
Every stuck or unpaid job across both locations, on one screen, before it ages.
17:45
The company read
Leadership sees both shops without asking either: what closed, what’s out, where the week went.
The stage decision
Who owns the standard?
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
Straight answers.
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.
Start
Start where you are.
$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.