The RevOps Company Emergent 3
Case study, 2026
Case study · Emergent 3

E3 helps schools respond in seconds. Now their revenue engine responds the same way.

Three teams. One HubSpot. Zero dropped handoffs.

Website. Billing. Quoting. CRM. E3 runs everything on HubSpotwe drew the blueprint.

Emergent 3 builds the platform hundreds of schools trust on their worst day. Behind it, we built the system their growth runs on, sales, onboarding, and support aligned in one HubSpot, with every handoff automated.

Revenue dispatch LIVE
SIGNAL  Demo booked on emergent3.com WEBSITE
AUTO  Deal created in the sales pipeline SALES
SIGNAL  Deal moves to closed won SALES
AUTO  Tags & health score applied CRM
AUTO  Round robin assigns an onboarding manager ONBOARDING
AUTO  Rep’s intro sent, onboarding call booked HANDOFF
SIGNAL  Subscription approaching renewal BILLING
AUTO  Renewal deal created · price ramp applied RENEWALS
Listening for the next signal
Client Emergent 3 (E3) Industry Public safety · SaaS HQ Utah, United States Scope Architecture · Sales · Onboarding · Renewals Status Live · long-term partnership
01

The client

Emergent3.com

Emergent 3 builds for the moments when seconds countemergency communication trusted by hundreds of schools.

One tap alerts an entire campus. Staff check in with two. Live smart maps show responders what’s happening, where, and after-action reports make every drill sharper than the last. When something goes wrong at a school, E3 is the platform everyone opens first.

And E3 doesn’t just use HubSpot, they run on it. Their website lives on HubSpot. Their quoting runs through it. So does their billing. That commitment is what makes this story possible.

Alert Check-In Smart Maps Chat Reunification Reports
The partnership ONGOING

This isn’t a five-week rescue. We’ve worked alongside founder Preston Keller and his team for years, and in that time the team has grown three-fold.

Every new rep, onboarding manager, and support hire lands in a system that already knows how E3 works. The architecture below wasn’t rebuilt in a sprint, it was laid as the base and grown deliberatelyone blueprint at a time.

Architected by The RevOps Company HubSpot Diamond Solutions Partner Diamond Solutions Partner · 50+ five-star reviews
At E3, things come in threes
3
teams, sales, onboarding & success, support, working in one HubSpot
team growth over the course of the partnership
Hundreds
schools protected by the platform this engine sells
1
platform underneath it all, website, billing, quoting & CRM on HubSpot
02

The base

The problem, defined

No crisis. No broken portal. The risk was quieter than that.

E3 was growing fast, hiring across sales, onboarding, and support at once. Each team needed to live in HubSpot. And three teams moving fast in one portal, without a shared architecture, is how CRMs quietly fall apart: everyone builds their own corner, and nobody owns the whole.

The most exposed moment was the quietest one: the seconds after a deal closes. Who owns the account now? How healthy is it? Who onboards them, and when? For a company that sells response protocols, the answer couldn’t be “whoever remembers.”

The mandate

Blueprint before build. Every team gets a lane, every handoff gets an automationso growth never depends on memory.

Designed against FAILURE MODES
The handoff lives in someone’s head
A deal closes and the next step depends on who noticed
HANDOFF
Accounts close without tags or a health score
Success inherits customers it knows nothing about
VISIBILITY
Three teams, three private systems
Sales, onboarding and support each drift into their own tools and habits
ALIGNMENT
Renewals surface too late to act
Subscription dates sit in billing while reps look the other way
REVENUE
03

The blueprint

Drawn before built

We started by drawing, not building, mapping how support, sales, and customer success would each work inside HubSpot without colliding.

Each team got its own lane, a pipeline, ownership rules, and automations of its own, but every lane reads and writes the same customer record. A rep, an onboarding manager, and a support agent all see one account, one history, one health score. That single decision is what every automation in this story hangs from.

SALES ONBOARDING & SUCCESS SUPPORT Demo → dealTAM & SDR listsAutomated outreach Round robinOnboarding pipelineForms & meetings TicketsHelp deskEscalations HubSpot ONE RECORD OF TRUTH
LANES A pipeline and clear ownership rules per team, no stepping on each other
MARKET E3’s entire addressable market loaded into HubSpot, SDR lead lists cut straight from it
HANDOFFS Every crossing between lanes defined up front, then automated
04

The protocol

Signal → response

E3 teaches schools that a good response is a rehearsed one: a signal fires, and everyone already knows their role. We built their revenue operation on the same principle. Three signals, three rehearsed responsesrunning automatically, every time.

