DocsHub - Competitive Positioning Battle Cards

Product: DocsHub (Documentation Platform) Purpose: Sales enablement - how to position against competitors Version: 1.0 Last Updated: January 2025

🎯 OVERVIEW

This guide provides competitive intelligence and positioning strategies for the 4 main competitors DocsHub faces in the South African market:

Microsoft SharePoint (Market leader, enterprise focus)
Atlassian Confluence (Developer/tech company favorite)
Notion (Modern, all-in-one workspace)
Google Workspace (Docs + Drive, ubiquitous)

How to Use This Guide:

Before Discovery Call: Review the competitor the prospect currently uses
During Demo: Use “When DocsHub Wins” talking points
In Objection Handling: Reference “Their Weaknesses” to overcome objections
In Proposals: Use pricing comparisons to justify DocsHub investment

🥊 BATTLE CARD 1: vs Microsoft SharePoint

Competitor Overview

What is SharePoint?

Enterprise content management and collaboration platform
Part of Microsoft 365 suite (bundled with Office, Teams, OneDrive)
Designed for intranets, document management, workflow automation
Market leader in enterprise (Fortune 500 companies)

Pricing:

R100-R170 per user per month (Microsoft 365 Business Basic to E3)
Typical SA organization (50 users): R5,000-R8,500/month
Requires Microsoft 365 subscription (can’t buy SharePoint standalone)

Market Position:

Market share: 60-70% of enterprise organizations
Strengths: Integration with Microsoft ecosystem, enterprise features
Weaknesses: Complexity, user experience, cost at scale

Their Strengths (Be Honest)

✅ Microsoft Ecosystem Integration

Seamless with Microsoft 365, Teams, Outlook, Office apps
Single sign-on with Active Directory
Organizations already paying for Microsoft 365 see it as “free”

✅ Enterprise Features

Advanced workflows (Power Automate)
Granular permissions (inheritance, security groups)
Compliance features (eDiscovery, retention policies)
Suitable for 10,000+ employee organizations

✅ IT Department Familiarity

Most enterprise IT teams already know SharePoint
Preferred by risk-averse IT departments (“Nobody gets fired for buying Microsoft”)

✅ Offline Sync

OneDrive integration allows offline document editing
Works well for distributed teams with poor connectivity

Their Weaknesses (Our Opportunity)

❌ Terrible User Experience

Notoriously bad search (users complain: “I can never find anything”)
Slow page load times (10-30 seconds common)
Confusing navigation (nested folders, broken breadcrumbs)
Quote: “SharePoint is where documents go to die”

❌ Complexity Requires Dedicated Admin

Steep learning curve (requires training)
Needs full-time SharePoint admin for medium orgs
Permission management is nightmare (inheritance issues)
Frequent breaking changes with Microsoft updates

❌ Per-User Pricing Becomes Expensive

R100-R170/user/month for 100+ users = R10,000-R17,000/month
Forces organizations to limit licenses (kills adoption)
“Who has access?” becomes political issue

❌ Not Purpose-Built for Documentation

SharePoint is a Swiss Army knife (does everything poorly)
Documentation is afterthought (designed for intranets, workflows)
No clean, public-facing documentation experience

❌ Mobile Experience is Poor

Mobile app is clunky and slow
Not suitable for field workers (construction, site managers)

When SharePoint Wins

Scenario 1: Large Enterprise Already Locked In

Organization with 5,000+ employees
Already paying for Microsoft 365 E3/E5
Enterprise IT team skilled in SharePoint administration
Complex workflow requirements (Power Automate)

Scenario 2: Deep Microsoft Integration Required

Heavy use of Power BI, Power Apps, Dynamics 365
Workflow automation critical (approval processes)
Need integration with on-premise Active Directory

Disqualify if:

They say “We’re happy with SharePoint and don’t see any problems”
Enterprise with dedicated SharePoint admin team (5+ admins)
Budget is locked into Microsoft EA (Enterprise Agreement)

When DocsHub Wins

Scenario 1: SME Fed Up with SharePoint Complexity

