$ vase features --list --verbose

For sales teams of 3 to 15: seven capabilities, one customer record.

Every module below reads and writes the same contact, company and deal objects. A reply in Gmail moves a lead score, the score changes the call list, and the forecast re-adds itself to the dollar. Here is what each one does, what it replaces, and where it sits in the week.

Deal pipelines

Move a deal, and the number above the column moves with it

Each card carries amount, win probability, owner and last touch. Column totals are computed from the cards on the board, so dragging Bluepeak Fabrication from Proposal into Won takes $41,200 out of one header and puts it in the other before you release the mouse.

Run a separate pipeline for each motion: new logo, renewal, partner referral. Stage history is saved on every move, and ⌘Z puts a card back.

Where it fits the week

Friday: groom the Proposal column. Monday: the same board is the agenda for pipeline review.

  • stages: custom
  • win % per stage
  • pipelines: ∞ on Bouquet
Drag + drop
Lead scoring

Fit and engagement, scored on two separate 0–50 axes

The sum sets Monday’s call list. The split tells you what kind of lead you are looking at: a 45-fit account gone quiet is a nurture task, a 45-engagement lead at a poor-fit company is a polite no.

Score 0–100

The rule set

Hot is 80 and above, Warm is 60–79, Cool is under 60. Fit reads company size, role and industry; engagement reads opens, replies and meetings. Weights are adjustable, and the default is 50/50.

Where it fits the week

Monday 09:00: filter Score ≥ 80, select the rows, press S to drop them into a sequence. Rescoring runs on every open, reply and meeting.

Committed / Best
Forecasting

Committed and Best case, never blended into one hopeful figure

Committed is Won plus the deals you have flagged as locked: $32,300 + $41,200 = $73,500. Best case adds every credible deal in Proposal and Qualified, landing at $132,650 against a $140,000 target. Both reconcile to the board, so the number you give leadership matches the cards.

The forecast refreshes nightly at 02:00 UTC. A weekly report on Bouquet posts the delta between this week and last.

Where it fits the week

Monday: read Committed aloud. Thursday: argue about the $7,350 gap between Best case and target, not about whose spreadsheet is right.

  • weekly report: Bouquet
  • custom models: Greenhouse
  • refresh: nightly
Auto-logged
Contact timeline

One timeline per contact, filled in by the inbox instead of by hand

Emails, calls and calendar meetings land on the contact record with sender, timestamp and outcome, matched by address. Open Isabel’s drawer and the last four touches read top to bottom, newest first, with unread replies marked.

When a rep is out, anyone on the team opens the record and picks up the thread, because the history was never in someone’s head.

Where it fits the week

Before every call: ten seconds on the timeline. After every call: log the outcome in one line, and the rest is already there.

  • emails · calls · meetings
  • matched by address
  • unread dots
Inbox + calendar sync

Two-way sync with Gmail, Outlook and the team calendar

Send from Vase or from your inbox and both sides stay in step. Calendar events attach to the matching deal, and an edit made in either place flows back within minutes. Direction is set per account: two-way, Vase to inbox, or inbox to Vase.

On connect, Vase backfills 90 days of threads and matches senders to contacts, so a new workspace opens with history instead of an empty board.

Where it fits the week

Day one: connect, wait for the backfill bar to finish, open the board. From then on nobody forwards an email to the CRM.

  • Gmail · Outlook
  • 90-day backfill
  • direction per account
Two-way
06 · 07 · Speed and control

A keyboard path for reps, a permission map for the people who sign off

Two capabilities that rarely get a screen of their own in a CRM, and the two that decide whether a team of fifteen actually keeps the board clean.

⌘K

06 · Command palette

Press ⌘K from anywhere, type four letters of a company, and run an action on the deal without opening it: move stage, log a call, assign an owner. Every action shows its shortcut so the palette teaches the keyboard.

Greenhouse

07 · Roles + permissions

Decide who can see, edit and export per role. Reps edit their own deals, managers reassign across the team, and only admins touch forecast models or export a full contact list.

Security · reliability · integrations

The unglamorous specs, stated plainly

What happens to your data, how often it syncs, and which tools Vase talks to. Anything not listed here is not claimed.

// security

Encrypted in transit and at rest

TLS on every connection, encrypted storage, and OAuth for Gmail and Outlook, so Vase never holds a mailbox password. SSO is available on Greenhouse.

  • TLS
  • OAuth mailbox links
  • SSO: Greenhouse
// reliability

Predictable sync cadence

Mail and calendar changes flow in within minutes. The forecast rebuilds nightly at 02:00 UTC. Stage history is saved on each move, and undo is one keystroke away.

  • sync: minutes
  • forecast: 02:00 UTC
  • undo: ⌘Z
// your data

Import in, export out

Bring a CSV or a Salesforce export on day one. Admins can export contacts, companies and deals at any time, restricted by role.

  • CSV import
  • Salesforce import
  • admin export

Eight connectors, one trigger each

  • Makescenario triggers
  • Zapierzap on deal.won
  • Microsoft Teamsstage-change alerts
  • Dropboxfiles on the deal
  • PagerDutystalled-commit pages
  • Jiratickets on accounts
  • Salesforceone-way import
  • Discordwebhook digests
Seven capabilities, three plans

Pick the plan that switches them on.

Sprout covers pipelines and contacts. Bouquet adds scoring, sequences and weekly forecasts. Greenhouse adds custom models, roles and SSO.

Get access