Project Plan: supporthandbook.com

This document serves as the persistent memory and master plan for supporthandbook.com. It contains the vision, current state, architectural layout, and the roadmap for the project. In any future session, you can ask me to reference this file to resume work exactly where we left off.

1. Project Vision

supporthandbook.com is designed to be the “GitHub + Wikipedia” of the customer support industry. It is a collaborative, open-source portal where customer support professionals can co-create, discuss, and refine standard support handbooks across various industries (SaaS, E-commerce, FinTech, etc.).

Instead of organizations writing support playbooks from scratch, they can copy, modify, and implement community-vetted templates.

2. Current Setup & Configuration Reference

Pillar 1: The Wiki (GitBook)

• Status: Connected & Active
• Subdomain: Configured on a custom subdomain (e.g., wiki.supporthandbook.com or docs.supporthandbook.com).
• DNS Settings (Cloudflare):
• Type: CNAME
• Name: wiki (or chosen prefix)
• Target: GitBook-provided target host (ends in .gitbook.io or .hosting.gitbook.io).
• Proxy Status: DNS Only (Grey Cloud). Must remain grey to avoid Error 1014.
• TTL: Auto

3. Future Architecture (To Be Implemented)

Pillar 2: The Community Forum (Discourse or Flarum)

Option A: Discourse (Standard)

• Goal: Host high-scale debates, edit suggestions, and discussions.
• Tech Stack: Discourse self-hosted on a DigitalOcean droplet.
• Requirements/Cost: Requires 1GB–2GB RAM VM ($6–$12/month) due to heavy Ruby/Docker stack.
• Integration: Add “Suggest Edit / Discuss” buttons on GitBook linking to forum threads.

Option B: Flarum on Fly.io (Lightweight & Cheap)

• Goal: Modern, fast, single-page app forum experience with full SEO benefits.
• Tech Stack: Flarum 2.0+ self-hosted on Fly.io using an SQLite database stored on a persistent Fly Volume.
• Requirements/Cost: Runs on a shared-cpu-1x VM with 512MB RAM ($3.32/mo) and a 1GB Fly Volume ($0.15/mo) for a total of ~$3.47/month.
• Note: Needs a swapfile or temporary scaling to 1GB RAM to prevent Out Of Memory crashes during Composer plugin installations.

4. Monetization Strategy

As a pure Media & Community platform, monetization is driven by traffic and engagement:

1. Affiliate Marketing: Recommend helpdesks (Zendesk, Intercom, Help Scout) using recurring-revenue affiliate links.
2. Premium Templates: Sell downloadable bundles (e.g., pre-made Zendesk Macros, onboarding templates, KPI sheets) for $49–$199.
3. Niche Job Board: Charge companies $99–$199 to post targeted remote customer support jobs.
4. Sponsorships: Host banner advertisements from customer service software tools once traffic grows.

5. Execution Roadmap

gantt
    title supporthandbook.com 90-Day Roadmap
    dateFormat  YYYY-MM-DD
    section Phase 1: Content Setup
    Draft Seed Articles       :active, 2026-06-14, 14d
    Establish Tone & Layout   : 14d
    section Phase 2: Community Setup
    Configure Discourse Forum : 2026-06-28, 10d
    Link GitBook & Discourse  : 5d
    section Phase 3: Outreach & Growth
    LinkedIn Ego-Bait Posts   : 2026-07-13, 30d
    Direct Outreach to Leads  : 30d
    section Phase 4: Monetization
    Add Affiliate Links       : 2026-08-12, 10d
    Launch Job Board          : 15d

Next Steps to Take:

• Write the first 3 “seed” articles (Handling angry customers, refund requests, and support metrics glossary).
• Launch the community forum (Flarum on Fly.io or Subreddit r/supporthandbook).
• Add the “Suggest Edits” / community buttons to GitBook.

6. Competitor Landscape & Strategy

The Competitors We Face:

1. Corporate Lead Magnets (HubSpot, Help Scout, Zendesk): Provide static, free templates to sell their software. They have massive SEO budgets.
2. Ephemeral Chat Communities (Support Driven): A massive Slack group for support professionals. Valuable knowledge is shared daily, but it gets buried in chat history.
3. Gated Blueprints (Reforge, Vitally): High-quality customer success playbooks locked behind paywalls or email-capture forms.

Our Strategic Edge (How We Win):

• Structured & Searchable (Not Chat): Instead of losing insights in a Slack feed, we organize them into an open-source, search-indexed, Wikipedia-style wiki.
• The “Git” Collaboration Workflow: Allowing users to submit modifications and changes directly, creating the first community-driven standard library for support.
• Niche & Specific Utility: Avoid generic SEO battles. Write highly specific, high-friction operational guides (e.g., handling legal threats, disputed charges, Stripe frauds) that corporate blogs avoid.
• Guerilla Distribution: Answer questions in existing communities (like Support Driven Slack or Reddit) and link back to our specific playbooks as the definitive answers.