Custom web applications
Greenfield builds in React + Node + PostgreSQL. From schema and ingestion to interface, written so the next developer can pick it up cold.
A decade of full-stack practice, distilled into engagements that actually launch. Custom web applications, e-commerce, and the careful modernisation of systems other developers won't touch -- shipped on time, on budget, and built to last.
The role on the box says solutions architect, which is true, but the work itself is rarely tidy. Most engagements need somebody who can write the proposal, draw the diagram, talk to the stakeholders, write the code, deploy the code, and explain the code -- the same person, the whole way through. That is what's on offer here.
Greenfield builds in React + Node + PostgreSQL. From schema and ingestion to interface, written so the next developer can pick it up cold.
Custom Node storefronts -- Next.js, headless catalogues, Stripe-backed checkouts. Carts, subscriptions, fulfilment, migrations -- delivered without losing orders along the way.
Classic ASP, old PHP, the systems no one else will touch. Incremental hardening rather than the high-risk rewrite that breaks the business.
REST, GraphQL, webhooks, third-party plumbing. Designed to survive the partner who didn't read the spec and the field that goes null on Tuesdays.
Figma to production React. Pixel-accurate, accessible by default, built to the design system instead of around it -- read carefully, not approximated.

No account manager between you and the work. No junior off-shore team copying your brief into Asana. The same person who scopes the engagement writes the code, deploys it, and is the one you email when something needs adjusting three months after launch.
Small practice perks that compound over the lifetime of an engagement. The kind of details that are easy to overlook in the proposal and impossible to overlook in the project.
Multi-monitor setup, gigabit fibre, redundant backups, and a quiet room. The infrastructure of a small studio, run by one person.
Stakeholders shouldn't need a glossary to follow their own project. Updates and proposals written in the language they actually use.
Based UTC-5, but the schedule flexes to a four-hour overlap with most working hours from Lisbon to Los Angeles when an engagement asks.
Engagements run on weekly demos and a fixed launch date -- but the actual hours of the week flex around your team's schedule, your stakeholders' availability, and the time zone you actually work in.