Skip to content
Vantro

About

A forecast shouldshow its work.

Thirteen weeks of a quarter as contour lines. The orange one is the forecast.

Why Vantro exists

Vantro started as a spreadsheet one sales ops team rebuilt every Thursday night, so their CRO had something to say on Friday.

The spreadsheet worked until it didn't. Rep calls came in optimistic, managers trimmed them by feel, and by the board meeting nobody could explain the number. So we started scoring deals from what was actually happening on them, and showing how unsure that score was.

We are a small team in Austin, spread across four US time zones, building for the people who own a revenue number and have to defend it.

Four things wewon't trade away.

  1. 01

    Every number travels with its range.

    A single figure hides how sure you are. Every forecast in Vantro carries its range, and the range is honest about how much pipeline is still open.

  2. 02

    Every score explains itself.

    If a manager can't see why a deal is at 64%, they won't trust it, and they shouldn't. Reasons sit next to every number.

  3. 03

    Reps shouldn't feed the model.

    We read what already happens: meetings, emails, stage changes. Nobody is asked to fill in another field so a forecast can exist.

  4. 04

    Keep score on ourselves.

    Vantro records every forecast it makes. At quarter end you see how close it was, next to how close your team's call was.

The team

Sales ops, data science and design, in roughly equal parts.

See your own pipelineas a forecast.

A 30-minute walkthrough built around how your CRM is set up. No slide deck.