Grab · Go-to-market · Entry · 45 to 60 minutes

How should Grab pilot a driver growth loop?

Grab is a Southeast Asian platform for ride hailing and other everyday services. Answer this product management case and get it graded line by line against a weighted rubric.

Segmentation
GTM planning
Experiment design
Metrics
Risk management

The situation

You are an associate PM at Grab, supporting the transport marketplace. Leadership wants faster growth in rides, but the main business teams mostly back proven campaigns and are hesitant to spend time on small, risky, or highly targeted experiments. A senior product leader asks you to propose the first driver facing growth pilot that a lean cross functional team could launch. The brief is tricky. The pilot should do more than create a one time spike. It should attract the right users, change behavior, keep those users engaged over time, and ideally create repeat usage or spillover effects in the system. At the same time, Grab operates across multiple markets, so the idea should be fast to test, measurable, and reusable without needing a large custom build for each city. Engineering can support basic experimentation, but team bandwidth is limited, and marketplace health cannot be harmed. Your job is to recommend who to target first, what mechanism to test, how to launch it, and how Grab should decide if it is worth scaling.

What to produce

A 1 to 2 page go-to-market memo for the first driver growth pilot.

Your answer must

Define the first target segment using needs and observable traits, and explain why this segment should be prioritized now.
Describe the proposed growth loop, including how the pilot will acquire, activate, engage, and drive repeat behavior or virality.
Outline the launch plan, including pilot scope, rollout sequence, and how you would use experimentation or A/B testing.
Specify a primary success metric that captures cost efficient ride growth, plus 2 to 4 supporting metrics or guardrails.
List the main risks, including possible harm to driver experience or marketplace quality, and give mitigations.

Constraints

Keep the proposal small enough for a lean team to launch as a pilot, not a major new platform build.
Do not rely on a new external partnership or a broad brand campaign.
The idea should be adaptable across markets, with limited local customization.
Protect marketplace health, especially driver acceptance, cancellations, and ratings.

Format

Use short sections with bullets where helpful. Make your assumptions explicit.

How Grab actually played it

Grab describes why it created a dedicated growth team to run risky or niche experiments and deliver growth loops. The post defines a growth loop in steps and explains how needs-based segmentation drives acquisition. Short but useful for understanding how a growth team is scoped inside a larger company.

Give a growth team permission to take risks that business teams avoid.
Think in loops (acquire, activate, reward, repeat), not one-off campaigns.
Segment by needs and observable traits before choosing channels.

Built from Grabbing Growth: A Growth Hacking Story by Grab Engineering.