Field service / HVAC
Dispatch boards, on-site state tracking, invoicing the moment the work is done, and an audit trail every operator can read. Single-tenant-multi-facility or one-tenant-per-location — both shapes ship.
HVAC contractors, electricians, plumbers, locksmiths, appliance-repair operators, and multi-trade shops with 5-50 field technicians across one or more locations. You have a dispatcher, an office team, and a customer base that mixes residential maintenance contracts, commercial service calls, and the occasional install. Your current stack is some combination of ServiceTitan, Housecall Pro, a homegrown spreadsheet, a separate accounting package, and a lot of Slack messages.
This page is for the moment you're evaluating a replacement for that stack or looking for the back-of- house operations layer underneath it.
What ships today
The field-service stack on FastYoke is a combination of marketplace apps plus the free Logistics core. Six apps cover intake-to-invoice end-to-end.
The flagship board for this vertical. Every job moves Created → Dispatched → On site → Completed → Invoiced → Paid. The dispatcher sees every open job by stage, what has stalled, and each technician's day; an operations assistant flags what to fix.
Customers, equipment-on-site, contract status, service history. Linked to the job entities so a dispatcher opening a job sees the full equipment history without a context switch.
AR / AP, invoicing, payment capture, GL posting and month-end close, with a chart of accounts built for a service trade — truck stock, deferred maintenance-plan revenue, warranty and callback cost.
Truck stock, parts on hand, reorder points. Stock issued from inventory depletes on hand, and the GL Pack posts COGS on issue if you flip the toggle.
Facilities, bins, zones, movements, immutable event log. Free with every tenant — the shared substrate every field-service multi-location operation builds on.
Public maintenance-request forms, online quote requests, contact forms. Cloudflare Turnstile + PDF copy on submit. Free forever; you don't pay extra for intake.
Extend without code
Field-service operations are full of small per-shop quirks — the pricing book, the truck-stock policy, the maintenance-contract billing cadence. Most don't require an engineer:
AwaitingApproval state between
On-site and Invoiced for jobs over a dollar
threshold. The FSM Designer adds the guard
({">": [{"var": "total"}, 1000]}). No code change.The low-code surface is bounded by what the schema can express. When the customization is broader than schema-shape, you're in customization territory — covered next.
Customize deeply
FastYoke ships a typed SDK (@fastyoke/sdk-next,
@fastyoke/sdk-vue, plus a Rust crate for the kernel).
For field-service contractors with engineering bench
(usually rare in this vertical), the SDK enables:
For most field-service operations, the right shape is a Strategic Partner engagement:
Most field-service prospects engage iNetko before they engage their own engineering team. The math usually wins on the partner side — iNetko has done this enough times to make scoping mistakes that you'd otherwise make yourself.
Honest tradeoffs
What FastYoke isn't for field service
If those tradeoffs are deal-breakers — stay on ServiceTitan. The vertical SaaS has those features because the vertical SaaS is built only for HVAC. FastYoke gives you the operational substrate, the workflow engine, and the multi-app integration story for the cases where the vertical SaaS is overkill or doesn't fit your specific shape.
Request early access
Talk to iNetko
Already in retail / POS / food service paired with field service? See Pay n Go Systems — our first named Channel Partner — for the integrated storefront-plus-field-tech shape.