tile 01 · design
ops writes
the workflow.
35 step-type primitives, dragged on a canvas, versioned like code, published in seconds. no release. no app store.
ops writes the workflow once. onfield runs it on every truck, every visit, every signoff — offline by default, synced before the tech leaves the driveway.
01 — the platform
tile 01 · design
35 step-type primitives, dragged on a canvas, versioned like code, published in seconds. no release. no app store.
tile 02 · run
one screen, one thumb, glove-friendly. offline queue, native camera, signed pdf — built for the truck, not the browser.
soon · jul 2026
tile 03 · close
signed pdf, captured signature, webhook to your crm — before the rep is back in the truck.
soon · jun 2026
tile 04 · see
live feed, flagged readings, per-workflow report. the audit is a query, not a binder.
soon · sep 2026
02 — verticals
the same runtime, the same evidence pipeline, the same offline queue — under every workflow. ops never makes a tech learn a new app to handle a new job type.
"we wrote the diagnosis form once. every tech runs the same one now — and i stopped getting 9 pm phone calls about which checklist."
"vitals, medication photo, condition note, signature. four steps. compliance auditor signs off in minutes, not days."
"barcode scan, drop photo, signature, COD. the driver does not fight a UI in the rain. dispatch sees the proof before they are back in the cab."
"site survey, sizing, pricing cascade, margin guard, branded proposal — signed at the kitchen table. no spreadsheet. no second visit."
"photo grid, scoring, signoff. the report is finished — and signed — before the inspector pulls out of the driveway."
"permits, sub-contractors, daily punchlists, walk-down. one workflow runs the job from kickoff to closeout — the GC sees what is actually done."
"hospice, dialysis, mobile vet. every visit is a record. every record is a charge. compliance auditors stop asking for the PDF."
the runtime does not care what you call the job. write the workflow; we will run it.
03 — built for the truck
we did not port a browser. the runtime was built for a panel van, in the rain, with one bar of signal — and a phone in a glove. tap targets that miss are a safety issue. tabs and wizards lose data. spinners get thrown across a parking lot.
— operators do not visit this page. ops does. this is the half ops cannot watch.
06 — why we built this
we tried creatio. it is a fine browser crm and a brutal mobile experience for anything that lives in a basement or a panel van. workflow apps run badly on it because the runtime was never written for the truck.
we tried custom-building it. one cpq screen for a field-sales rep was 80+ hours of bespoke react-native, then it had no offline, then ops could not change it without us. then we did it again for an asset-tracking app. then again for an inspection app.
onfield is the third try. one runtime. one file format. the workflow is configuration. the dispatcher edits it on a tuesday afternoon. engineering does not ship a release.
— made by people who got tired of building the same panel-van screen.