Use cases
Same foundation, whatever you build.
Whatever you’re building, the backend underneath looks the same: tenants, a data model, rules, an audit trail. Here’s how that maps onto four industries.
Clinic management
HealthcareThe model you’d sketch
Patients belong to clinicians, appointments link the two, invoices roll up per patient. Each clinic is a tenant with its own data.
What Fluidlee runs
- A rule blocks any invoice over a threshold pending manual review
- A per-clinic custom field for whatever one practice needs all its own
- 365-day audit retention on the tier that regulated clinics ask for
What stays yours
The scheduling experience, the clinical workflow, the brand your clinics log into every morning.
Field service
OperationsThe model you’d sketch
Jobs reference a technician and a site; assets track what’s installed where. Each operator running the platform is a tenant.
What Fluidlee runs
- A webhook fires the moment a job flips to “complete”, into billing, into notifications
- A computed “overdue” flag derived from the due date and status
- A nightly scheduled rule that sweeps for jobs past SLA and escalates them
What stays yours
Dispatch logic, the technician’s mobile app, the routing that makes your product worth paying for.
Property management
Real estateThe model you’d sketch
Properties contain units, units carry leases, leases link to residents. Every management company on your platform is a tenant.
What Fluidlee runs
- Foreign-key validation that keeps every lease pointing at a unit in its own company
- A rule that creates a renewal task 60 days before a lease ends
- An audit trail on every rent change, with the before and after captured
What stays yours
The resident portal, the accounting integrations, the reporting your customers renew for.
Inspection & compliance
Regulated opsThe model you’d sketch
Inspections gather findings and produce reports; inspectors are scoped per organization. Each firm is an isolated tenant.
What Fluidlee runs
- A rule that keeps an inspection open until every finding is resolved
- Stored calculated risk scores that stay filterable and sortable
- A dedicated database per tenant for the firms whose contracts demand it
What stays yours
The inspection workflow, the offline capture, the report templates that are your actual product.
The pattern
Every one of these products wins on the part only you can build, not on tenants, audit logs or foreign-key validation. Fluidlee runs everything in the first list, so your time goes to the last one.
Building something not on this list?
Fluidlee adapts to any product you build. You define exactly the entities it needs. Tell us yours.