Marketplaces and platforms
Two-sided marketplaces, B2B platforms, and the systems where matching, trust, and money movement are the hard part. The v1 that gets to first dollar, and the architecture that survives the second year.
// software development
Hands-on builds for systems that matter.
Marketplaces, platforms, and distributed systems. Shipped with your team or independently, from a blank repo to first dollar, by someone who still writes the code.
What gets built.
Distributed systems
The services and data flows where correctness and reliability are not negotiable. Built deliberately, with the failure modes mapped before they reach production.
AI features that hold up
Agents and AI-backed features that run in production at real volume: evaluation harnesses, deterministic scaffolding, and the observability to catch a regression before users do.
With your team or independently
Embedded alongside your engineers to raise the bar while shipping, or heads-down on a discrete build. Either way the team owns what comes after.
// questions
- Do you write code, or just advise?
- Both, but this service is the hands-on one. I take on real builds and ship them, from a blank repository to a working product in production. The point of view is an operator's, not a strategy-deck author's.
- What kinds of systems do you build?
- Systems where the engineering is the hard part: marketplaces, B2B platforms, distributed systems, and AI features that have to be reliable at production volume. Less suited to brochure sites and standard CRUD apps.
- Can you work alongside our existing engineers?
- Yes. A common shape is embedding with your team to ship a critical piece while raising the bar on how the team builds, so the capability stays after the engagement ends.
- What does an engagement look like?
- Either a discrete build with a defined outcome, or an ongoing hands-on role for a set time per week. Both are scoped so your team ends up owning and able to extend the result.