Company Overview

ChangeEngine helps organizations deliver employee experiences at scale. But like many fast-moving SaaS companies, the product evolved faster than the documentation supporting it.

As the platform changed continuously and customer volume grew, product knowledge became harder to maintain, harder to access, and increasingly dependent on one person. That person was the Sr. Director of Implementation and Customer Operations who was responsible for onboarding, integrations, training, post-implementation support, and internal enablement, all at once.

Something had to change.

The Challenge

One person. Five audiences. A product that could change morning to night.

Before Brainfish, ChangeEngine's documentation lived in a Notion-based resource with no real search and virtually zero usage. Customers couldn't find answers. Internal teams had no reliable place to look. Product knowledge lived in one person's head and that person was spending 80% of every day answering the same questions on repeat.

The team was fielding 30–50 questions per day, logging 2–4 hours of reactive support daily. At peak, that meant early mornings and late nights just to keep up. And because the product shipped continuously, with eight engineers pushing updates day to day, any article written today could be outdated by next week.

The challenge compounded across five distinct audiences, each needing different answers:

• Customer success teams needed learning-oriented content they could reuse in training
• Customer admins needed clear, task-level how-to guidance
• Contributors needed documentation scoped to limited-access experiences
• IT and HRIS teams needed implementation-specific detail
• Customers broadly needed a guided help center experience, not a scattered archive

Generic documentation couldn't serve all five. And with no product marketing function dedicated to docs, and no efficient way to keep content current, the system couldn't scale.

Why Brainfish

ChangeEngine didn't just need a chatbot. They needed a knowledge system.

The team initially set out to find an AI chatbot that could answer product questions in-app. During the evaluation, the scope of the problem became clear, and so did the solution.

Brainfish stood out by bringing everything together in one platform:

• A searchable, customer-facing help center
• In-app knowledge access for internal teams
• Slack-based knowledge for async internal support
• An Ambient agent that surfaces suggested content updates automatically
• Analytics that prove usage and justify ROI
• Fast implementation, no ticketing overhead, no complex rollout

ChangeEngine also evaluated Zendesk, but quickly ruled it out. They didn't need a full support operation. They needed a lean, flexible knowledge layer that could scale without adding complexity.

Three requirements were non-negotiable: analytics to prove people were actually using it, easy content maintenance so updates didn't create new bottlenecks, and fast implementation the team could stand up without a major lift.

The Ambient agent became the key differentiator. It meant Brainfish wasn't just a support layer, it was a system that could keep documentation aligned with a rapidly evolving product.

How They Use Brainfish Today

One platform, five audiences, two workflows for customer-facing and internal.

1. 1 in 4 customers now use the help center every month — up from 0
The old Notion setup had effectively zero regular users. Customers couldn't find anything, so they stopped trying. Now they’re working through a natural path from getting started, to next steps, to going deeper, without needing to reach out.

2. In-app support for internal teams
Customer success and implementation teams access knowledge inside the product via the in-app widget. Their questions are contextual, tied to what they're seeing in the app at that moment, so the in-product experience fits their workflow better than a standalone help center.

3. Slack knowledge for async internal support
One of the earliest Brainfish workflows ChangeEngine adopted. It created a separate internal knowledge path for teams that needed product answers without going to the external customer-facing help center, important because internal and external answers often need to be framed differently.

4. Persona-specific routing
Because ChangeEngine supports five user types interacting with the same product in different ways, Brainfish routes people toward the right answers based on persona. Admins and contributors get different guidance. IT and HRIS teams have their own article paths and implementation context.

5. Content creation — 2–3 days → same day
ChangeEngine ships fast. Keeping documentation current used to mean manually reviewing every article after every release. Now, the team records a walkthrough in a test account, drops the recording into Brainfish, and the article is ready the same day. The Ambient agent surfaces suggested updates automatically. The team reviews and approves instead of starting from scratch.
‍

"The product can change from morning to night, day to day, or week to week. Brainfish gives the team a way to keep documentation moving at the same speed as the product."
— Jess Chen, Sr. Director of Implementation & Customer Operations

Results

The metrics tell a cause-and-effect story.

It started with a content problem. ChangeEngine couldn't create articles fast enough to keep pace with the product, which meant what existed was often outdated, incomplete, or hard to find. Customers stopped using the help center. Internal teams stopped trusting it. Questions routed to one person.

Brainfish changed the input. With video-to-article generation and the Ambient agent surfacing updates automatically, the team went from spending 2–3 days on a single article to publishing the same day. Better content changed customer behavior.

Help center usage went from 0% to 25% of the active customer base per month. Once customers could actually find what they needed, they used it. The help center became a first stop, not a last resort.

More self-serve meant fewer inbound questions. The implementation and customer operations function had been spending 80% of every day on answers. That number dropped to 20%. The hours recovered didn't disappear — they went toward integrations, enablement, and improving the customer experience.
‍

"Previously, I was spending about 80% of my day on questions. Now I'm down to about 20%... that is just so much time I get back in my day."
— Jess Chen, Sr. Director of Implementation & Customer Operations
‍

Analytics made the ROI visible. During a tight budget cycle, Brainfish was at risk of being cut. The usage data changed that conversation, leadership could see exactly how many customers were engaging with the platform and map that directly to time savings.
‍

"When I was able to show the ROI through the analytics, it provided proof. Hey, people are using this. This is a huge time save."
— Jess Chen, Sr. Director of Implementation & Customer Operations
‍

The biggest structural shift: product knowledge no longer lives with one person. It's searchable, current, and accessible to anyone — customers and internal teams alike.

What's Next

ChangeEngine is expanding Brainfish as the product and team grow.

• Adding more video-based knowledge content to accelerate article creation
• Deepening "What's New" and product launch documentation workflows
• Extending persona-specific experiences as the customer base diversifies
• Exploring broader internal use cases to replace manual onboarding guidance

Closing

If Brainfish disappeared tomorrow, the work doesn’t go away, it just falls back on the team. Customer education, support deflection, content freshness, usage insights. 

For a lean team supporting five distinct audiences, those aren’t nice-to-haves. Brainfish is the system that makes all of it manageable. 

"If we were to lose Brainfish tomorrow, we'd lose all of our help center, all the amazing analytics. We're almost moving back to the stone ages of everything having to be manually written."
— Jess Chen, Sr. Director of Implementation & Customer Operations