Explain the number
A lead score of 91 is split into fit and engagement, each out of 50, with the last signals listed beside it. A score you cannot interrogate is a guess with a decimal point.
score = fit 0–50 + engagement 0–50
$ vase about --scope company
For sales teams of three to fifteen: a CRM sized to fit, not shrunk down.
Vase exists because most CRMs are built for a sales org of two hundred and then discounted for everyone else. We build for the small team first: fewer objects, fewer fields, and numbers that explain where they came from.
The problem · scattered context
A deal lives in four places, and the forecast lives in a fifth
A small sales team usually runs on a spreadsheet for the pipeline, an inbox for the conversation, a calendar for the meetings and a slide for Monday. Each tool is correct about its own slice and wrong about the whole.
The cost shows up in the review: two reps quote different amounts for the same deal, a lead that went quiet nine days ago still sits in Proposal, and the number given to leadership cannot be traced to a card.
Vase was built to collapse that into a single record per customer. Email, calls and meetings attach by address, stages carry a win probability, and the forecast is computed from the same cards you drag.
// before
Pipeline spreadsheetstale
Shared inbox threadsunlinked
Calendar invitesunattached
Monday forecast slidere-keyed
// after
Vase · one workspacesynced
Principles · four design constraints
Four rules every feature has to pass
These are the checks a change is held against before it ships. When a feature fails one, it is redesigned or dropped.
Log nothing by hand
If the inbox or calendar already holds the fact, Vase reads it. Reps type notes and decisions; they do not retype sent emails or meeting times.
source of truth: inbox · calendar
Keep Committed and Best case apart
Blending a locked deal with a hopeful one produces a figure nobody can defend. Vase reports both lines and shows the gap between them.
forecast: Committed / Best case
Stay sized for the team
Three stages to start, custom ones when you need them, fifteen seats on the middle plan. Admin screens exist to be finished, not lived in.
setup target: one afternoon
Audit trail
How it is built · how it is supported
Boring where it counts, readable everywhere else
Sync, scoring and forecasting run as scheduled jobs against your own records, so every figure has an inspectable input. When something looks off, support can read the same trail you can.
- sync
- Two-way with Gmail, Outlook and calendar; 90-day backfill; direction set per account.
- scoring
- Recomputed on every open, reply and meeting. Weights adjustable per workspace.
- forecast
- Rebuilt nightly at 02:00 UTC from the pipeline cards; reconciles to the board.
- data in / out
- CSV and Salesforce import; Make, Zapier and webhook triggers out.
- support
- Email support@vasestudios.com; replies come from the people who maintain the product. Greenhouse adds a dedicated success manager.
Direction · what we are working toward
Where Vase goes from here
A direction, not a delivery calendar. Items move when they pass the four rules above, and not before.
Sharper scoring inputs
More signals feeding engagement, with each one visible on the lead so a rep can see why a number moved.
Forecast models you can edit
Per-stage probabilities and category rules you can adjust, with the Committed and Best case split kept intact.
More connectors, same record
Additional inbox, chat and ticketing integrations that write to the existing contact timeline rather than adding a new screen.
// roadmap is directional and changes with what teams tell support@vasestudios.com
Plans from $0 · Sprout, Bouquet, Greenhouse
Hand leadership a number you can trace.
Pick the plan that fits the headcount, connect the inbox, and the first forecast builds overnight.
Get access