Composable
Use what's solved. Compose where it works. Build custom where it earns its place.
Custom when needed. Built to scale.
Use what's solved. Compose where it works. Build custom where it earns its place.
Designed to grow from day one, not patched under fire. Most apps bolt this on later.
Auth done right. Permissions modeled, not assumed. Most apps treat security as a sprint they'll get to later.
Local-first by default. State that survives, syncs that resolve. Most apps die when the network blinks.
The Stack
A curated short list of the tools I reach for when shipping something new. Opinionated, not exhaustive.
Claude is the model I reach for. Code, copy, decisions.
Zero JS by default. Svelte islands where interactivity earns its place.
The Proof
A real SaaS, running in prod. Built on the same stack I'd recommend to you.
QuoteLogic started as a tool I needed myself. The thesis: pick modern, composable primitives, wire them well, and spend your time on product, not plumbing. QuoteLogic took less than a month to productize.
The result is a system that ships features fast, holds up under load, and doesn't require a retention engineer to keep running. It's a working blueprint for what "composable" looks like in practice.
The Build
Stack decisions, tradeoffs, things that worked, things that didn't. Documented so you can evaluate the thinking before you evaluate the work.
I had a product. I needed auth, billing, a real database, production infra. Here's how I composed it in four weeks, but that's not the timeline I quote to clients.
Postgres was the proven default. Convex was the right call. Where I'd reach for Postgres anyway.
Contact
No pitch, no sales call. Tell me what you want to build. I'll email back within 48 hours.