Start here · one day

AI code review in a day: your rules, on every change.

An AI reviewer that knows your standards, reads every change before a person does, and cites the written rule behind every finding. Installed in your pipeline, on one repository, in one day. $5,000–7,000 + GST, depending on the pipeline.

What you get

A reviewer that never reviews with an empty context

Most AI review steps produce generic comments at a surprising cost because they were never given the organisation's rules. Ours is built the other way round: the rules come first, every finding cites one, and the reviewer proves itself on defects we plant.

The method is the one in our engineering-standards case study: three repositories, one harness, running cost cut sevenfold.

  • Your standards compiled into numbered checklists: architecture, security, conventions
  • Two-pass review on every change: a fast pattern scan, then a logic review on a stronger model
  • Every finding cites a rule, maps to its line, and resolves itself when the code is fixed
  • Honest states: passed, inconclusive or partial, never a green tick for a review that did not run
  • A seeded-defect canary that fails the pipeline if the reviewer stops catching what it should
  • Cost controls: cached context, skipped re-reviews, model tiers chosen by evidence

The day

Morning: your rules. Afternoon: your pipeline.

  1. Step 1

    9am · Rules

    Your architecture, security and coding documents compiled into checklists with rule identifiers, with you in the room.

  2. Step 2

    11am · Install

    The harness added to one repository's pipeline, with your model accounts and your access controls.

  3. Step 3

    2pm · Prove

    The canary and three real recent changes run through it; findings read together.

  4. Step 4

    4pm · Hand over

    Your engineers shown how to add a rule, tune a tier and read the states; the scripts are yours.

One day, one repository

$5,000–7,000 + GST

The lower figure for GitLab CI or GitHub Actions with existing standards documents; the upper figure where the standards still have to be written down with you, or the pipeline is unusual. Further repositories on the same harness are a half day each.

Model usage is billed by the vendor to your own account; on our reference engagement it runs at about USD 20 a week.

  • Paid on completion
  • Advisory by design: a model outage never blocks a release
  • Scripts and checklists are yours, in your repository
  • One follow-up call two weeks later, included

Pick the repository, and a day.

A free 30-minute call to check your pipeline and your standards documents, and to book the day.

Call Book a call