Elite Smart Build.

The context

Elite Smart Build delivers turnkey hotel refurbishments without structural works. It has thirteen years in the market and more than 200 projects across twenty countries. Its seven departments, from purchasing and logistics to the site teams, run dozens of works at the same time, and the company wanted a platform of its own where everyone sees the same live information: the daily plan, budgets, tasks and every delivery that reaches a site.

What we found in discovery

We started from the way Elite already works, not from a blank page: its works calendar, its quotations, its site procedures and its phases by department. From those we derived the entities that matter: works, phases, departments, people, suppliers, quotations, shipments, receptions and incidents. Twelve modelling questions were agreed with the client in writing before a line of application code existed, and the scope was fixed in a signed specification: eleven modules for Phase 1.

How it runs now

Access control lives in the database, not in the interface: row-level security is enabled and forced on all 23 tables, roles come from a ten value enum, and a trigger writes every change to an immutable audit log that only management can read. A Supabase Edge Function on Deno runs Monday to Friday and emails each department its open items from the client's own domain, verified for DKIM and SPF through Resend.

The application was scaffolded in Lovable and then fully detached: its own GitHub repository, its own Supabase project and its own Vercel deployment, with no dependency on a third-party runtime. Before the first user logged in the platform passed an adversarial multi-agent audit and all 59 confirmed findings were fixed. The first version reached production about a month after development started, with ten role-based accounts and a weekly review cadence with the client team.