Case study — Confidential D2C SaaS
This case study has been anonymized to protect client confidentiality while preserving accurate metrics and outcomes.
At a glance
Industry
D2C SaaS
Timeline
6 months
Starting community
0 members
After 3 months
40,000+
After 6 months
200,000+
Services
Community Ops · Discord · Growth
Pre-launch
0
Members
Month 3
40k+
Members
Month 6
200k+
Members
Overview
The client approached Velko before their product had launched. They had a name, an audience beginning to take shape, and a vision — but no community infrastructure to support it.
Their Discord server started at zero. The goal was to build it into the primary hub for customer support, announcements, user feedback, and community engagement — all before and during the public launch window.
The expectation from day one was scale. Infrastructure, moderation systems, and growth channels all needed to be built for thousands of members, not dozens.
Challenge
Starting a community before a product launches is one of the harder things to get right. No existing user base, no organic pull, no margin for a poor first impression.
They needed a partner who could own the full build — architecture, tooling, and day-to-day operations — while the founding team stayed focused on product.
Our role
Velko took full ownership of the community build and operations. The client focused on product — we handled everything else.
Infrastructure & Setup
Moderation & Safety
Community Operations
Growth & Distribution
* Strategic contribution: Velko proposed the performance-based Instagram creator program. The client implemented and operated it themselves. Velko did not manage Instagram content creation.
Growth strategy
Growth in the first few weeks was deliberate and relatively slow. The focus was on building the foundation correctly before opening the floodgates. Rather than relying solely on paid advertising, the strategy shifted toward community-led growth across several channels working in parallel.
Product success and the client's broader marketing contributed meaningfully to community growth. Velko built and operated the infrastructure that could support that scale — the product and launch brought people to the door.
Retention
Rapid growth creates a problem: members join and disappear. The systems built here were designed to reward participation and make long-term membership feel valuable.
The community developed its own rhythm — members returned because the experience was worth returning to.
Moderation & security
A community growing at this pace is a target. Spam, scammers, and coordinated raids are predictable — the infrastructure was built to handle them before they became problems.
Automated systems
Human moderation
Automation handled the volume; human moderators handled the nuance. The community stayed healthy without requiring constant manual intervention.
Results
Pre-launch
0
Members at start
3 months
40k+
Members
6 months
200k+
Members
Velko built and operated the community infrastructure that supported this scale throughout the product launch and growth period. The product and the client's broader marketing contributed meaningfully to growth — the result was a functioning community at significant scale, with active members, working moderation, and systems robust enough to keep running.
Services delivered