Fixing retention by transforming onboarding for a scrappy SaaS platform
Overview
Member365 was a small, fast‑moving B2B SaaS company offering an all‑in‑one platform for membership‑based organizations. From payment processing to event planning, email campaigns, forms, and fundraising, the product aimed to centralize every administrative function a membership organization might need.
I joined the marketing team during a period of aggressive growth following second‑round financing. Our job was to scale acquisition — and we did. But rapid growth exposed a deeper problem: customers weren’t staying.
The Retention Problem
Despite strong sales performance, Member365 struggled with churn. The issue wasn’t product quality — it was onboarding.
Membership organizations vary dramatically in structure, workflows, and expectations. Many customers spent months trying to configure the platform to match their needs. Confusion, frustration, and stalled implementations created a massive leak in the funnel.
To solve this, I partnered with the company to build the Member365 Knowledge Base — a self‑serve onboarding and support system designed to reduce time‑to‑value and improve retention.
Challenges
1. What do we write first?
There was no shared understanding of which articles mattered most. Different business units had different priorities, and waiting for alignment wasn’t an option.
To break the deadlock, I created a shared spreadsheet that pulled data directly from Zendesk. This allowed teams to:
- Feed real support tickets into the backlog
- Identify recurring issues
- Prioritize articles based on volume and urgency
This turned prioritization into a data‑driven system, not a debate.
2. Taxonomy chaos
Membership management is a world of ambiguous terminology. Even internally, no one fully agreed on what certain roles or concepts meant.
Instead of delaying delivery with philosophical debates, I:
- Made informed judgment calls
- Accepted ambiguity where necessary
- Allowed terms to remain flexible so users with different mental models could still find what they needed
Sometimes ambiguity is a feature, not a bug.
3. Cross‑functional coordination
The knowledge base touched every part of the business:
- Support
- Product
- Sales
- Marketing
- Customer success
I worked across all these groups to gather information, validate workflows, and ensure documentation reflected real user needs.
What I Built
The Member365 Knowledge Base became:
- A centralized onboarding resource
- A searchable library of how‑to guides
- A system for reducing support load
- A retention‑driving asset that helped customers reach value faster
By grounding the backlog in Zendesk data, we ensured we were always writing the highest‑value article next — without meetings, debates, or guesswork.
This is how you get the most value from writers: give them a system that decides what matters.
Learnings
1. SaaS success is retention
Acquisition is expensive. Retention compounds. A strong onboarding experience can transform long‑term revenue far more effectively than top‑of‑funnel growth.
2. Outcomes matter more than inputs
I began my career as a copywriter, where words only matter if they do something. That mindset shaped this project.
- Publish something acceptable
- Observe how users interact with it
- Improve based on real behavior
Polish is easier — and more accurate — after you ship.
3. Ambiguity isn’t always the enemy
Different users bring different mental models. Sometimes a term needs to be broad enough to accommodate multiple interpretations. In the knowledge base, embracing ambiguity helped more users find what they needed.
Reflection
This project taught me how to build content systems that directly influence business outcomes. It reinforced that content design isn’t about perfect words — it’s about reducing friction, accelerating value, and helping users succeed.
The Member365 Knowledge Base wasn’t just documentation. It was a retention strategy, a product accelerator, and a reminder that the right content, delivered at the right time, can change the trajectory of a SaaS business.
Leave a Reply