Skip to content

Design partners

Help shape it with a real codebase.

I am looking for a small number of engineering teams to build this with. You bring the hard problems. I bring the product, built against them first.

Is it a fit?

Teams that change code they cannot fully see.

A good fit

  • A product spread across several repositories, with Java, JavaScript or TypeScript on GitHub.
  • Code older than most of the people working on it, or a fast-growing share written by AI agents.
  • Changes that keep surprising you after release: a client you forgot, a job that read the column.
  • A CTO or engineering lead who can give the work real attention.

Probably not yet

  • A single small repository that one person understands end to end.
  • A need for a finished, supported product this quarter.
  • Code that cannot be read by any external tool, even under agreement.

The exchange

What you get, and what I ask.

You get

  • Early access as each part becomes usable.
  • Real influence over what gets built first.
  • A direct line to me, not a support queue.
  • A twin of your product to keep using as it matures.

I ask

  • A real or representative codebase to work against, under a clear agreement.
  • A short session every two weeks.
  • Specific, honest feedback, especially when it is wrong.

How it starts

Three steps, no sales process.

  1. Tell me where it hurts

    A message with the last change that surprised your team, and roughly how your code is laid out.

  2. One working session

    We walk through a real change together and decide whether the twin would have helped.

  3. Build against it

    If it fits, we agree how the code is shared and start with the area that hurts most.