GitLab · Strategy · Mid · 45 to 60 minutes

How should GitLab price private repos?

GitLab is a web based platform for hosting Git repositories and collaborating on software development. Answer this product management case and get it graded line by line against a weighted rubric.

Pricing strategy
Segmentation
Competitive analysis
Product judgment
Written communication

The situation

You are the PM responsible for GitLab's SaaS hosted repository plans. GitLab's CEO asks you for a recommendation on whether the company should change how it prices private repositories after a major competitor updates its paid plans to allow unlimited private repos. Some prospects now question GitLab's pricing page, and internal teams worry that repository based pricing may look less competitive, especially as software teams adopt microservices and create many more repositories than before. At the same time, any change could shift who pays more, reduce predictability for customers, or weaken the economics that fund GitLab's free tier. Large organisations with many occasional contributors may react differently from small teams with many repositories. Leadership wants a product point of view, not just a finance answer, because pricing affects positioning, fairness, growth, and how clearly customers can map price to value. Assume you have access to current customer mix by team size and repository count, plus public pricing pages from competitors.

What to produce

A 1 to 2 page pricing strategy memo.

Your answer must

Define the decision, the goal of the pricing review, and 3 to 5 evaluation criteria for choosing a pricing model.
Compare at least two pricing units GitLab could use, including per user and per repository, and explain how each maps to customer value, predictability, and simplicity.
Segment customers into at least three groups and identify who is likely to benefit, who is likely to pay more, and why, including the effects of microservices and large contributor heavy teams.
Include a side by side comparison of GitLab's plan structure versus at least one competitor's public plan structure at a high level, and explain the competitive implications.
Recommend one path forward and include the main risks, mitigations, and how the free tier would remain funded by paid offerings.

Constraints

Use only the context provided and public competitor pricing structures, do not invent confidential facts, exact market shares, or unsupported numbers.
Keep the recommendation focused on SaaS hosted repository pricing, do not solve the problem by changing GitLab's core product scope or enterprise sales motion.
Preserve a free tier in your proposal and explain the business logic for supporting it.
Keep the pricing model simple enough to explain clearly on a public pricing page.

Format

Use short headings and one simple comparison table.

How GitLab actually played it

GitLab's CEO responds to GitHub offering unlimited private repositories on paid plans by comparing plans and arguing that per-user pricing is the most predictable model, tied to organisational value. The post works through who wins and who loses, noting that microservices multiply repositories and that large contributor-heavy groups may pay more. A grounded look at competitive pricing analysis.

Compare competitors' plans side by side with real prices.
Think through which customer groups benefit and which pay more under a new model.
Tie price to a unit that scales with customer value, such as users.
Explain how the free tier is funded by paid offerings.

Built from The future of SaaS hosted Git repository pricing by Sid Sijbrandij, GitLab.