Case Studies

How Did a School Services Provider Unite Two Sales Teams in HubSpot?

Written by Talia Price | Oct 19, 2026, 9:57:55 PM

A developing story. Chapter 1: The Build.

Two sales teams. Multiple spreadsheets. One HubSpot portal, and only one of those teams was selling from it. Vested had both teams working in HubSpot in under 90 days, with their deal data reconciled to their own trackers. Then leadership asked what we could build next.

 

At a glance:

Client

National K-12 services provider

Platform

HubSpot Sales Hub Professional, plus custom objects and a sandbox from the client's existing Marketing Hub Enterprise subscription

Services

Portal audit and optimization, full pipeline build, data migration, automation, reporting, SOPs, team training

Teams

Two sales teams with separate processes, vocabularies and leaders

Timeline

Under 90 days from kickoff to both teams live

Engagement

Fixed fee, two line items: Build and Configuration, Training and Enablement

Status

Ongoing. This is Chapter 1.

What problem were two sales teams trying to solve?

Both teams needed a system leadership could trust. They were starting from opposite ends.

One team already lived in HubSpot for outreach. Reps sent sequences and logged calls every day. But deals weren't tracked in stages, managers couldn't see where a district stood, and the team's pipeline and revenue lived in a spreadsheet.

The other team had the opposite problem. Their pipeline and dashboards were already built in HubSpot, but reps had never worked in it day to day. Districts and contacts lived in a separate project management tool, and the spreadsheet was still the source of truth.

The portal itself had problems:

  • No view of the work that creates pipeline. Deal reports showed what was open. They couldn't show whether reps were creating enough new opportunities to hit goal.
  • Statuses nobody trusted. Reps set statuses by hand, and an "In Sequence" status blurred how a contact was being reached with how far they'd gotten.
  • Duplicate and mis-linked records. Some districts existed several times over, one of them 11 times. Some deals were attached to the wrong organization.
  • Internal email noise. Internal emails were auto-logging to employee records. One company-wide email assigned a sales owner and fired follow-up tasks.
  • A billing cliff. The portal was already over its marketing contact tier and had auto-upgraded once. A careless import of thousands of contacts would have raised the bill again.

What did Vested build?

The biggest change is a second layer under the deal pipeline. Deals show the opportunities that already exist. The contact layer shows the outreach that creates them, so leadership can spot a thin pipeline before it hits the deal report.

  • An outreach layer under the pipeline. A status ladder for each team in its own words, a sequence status pulled straight from HubSpot, and saved views that replaced the territory spreadsheets.
  • Team activity dates, live. Every logged email, call and meeting stamps the contact's last-activity date for the rep's own team. Two teams can share a district without overwriting each other. We backfilled 60 days of history first, so the dates were right on day one.
  • Rebuilt pipelines. One deal per district per school year for the first team, with stage gates that require the revenue inputs. An audited, simplified pipeline for the second team.
  • Placement-level revenue. A custom Placements object that tracks each placed candidate's expected, actual and missed revenue against the district's deal.
  • Staged automation. Forward-only status updates, owner and director assignment, and hold follow-up tasks. Each one is scoped to one team and ready to turn on.
  • Reporting and enablement. 12 custom reports that mirror the second team's spreadsheet dashboard, SOPs for each team, live training at go-live, and office hours after launch.

How did Vested handle change requests without derailing the project?

Every change got the same test: does this make the rep's job simpler, or just make the system bigger? We said yes to changes that matched how the teams sell. We pushed back on fields nobody would fill. And we showed options in a demo portal before touching the live one.

What changed

How we handled it

What it got the client

A revised tracker landed mid-build.  The second team's new tracker expanded opportunity types from 5 to 18, outreach types from 8 to 14, and restructured departments.

Compared the new tracker to the build side by side, listed every difference, and got all decisions in one round before changing anything.

Dropdowns matched the tracker before import, so deals mapped cleanly on the way in.

A status flaw surfaced in testing. Date-based rules would have dropped a contact who replied 31 days ago back a rung.

Split one overloaded status into two: a human outreach ladder and a machine sequence status. Added a guard so status can only move up.

Statuses that move only with real progress and never overwrite a rep's judgment.

Revenue needs went deeper. After the pipeline was built, the first team's leader confirmed how revenue is counted and asked for expected versus actual revenue on every placement.

Re-pointed the opportunity formula, then built a Placements object on the client's existing Enterprise features, with missed revenue calculated automatically.

Pipeline value that follows the leader's own rules, and placement-level revenue with no new subscription.

A new request: contract tracking. Leadership asked to replace a manual contract spreadsheet with HubSpot.

Scoped it as its own project, prototyped it in our demo portal, then built it in a sandbox ahead of production.

The core build stayed on schedule, and the new work will start cleanly.

What were the results?

Both teams went live in under 90 days, working from their own pipelines, views and dashboards.

What leadership can see now

  • Where every contact stands on each team's outreach ladder, rep by rep.
  • Every deal by stage, region and department, with contracted revenue against each business line's goal.
  • Expected, actual and missed revenue for each placement.

The numbers

  • 738 of 914 contacts ever enrolled in a sequence had been pulled out early by a rep. Statuses based only on "currently enrolled" would have erased that history, so we set 3,101 statuses from activity history instead.
  • 6,562 districts migrated for the second team: 2,403 new and 4,159 updated, nothing overwritten, and 72 unclear matches held for a person to decide.
  • In the first two weeks, 460 contacts on the first team and 507 on the second picked up an automatic team activity date.
  • The first deal imports reconciled to the dollar against each team's tracker, and 7 deals moved off the wrong organization onto the right district.

Problems we headed off

  • Internal email logging, fixed at the source. 328 employee records picked up logged activity in the 10 days before the fix. In the weeks after, 2 did, and both were explained edge cases.
  • No jump in the contact bill. All 236 new contacts came in as non-marketing, in a portal already past its tier.
  • No new subscription for placement revenue. The Placements object runs on Enterprise features the client already owned.

Before and after

What happens next?

Chapter 1 got two teams selling from one system. Chapter 2 builds on it. We'll update this page when it lands.

Starting fresh, or fixing what you have?

New to HubSpot, spread across several tools, or stuck with a portal that grew without a plan? Either way, we start by learning how your teams sell. Then we build the system around that.

  • Starting from scratch? We design your pipelines, properties, and automation around your process, migrate your data cleanly, and train your team through go-live.
  • Working out of another CRM, spreadsheets, or several systems at once? We map what lives where, move it into HubSpot without overwriting or duplicating records, and flag anything unclear for a person to decide.
  • Already in HubSpot, but it isn't working? We audit your setup, keep what works, fix what doesn't, and use what you already pay for before we recommend anything new.

Vested is a HubSpot Diamond Partner. This is the work we do every day.

Book a call with our HubSpot team. Starting fresh? We'll map out your build. Already in HubSpot? We'll review your portal and show you what it takes to get your team selling from one system.

 

BUILT ON RELATIONSHIPS. DRIVEN BY RESULTS.

About Vested Marketing

Vested Marketing is a HubSpot Partner agency based in Lafayette, Louisiana. At our core, we’re problem solvers: a team of engineers turned marketers who apply the same structured, data-driven approach used to design and build systems.

We provide HubSpot consulting and implementation, CRM and platform integrations, SEO and answer engine optimization (AEO), website design and development, and inbound content programs, each tied to measurable business goals across all industries.