Skip to content
All work
Case Study Writing

B2B SaaS Customer Case Study

A complete customer case study for a helpdesk software company, written from a customer interview into a story sales teams can actually send.

Helpdesk software vendor (fictional)Case StudySaaSSales Enablement

The brief

A helpdesk software company had happy customers but only one case study, which read like a product brochure with a logo on top. Sales wanted stories prospects would actually read, and that answered the doubts that came up on sales calls.

The approach

Case studies like this are built from a 40-minute interview with the customer, focusing on what life was like before, why they chose this vendor over the alternatives and what nearly stopped them. The story leads with the result, uses the customer's own words, and gives the "almost didn't buy" moment real space, because that's the doubt prospects share.

Delivered

  • Customer interview questions and 40-minute interview
  • Full case study (web and PDF versions)
  • Results summary box for skimmers
  • Pull quotes for sales decks and social posts

The work

Read the full sample

2 min read

Both companies and the people in this case study are fictional, created for this sample. The figures are illustrative of the format. In real projects, every number is confirmed with the customer before publication.

How Brightpath Tutoring cut first-response time from 9 hours to 40 minutes, without hiring

Results at a glance

Before After six months
Median first response 9 hours 40 minutes
Support team size 4 4
Parent satisfaction (CSAT) 81% 93%

Measured by Brightpath using Tidewell's reporting, comparing January with July.


The situation

Brightpath runs online tutoring for 6,000 families. Every evening between 6 and 9 pm, parents send the same handful of questions: can we move Thursday's lesson, why didn't the link work, when is the next invoice?

"It all came in at once, to a shared inbox," says Aisha Rahman, Brightpath's head of family support. "By the time we'd answered the easy ones, the urgent ones (a child sitting in front of a broken link) had been waiting an hour."

The team of four was working hard. The inbox just made it impossible to see what mattered.

Why they almost didn't switch

Brightpath had tried a helpdesk tool before. "It took two months to set up, and the team hated it," Aisha says. "When I suggested another one, I could see everyone's faces."

What changed her mind was the trial. Tidewell imported three months of old emails, and within a day the team could see their own conversations sorted into categories. "It wasn't a promise in a demo. It was our actual inbox, already making sense."

What they set up

Brightpath kept things deliberately simple:

  • Urgent routing. Any message mentioning a lesson happening today goes to the top of the queue.
  • Saved replies for the ten most common questions, written in the team's own tone.
  • A self-serve rescheduling link in every lesson confirmation, which removed a whole category of messages.

Setup took one afternoon with Tidewell's onboarding team.

The result

Within six months, median first-response time fell from nine hours to 40 minutes, with the same team of four. Parent satisfaction scores rose from 81% to 93%.

"The biggest change isn't the numbers," Aisha says. "It's that the team goes home at nine without feeling like they've left someone waiting."

What's next

Brightpath is now using Tidewell's reporting to find the questions that shouldn't need to be asked at all, starting with making invoice dates clearer in the parent app.


Why it works: The headline states the result, the timeframe and the constraint ("without hiring"), which is what makes it impressive. The results table serves skimmers; the story serves readers. "Why they almost didn't switch" addresses the most common objection to any new tool (we tried one, it failed) in the customer's own voice, which is far more persuasive than the vendor saying it. The note under the table explains how the numbers were measured, which is what makes them believable.

Why it works

The case study reads as a story rather than an advert: the customer is the hero and the software is the tool. Results are stated plainly, with the timeframe and how they were measured. Including the customer's hesitation gives it credibility, and it's the section sales teams find most useful, because it answers the objection prospects raise.

Want something like this for your business?

Send a short brief. You’ll get a reply from me, not an account manager, with a recommended scope, a fixed quote and a delivery date.

Umair ZararFounder, KhanCopyX