Four doors.One studio behind them.
Lead with the door you walked through — not the full menu.
Payload for content. Medusa for commerce. Custom JavaScript when the platform isn't the answer. AI when the product actually calls for it. Same engineers, end to end.
The four doors
/ 04Pick the door that fits. We'll handle the corridor.
Each door is a real scope, a real timeline, and a senior engineer who has shipped it before. Open one to read the receipts.
- 01Headless content · TypeScript-first
Payload CMS
A CMS your editors actually like and your engineers don't fight.
Payload gives content teams a real interface — typed fields, live previews, role-based permissions — and gives engineers a TypeScript-first backend they can ship features against. We design the schema, build the blocks, migrate the content.
3–8 weeks · single team
Open door - 02Owned commerce · Composable stack
Medusa JS
Headless commerce with the operating model of an in-house team.
Medusa gives you a composable, owned storefront — you keep control of payments, fulfillment, promotions, and the data. We architect the storefront, integrate the stack (Klaviyo, Algolia, your ERP), ship to production.
4–12 weeks · replatform
Open door - 03Bespoke product · Owned codebase
Custom JavaScript
When neither Payload nor Medusa is the right answer.
Sometimes the right system isn't a platform at all. We build custom JavaScript applications — internal tools, marketplaces, niche commerce, B2B portals — when off-the-shelf doesn't fit. Stack: TypeScript, Next.js, Postgres, your auth, your infra.
Scoped per project
Open door - 04Shipped AI · Evals & review
AI Integrations
Claude, OpenAI, Gemini — in the product, not the press release.
AI-native search, support agents, content pipelines, internal copilots, RAG over your data, automation flows. We architect the integration, build the prompt and tool layer in TypeScript, ship to production with evals.
Scoped per project · evals included
Open door
How an engagement runs
/ 04 stepsFour steps. No bench, no handoff.
The same engineer reads your brief, writes the scope, and ships the final code commit. The contract is the codebase — not a deck.
- 01
Day 0–1 · Brief read
A real engineer reads it.
We reply in writing within one business day. Usually with a question or two — sometimes with a polite no. Never with a CRM autoresponder.
- 02
Week 1 · Scope in writing
We propose what we'd actually build.
Architecture, integrations, what's in scope, what we'd push to phase two, what we won't do at all. Fixed-fee where the brief allows, T&M where it doesn't.
- 03
Build window · Working URL
Demos on the real branch, weekly.
Every line is human-reviewed before merge. You watch the product come together on a staging URL — not in a slide. AI accelerates writing, never replaces review.
- 04
Handover · You own it
Codebase, environment, docs — yours.
No platform tax stacked on top. We keep retainer support optional, never mandatory. The repository is yours from day one and stays yours.
What we ship against
TypeScript front to back. Postgres of record.
No mystery stack, no proprietary lock-in. The same building blocks, picked for the door you opened.
Payload CMS
- Next.js storefront · React Server Components
- Payload 3.x · Postgres · Lexical rich text
- Vercel / Node · S3 media · role-based admin
Medusa JS
- Next.js storefront · Medusa modules
- Postgres · Redis · Meilisearch or Algolia
- Klaviyo · Stripe · ERP connectors as needed
Custom JavaScript
- TypeScript · Next.js App Router
- Postgres · your auth provider
- Your infra (Vercel, AWS, GCP)
AI Integrations
- Claude · OpenAI · Gemini SDKs
- TypeScript prompt + tool layer
- Evals · tracing · prompt versioning
// Pick a vendor for the right reasons. Switch when something better lands.
Discovery
Pick a door. Or describe what's broken.
We pitch the problem, not the platform.
Reply within one business day · No discovery deck tax