20-200 employees
No dedicated SharePoint admin (IT person wearing multiple hats)
Complaints about search, speed, user experience
Paying per-user and costs are escalating

Scenario 2: Need Public-Facing Documentation

Training provider needing SETA-compliant documentation portal
Tech company needing customer help center
Municipality needing public transparency portal
SharePoint requires login (can’t make truly public)

Scenario 3: South African Data Residency (POPIA)

Microsoft 365 data often stored in EU or US (not SA)
POPIA compliance requires SA data residency
DocsHub hosted in Hetzner Cape Town (guaranteed SA)

Scenario 4: Mobile-First Use Case

Construction company needing site access to safety docs
Field workers needing documentation on tablets/phones
SharePoint mobile experience is terrible

Key Talking Points (Sales Script)

Discovery Questions:

“How do your users feel about SharePoint? Do they find documents easily?” (Listen for frustration)
“Do you have a dedicated SharePoint administrator?” (If no, highlight complexity)
“How much are you paying per user per month?” (Calculate total, compare to DocsHub flat pricing)
“Do you need public-facing documentation without requiring login?” (SharePoint can’t do this well)

Positioning Statement:

“SharePoint is a powerful enterprise tool, but it’s designed for intranets and workflows - not documentation. Organizations tell us they chose SharePoint because it came with Microsoft 365, but their teams hate using it. DocsHub is purpose-built for documentation: fast search, clean interface, mobile-friendly, and fixed pricing. Think of it this way: You wouldn’t use Excel for project management just because you already have Office. Same logic - use the right tool for documentation.”

Price Comparison (50 Users):

SharePoint (Microsoft 365 Business Standard):
- R136/user/month × 50 users = R6,800/month = R81,600/year

DocsHub Professional:
- R7,500/month flat = R90,000/year
- INCLUDES migration, training, support (SharePoint = extra cost)
- NO per-user scaling (add 50 more users = R0 extra cost)

Proof Points:

“Pentacon Construction switched from SharePoint to DocsHub - their project managers said search went from 45 minutes to 2 minutes”
“Training providers love DocsHub because auditors can access docs without SharePoint login complexity”

🥊 BATTLE CARD 2: vs Atlassian Confluence

Competitor Overview

What is Confluence?

Wiki and collaboration platform for teams
Popular with software developers and tech companies
Part of Atlassian suite (integrates with Jira, Trello, Bitbucket)
Modern UI, better user experience than SharePoint

Pricing:

Standard: R70/user/month (1-100 users)
Premium: R140/user/month (collaboration features, analytics)
Typical SA tech company (30 users): R2,100-R4,200/month
Volume discounts at 500+ users

Market Position:

Market share: 30-40% of tech companies, developer teams
Strengths: Developer-friendly, Jira integration, clean UI
Weaknesses: Per-user pricing, limited customization, not great for public docs

Their Strengths (Be Honest)

✅ Developer-Friendly

Markdown support (devs love this)
Code syntax highlighting
Integration with Jira (requirements → documentation)
API for automation

✅ Better UX Than SharePoint

Clean, modern interface
Decent search (better than SharePoint, not as good as DocsHub)
Page templates and macros for consistency

✅ Collaboration Features

Inline comments on pages
@mentions and notifications
Real-time collaborative editing
Activity streams (who changed what)

✅ Atlassian Ecosystem

Organizations already using Jira find integration valuable
Single login across Atlassian products
Familiar to tech teams

Their Weaknesses (Our Opportunity)

❌ Per-User Pricing Scales Poorly

R70/user/month × 50 users = R3,500/month (seems cheap)
R70/user/month × 200 users = R14,000/month (now expensive)
Forces orgs to limit licenses (kills knowledge sharing)

❌ Not Built for Public Documentation

Guest access is clunky (per-space invites)
No clean, public-facing experience (looks like internal wiki)
Can’t create customer help centers easily

❌ Limited Customization

Branding limited to logo and colors
Can’t fully white-label
Stuck with Confluence look-and-feel

❌ Confluence Cloud = No SA Data Residency

Data stored in AWS (Sydney or US regions)
No South African data center option
POPIA compliance risk

