How Freshworks drives behavior change

Companies spend tens of thousands of dollars per employee per year on software. And almost half of all knowledge workers feel overwhelmed by the tools they're supposed to use. Gartner puts the number at 49% for sellers specifically — and those sellers are 43% less likely to hit quota.

That's not a training problem. It's not a rollout problem. It's a strategic gap that sits between the people who buy the technology and the people who have to live inside it every day.

Most enablement teams know this. Most don't have a framework for solving it. They get handed a launch date, a loose-leaf description of the new tool, and a mandate to "train everyone." So they build a deck, run a session, drop some PDFs into a folder, and hope behavior changes.

It doesn't.

What we've seen across hundreds of customer rollouts — and what Freshworks proved out at scale — is that adoption is not an event. It's a journey. And it requires content engineered for where the learner actually is at each point along the way.

This is the playbook for running it.

Meet Freshworks

Freshworks is a global SaaS company with 1,500+ sellers across multiple GTM motions. In 2024, they took on a project most enablement teams would call impossible: a complete CRM overhaul, plus a coordinated rollout of a dozen-plus other GTM tools, on a compressed timeline.

The constraints stacked up fast:

A tight go-live deadline. A normal CRM migration of this size runs 18 months. They had eight.
No sandbox access for reps until launch day. Practice had to happen somewhere else.
A lean enablement team. Nicki Nuñez, Manager of Learning Platforms & Digital Adoption, was the only person primarily focused on tool adoption across the entire GTM stack.
3,600 partner users in a separate ecosystem who needed their own version of all of it.

What Freshworks did wasn't to throw more bodies at the problem. They built a system. A repeatable, learner-first framework that scaled across every tool in the stack — and that they're now using to onboard their entire partner ecosystem on the exact same blueprint.

That framework is what the rest of this post is about.

The Learner Adoption Journey

The framework is built on a simple principle: knowledge workers don't adopt tools the way training programs assume they do. They adopt in stages, and each stage has a different question, a different mindset, and a different content type that actually works.

Five stages:

First Exposure — "What is this, and what's in it for me?"
Orientation — "Okay, I'm in. Where do I start?"
Ramp & Practice — "I've seen it. But can I actually do it?"
Competency — "Am I ready to use this in a real deal?"
Reinforcement — "Where do I go when I forget how to do something?"

Most enablement programs collapse three or four of these into a single live training session and then declare victory at completion. That's the gap. Each stage needs its own content, its own delivery surface, and its own measurement — and the magic happens when they connect.

Here's how Freshworks ran it.

Stage 1: First Exposure

The learner's question: "What is this, and what's in it for me?"

The goal: Not to teach. To create excitement.

This is the stage almost everyone skips. A new tool gets announced, the Slack message goes out, and the next thing reps see is a calendar invite for training. By the time they show up, they're already resistant — because nobody answered the only question they actually cared about: why should I care?

First Exposure is the work that happens before formal training starts. Short teaser content. High-level overviews. Executive endorsements. Sneak peeks. The content's job is to whet the appetite, not to teach the workflow.

Reps should walk away from this stage thinking "okay, this is actually going to help me" — not "oh great, another tool I have to learn."

How Freshworks ran it

Freshworks built a Tooling Hub — a dedicated Seismic page for every tool in the GTM tech stack. One stop, one page per tool, always current.

When a new tool was coming, the first thing Nicki did was update that page with a teaser tutorial, an exec endorsement clip explaining why the company invested, and a short overview of the most exciting benefits reps would get. She'd then socialize the same content through Slack and email — short bursts, designed to create curiosity, not to train.

The result: by the time formal training started, reps were already asking questions. They were anxiously waiting for the course to drop. The Tooling Hub became the one-stop shop reps knew to check first for any resource — training decks, recordings, FAQs, tutorials — for any tool. Nicki still gets the occasional "I looked on Seismic but couldn't find it" Slack — but the volume has dropped significantly.

The template

One page per tool. Pick a single living destination — a Seismic page, a Notion page, a confluence space, whatever your team already uses. One per tool. Owned by enablement.
Update it before launch announcement. When a new tool or major update is coming, the page gets the teaser content first. Everything else points back to the page.
Lead with WIIFM. What is this, and why does it matter to you. Not feature lists. Not specs. The benefit, in the rep's own language.
Use multiple surfaces. Slack announcements, email, exec endorsements — but everything links back to the same page. Don't fragment.

Stage 2: Orientation

The learner's question: "Okay, I'm in. Where do I start?"

The goal: Give them a clear path forward.

First Exposure built curiosity. Now reps need structure. Without it, they show up on day one feeling lost and immediately fall back on the worst habit in software adoption: asking someone instead of figuring it out themselves.

