Cases I Picap LATAM

Five countries. A million rides a month. A forecast scorecard the C-suite could finally plan against.

Picap LATAM

Mobility · 5 countries · Head of Engineering · Multi-year engagement

Sector

Mobility · 5 countries

Role

Head of Engineering

Engagement

Multi-year engagement

Industry

Consumer mobility platform · LATAM

The Receipts

Public-safe, aggregate. The receipts.

1M+

Monthly rides — sustained, consumer-grade volume across the region

99.9%

Uptime at scale — multi-country, multi-stack, multi-stake

5

Countries onboarded without re-architecting per market

Scorecard

Monthly C-suite forecast — built bottom-up from the data

A regional platform crossing the line from startup to platform.

Picap was scaling a regional mobility business across five Latin American markets at consumer-grade volumes. The product was working; the engineering function had to absorb the growth without breaking.

The C-suite needed a credible forecast — not a story. Drivers, riders, revenue, cohort retention. A number they could plan against.

The forecast scorecard was the first credible number the C-suite had to plan against.

Outcome · Picap C-suite · multi-year engagement

Function. Infrastructure. Motion. Forecast.

  1. I.

    Installed the engineering function.

    Hired and structured the team for multi-country operations. Defined what 'Head of Engineering' actually meant in a company crossing the line from startup to regional platform.

  2. II.

    Built infrastructure for sustained scale.

    99.9% uptime at consumer-mobility volumes — what looks like a number is a hundred decisions about caching, queues, observability, and pager rotations done correctly the first time.

  3. III.

    Translated the revenue motion across geographies.

    Same product, five different unit economics, five different regulatory contexts. The motion got documented and re-run, not re-invented per market.

  4. IV.

    Installed the forecast scorecard.

    The C-suite got a credible monthly number for the first time — built bottom-up from the data, not from optimism. Drivers, riders, revenue, cohort retention. Plannable.

Forecast scorecard Picap leadership dashboard view · drop a sanitized screenshot
— image placeholder · drop a screenshot or photo here —

A million rides, a credible forecast, five countries on rails.

  • 1M+

    Monthly rides at sustained 99.9% uptime across the region

  • 5

    Countries onboarded — no re-architecting per market

  • Scorecard

    Monthly C-suite forecast — built once, run every month

What it runs on. Who runs it now.

  • Rails
  • PostgreSQL
  • Redis
  • AWS
  • Datadog
  • Multi-country payment rails
Detail: User to add: timeline, team size grown from N → N, specific markets, key inflection points, before/after metrics where shareable.

— end of chapter I —

Picap LATAM

Engagement led by Brainz · Picap LATAM

Same loop. Your team next.

If this pattern fits your room, let's have a conversation.

A single discovery call. Then a written, scoped Companion engagement — or a clean no, with notes on what we saw.