GitLab · AI product · Mid · 45 to 60 minutes

How should GitLab price AI code reviews?

GitLab is a software development platform where teams plan, build, secure, and ship code together. Answer this product management case and get it graded line by line against a weighted rubric.

Pricing strategy
Product judgment
AI product thinking
Metrics design
Structured communication

The situation

You are the PM for GitLab's upcoming agentic Code Review Flow. The feature uses AI to review merge requests and flag likely issues before a human reviewer finishes the job. Your VP of Product wants a launch pricing recommendation for the next planning cycle. The timing is urgent because AI coding tools are increasing code output, customers say review queues are becoming a bigger bottleneck, and GitLab sees review speed as a visible part of the path to merge. Internal research also points to long waits, with a typical merge taking about 13 hours to get through review. At the same time, competing AI code reviewers are often priced around 15 to 25 dollars per review, which gives buyers a clear comparison point. GitLab now has to choose a price and billing approach that customers can understand, sales can explain, and the business can support without creating open-ended usage risk. Your job is to recommend how this new capability should be priced at launch, and why.

What to produce

Write a 1 to 2 page product decision memo.

Your answer must

Define the decision, the primary user or buyer, and why code review latency matters now for GitLab customers.
Compare at least two launch pricing options, including a lower and a higher price point, and explain the expected customer usage pattern, value story, and business risk for each.
Recommend one pricing approach and justify it using the facts provided, including the 13-hour review wait and the 15 to 25 dollar competitive reference point.
Propose 3 to 5 success metrics and a 90-day validation plan to test whether the pricing is helping or hurting adoption, usage, and economics.
List your key assumptions and name 2 major risks or failure modes, with a mitigation for each.

Constraints

Use only the facts in this prompt, and clearly label any assumptions.
Recommend a standard list price and billing unit that a customer can estimate before enabling the feature.
Do not rely on custom contracts or manual services outside the product to make the launch plan work.

Format

Use short sections with headings: problem, options, recommendation, metrics, risks.

How GitLab actually played it

GitLab prices its agentic Code Review Flow at a flat 25 cents per review so teams can enable it on every merge request instead of rationing it. The reasoning cites rising review times with AI coding tools and a typical 13-hour wait for merges, and compares with competing reviewers priced at 15 to 25 dollars. A clear example of picking a price point to change usage behavior.

Set a price low enough that customers switch the feature on everywhere.
Anchor value against the cost of the manual alternative.
Name the bottleneck the product relieves (review time) with data.
Use a credit unit so cost is easy to compute.

Built from Agentic code reviews for $0.25 each by GitLab.