Selected partnerships

For product questions that need research and engineering.

We work with selected partners on product research, technical exploration, validation, and advisory — continuing into a focused build when the direction and fit are right.

Research first. Build when it’s warranted.

A partnership can focus on one part of the product journey or connect several. The shape of the work follows the question, not a predetermined deliverable.

01

Product research

Clarify the problem, study the people and workflows around it, and identify the assumptions that need evidence.

02

Technical exploration

Explore what new capabilities — including AI — make possible, prototype the uncertain parts, and decide what is feasible and worthwhile.

03

Validation

Test the product direction and the riskiest assumptions before a full build turns uncertainty into expensive commitment.

04

Product advisory

Work through difficult choices about product scope, interaction, technical direction, and what the first version must refuse to do.

05

Focused build

Continue into design and engineering when the problem is focused, the direction has earned the work, and a small team can carry it end to end.

Not every investigation should become a build.

Research may clarify the opportunity, prove a technical direction, or show that a product should not move forward. When the evidence supports the commitment and the fit is right, we can continue into design and engineering.

Partner work is shared publicly only when the partner wants it made public.

Close partnerships, chosen carefully.

We work together only when there is room to investigate the problem, influence the product direction, and materially improve what gets built.

A strong fit

  • The product direction is still open, and the riskiest questions need investigation before a team commits.
  • A new technical capability may unlock something useful, but its role in the product is not yet clear.
  • The team needs evidence of demand or usefulness before funding a full build.
  • An existing product is not landing, and the underlying problem is still uncertain.
  • The work is focused enough for a small, accountable team to carry from decision to delivery.

Where we are not a fit

  • Staff augmentation. We do not supply developers to work through someone else’s backlog.
  • Building to a settled spec. If every decision is already made and only execution remains, a delivery agency will serve you better.
  • Maintenance, support, and keeping existing systems running.
  • Large, long-running enterprise programs that need big teams and heavy process.

If that sounds like the product challenge in front of you, tell us what you have noticed