Trust One
Client, task and billing system for a professional-services firm: projects, appointments, invoices with split payments, and multi-level approvals.
- Type
- Client projects
- Stack
- Laravel
- Client
- Trust One
- Year
- 2022 to 2026
- Role
- Backend developer.
The problem
The firm had grown into 341 routes of legacy modules where permissions were checked per menu rather than per action.
What I decided
- Refactored authorization into role plus action across every route, with an approval hierarchy on top.
- Modelled invoices and debit notes with multiple payments, each with its own proof, instead of one paid flag.
- Exported to the accounting package the firm already used, so nobody retyped numbers.
Where it landed
Production data today: 432 clients, 1,981 transactions and 8,322 tasks across the firm.
All projectsNext project: Foodcourt Sungai Panas
Client systems stay private: no source code, internal URLs or production screenshots appear here. Every figure comes from the repositories or a read-only count on the production database.