Each project, told plainly: what we inherited, what we decided, and what changed for the people who use the result. Clients are anonymised. The engineering is not.
A full WordPress site rebuilt as static HTML with WordPress kept as a headless CMS. Pressing publish is what builds the site, and the CMS can be down without anyone outside the office noticing.
Someone else's React app and a Django admin panel doing duty as a CMS. Three years of quiet work later: a static site, a real authoring experience, and a build that can refuse to deploy.
A concierge team's low-code proof of concept rebuilt as a production application with the same workflow, plus authentication, per-facility isolation, audit trails and PHI handled as PHI.
Spreadsheets, a photo folder and a group chat replaced by one auditable system of record that runs from intake to catalog to auction, with AI drafting the tedious part and a person approving all of it.
A public site, a members' app and the back office a small nonprofit now runs itself from, built for people arriving in grief, with a Hebrew-calendar memorial at its centre.
A giving platform that takes payments for other organizations, so sanctions screening, charity verification and retry-safe grants shaped the architecture instead of arriving after it.
Every one of these started as a conversation about something that mostly worked. Tell us what you have and what it has to do, and we will tell you what we would change and what we would leave alone.