Context

In facility management and construction, work requests travel over WhatsApp, email and Teams: nothing is traced, ownership is unclear, and billing is done from memory. t-ket centralises that flow into a single multi-tenant system of record.

My role

Founder and sole developer: architecture, backend, domain model and billing. A freelance front-end developer helped occasionally on the UI.

Key features

• Full domain model: sites, buildings, zones and rooms, roles and teams, with multi-tenant isolation.
• 6-status Kanban board and multi-view planning (day / week / month / team).
• Exports to .ics (calendars) and .xlsx (reporting).
• Work-order ingestion by email: a request sent by email becomes a qualified ticket.
• SaaS billing engine: per-session seat counting, overage handling with budget safeguards, price lists, capped discounts and a white-label mode for partners.

Status

In production with its first client, currently being commercialised.

The application

Home: operational counters (overdue, unassigned, due today, to verify) and the six-status work-order board.

Multi-view planning: calendar, week per technician and board. Who works, on what, and who is away.

Milestones: what gets delivered together, by when, and who owns it. A milestone groups work orders with its own progress.

Sites: the location system of record, with access codes, on-site contact and a breakdown into zones and rooms.