The engineer who builds and ships
I use the same stack I sell
I use the same stack I sell. 4Fleet is a live B2B fleet-management SaaS I built and run. NumWise is a live accounting SaaS with format-agnostic bank-statement import across six file formats. Bilanso is a live multi-tenant marketplace reconciliation platform. These are production systems - not showcase projects, not lorem ipsum demos. When I quote a timeline, I am drawing from the last time I built the same thing, not from an estimate spreadsheet.
View full portfolio6+ production systems live
Next.js / Supabase / Claude API
Next.js / Supabase / Drizzle
Next.js / Supabase / Drizzle
- MeowBaby CCinternal/delivered
Next.js / Supabase / KSeF API
- SURBinternal/delivered
Next.js 15 / tRPC / Drizzle
- Irish Transferinternal/delivered
Next.js / Sanity CMS
Engineering quality, not agency markup
Most agencies assign a junior to your project, wrap it in account management, and charge you the markup. I write every line myself - no handoff, no relay. The price reflects the lower overhead, not lower quality. When you message me, the engineer responds; when you ask about a decision, I explain it because I made it.
AI accelerates delivery - it does not cut quality
I use AI as a tool for faster code writing - the same way Excel accelerates an accountant. I design the architecture, review every line of code, and own the outcome. Every project is tested and live in production. Faster delivery is not a quality reduction - it is lower overhead passed to you.
What I build with
Next.js / React / TypeScript (strict) / Supabase / Drizzle / Vercel / Stripe / Claude API / Playwright. Standard, widely-used stack - any senior developer can pick it up.
$ whispr --stack
> next.js 16 . react 19 . typescript (strict)
> supabase . drizzle . stripe . claude-api
> shipped: 4fleet . numwise . bilanso . surb
> status: live in production