Sales · Pipeline

A pipeline review that is assembled before the meeting

The forecast meeting is worth having. Spending the first twenty minutes reconstructing what happened is not.

What the worker does

Pipeline management in Polaris means a weekly task assigned to an AI worker with the HubSpot connection. The worker reads every open deal, checks it against the stage definitions in its skill file, and delivers a stage-by-stage review as a comment: what moved, what stalled, what has no next step and no date. Each stalled deal arrives as a proposed task for the rep who owns it.

Connections
HubSpot · Slack
Cadence
Weekly, before the forecast call
Output
Review comment plus one task per stalled deal

Two different meetings

In the first kind, the manager reads the pipeline aloud and each rep explains from memory what happened. It takes an hour and produces a shared feeling rather than a decision.

In the second, everyone has already read the same written review: which deals moved a stage, which have not been touched in fourteen days, which are dated to close this month with no meeting booked. The meeting is about the five hard ones. It takes twenty minutes.

The only difference is that somebody wrote the review. That somebody does not have to be a person.

What the review contains

  • Movement

    Deals that changed stage since the last delivery, in both directions. Backwards movement gets named, because that is the number that predicts the quarter.

  • Silence

    Open deals with no activity for longer than the threshold in the skill file, with the number of days and the owner.

  • Dates that cannot be true

    Deals dated to close inside a window shorter than your average cycle for that stage.

  • Missing next steps

    Every open deal with no next action recorded, which is the single most reliable predictor of a deal that will not close.

  • What the worker could not check

    Fields it could not read or deals with data it did not trust, stated rather than smoothed over.

From review to work

  1. 1

    The worker delivers the review

    One comment on the weekly task, structured the same way each week so the comparison is easy.

  2. 2

    Stalled deals become suggestions

    Prefilled task suggestions land in the Inbox with the deal, the owner, the lane and a due date already set.

  3. 3

    The rep accepts what is real

    One click each. A deal the rep knows is dead gets rejected instead, and that judgement stays with the person who has the context.

  4. 4

    The important ones go to Focus

    Deals closing this week sit in the Focus lane, which is pinned first in every view and does not scroll away.

Questions people ask

+Does it write back to HubSpot?

The deliverable is a review comment and a set of proposed tasks. Treat any change to a CRM record as a human action, approved by the rep who owns the deal.

+How does it know what stalled means for us?

You define it during hiring, and it lives in the worker's SKILL.md as a real file. Changing the threshold from fourteen days to seven means editing a line in that document.

+Can each rep get their own review?

Yes. Assign the worker one task per rep, or one per segment, and each delivery is a separate comment on a separate task with its own audit trail.

+What does a weekly pipeline review cost?

It is billed by human-equivalent hours at about $2 each, computed from observable effort and clamped between five minutes and eight hours per session. Every session appears as a challengeable line on the worker's work log.

Your next hire takes 60 seconds.

The software is free — unlimited people, tasks, workstreams and docs. You pay only for work an AI worker actually delivers, itemised by the hour.

Get started free

Last checked .