A small stack, chosen for clean handover
Every project ships as code your team can take over without a manual. These are the four tools I reach for most and what I use them for.
Astro · Medusa · Sanity · WordPress
What I build with it
Pick the tool per project, not the other way around. If your team runs a specific stack, I adopt it.
Astro
WebsitesCorporate websites, landing pages and marketing sites. Static-first and fast without tuning, with clean components any frontend developer can pick up.
Medusa
E-commerceCustom webshops without platform limits. Your own checkout, admin and integrations, built on an open source commerce backend that ships its own MCP server and AI toolkit.
Sanity
ContentStructured content your client can actually edit. Real-time preview, custom workflows and no template lock-in.
WordPress
CMS classicsCustom themes and WooCommerce, done properly. The right call when your client's team already lives in WordPress.
Project lifecycle
Scope
A short intake call settles scope, stack, timeline and a fixed price.
- Fixed price before work starts
- A realistic timeline, not a sales timeline
- NDA if you want one
Build
I design and build in your tools or mine, with progress you can show your client every week.
- Weekly visible progress
- Early flags on risks
- Your brand on everything
Handover
Your team takes over a documented codebase, or I stay on for hosting and support under your brand.
- Clean, documented code
- Support under your label if you want it
- No lock-in on my side
Let's talk through your next build.
Send me the brief and I will tell you which of these tools fits, and which one I would leave out.
Got a quick question?Message me on WhatsApp
