Custom ERPs, web apps, dashboards and AI automation — built, deployed and kept running, end to end.
One system for the whole business, built around how it actually works.
Typically3 — 10 months
How this worksInfrastructure your engineers use without filing a ticket.
Typically4 — 12 months
How this worksAI systems that are trustworthy enough to keep in production.
Typically2 — 7 months
How this worksPHP and Laravel are where most of my production code lives. Everything else here earns its place by being in something I have actually shipped.
I deploy and run what I build. Owning the server is not a side task — it is where most of the real failures show up.
A dashboard is only useful if the person opening it trusts the number. Most of the work is upstream of the chart.
Practical automation inside real workflows, with the human checkpoints kept in.
The parts of the job that are not code but still decide whether a project lands.
Listed honestly. I am working in these, not claiming years in them.
Code that works on my machine is half a job. I would rather design the database, ship the deployment and carry the pager than hand over at the edge and hope.
A dashboard nobody believes is worse than no dashboard, because people start keeping a private spreadsheet instead. Getting the data right upstream is most of the work.
A nightly file drop that works today beats an elegant API that arrives next year. I would rather remove a dependency than argue with it.
Every framework I have picked up stuck because I shipped something real in it and had to live with the decisions afterwards.
Open to full-time engineering roles, and taking on selected freelance work.
