Services / What we ship
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.
Typical scope · scoped per project
Symptoms we recognise
What ships
/ 04 deliverablesBespoke product
Internal tools, marketplaces, B2B portals, niche commerce — built around how you work, not how SaaS thinks you should.
TypeScript front-to-back
Same TypeScript on frontend, API, worker, migrations. Refactors travel safely across the stack. No JS-to-Python rubicon.
Postgres of record
A Postgres schema you can read. Views, indexes, foreign keys — not vendor table magic. SQL you can audit at 2am.
Owned codebase
GitHub, your environment, your deploy. We pair with your team during build and step away cleanly. No license you keep renting.
How this engagement runs
Week 1 · Discovery & spike
One week to model the domain. We ship a thin vertical slice of the gnarliest piece — auth, billing, the workflow nobody wants to own — before scoping the rest.
Week 2 · Architecture in writing
Decisions written down before code lands. Reviewed with your team. Trade-offs in the open.
Build · Vertical slices
Not horizontal layers. You see real users in real flows, weekly. The thing that ships in week 3 still works in week 12.
Hand off · Step away
Knowledge transfer happens during the build, not at the end. We're a phone call away, not a dependency.
Stack we ship against
We pass when
The brief is undefined, or you need a vendor to staff tickets instead of a team that ships product.
Field questions
We ask whether the problem fits a CMS shape or a commerce shape. If it does, we use the platform. If it doesn't, custom is honest. We won't sell you on custom just because we like the work.
Yes — usually we pair with one or two of your engineers from week two onwards. Knowledge transfer happens during the build, not in a handover meeting.
Architecture decisions are written down before they're coded. Changes get a rewrite of the decision doc and a delta estimate — not silent scope drift.
Native iOS / Android is outside our scope. We ship responsive web and PWAs. For native, we'll point you to people we trust.
From the principal engineer
The discipline of custom is saying no to everything that isn't the product. Every dependency added is a dependency you'll inherit.
Related work
— / no shipped cases under this door yet
Discovery
We pitch the problem, not the platform.
Reply within one business day · No discovery deck tax