Design partners

Run the next review modes before they ship

The VeriFlow design-partner program gives engineering teams early access to the review modes we are still tuning, a close feedback loop with the engineers behind the agent, and the option to publish a case study together once the cohort signal lines up.

We are looking for engineering teams — typically 3-30 engineers shipping a steady stream of pull requests — that are evaluating early AI code review tools and want to influence what the next release looks like.

What you get

Three things design partners get that other teams do not

The program is small on purpose — a handful of teams shipping a steady stream of PRs, with the time to give feedback that actually lands in the queue.

Early access

Run the review modes that have not shipped yet

Design partners see new VeriFlow review capabilities weeks before they reach the public release — including modes we are still tuning on the cohort. You get a direct toggle, a short note on the design choices, and the option to keep it on once it lands in general availability.

Direct line

A close feedback loop with the team

Every design partner gets a shared Slack-style channel with the engineers building the agent. Feedback — false positives, missed edge cases, score-card disagreements — lands in the product backlog the same day. No "report a bug" handoff, no triage queue.

Case study

Optional: a public case study with your team

If the cohort signal lines up, we publish a short case study with your team — what shipped, what changed, what we measured — credited and reviewed before anything posts. This is opt-in: if you prefer a quiet retrospective, that works too.

What we ask in return

Three commitments that make the program worth running

The shape of the program is small and stays small on purpose — three commitments and the rest of the relationship follows from them.

  • Run on a real repo

    Install the GitHub App on one of your working repos

    Pick a repo you actually ship to — not a sandbox. The point of the program is to validate the agent on real diffs, so we want feedback that mirrors what your team will see in production.

  • Bi-weekly call

    ~30 min, every other week, with the engineers behind the agent

    A short, working call — what shipped since the last one, what is shipping next, what we got wrong. We come with the diffs in hand and you tell us which comments would have been wrong on your last PR.

  • Feedback in the shared channel

    Async feedback in the shared channel between calls

    Between calls, post false positives, missed edge cases, and the comments you would have written yourself. The channel is the fastest path from "this is wrong" to "this shipped a fix next week".

The close feedback loop

How the program actually runs week to week

The cadence is bi-weekly on purpose: long enough for a meaningful slice of new PR review traffic to accumulate, short enough that feedback lands before the team’s mental model of the agent drifts. Between calls, the shared channel is where the day- to-day feedback lives — every false positive, every missed edge case, every comment you would have written yourself stays one search away from the engineers behind the agent.

Most weeks the program runs as expected — a small batch of fixes ships to your repo before the rest of the cohort sees them, and the cohort signal from your team lands in the next release notes. A few times a quarter we will ask for a 60-min deep dive on a specific review mode we are tuning; you opt in if the mode is on your path, and skip it cleanly when it is not.

Design partners graduate when the rollout reaches general availability. There is no premium surcharge from having been a design partner — you roll onto the published team plan that fits your repo count, and the relationship continues in the same shared channel if you want it to.

FAQ

The three questions we hear most before applying

Engineering teams — typically 3-30 engineers — actively evaluating early AI code review tools and willing to put VeriFlow on a real repo of their choice for the program duration. Solo maintainers are welcome, but the program is tuned for teams shipping a steady stream of pull requests and looking for close collaboration with the team.

Apply to the program

Drop your work email to apply
One field. We follow up by email within five business days with a short set of questions about your team, your repo, and what you would want to see in the next release. There is no procurement form, no quote, no demo gate.

Applications are reviewed weekly — we reply within 5 business days even if it’s a no.