Platform
Web apps I build and where I draw the line
I build inventory tools, booking systems, client portals, SaaS MVPs, dashboards, and approval workflows. The focus is business software that replaces spreadsheets and email chains. For broader platform work, see the Webflow developer overview.
Technical
The right stack for the job
The interface, data and automation should fit the product rather than force it into one platform. I use Astro or a custom front end for browser products, and Expo when an app needs a shared path across mobile and web. PostHog can help measure behaviour, while Vercel, Cloudflare and Resend support delivery and communication where they fit. I choose the simplest setup that meets the users, security and growth plan. See how I choose the stack.
SaaS
SaaS development: from idea to paying customers
I ship the smallest version that proves demand, then add authentication, admin tools, and a heavier backend only when usage justifies it. This keeps the first release focused and gives later decisions real data.
Process
How I build web apps that teams actually adopt
Discovery starts with the workflow your team uses now. A working prototype reaches users early, so I can remove friction before the full build. The aim is a familiar tool that saves time from day one. See conversion optimisation.
From manual workflow to useful software.
- Discovery and workflow mappingMap the current workflow and the best automation opportunity.
- MVP build and user testPut a working prototype in front of real users and data.
- Launch, monitor, iterateShip the MVP and prioritise new features from actual usage.
Show me the work that still lives in spreadsheets and email.
I can help turn the repeated steps into a useful product your team or customers can actually use.