Skip to content
Evergrowth Documentation

Velocity widgets

A velocity widget is a live tile on your dashboard that pairs a working set of accounts or contacts with a one-click way to act on them. Instead of opening the Accounts or Contacts list, rebuilding a filter, and then launching an agent, you set the audience once and the widget keeps a running count and a launch button in front of you every time you land on your dashboard.

What it is

Section titled “What it is”

Every velocity widget has two halves: an audience and, optionally, a workflow. The audience is a working set of accounts or contacts, defined either by a saved view you already use or by a filter you build directly on the widget. The workflow is the agent or workflow you want to run against whoever currently matches - anything from an Account Qualification pass to a fully custom workflow you built yourself.

Once created, the widget sits on your dashboard showing how many records currently match, refreshed automatically on a regular cadence and refreshable by hand at any time. When the count is worth acting on, one click launches the attached workflow - across every matching record, or a smaller number you choose on the spot - with no trip to the Accounts or Contacts list, no rebuilding the filter, no re-selecting rows.

Why it exists

Section titled “Why it exists”

Most of the operational work in a sales org is the same handful of questions asked again and again: which accounts have gone quiet, which contacts are missing a play, which qualified accounts still have no plan. Answering any one of them today means opening a list, applying a filter, reading the count, then deciding whether it is worth doing something about - and repeating that whole loop the next time you want to check.

A velocity widget collapses that loop into a standing fixture. You decide once what “worth watching” looks like for a given question, and from then on the answer is sitting on your dashboard every time you look, with the action to fix it one click away. It turns a list-and-filter habit into a glance-and-launch one, and because the count updates on its own, a widget going quiet - or suddenly climbing - is itself a signal worth noticing.

Personal and shared widgets

Section titled “Personal and shared widgets”

A widget starts personal to whoever creates it. Share it with specific teammates or teams and it becomes a shared widget: everyone it is shared with sees the same tile, on their own dashboard, and any of them can act on it. This is what makes a widget useful beyond an individual’s own habits - a RevOps lead can stand up “accounts that qualified but have no plan yet” once and put it in front of the whole team, so the same operational gap is visible and actionable to everyone responsible for closing it, not tracked in one person’s head.

Templates give you a running start

Section titled “Templates give you a running start”

Rather than building an audience and picking a workflow from nothing, a gallery of ready-made templates covers the questions that come up across most sales teams - accounts whose research has gone stale, qualified accounts still missing a plan, contacts with no email or phone on file, recently found accounts not yet enriched, and similar recurring gaps. Starting from a template still leaves the audience and workflow fully yours to adjust; it just means the first widget you build does not start from a blank page.

How a sales team gets value from it

Section titled “How a sales team gets value from it”
  • Turn a recurring check into a fixture, not a habit to remember. Any question you find yourself re-filtering for weekly - “who’s gone cold,” “who qualified but has nothing planned” - becomes a widget once, and after that it is simply always in view.
  • Close the gap between noticing and acting. A list only tells you what matches. A velocity widget tells you what matches and lets you run the fix in the same click, so seeing a problem and doing something about it stop being two separate steps.
  • Give a team shared visibility into shared work. A widget shared across the team means everyone is watching the same operational gaps, using the same definition of what counts, rather than each rep keeping their own mental list.
  • Let the count itself be the signal. Because it refreshes on its own, a widget’s number climbing between visits is information - a segment quietly piling up before anyone thought to go looking for it.

In practice

Section titled “In practice”

A RevOps lead notices reps keep manually re-checking which qualified accounts still lack an account plan. They build a widget for exactly that audience, attach the Account Plan agent as its workflow, and share it with the sales team. From then on, every rep’s dashboard shows the current count of qualified-but-unplanned accounts, and closing the gap is one click rather than a fresh filter session. When the number is zero, everyone can see the team is caught up; when it climbs, it is visible before it becomes a backlog.

Section titled “Related”