Manifesto

What we believe.

Five stances on building software in 2026 — and how a team of two with AI as a co-builder gets to do work that used to need ten.

  1. 01

    Small teams + AI beat big teams alone.

    The cost of building software is collapsing. The bottleneck moved from typing to taste. We're a team of two, by design.

  2. 02

    AI is a co-builder, not a co-pilot.

    We use AI for the work, not the credit. It writes, refactors, debugs, and reviews with us. We own every line of code.

  3. 03

    Ship in days. Iterate in public.

    Long roadmaps are a hedge against not knowing what to build. We compress the cycle so we can be wrong faster — and right sooner.

  4. 04

    Real products beat case studies.

    You can't fake a live product. We'd rather have one real thing in the world than ten slides about hypothetical capability.

  5. 05

    Privacy is a feature, not a footer.

    Your data stays where it should. We default to local processing, transparent prompts, and auditable agent runs.

How we work

One shared brain.

Almost everything that matters to us lives in one Notion. The rules we hold ourselves to, what each product is for, how we talk about it to the people who use it. Both of us read from it and both of us add to it, so there’s no piece of work that only one of us understands.

That shared context is the whole trick. It lets us build at the same time, in different corners of the same product, each of us with AI doing the heavy lifting, and the pieces still line up when they meet in the middle. The AI is working off the same goals and the same rules we are. It isn’t guessing at what we want, because what we want is already written down.

Tools

We don’t have a stack.

We have a process for picking one. Every project gets the technology that fits the problem — not the one we’re most comfortable with, not the one that was hot last year. Quality and fit drive the call. Familiarity is a tiebreaker.

The right answer in 2026 is rarely the right answer in 2027. We’re built to swap. Models change, frameworks change, the best database for the job changes. We change with them.