The platform

Eight modules, one registry.

Tickets, assets, preventive plans, costs and suppliers share the same base. There is no parallel spreadsheet and no export to “the other system”.

A cook opens a ticket from his phone in front of a freezer caked with ice, attaching a photo and a voice note to the record.
The ticket starts where the problem is, with photo, voice and asset already attached.

Illustrative images · screens shown with sample data

Tickets with evidence

Seven states, priority, deadline, emergency flag with written justification, comments, responsibility matrix and full history. Resolving requires an attachment.

Assets with memory

Technical profile, versioned documents, occurrences, alerts with per-person read receipts, costs and asset-tag control.

Automatic preventive work

Eight frequencies. Orders are generated inside the database on a schedule — a forgotten plan produces one order, not thirty.

Cleaning

Same engine as preventive work, its own view, with checklist and materials. One order counts in both modules without being executed twice.

Costs

Entries by category, budget versus actual, monthly trend, anomaly flags and attached invoices.

Management dashboard

Five maintenance indicators with editable targets and twelve clickable charts — every number opens the already-filtered list.

Team and access

Four roles, page-level access per person, per-site scoping and bulk user import from a spreadsheet.

Audit trail

Append-only record of who changed what and when. Nothing is deleted; records are deactivated, never removed.

Ready to get maintenance out of WhatsApp?

A 30-minute conversation and a demo using your operation's real data, not sample data.

Create your account, upload your spreadsheets and WhatsApp group — the system arrives already set up. No credit card.