No. 05 — Design partnersFive teams

Bring one workflow. If two of these are true, we should talk.

  1. 01

    There is no consistent way your team works with agents.

    Vibe coding, spec-driven, something in between — or you have a process and do not trust it.

  2. 02

    You use more than one model, or want to.

    Picking the right brain for the job, instead of whichever one the tool ships with.

  3. 03

    You cannot say which agent made a change.

    Today it takes human judgement, it is manual, and it is easy to get wrong.

  4. 04

    Policy and control are not negotiable for you.

    You want every detail of how each ticket ran, and no drift from what you approved.

You get

  • Your workflow built with you, not handed to you
  • A direct line to the founder for eight weeks
  • What you hit in week two shapes what ships in week four
  • Founding-partner terms, agreed before we start

We ask

  • One workflow, and one owner on your side
  • Thirty minutes every second week, for eight weeks
  • Honest feedback, including "this does not work"
  • Permission to fix things in your workflow while you watch

Tell us about the workflow.

Five questions. We reply within two working days.

Which agents write code for you today?

One sentence is plenty — for example, bug fixes from the support queue, handled by Claude Code.

An honest maybe is more useful to both of us than an optimistic yes.

Optional.