❌ Page Hierarchy Gets Messy

Flat page structure (no true folders)
Navigation breaks with 500+ pages
Search becomes only way to find content

When Confluence Wins

Scenario 1: Developer Team Heavily Using Jira

Software development team (10-30 devs)
Tight integration with Jira workflows required
Documentation tied to Jira issues/epics
Tech debt tracking in Confluence + Jira

Scenario 2: Small Team Needing Collaboration

5-15 person startup
Collaborative editing is primary use case
Need inline comments and @mentions
Budget allows per-user pricing

Disqualify if:

They say “We need real-time collaborative editing like Google Docs”
Tiny team (5 users) where per-user pricing is cheap
Requires tight Jira integration

When DocsHub Wins

Scenario 1: Team Growing Beyond 50 Users

Started with Confluence when team was 10 people (R700/month)
Now 50+ people and costs are R3,500+/month
Confluence per-user pricing no longer makes sense

Scenario 2: Need Public-Facing Documentation

Tech company needs customer help center
Confluence guest access is clunky
DocsHub designed for public docs (no login required)

Scenario 3: South African Data Residency

Training provider, municipality, regulated industry
POPIA compliance requires SA servers
Confluence Cloud = AWS Sydney (not SA)

Scenario 4: Need Clean, Professional UX

Confluence looks like internal wiki (because it is)
DocsHub looks like professional documentation site (like docs.stripe.com)
Customer-facing use cases need professional appearance

Key Talking Points (Sales Script)

Discovery Questions:

“How many users do you have on Confluence today? What’s your monthly cost?” (Calculate scaling cost)
“Do you need external customers to access documentation?” (Confluence guest access pain)
“Are you concerned about POPIA compliance and data residency?” (Confluence = AWS Sydney)
“How important is Jira integration to your documentation?” (If critical, might not be good fit)

Positioning Statement:

“Confluence is great for internal wikis and teams already using Jira. But if you’re using it for documentation - especially customer-facing docs - you’re paying per-user for a tool that’s not designed for that. DocsHub is purpose-built for documentation: professional appearance, SA data residency, fixed pricing. Keep Confluence for internal wikis if you need Jira integration, but use DocsHub for serious documentation.”

Price Comparison (50 Users):

Confluence Standard:
- R70/user/month × 50 users = R3,500/month = R42,000/year

DocsHub Professional:
- R7,500/month flat = R90,000/year

