ZARAS · Industries
Every trade runs differently. The operating record stays the same.
HVAC tune-ups, plumbing emergencies, electrical projects, cleaning routes, roofing storms — different rhythms, one record from call to schedule to invoice to paid.
Trades supported30+
Operating shapes6
Crew range1–40
Private beta — fit reviewed within 48h.
01 · Trades
Built for home-service operators across 30+ trades.
Trades are labels. The work has a shape.
30+ trades, six operating shapes. Pick any trade to see how it maps — or pick a shape to see the trades that run it.
The record stays the same
An HVAC tune-up, a July no-cool call, and a rooftop replacement are three different shapes of work — one customer, one record, first call to paid. Pick any trade to see the shapes it runs.
Zaras runs
Also supports:
chimney & fireplace, junk removal, irrigation, concrete & masonry, flooring, remodeling, snow removal, restoration, locksmith, solar, septic, gutter, deck & patio.
02 · The work mix
The work varies. The record doesn't.
No trade runs one kind of work. The same business answers an emergency, holds a standing route, and closes a multi-week project in the same stretch — and that mix is where single-purpose tools break.
- One customer record
- No re-keying between steps
- First call to paid, one trail
-
HVAC
A spring tune-up, a July no-cool call, a rooftop replacement.
-
Plumbing
A leaking shutoff, a water-heater quote, a property-manager drain ticket.
-
Electrical
A breaker trip, a panel upgrade, a change order.
-
Landscaping
Spring routes, midsummer overgrowth, fall cleanup.
-
Cleaning
Every other Friday at one home, nightly at an office, six sites on one account.
-
Roofing
A storm call, an inspection, a deposit.
03 · Operating shapes
Built for the shape of the operation.
Most operators run two or three shapes at once — recurring routes, urgent calls, projects, commercial accounts, branches, and seasonal peaks. Zaras maps each trade to the operating shapes underneath, so one system can bend to how the work actually moves.
01Maintenance
Recurring service
A maintenance plan fills Tuesday's route before the phones open. The tech sees prior notes, the customer gets the arrival window, and the next visit stays tied to the same record.
Zaras runsRecurring visits, route assignment, customer history, crew notes, and renewal timing on the customer record.
Record holdshistory · route · renewal
02Break-fix
On-demand repair
A 4:12 PM no-cool call comes in. Dispatch finds the right tech, the customer gets an ETA, and the diagnosis turns into an approved repair before the truck rolls.
Zaras runsSame-day intake, dispatch, on-the-way updates, customer history at the door, and approval-to-payment in one flow.
Record holdsETA · diagnosis · approval
03Multi-day
Project work
An estimate gets accepted and the job stops being a maybe. The deposit invoice goes out, the crew gets scheduled, and every update stays attached until final payment.
Zaras runsEstimates, deposit invoices, crew scheduling, job updates, change tracking, and final collection from one record.
Record holdsdeposit · crew · change order
04B2B
Commercial accounts
A property manager opens work across multiple sites. Each visit routes to the right crew, rolls into account history, and stays clean for terms billing.
Zaras runsMulti-site work, account-level history, NET-term invoicing, service records, and commercial billing context that survives every visit.
Record holdsaccount · sites · terms
05Multi-branch
Regional operators
One crew gets overloaded while another has room on the board. Dispatch needs shared visibility across locations without losing which crew owns the work, revenue, and follow-up.
Zaras runsShared dispatch, crew assignment, location tags on every job, and reporting that keeps local work tied to the larger operation.
Record holdsbranch · owner · reporting
06Cyclical
Seasonal operations
Peak season hits and the route board compresses fast. New crews come on, repeat customers return, and every visit still needs history from last year.
Zaras runsSeasonal scheduling, crew assignment, route density, customer history, and service records that carry into the next peak.
Record holdspeak crews · repeats · season history
Private beta access
REQ-2847-OPS
OPEN
01
Request
Shape-of-business form. Crew count, current stack, where it hurts.
T+0s
form submitted
REV-████████
REVIEWING
02
Review fit
Scope + stack check. No queue, no waitlist — fit reviewed within 48h.
T+≤48h
reply either way
WO-PENDING
APPROVED
03
Onboard
Workspace live, imports done, first dispatch on the operating layer.
T+0d
first dispatch live
ZRS · Operating record
Whatever the trade, the work runs on one record.
Private beta for service businesses running 1 to 40 crews. Tell us your trade, crew count, current stack, and where the handoffs break — we'll review fit within 48 hours.