Concept build: a demonstration project, not client work
A multi-tenant SaaS platform for field-service companies, covering jobs, crews, billing and a complete audit trail.
| Order | Customer | Status |
|---|---|---|
| #20417 | Northwind Depot | Scheduled |
| #20416 | Harbor Clinic | In progress |
| #20415 | Ridge Foods | Awaiting parts |
| #20414 | Cobalt Labs | Completed |
Interface shown with illustrative data.
Say you sell software to HVAC and cleaning contractors. Each customer company has office staff, dispatchers and technicians who need different access. Accounts add seats and change plans. Someone will ask who moved a job, and when. Bolt these on after a quick prototype, and you get leaked data and wrong invoices.
Fieldkeel lays those foundations first: every table carries a tenant ID, enforced by row-level security in PostgreSQL. Roles live in data, so each company sets its own rules. Stripe handles plans and seats, and webhooks keep limits in sync. Every write leaves an audit entry. Office staff dispatch from a Next.js console, and technicians work from a React Native app.
Row-level security scopes every query to one tenant. A forgotten filter in app code can't leak another company's jobs.
Each change records who, when, the old value and the new one. The app can't update or delete it.
Technicians open jobs, log work and take photos without coverage. Changes queue on the phone and sync with conflict checks.
How a request moves through the system.
01Dispatcher creates or assigns a job in the console
02The API checks role and tenant before any write
03The change is saved with an audit entry
04Technician's app pulls the job and syncs updates back
05Stripe webhooks adjust limits when a plan changes
Next concept build
AisleviewMulti-location retailDescribe your version of the problem. We reply with questions and a proposed approach.