SEEMS MORE EXPENSIVE - BUT:
- DocsHub includes migration, training, support (Confluence = DIY)
- DocsHub has no scaling cost (add 100 more users = R0 extra)
- DocsHub has SA data residency (POPIA compliance)
- DocsHub designed for public docs (Confluence isn't)

At 100 users: Confluence = R7,000/month vs DocsHub = R7,500/month (nearly equal)
At 200 users: Confluence = R14,000/month vs DocsHub = R7,500/month (DocsHub 47% cheaper)

Proof Points:

“CodeCraft Solutions switched from Confluence to DocsHub - saved R4,000/month and their customers love the new help center”
“Tech companies choose DocsHub when they realize Confluence per-user pricing doesn’t scale”

🥊 BATTLE CARD 3: vs Notion

Competitor Overview

What is Notion?

All-in-one workspace (wiki, docs, databases, project management)
Beautiful, modern UI (very popular with startups)
Viral growth (many teams adopted during COVID)
Positioned as “replace all your tools” solution

Pricing:

Plus: R135/user/month (small teams)
Business: R270/user/month (larger teams, advanced features)
Enterprise: Custom pricing
Typical SA startup (20 users): R2,700-R5,400/month

Market Position:

Market share: 10-20% of startups, modern teams
Strengths: Beautiful UX, flexible, all-in-one
Weaknesses: Per-user pricing, not built for documentation, slow with large content

Their Strengths (Be Honest)

✅ Beautiful, Modern UX

Clean, minimalist design (users love it)
Drag-and-drop interface
Easy to learn (low training required)
Mobile app is good

✅ Flexible/All-in-One

Wiki + Docs + Databases + Tasks in one tool
Reduces tool sprawl
Embedded content (videos, files, calendars)
Templates for various use cases

✅ Viral Adoption

Individual users adopt it personally, bring it to work
Free for personal use (low barrier to entry)
Community-created templates

✅ Collaboration

Real-time collaborative editing
Comments and @mentions
Version history

Their Weaknesses (Our Opportunity)

❌ Not Built for Documentation at Scale

Performance degrades with 1,000+ pages
Search is slow with large content volume
No true folder structure (everything is nested pages)
Not suitable for technical documentation (API docs, code samples)

❌ Per-User Pricing is Expensive

R135-R270/user/month adds up fast
Business tier required for many features
Limits adoption (who gets a license?)

❌ No South African Data Center

Data stored in US (AWS Virginia, Oregon)
POPIA compliance risk
Latency for SA users (300-400ms)

❌ Jack of All Trades, Master of None

Tries to be wiki + project management + CRM + database
Documentation features are basic
No advanced documentation features (versioning, approval workflows)

❌ Public Sharing is Limited

Can share pages publicly, but looks like Notion (can’t white-label)
No custom domain (notion.site subdomain only)
Not suitable for professional customer documentation

❌ Vendor Lock-In

Proprietary format (hard to export)
Can’t self-host
Dependent on Notion staying in business

When Notion Wins

Scenario 1: Small Startup (5-15 people)

Need all-in-one tool (wiki + tasks + CRM)
Budget-conscious (can’t afford multiple tools)
Team loves modern UX (design-forward culture)
Limited documentation volume (< 200 pages)

Scenario 2: Internal Use Only

No customer-facing documentation needs
Team collaboration is primary use case
Already using Notion for everything else (project management, meeting notes)

Disqualify if:

They say “We love Notion’s flexibility and use it for everything”
Tiny startup (5 users) where cost isn’t issue yet
No customer-facing documentation requirements

When DocsHub Wins

Scenario 1: Growing Beyond 30 Users

Started with Notion when team was 10 people (R1,350/month)
Now 50 people and costs are R6,750/month (Business tier)
Per-user pricing becoming unsustainable

Scenario 2: Need Professional Documentation

Tech company needs API documentation
Training provider needs SETA compliance documentation
Construction company needs ISO quality documentation
Notion’s flexibility = lack of structure

Scenario 3: Performance Issues at Scale

Have 500+ pages in Notion
Search is slow, pages take 5+ seconds to load
Need purpose-built documentation platform

Scenario 4: POPIA / Data Residency

SA organization requiring local data storage
Notion = US servers only
DocsHub = Hetzner Cape Town

Scenario 5: Customer-Facing Docs

Need custom domain (docs.yourcompany.co.za)
Need white-label branding
Notion’s public sharing looks unprofessional

Key Talking Points (Sales Script)

Discovery Questions:

“Do you use Notion for everything, or primarily for documentation?” (If everything, harder to displace)
“How many pages do you have in Notion? Are you experiencing performance issues?” (500+ pages = pain)
“Do customers or external partners access your documentation?” (Public sharing limitations)
“How much are you paying per month for Notion?” (Calculate scaling cost)

Positioning Statement:

“Notion is an amazing all-in-one tool for internal collaboration, and we’re not suggesting you replace it entirely. But if you’re using it for serious documentation - especially customer-facing or compliance documentation - you’re using a Swiss Army knife where you need a scalpel. DocsHub is purpose-built for documentation: fast search at scale, professional appearance, SA data residency, white-label branding. Keep using Notion for project management and internal notes, but move your documentation to DocsHub.”

Price Comparison (30 Users):

Notion Business:
- R270/user/month × 30 users = R8,100/month = R97,200/year

DocsHub Professional:
- R7,500/month flat = R90,000/year

DocsHub is R7,200/year CHEAPER + includes:
- Purpose-built for documentation (not trying to do everything)
- SA data residency (POPIA compliant)
- Custom domain + white-label
- Migration, training, support included

Proof Points:

“Tech startups love Notion until they hit 500+ pages and performance degrades - that’s when they switch to DocsHub”
“You can’t build a customer help center on Notion (notion.site subdomain looks unprofessional) - DocsHub gives you docs.yourcompany.co.za”

🥊 BATTLE CARD 4: vs Google Workspace (Docs + Drive)

Competitor Overview

What is Google Workspace?

Suite of productivity tools (Gmail, Drive, Docs, Sheets, Slides)
Ubiquitous (most organizations already use it)
Simple, collaborative, cloud-native
Low cost, easy adoption

Pricing:

Business Starter: R97/user/month (30GB storage)
Business Standard: R136/user/month (2TB storage)
Business Plus: R237/user/month (5TB storage, advanced security)
Typical SA SME (25 users): R2,425-R3,400/month

Market Position:

Market share: 50-60% of SMEs (email + file storage)
Strengths: Ubiquitous, easy to use, low cost
Weaknesses: Not built for documentation, search is poor, no structure

Their Strengths (Be Honest)

✅ Ubiquitous / Already Have It

Most organizations already pay for Google Workspace (Gmail)
Seen as “free” (already included)
No procurement process needed

✅ Easy to Use

Zero learning curve (everyone knows Google Docs)
Real-time collaborative editing (best in class)
Mobile apps work well

✅ Low Cost (Per-User)

R97-R136/user/month for email + storage + docs
Competitive vs Microsoft 365

✅ Search (Sometimes)

Google search technology (when it works)
Full-text search across all docs

Their Weaknesses (Our Opportunity)

❌ Not Built for Documentation

Google Drive is file storage, not documentation platform
No navigation structure (just nested folders)
No homepage or central starting point
Users rely on “Starred” or recent files

❌ Search Finds Everything (Information Overload)

Search for “budget” → 500 results across all Docs, Sheets, Slides
No relevance ranking for documentation
Can’t filter by document type or section

❌ Scattered Across Folders

Inconsistent folder naming (everyone organizes differently)
Broken links when files are moved
“I can’t find the document” despite having a search

❌ No Version Control

Google Docs has revision history, but no “approved version” concept
Can’t mark Document v2.0 as “official” and deprecate v1.0
Multiple copies of same doc (FINAL, FINAL_v2, ACTUAL_FINAL)

❌ No Public Documentation Experience

Can make Docs public, but:
- Still looks like Google Doc (not professional)
- No custom domain
- No navigation between related docs
Not suitable for customer help centers

❌ No South African Data Center

Google Cloud data stored in US or EU (not SA)
POPIA cross-border data transfer issues
Latency for SA users

❌ Permission Management is Nightmare

Per-document permissions (not site-wide)
“Can view” vs “Can comment” vs “Can edit” confusion
Constantly managing who has access to what

When Google Workspace Wins

Scenario 1: Tiny Organization (< 10 people)

Need email + file storage + basic docs
Limited documentation volume (< 50 docs)
Budget-constrained (R1,000/month max)
No compliance requirements

Scenario 2: Collaborative Document Editing is Primary Need

Need real-time co-editing (Google Docs best in class)
Documentation is secondary use case
Most work is creating documents, not finding them later

Disqualify if:

They say “Google Drive works fine for us, we don’t have any problems”
Micro business (3-5 people) where documentation isn’t critical
No budget (< R2,000/month)

When DocsHub Wins

Scenario 1: “I Can’t Find Anything” Problem

Organization with 200+ Google Docs
Employees complain: “Where is the policy for X?”
Search returns too many results (information overload)
Scattered across folders with inconsistent naming

Scenario 2: Need Professional Documentation Site

Training provider needs SETA audit-ready documentation
Tech company needs customer help center
Construction company needs ISO quality documentation
Google Docs public sharing looks unprofessional

Scenario 3: POPIA / Compliance

Training provider with learner records
Municipality with resident information
Construction company with client data
Google Workspace = US/EU servers (not SA)

Scenario 4: Version Control / Audit Trail

Need “approved version” concept
Need to prove “this was the policy in effect on date X”
Regulatory compliance (SETA, ISO, ECSA)
Google Docs revision history isn’t enough

Scenario 5: Growing Beyond 50 Users

Google Workspace per-user costs adding up
R136/user × 100 users = R13,600/month
DocsHub flat pricing more economical at scale

Key Talking Points (Sales Script)

Discovery Questions:

“How do your employees find documentation in Google Drive today? Do they use search, or browse folders?” (Listen for pain)
“Do you have multiple versions of the same document? How do you know which is official?” (Version control pain)
“Do external people (customers, auditors) need access to documentation?” (Public sharing limitations)
“Are you concerned about POPIA compliance with Google storing data outside SA?” (Compliance pain)

Positioning Statement:

“Google Workspace is excellent for email and collaborative document creation. We’re not suggesting you replace it. But Google Drive is file storage, not a documentation platform. Think of the difference between storing photos on Google Drive vs organizing them in Google Photos - same files, but Photos has structure, search, and sharing features. DocsHub is the ‘Google Photos’ for your documentation. You keep creating docs in Google Docs if you want, but publish them to DocsHub for centralized, searchable access.”

Integration Pitch:

“You can actually keep creating documents in Google Docs and sync them to DocsHub. Best of both worlds: familiar editing interface + professional documentation site.”

Price Comparison (50 Users):

Google Workspace Business Standard:
- R136/user/month × 50 users = R6,800/month = R81,600/year
- Includes: Email, Drive, Docs, Sheets, Slides (not just documentation)

DocsHub Professional:
- R7,500/month flat = R90,000/year
- R8,400 more expensive, BUT:
  - You're comparing apples to oranges (Google = email + storage + docs, DocsHub = pure documentation)
  - Real comparison: Google Drive file storage vs DocsHub documentation platform
  - Google Drive for file storage = included, DocsHub for documentation = R7,500/month

POSITIONING: "You're not replacing Google Workspace, you're adding a documentation layer on top."

Proof Points:

“Edge Training Solutions had 245 Google Drive folders before switching to DocsHub - now their team finds documents in 30 seconds instead of 30 minutes”
“Google Drive is for file storage. DocsHub is for knowledge sharing. Different use cases.”

🥊 BATTLE CARD 5: vs DIY / Custom Build

Competitor Overview

What is DIY / Custom Build?

Organization considers building their own documentation platform
Usually MkDocs, Jekyll, Hugo, or custom CMS
Common in tech companies with developer resources

Pricing:

Perceived cost: “Free” (open-source)
Actual cost: Developer time (40-80 hours initial + 4-8 hours/month ongoing)
At R800/hour developer rate = R32,000-R64,000 initial + R3,200-R6,400/month ongoing

Market Position:

Prevalence: 10-15% of tech companies consider this
Strengths: Full control, no vendor lock-in, customizable
Weaknesses: Developer time cost, maintenance burden, opportunity cost

Their Strengths (Be Honest)

✅ Full Control

Complete customization (any feature imaginable)
Own the code and infrastructure
No vendor dependence

✅ No Vendor Lock-In

Open-source tools (MkDocs, Hugo, Jekyll)
Can self-host anywhere
Data in standard formats (Markdown, Git)

✅ Technical Learning Experience

Developers learn new skills
Company gains infrastructure expertise
Pride in “we built this ourselves”

✅ Perceived Cost Savings

“It’s free” (ignoring developer time)
No monthly subscription fees

Their Weaknesses (Our Opportunity)

❌ Developer Time Opportunity Cost

Initial build: 40-80 hours (1-2 dev-weeks)
Ongoing maintenance: 4-8 hours/month
Cost: R32,000-R64,000 initial + R3,200-R6,400/month ongoing
Opportunity cost: Developers could be building product features that generate revenue

❌ Hidden Complexity

Basic MkDocs setup: 8 hours
Custom theme/branding: 12 hours
User authentication: 16 hours
Search optimization: 8 hours
Hosting, SSL, CDN, backups: 8 hours
Migration scripts: 16 hours
Total: 68 hours minimum

❌ Ongoing Maintenance Burden

MkDocs/plugin updates
Security patches
Server monitoring
Backup verification
User support (“How do I add a page?”)

❌ No Support When Things Break

Developer on vacation when site goes down?
SSL certificate expires at 5pm Friday?
Plugin breaks after update?
You’re on your own

❌ Slower Time to Value

6-8 weeks from start to launch (vs 2 weeks with DocsHub)
Documentation delayed = business value delayed

When DIY Wins

Scenario 1: Large Tech Company with Resources

200+ developers
Have dedicated docs team (3+ people)
Documentation is core competitive advantage (e.g., Stripe, AWS)
Already have mature DevOps infrastructure

Scenario 2: Unique Requirements

Need custom features that no vendor offers
Complex integration with proprietary systems
Budget for dedicated maintenance

Scenario 3: Open-Source Commitment

Company culture values open-source
Want to contribute back to community
Documentation platform is part of product offering

Disqualify if:

They say “Our CTO wants to build it ourselves as a learning exercise”
Small team (< 5 developers) where losing 2 dev-weeks is negligible
Documentation is not business-critical

When DocsHub Wins

Scenario 1: Developer Time is Expensive

Developer hourly rate: R800-R1,200/hour
Build cost: R32,000-R64,000 + R3,200-R6,400/month ongoing
DocsHub: R7,500/month (flat)
Break-even: 4-8 months (then DocsHub saves money every month)

Scenario 2: Want Docs Now (Not in 8 Weeks)

Business need is urgent (audit, client request, compliance deadline)
Can’t wait 6-8 weeks for custom build
DocsHub: Live in 2 weeks

Scenario 3: Small Dev Team (Opportunity Cost)

5-15 developers
Every dev-hour should go to product features (revenue-generating)
Documentation platform is not core business value

Scenario 4: No Maintenance Burden Desired

Don’t want to be “on call” for documentation platform
Need guaranteed uptime (99.9% SLA)
Want phone support when things break

Scenario 5: Future-Proofing

What if developer who built it leaves?
What if MkDocs project becomes abandoned?
DocsHub handles all updates, security, infrastructure

Key Talking Points (Sales Script)

Discovery Questions:

“How much is your developer time worth per hour?” (Calculate true cost)
“If you assign a developer to build this, what product features won’t get built?” (Opportunity cost)
“Who will maintain this platform long-term? What happens when they leave?” (Maintenance burden)
“How urgent is your documentation need? Can you wait 6-8 weeks?” (Time to value)

Positioning Statement:

“I love that you’re considering building this yourself - it shows you understand the value of good documentation. Here’s the reality: DocsHub is a custom MkDocs build. We’ve already invested 500+ developer hours building, testing, and maintaining it. You could rebuild what we’ve built in 40-80 hours, but then you own maintenance forever. Our question for you: Is a documentation platform your core competitive advantage? If yes, build it. If no, let us handle it while your developers focus on features that generate revenue. You’re not buying software - you’re buying back developer time.”

ROI Calculation (Real-Time):

Developer hourly rate: R800/hour
Initial build time: 60 hours = R48,000
Ongoing maintenance: 6 hours/month = R4,800/month

Year 1 Total Cost:
- Build: R48,000
- Maintenance: R4,800 × 12 = R57,600
- TOTAL: R105,600

DocsHub Year 1 Cost:
- R7,500 × 12 = R90,000
- Includes: Migration, training, support, updates, hosting, backups

Savings: R15,600 in Year 1
Savings Year 2+: R57,600/year (no build cost, only ongoing maintenance)

Proof Points:

“We’ve had 3 customers come to us after trying DIY - all said the same thing: ‘We underestimated maintenance burden’”
“DocsHub is MkDocs Material under the hood - you’re never locked in. Export and self-host anytime.”
“Your developer time is worth R800/hour. Ours is included in your R7,500/month subscription.”

📊 COMPETITIVE SUMMARY MATRIX

Competitor	Best For	Weaknesses	When DocsHub Wins
SharePoint	Large enterprises (5,000+ employees)	Terrible UX, complexity, per-user cost	SMEs fed up with complexity, public docs needed, POPIA compliance
Confluence	Developer teams using Jira	Per-user cost scaling, no SA data residency	50+ users, customer docs needed, POPIA compliance
Notion	Small startups (5-15 people)	Not built for docs at scale, per-user cost	30+ users, professional docs needed, performance issues
Google Workspace	Tiny orgs (< 10 people)	No structure, poor search, no versioning	50+ docs, “I can’t find anything” problem, compliance
DIY / Custom	Large tech with dedicated docs team	Developer time cost, maintenance burden	Small dev teams, need docs now, opportunity cost

🎯 SALES PROCESS INTEGRATION

During Discovery Call

Ask: “What do you currently use for documentation?”

If SharePoint:

“How do your users feel about SharePoint? Do they find documents easily?”
“Do you have a dedicated SharePoint administrator?”
Pull SharePoint battle card - focus on UX and complexity

If Confluence:

“How many users do you have? What’s your monthly cost?”
“Do external customers need access to documentation?”
Pull Confluence battle card - focus on scaling cost and public docs

If Notion:

“How many pages do you have in Notion? Any performance issues?”
“Do customers access your documentation?”
Pull Notion battle card - focus on scale and professionalism

If Google Drive:

“How do employees find documentation? Search or browse folders?”
“Do you have multiple versions of the same document?”
Pull Google Workspace battle card - focus on “I can’t find anything” problem

If considering DIY:

“How much is your developer time worth per hour?”
“Who will maintain this long-term?”
Pull DIY battle card - focus on opportunity cost

During Demo

Positioning vs Current Tool:

vs SharePoint: “Notice how fast search is? SharePoint takes 10-30 seconds. DocsHub is instant.”
vs Confluence: “See this custom domain and white-label? Confluence can’t do this professionally.”
vs Notion: “We have 1,000+ pages loaded. Notion would be slow by now.”
vs Google Drive: “This navigation structure - you can’t do this in Google Drive folders.”
vs DIY: “This is MkDocs Material, fully configured. Would take you 60+ hours to build this.”

In Proposal

Include Competitive Comparison Section:

## Why DocsHub vs [Current Tool]

[Competitor Name] Strengths:
- [Acknowledge 2-3 strengths]

DocsHub Advantages for Your Organization:
- [List 4-5 specific advantages based on their pain points]

Total Cost of Ownership (3-Year):
- [Current Tool]: R[X] (breakdown)
- DocsHub: R[Y] (breakdown)
- Savings: R[Z]

In Objection Handling

Objection: “We’re already paying for SharePoint, why should we pay for another tool?”

Response: “Great question. You’re right that SharePoint is included in Microsoft 365. Here’s the reality: Organizations tell us they keep paying for SharePoint, but their teams hate using it and waste hours searching for documents. The real cost isn’t the R7,500/month for DocsHub - it’s the R50,000+/month in lost productivity from poor search and complexity. Think of it this way: You already pay for Outlook, but you probably also use Slack or Teams for chat, right? Different tools for different jobs. SharePoint for intranets, DocsHub for documentation.”

(See Objection Handling Guide for full scripts)

📞 NEXT STEPS

For Sales Reps:

Memorize: “When DocsHub Wins” scenarios for each competitor
Practice: Positioning statements out loud (role-play with colleague)
Customize: Adapt talking points to prospect’s specific pain points
Update: Share new competitive intel back to this guide (continuous improvement)

For Sales Managers: 5. Train: Use battle cards in weekly sales training 6. Track: Which competitors do we win/lose against most? 7. Evolve: Update battle cards quarterly based on win/loss analysis 8. Share: Ensure all reps have latest competitive intelligence

Version History:

v1.0 (January 2025): Initial battle cards (SharePoint, Confluence, Notion, Google, DIY)

Related Resources:

Email Templates: /docs/products/docshub/sales/email-templates.md
Demo Script: /docs/products/docshub/sales/demo-script.md
Objection Handling: /docs/products/docshub/sales/objection-handling-guide.md
Pricing Guide: /docs/products/docshub/sales/pricing-investment-options.md
Use Cases: /docs/products/docshub/sales/use-cases-case-studies.md

Competitive intelligence is living document. Submit updates to info@isutech.co.za when you encounter new competitor strengths, weaknesses, or positioning opportunities.