Case study
Happy To Deliver platform
Rebuilt a package-delivery platform from a legacy no-code app into a Laravel monolith that couriers, building staff and residents use every day.
- Role
- Lead developer & project manager
- Status
- Live
- Stack
- Laravel 12 · Vue 3 · MySQL · Filament · S3
- Scale
- 49 tables · field couriers · residents across managed buildings
- Base
- New Jersey, USA
Overview
Happy To Deliver receives packages on behalf of residential buildings and gets them to residents. The original product ran on a no-code app that had hit its ceiling: slow to change, hard to secure, and impossible to integrate with the property systems buildings already use.
I led the rebuild as a Laravel 12 monolith, owning the data model, the access rules and the release plan, and running the distributed team that shipped it. The result is one platform with a Filament admin for operations, a Vue 3 app for couriers in the field, and resident-facing notifications, all on a 49-table schema designed for the integrations that came next.
Modules & integrations
-
Region-to-building access scoping
Every staff account sees exactly the regions and buildings it is assigned to, enforced in the data layer rather than the UI.
Operators, drivers and building staff all work in the same system but must only see their own slice of it. Access is scoped from region down to building and applied where the data is queried, so a new screen cannot accidentally leak another building’s packages.
-
Passwordless email & OTP login
Residents and staff sign in with a one-time code instead of a password.
Most residents log in rarely, so passwords were a support burden. Sign-in works with an emailed link or a one-time code; hashing those codes at rest is part of the current security review.
-
Courier operations app
A Vue 3 app couriers use in the field to receive, sort and hand over packages.
The field app is built for speed on a phone in a mailroom: scan, assign, hand over, with the admin panel in Filament for everything that happens back at the office.
-
Yardi integration
A read-only sync of resident, unit and lease data from Yardi, replacing fragile email matching with a real property-system link.
Buildings already keep their resident records in Yardi. Syncing units, residents and leases directly means packages match the right person without anyone retyping a name.
-
Entrata integration
The same property-system link for buildings that run on Entrata.
Following the Yardi pattern, Entrata-managed buildings get resident and unit data synced from their own system of record.
-
Notification reliability
Tracing why some residents never received delivery alerts, and giving them a self-service fix for carrier-level blocks.
Some delivery alerts were being dropped before reaching residents’ phones. The fix traces delivery per message and gives residents a way to clear carrier-level blocks without waiting on support.
Open channel
Got a project?Let's ship it.
Tell me what you're building, the deadline, and whether you need a developer, a project manager, or both. I reply within a working day.