CORE
One inbox. Every truck.
Multi-tenant from the ground up. Add crews,
role-based permissions, audit trails. Strict data
isolation between accounts — the kind built
for franchises and multi-location ops who don't get
to "trust" the database to keep things separate.
Tenant isolation
Audit logs
Role permissions
Encrypted credentials
API keys
INTAKE
Smart deduplication.
If "Jane @ Bayview" emails three times in an hour,
you get one work order — not three. We match
across name, email, address, and intent.
SCHEDULE
Drag-to-schedule.
Calendar by tech, by week, by month. Double-bookings
surface before the truck rolls. Techs get a
phone-friendly view of today's jobs — status,
photos, and customer signature from the field.
EXPORT
Your data, on your terms.
One-click export of every customer, work order, and
message — CSV or JSON. No "talk to support"
gates.
MONEY
Quote it. Bill it. Get paid.
Build estimates with line items, tax, and discounts;
send them for one-click customer approval; convert an
approved estimate straight into an invoice. Invoices
send as a PDF with a pay-online link — card
payments settle through Stripe, and reminders chase
the ones that don't.
Estimates
Approve / decline
Invoices & PDF
Online card pay
Payment reminders
PORTAL
A portal for the customer.
Customers track their job's status, book their own
appointment window, approve or decline an estimate,
and pay an invoice — no login, no internal data
leaked.
REPORTS
Know where the day went.
Revenue collected, completion rate, average time to
close, technician utilization, top customers —
on screen or exported to CSV.
RECURRING
Set the standing jobs once.
Weekly, monthly, quarterly — recurring plans
auto-generate the next work order on schedule so the
maintenance route books itself.
MESSAGING
Texts that land as work.
Inbound SMS attaches to the right work order as a
note; appointment and invoice reminders go back out
by text over Twilio.
INTEGRATIONS
Plugs into your stack.
Push paid invoices and customers to QuickBooks Online
or Xero, fan out signed webhooks to Slack, Teams, or
Zapier, and build on the REST API with scoped keys.
SECURITY
Locked down for real crews.
Two-factor auth (TOTP) with recovery codes, encrypted
credentials, per-role permissions, and a full audit
trail — the table stakes multi-location ops
actually check for.