GitLab · Strategy · Mid · 45 to 60 minutes

Should Free SaaS limit private group seats?

GitLab is a software development platform that helps teams plan, build, secure, and deploy code, offered as both a hosted SaaS service and self-managed software. Answer this product management case and get it graded line by line against a weighted rubric.

Strategy
Monetization
User segmentation
Change management
Written communication

The situation

The VP responsible for GitLab.com growth and monetization asks you to recommend how the Free SaaS tier should handle larger private teams. Usage on hosted private collaboration has grown, and finance and sales believe some teams are getting meaningful business value from GitLab.com without either converting to paid plans or covering the cost to serve. At the same time, GitLab's brand depends on trust with developers, small teams, educators, and open source communities, many of whom start on free offerings before they ever pay. Your job is to propose a policy for private top-level groups on the Free SaaS tier: keep things as they are, add some kind of user limit, or take another approach. Leadership wants a recommendation before the next planning cycle so product, support, billing, and communications can align. The hard part is balancing monetization and infrastructure cost against backlash risk, fairness, and the chance of pushing valuable future customers away.

What to produce

A 1 to 2 page strategy memo.

Your answer must

Make a clear recommendation on whether GitLab should change the Free SaaS policy for private top-level groups, and why.
Identify the main user segments affected, including which segments should be protected or exempt, if any.
Compare at least two realistic policy options and explain the trade-offs across revenue, cost to serve, user trust, adoption, and community impact.
Propose a rollout plan with notice period, communication channels, enforcement approach, and user paths forward.
Define the key success metrics and guardrails you would track in the first 90 days after launch.

Constraints

Your recommendation can change only the GitLab SaaS Free tier policy for private top-level groups, not the self-managed product or paid plan feature set.
The policy must preserve a credible path for open source or other community-oriented use cases on GitLab.com.
The rollout should be feasible within one quarter using existing billing, account controls, email, and in-product messaging systems.

Format

Use short sections with headings and put your recommendation first.

How GitLab actually played it

GitLab limits private top-level groups on its Free SaaS tier to five users, stating the change affects fewer than 2 percent of Free users and about 0.3 percent of top-level groups. It lists exemptions, a 60-day notice and options such as upgrading, self-hosting or applying to the open source program. A clear template for tightening a free tier while limiting harm.

Quantify who is affected (under 2 percent of users) to show the change is targeted.
Exempt public projects, community programs and personal accounts to protect goodwill.
Give long notice both in-app and by email.
Offer several paths: upgrade, self-host, or join a community program.

Built from Upcoming changes to user limits on Free tier of GitLab SaaS by GitLab.