PingBell
sales performance
b2b-saas
sales-setup
crm

Setting up a sales counter for a B2B SaaS (complete tactical guide)

Step-by-step walkthrough: connecting your CRM, defining the right counter, and avoiding the common setup mistakes.

Yoav Shalev ·

This post is the operational manual for setting up a live sales counter in a B2B SaaS company with 5-50 sales reps. If you’re running 1-4 reps or a >100-rep enterprise floor, some of the tradeoffs differ; see the live sales counter for the office TV for the broader framing.

Step 1: Pick the metric

Your primary counter should measure the activity that leads revenue by the shortest reliable path. For most B2B SaaS teams:

  • SDR-heavy motion: Demos booked today
  • AE-heavy motion: Demos held today
  • High-velocity close motion: Deals closed this week
  • Long-sales-cycle enterprise: Pipeline added this month (ACV)

Don’t start with “revenue” or “ARR”. Those are lagging and lumpy. Start with a leading indicator.

Step 2: Connect the CRM

The source of truth is your CRM. Connect through Zapier, Make, or your CRM’s own webhook action:

  • HubSpot: workflow with the “Send a webhook” action, trigger on deal stage or activity
  • Salesforce: Outbound Message or Flow Builder “Send HTTP request” on Opportunity stage
  • Pipedrive: webhook automation on deal stage change
  • Close: webhook on opportunity stage
  • Copper / Monday CRM / Insightly: Zapier triggers

For each, the setup is roughly:

  1. Build the workflow / Zap / webhook in your CRM
  2. Pick the object (Deal, Opportunity)
  3. Pick the event (stage changed to X)
  4. POST the relevant fields (amount, close date) to your PingBell counter URL

Takes 5 minutes if you have admin access to the CRM.

Step 3: Filter out the noise

CRMs have a lot of junk. Filter:

  • Test deals: Filter out deals tagged “test” or owned by specific internal emails
  • Duplicate stages: Salesforce sometimes fires multiple stage-change events for the same transition; dedupe on deal ID + new stage
  • Internal pipelines: Exclude pipelines used for procurement, HR, or non-sales purposes

The cleaner the input data, the more trustworthy the counter.

Step 4: Pair the TV

Install the broadcasting tool’s TV app on a Fire Stick, Apple TV, or Android TV. Pair with a code. Done.

Physical placement matters:

  • Sales floor central wall: Maximum visibility, maximum cultural impact.
  • Near the break area: Visible during breaks but not constantly intrusive.
  • Near the SDR pit: Right where the activity happens. Usually the best placement.

Don’t put the TV where it’s behind the team. They won’t see it naturally.

Step 5: Install mobile apps

Every rep installs the mobile app. Sign in. Subscribe to the relevant counter. Now every close or demo-booking event fires a push notification with a custom sound on the rep’s phone.

The mobile side creates a “team on the move” experience. Reps who are in external meetings still hear the bell when a colleague closes. The floor feeling travels.

Step 6: Set a goal

Add a goal line: “Q2 target: 150 deals”. The counter displays progress against the goal. The team sees whether they’re on pace.

Set the goal realistically:

  • Below the official quota to build a cushion (if quotas are aggressive)
  • At the official quota to create urgency (if quotas are reasonable)
  • Above the official quota if leadership wants an aspirational target

Change the goal at most once per quarter. Moving the goalposts mid-quarter kills trust.

Step 7: Test the whole flow

Before announcing to the team, test:

  1. Create a test deal in the CRM
  2. Move it to the counted stage
  3. Watch the counter increment on the TV within 5 seconds
  4. Confirm the mobile push fires on test subscribers’ phones
  5. Delete the test deal and confirm the counter decrements

If any step fails, fix it before launch. A counter that’s wrong on day 1 loses team trust that takes months to rebuild.

Step 8: Launch with context

Don’t just install the TV overnight. Announce:

  1. What the counter measures and why
  2. How it will and won’t be used (celebration + coaching, not performance management)
  3. What the team should expect different about their day-to-day
  4. How to opt out of mobile notifications (quiet hours, per-counter mute)

Answer questions in the launch meeting. Address concerns. Adjust based on feedback.

Step 9: Tune over time

Every 4-6 weeks, review:

  • Is the metric still the right one?
  • Is the goal still calibrated?
  • Does the reset cadence feel right?
  • Is there a counter we should add or remove?

Sales orgs evolve; the dashboard should evolve with them. Stale dashboards lose the team.

The common mistakes

The five failure modes I’ve seen most:

  1. Measuring the wrong thing. Put revenue on the TV, rest of sales funnel ignored. Fix: pick a leading indicator.

  2. Counting unequal contributions. If one rep handles enterprise and another SMB, raw count favors the enterprise rep. Fix: segment counters by territory, or weight by deal size.

  3. No celebration mechanic. Counter ticks up silently. Team doesn’t notice. Fix: add custom sound on events.

  4. Surveillance framing. Manager uses the counter to blame, not celebrate. Fix: explicit launch framing + manager discipline.

  5. Setup, then forget. Counter runs for 6 months without review. Team loses engagement. Fix: scheduled review cadence.

Avoid these and the counter genuinely changes the culture.

Start here

Start a free PingBell trial. Follow the steps above. Your sales floor will feel different within two weeks.

Related: live sales counter for the office TV, how to display demos booked on an office TV.

Put your most important numbers on every screen your team sees.