Orientation is the structured learning experience. A sequenced path that tells reps what to learn and when. E-learning that walks them through the tool before they ever touch it live. Safe practice so they can make mistakes before those mistakes cost a deal.

This is where most teams build their training. The mistake is treating it as the whole training program rather than one stage of a longer journey.

How Freshworks ran it

Two weeks before go-live, Nicki's team launched the e-learning through Seismic Learning. Required prework. Built in-house when it was a major launch, supplemented with vendor-provided content (Outreach University, Seismic University) for smaller updates.

The e-learning was engineered for retention. iorad simulations were embedded throughout — letting reps practice the actual workflow inside the tool without ever needing live tool access. With no sandbox available to reps, the simulations became the sandbox.

One week before go-live: a live platform walk-through. The e-learning was prework, so the live time was for hands-on, interactive work — not information dumps. Nicki would call on reps to share their screen and walk through the workflow themselves while she narrated. When reps didn't have access to the tool yet, she'd pull up a sandbox and run "Seismic Scavenger Hunts" to get them familiar with where resources lived.

By the time go-live hit, reps had already seen every screen. Multiple times. From multiple angles.

The template

Sequence the path. Don't drop reps into a content library and tell them to figure it out. Build a course. Assign it by role. Give them a clear first thing to do.
E-learning as prework, live training as practice. Don't burn live time on information delivery. Use live time for the things only live time can do: questions, hands-on practice, real reps demoing in real tools.
Embed practice inside the e-learning. This is non-negotiable when sandbox access is delayed or doesn't exist. Reps need to put their hands on the workflow before launch day, even if it's a simulated version.
Reference the Tooling Hub constantly. Every course should point back to the page. Reps should leave training knowing exactly where to look next.

Stage 3: Ramp & Practice

The learner's question: "I've seen it. I've been shown it. But can I actually do it?"

The goal: Build confidence through doing — not through more content.

This is where almost every adoption program fails. The course wraps. The live session ends. Enablement assumes reps are now "trained." Reps assume they're now expected to know what they're doing. Both are wrong.

Knowledge work doesn't move from seen to can do in a single session. It takes scenario-based practice. Reinforcement at the right intervals. Low-stakes repetition where failure is part of learning, not a career-limiting moment.

The pattern that separates programs that produce confident reps from programs that produce frustrated ones: when a question hits Slack, the answer isn't a text explanation. It's a link to the tutorial. Every question becomes a practice opportunity.

How Freshworks ran it

Nicki built a hypercare system where every FAQ became a practice rep.

Reps would Slack her with a question — "how do I log this activity on this opportunity?" — and her response was almost always the same: a link to the relevant iorad tutorial. Not a screenshot. Not an explanation. Not a Zoom call. The tutorial, every time.

It took repetition. It took her resisting the urge to just answer the question quickly to be helpful. But over time, behavior changed. Reps started checking the library before they asked. The proof point Nicki points to: a rep recently Slacked her, got a tutorial link back, and replied "I can't believe I didn't check to see if there was a tutorial before I bugged you."

That's the inflection. That's when self-serve becomes a habit instead of a feature.

To support it, Freshworks built tutorial libraries embedded everywhere reps work — inside the e-learning, on the Seismic page for the tool, accessible via the iorad extension inside the tool itself. Reps can search by keyword, find the tutorial in seconds, and run through it as many times as they need.

She also runs a weekly office hours call. When reps ask a question live, the answer is the same — here's the tutorial, and here's the link so you can come back to it. The office hours became one of the most well-attended in the company, partly because of the cultural reinforcement: every interaction trained reps where to look first.

The template

Tutorial-first answers. Every FAQ that hits enablement becomes a tutorial. Once it exists, the answer is the link. Always.
Tutorials live in three places. The e-learning. The Tooling Hub page. The in-app library inside the tool itself. Same content, multiple surfaces.
Weekly office hours as a forcing function. Don't be the heroic Slack responder. Train reps to bring questions to office hours, and answer with tutorial links there too.
The repetition is the work. It feels redundant. It feels like you're being unhelpful by sending the same link 50 times. Send it the 51st time. That's how the habit forms.

Stage 4: Competency

The learner's question: "Am I ready to use this in a real deal?"

The goal: Move from "practiced" to "performing in live work."

There's a gap most enablement teams don't measure: the gap between course completion and actual capability. Reps complete the training. Reps attend the session. Reps say they got it. And then they sit down to log a real opportunity in a real CRM and freeze.

Competency is earned in real work, not declared in a training session. Which means the support has to be available inside the tool, at the moment of need — not in a separate training portal that reps have to remember exists.

How Freshworks ran it

Freshworks built an in-app tutorial library accessible directly inside the tools reps were using. The iorad extension surfaces a contextual library — when reps open it inside Salesforce, they see Salesforce tutorials. When they open it inside Outreach, they see Outreach tutorials. Search by keyword, get the tutorial, run through it without leaving the tool.