Signal 01 · A buyer shows up

A demo gets booked on the website, and the pipeline already knows.

The website runs on HubSpot, so there’s no form-to-CRM plumbing to break: a booked demo creates the deal itself. Outbound runs on the same rails, E3’s total addressable market lives in HubSpot, SDRs work lead lists cut straight from it, and automated sequences carry the follow-up so reps aren’t the only touch a prospect gets.

TRIGGER
Demo booked on emergent3.com
AUTO
Deal created in the sales pipeline
No copy-paste, no lag between website and CRM
AUTO
SDR lead lists generated from the TAM
The whole addressable market, already in HubSpot, opportunities created from the list
AUTO
Automated outreach runs alongside the reps
Sequenced touches keep deals warm between calls
Signal 02 · The deal closes

Closed won, the moment that used to depend on memory.

This was E3’s biggest gap, so it got the deepest automation. The instant a deal closes, the account is tagged and health-scoreda round robin picks the onboarding manager, a ticket lands in the onboarding pipeline, and the rep’s handoff email introduces the exact person who’ll run onboarding, with the call booked before the celebration ends.

TRIGGER
Deal marked closed won
AUTO
Tags & health score applied to the account
Success inherits a customer it already understands
AUTO
Round robin assigns an onboarding manager
Fair distribution, zero deliberation
AUTO
Onboarding ticket created in the pipeline
The new customer exists for the onboarding team the second they sign
AUTO
Handoff email introduces the onboarding manager
Sent as the rep, naming the assigned manager, onboarding call booked from it
Signal 03 · Onboarding begins

A pipeline that measures itself while it runs.

Onboarding isn’t a checklist in someone’s notebook, it’s a pipeline of its own. Forms collect what the team needs before the first call, meetings are booked automatically at the right stages, and because every step is a stage change, time-to-onboard reports itselfthe metric leadership actually watches.

TRIGGER
Onboarding ticket enters the pipeline
AUTO
Onboarding forms go out, answers land on the record
The team walks into the first call already briefed
AUTO
Meetings created at the right stages
Kickoff to go-live, scheduled by the pipeline, not by chasing calendars
REPORTED
Time-to-onboard, tracked per account
Stage timestamps make the number automatic, and honest
05

The loop

Renewals & ramping

Because billing, quoting, and the website all live on HubSpot, the customer lifecycle closes its own loop.

Most companies bolt a CRM onto their stack and spend forever syncing it. E3’s stack is the CRM. When a quote is accepted, the subscription exists in HubSpot automatically, no export, no reconciliation. Which means HubSpot always knows the one thing most CRMs never do: exactly when every customer is due for renewal.

As a renewal approaches, a renewal deal is created in a dedicated pipeline and lands with the right sales rep, turning renewals from a date somebody should remember into a pipeline that fills itself.

HubSpot EVERYTHING IN ONE PLACE WEBSITE built by us, on HubSpot QUOTES accepted in HubSpot BILLING subscriptions, automatic RENEWALS deals create themselves
Custom build · Price ramping

Every subscription steps up every year, by itself.

E3’s pricing includes an annual increase on every client subscription. Done by hand, that’s hundreds of small calculations waiting to be missed. We custom-built a price-ramping engine in HubSpot: when a renewal comes due, the new price is already computed and applied to the renewal deal.

No rep does renewal math. No increase gets forgotten. Revenue ramps as designed.

YEAR 1
base
YEAR 2
ramp applied
YEAR 3
ramp applied
YEAR 4
ramp applied
Illustrative, ramp size varies per contract
06

The partnership

Years in

None of this shipped in a quarter. It was laid, layer by layerover years of working side by side.

That’s the quiet advantage of a long partnership: every new hire joins a system that already works, every new motion gets blueprinted before it’s built, and the architecture stays clean while the team behind it has grown three-fold. E3 keeps embracing more of HubSpot, and the base keeps carrying whatever they put on it.

Strategy before software
every new team or motion starts as a drawing on the blueprint
Automation where it counts
handoffs, renewals, and ramps run themselves, people handle judgment
Reporting that answers the next question
from time-to-onboard to renewal tracking, measured as a by-product of the system
The RevOps Company and myself have pushed to keep everything in the HubSpot ecosystem. The payoff is transparency. As we scale, this has been a lifesaver: the entire company can see what’s happening with any account, at any time.
Preston Keller Preston KellerFounder, Emergent 3