Skip to content

Case Study: RevenueHunt

Building a complete documentation ecosystem for a Shopify app with thousands of users

5 Years of collaboration
100s Help articles published
30+hrs Tutorial video content
20K↓ Support tickets reduced

The client

RevenueHunt builds product recommendation quiz apps for Shopify stores. Their flagship product — Shop Quiz — helps e-commerce stores guide shoppers to the right products through interactive quizzes, driving higher conversion rates and average order values.

The product is feature-rich and technically sophisticated, with integrations across dozens of Shopify themes, email platforms, and analytics tools.


The challenge

When I joined RevenueHunt in 2021, the documentation situation looked like what you'll find at most fast-growing startups: scattered, inconsistent, and constantly playing catch-up with a rapidly evolving product.

Specifically:

  • No central documentation structure — information was spread across Zendesk tickets, FAQs, and informal guides
  • High support volume for questions that should have been self-serve
  • No video content — users were asking for walkthroughs but there was nothing to point them to
  • Docs not keeping pace with development — new features shipped without documentation

The approach

1. Information architecture first

Before writing a single word, I audited everything that existed and mapped out a new structure using the Diátaxis framework — separating content into four clear categories:

  • Tutorials — learning-oriented, step-by-step for new users
  • How-to guides — task-oriented, for users who know what they want to do
  • Reference — information-oriented, comprehensive feature documentation
  • Explanation — understanding-oriented, the why behind design decisions

This structure means users always land in the right place. A new user gets a tutorial. An experienced user looking for a specific setting gets reference docs. Neither group has to wade through content meant for the other.

2. MkDocs with Material theme

I chose MkDocs with the Material theme for the documentation site because it delivers:

  • Fast, client-side search with no backend required
  • Clean, professional UI that matches the quality of the product
  • Easy navigation for both simple and complex content structures
  • Simple Markdown authoring that non-technical team members can contribute to
  • Excellent mobile experience

3. Content writing at scale

Over five years, I've written and maintained hundreds of help articles covering:

  • Complete onboarding tutorials for new merchants
  • Integration guides for every major Shopify theme
  • API and developer reference documentation
  • Step-by-step how-to guides for every product feature
  • Release notes and feature announcements
  • Troubleshooting guides based on real support ticket patterns

4. Video tutorial channel

Alongside the written docs, I built and maintain a YouTube tutorial channel with hours of walkthrough content. Each video is:

  • Scripted for clarity and searchability
  • Recorded with clear screen capture and professional narration
  • Edited with chapters so users can jump to the relevant section
  • Cross-linked from the relevant written documentation

The result

Paulina transformed how our users experience our product. The documentation site she built is something our whole team is proud of — and more importantly, our users actually use it. Support tickets for questions covered in the docs dropped significantly, and we regularly get compliments on the quality of our help content.
— RevenueHunt Team

The live documentation site is at https://docs.revenuehunt.com/ — you can explore it directly to see the structure, writing style, and navigation in action.


What this means for you

RevenueHunt is a live proof of concept for what a well-structured documentation ecosystem can do for a SaaS product. If you're looking for the same result — fewer support tickets, better user activation, and documentation your team is proud to share — let's talk.

Get in touch   See services & pricing