The shift Nicki has been driving: getting reps to use the site help button — a question mark icon embedded directly on URLs with enabled tutorials. Even less friction than the extension. Reps don't have to remember they have iorad. The help is just there.

Some tutorials run in click-through mode in the iorad window. Where it makes sense, Freshworks enabled "Do It Live" mode — where the tutorial guides reps through actions on the actual screen, in their actual tool, with their actual data.

The measurement shift that matters: course completion is not the same thing as capability. What Freshworks watches for is behavior — reps pulling tutorials mid-deal without being told to, the same question stops showing up in office hours, page views drop while referenced content shares go up.

The template

In-app, not in-portal. If reps have to leave the tool to find help, they won't. The library has to live inside the tool itself.
Default to one-click access. Extensions work. Site help buttons work better. Anything that reduces friction between "I have a question" and "I have an answer" is worth the lift.
Use Live mode where the QA cost is justified. Live guidance is powerful but maintenance-heavy. Use it for high-frequency, high-stakes workflows. Use Try mode for everything else.
Measure behavior, not completion. Track the questions that stop getting asked. Track the tutorials that get shared rep-to-rep. That's where competency shows up.

Stage 5: Reinforcement

The learner's question: "Where do I go when I forget how to do something?"

The goal: Keep knowledge alive without pulling reps back into a classroom.

By this stage, reps are fully functional. They know the workflows. They're closing deals. But not every workflow gets used every day, and software changes constantly. The work of Reinforcement is keeping knowledge sharp for the things reps don't do often, and keeping content current as the tool evolves.

This is also where most adoption programs go to die. The library gets stale. One outdated tutorial, and reps lose trust in the whole thing. They go back to Slacking enablement. The system collapses.

Reinforcement done right is a governance problem more than a content problem.

How Freshworks ran it

Two practices keep Freshworks' adoption alive long after launch.

The first is the Tool Sprints program. Each week, Nicki's team highlights one tool feature — what it does, why it matters, and a tutorial showing how to use it. The content goes out as a Seismic News Center post, an update to the Tooling Hub page, a Slack message, and an email. Same content, four surfaces. They've gamified it — leaderboards for the fastest tutorial views, streaks for reps who keep up week to week. Adoption became culture.

The second is the living tutorial library. As the GTM tools evolve — UI updates, new fields, changed workflows — the tutorials get updated to match. Because the tutorials are surfaced through Seismic Pages, the e-learning, and the in-app library all from the same source, one update propagates everywhere. No hunting for the old version. No maintaining four copies.

The template

One nudge per week, multiple surfaces. Pick one feature. Make one tutorial. Send it through Slack, email, your enablement platform, and your tool's resource page. Don't fragment.
Gamify where it fits your culture. Leaderboards and streaks aren't a fit for every org. Where they work, they turn passive consumption into active competition.
Update at the source, not at every surface. This is why governance matters. If you have to update the same tutorial in five places, you'll stop updating it in any of them.
Watch the trust signal. When reps stop trusting the library, you'll see it in the Slack volume. Treat library health as an operating metric, not a side project.

What Freshworks would do differently

A playbook isn't honest unless it acknowledges what's still hard.

Three things Freshworks would change with hindsight:

More time for change management. The compressed eight-month timeline forced compression on the enablement side. With more time, Nicki and Alexa would have given reps more space to wrap their heads around the change before go-live — not more content, just more breathing room for the content they had to land.

Earlier sandbox access — even when it's expensive. Simulated practice through iorad covered the gap, but the team would push hard for real sandbox access for reps if the licensing math could be made to work. There's no full substitute for hands on the actual live tool before launch.

More disciplined Live-mode rollout. "Do It Live" tutorials are powerful but high-maintenance. Where the QA process couldn't keep up, Try mode covered the workflow. The lesson: pick the workflows where Live mode pays for itself, and don't try to convert everything.

The pattern that scales

The reason Freshworks' framework works isn't the specific tools they used. It's that they treated adoption as a journey with distinct stages, and built a content type and a delivery surface for each one.

Most teams skip First Exposure entirely and start at Orientation. They collapse Ramp and Competency into a single training session. They abandon Reinforcement as soon as the launch ticket gets closed. The result is the same gap that costs companies tens of thousands of dollars per employee per year: tools that get bought, deployed, and never actually used.

The fix is structural. Build for the learner's actual journey, not the launch project plan.

If you're inside a tool rollout right now and any of this is hitting close to home — the compressed timeline, the lean team, the change management you're trying to do without a clear framework — this is the playbook. Steal it. Adapt it. Run it against whatever tool is on your desk this quarter.

And if you want to talk through how to apply it to your specific stack, we'd love to compare notes.

How Freshworks Drives Behavior Change