Roles and permissions
Who can see and change what, defined in the data model rather than bolted on.
SERVICE 02 / WEB APPLICATIONS
Dashboards, portals, bookings, invoicing and internal tools — Laravel with Vue and Inertia, or Next.js, built to your process instead of a template’s.
Laravel / Vue / Inertia / Next.js / MySQL / Redis
Fixed scope, agreed in writing before the build starts.
Who can see and change what, defined in the data model rather than bolted on.
The lists and totals your team actually asks for, with a way to get the data out.
Where money moves, the audit trail is part of the feature, not an afterthought.
Email or in-app alerts tied to events, with a way to turn them off.
The accounting, messaging or POS system you already run.
Every consequential change is attributable and reversible.
STACK
What exists, what it must do, and who maintains it after handover.
A written scope and a fixed quote before anything is built.
Slices you can click in staging, with changes priced in writing.
Monitoring, updates, backups and support under a one-year warranty.
Enough to name the screens and the data. If the process lives in one person’s head, the survey is where it gets written down.
That is usually the brief. The risk is the spreadsheet has years of quiet exceptions — the survey exists to find them.
Yes. Handover includes the repository, the database and the credentials.
The screens your staff use in the field are designed narrow-first; the admin side is designed for a desk.