I cultivate web applications from the root system up — clean domain models, well-tested APIs and backends that keep growing calmly as traffic, teams and features multiply.
Growing instructions, origin and temperament of a backend developer who prefers deep roots over quick blooms.
I'm Brandon, a backend-focused PHP developer who has spent the better part of a decade building with Laravel. My work lives where business rules meet databases: billing engines, booking systems, multi-tenant SaaS platforms and the APIs that feed mobile and SPA front-ends.
I like code that is easy to prune. That means expressive Eloquent models, thin controllers, well-named service and action classes, queues for anything slow, and a Pest or PHPUnit suite that lets the next person refactor without fear.
Beyond writing features, I care about the soil: CI pipelines, Dockerised local environments, sensible caching with Redis, observability, and the occasional rescue mission for a legacy PHP 5 codebase that needs careful repotting into modern Laravel.
Each skill is potted and measured by growth stage — from seedling to fully mature, flowering in production.
A few labelled specimens from the greenhouse — each grown from a seed of a problem into something people rely on daily.
A multi-tenant subscription and invoicing platform for B2B software vendors, handling plans, metered usage, proration and dunning across several currencies.
An appointment scheduler for a network of private clinics, with practitioner calendars, SMS reminders, waitlists and a patient self-service portal.
A versioned REST API that unifies five courier integrations behind one contract, with rate-limiting, Sanctum token auth and OpenAPI documentation.
Incremental migration of a 12-year-old custom PHP 5 publishing CMS to Laravel using the strangler-fig pattern, with zero downtime for the editorial team.
Read the trunk from the bark inward: every ring is a season of shipping, learning and branching out.
Have a Laravel project that needs planting, pruning or repotting? Reach out directly — I usually reply within one working day.
Whether it's a fresh Laravel build, an API that needs to scale, or a legacy PHP application ready for careful repotting, I'd love to hear what you're growing.