Customer Story · Enterprise ServiceNow Platform HubSpot

HubSpot's ServiceNow team ship 5× faster with complete instance awareness.

HubSpot's ServiceNow instance is the single front door for its worldwide ITSM, HR, and SecOps workflows — maintained by just seven engineers against an ever-growing backlog. Echelon mapped their highly customized instance from the inside out, and made their strongest engineers five times faster.

~5×

Faster engineering throughput

4,000

Developer hours unlocked

30+

Business analysts building safely

Meet HubSpot

HubSpot's ServiceNow instance is the operational backbone of a global enterprise — the single front door for any employee, with modules from ITSM to HR, and SecOps to CSM. Behind it sits a mature platform team, supported by a handful of contractors and a 30-plus business-analyst community out in the business.

Internal ServiceNow engineers

30+

Business analysts across the org

10+

ServiceNow modules in production

The Challenge

Accelerating development without scaling risk

After over a decade building a mature ServiceNow development squad, the challenge for HubSpot was never capability — it was development speed on a highly custom instance with growing demand. A small expert team wanted to move faster, while a growing community of 30+ business analysts meant more hands pushing changes into a deeply customized instance.

Every new business analyst is a governance risk when best practices live in a few experts' heads. The instance complexity runs deep — years of custom app scopes, configurations, and workspace-specific behaviors — so each change has to respect a lot of standards.

An iceberg. Above the waterline, a small tip labelled 'the visible backlog.' Below the surface, far larger, sits what HubSpot's ServiceNow team understands: years of customizations, custom app scopes, catalog configurations, workspace-specific behaviors, and countless modules. The obstacle wasn't headcount — it was everything below the surface.

Pressures on a scaling platform team:

Highly custom instance

Manual development limits output

A growing business-analyst base raising quality risk

No consistent review across many update sets

Instance-Aware Development

Why generic AI tools
failed for HubSpot

Generic AI tools failed for HubSpot work because they didn't know their specific instance or the standards they wanted to enforce within it — its app scopes, custom configurations, naming conventions, and governance rules. Echelon mapped their instance before any work began, so its output aligns with HubSpot's internal standards by default.

"We don't use ServiceNow as a fresh install. There have been configurations, there have been customizations, and we need it."

Stephen Sturdevant · HubSpot

Generic coding agents

Echelon

Not trained on ServiceNow in any way

Taught ServiceNow best practices

Blind to custom app scopes & configs

Maps your instance before work begins

Does not follow your governance standards

Code outputs aligned to your governance model

How Echelon Works at HubSpot

The first stop for every team member

Echelon is the first stop for everyone who touches the instance at HubSpot — business analysts and engineers alike. They use it to research, troubleshoot, answer questions, and do real development work, integrated deeply into their day to day workflow.

Track 1 · Business Analysts

Research and build, safely

Instance research that once took days now takes minutes
No more queuing for engineers to answer questions
Self-serve building without learning every instance nuance
Every change held to the same best-practice standards

Track 2 · Engineers

Accelerate a strong team

An AI teammate embedded in every workflow
Troubleshooting, instance questions, and real build work across all modules
5× engineering velocity — without adding headcount

Governance at the Moment of Change

Every business analyst update set, automatically reviewed.

HubSpot already promoted changes from dev to prod through a Slack approval workflow — every push posts the change to Slack for sign-off. Echelon plugs straight into that flow: it automatically reviews each change against governance rules and instance standards, so business analysts can promote safely and approvers sign off with confidence.

With Echelon · the dev-to-prod approval flow

What HubSpot got

Engineers build 5× faster

Governance enforced on every update set

Business analysts building fast — safely

Echelon fully integrated in existing workflows

Business analysts & the business

A growing developer base moved fast — without putting governance at risk.

Before Echelon

After Echelon

Business analysts a governance & quality risk

Business analysts move fast, governed by default

Quality varied across many developers

Consistent enforcement at the moment of change

Platform team gatekept every change

Self-serve with an automated safety net

A tool that needs babysitting

A deep, ongoing innovation partnership

Key Takeaways

Key takeaways

For a mature team, the bottleneck isn't skill — it's leverage. An AI teammate embedded in every squad lets a strong team operate at far higher velocity.

A growing business-analyst base is only a risk when governance is manual. Reviewing every change at the moment it's pushed lets the business build fast without drift.

The most durable adoption comes from being the first stop for every developer — and consistently the best one.

Framework, not headcount

An approach that knows your environment well enough to become indispensable.

Book a Demo Read more stories

"We needed a partner that didn't just provide staff augmentation, but brought an automated framework to handle the lifecycle of our service catalog. Echelon did exactly that."

HubSpot Leadership

Reference

Update set: A packaged set of configuration changes in ServiceNow, promoted between instances (dev → test → prod). At HubSpot, every push triggers an automatic Echelon review.
Business analyst: A business-side user who builds or configures ServiceNow apps and workflows without being a full-time platform engineer. At HubSpot, business analysts make up a 30-plus developer community pushing changes into the instance.