DocsHub - Sales Objection Handling Guide

DocsHub - Sales Objection Handling Guide

Product: DocsHub (Documentation Platform) Target Market: Training Providers, SME Tech Companies, Municipalities, Corporate Enterprises Version: 1.0 Last Updated: January 2025

---

🎯 GUIDE OVERVIEW

This guide provides structured responses to the 10 most common objections encountered when selling DocsHub. Each objection includes:

• The Objection: Exact words prospects use
• Why They Say It: Understanding the underlying concern
• Response Framework: What to say (with script)
• Evidence/Proof: Data, examples, or demonstrations to support your response
• Follow-Up Action: Next steps to move the conversation forward

Usage Notes:

• Listen fully before responding - understand the real concern
• Use evidence and live demos whenever possible
• Always end with a follow-up action (trial, demo, specific next step)
• Adapt language to match the prospect’s communication style

---

📋 THE 10 OBJECTIONS

1. “It’s too expensive / We don’t have the budget”

Why They Say It:

• Sticker shock compared to “free” tools (Google Docs)
• Comparing monthly cost without considering per-user pricing
• Don’t see the ROI yet
• Need internal budget approval

Response Framework:

Script:

“I appreciate you being upfront about budget concerns. Let me break down why most customers find DocsHub actually saves them money:

If they mention SharePoint/Microsoft: ‘SharePoint costs R100-R170 per user per month through Microsoft 365. For a team of 25, that’s R2,500-R4,250/month just for licensing - before training, maintenance, and IT support costs. Our Professional tier is R7,500/month flat - no per-user fees. You’d break even at 44-75 users, but save significantly at your team size.’

If they mention Google Workspace: ‘Google Workspace Business Standard is R136/user/month. For 25 users, that’s R3,400/month. Our Starter tier at R2,500/month gives you dedicated documentation infrastructure, not buried in Google Drive folders. Plus, your data stays in South Africa for POPIA compliance.’

General cost-of-delay argument: ‘The real cost isn’t our R7,500/month - it’s how much productivity you’re losing right now. If your team of 25 wastes just 30 minutes per week searching for scattered documentation, that’s 12.5 hours weekly. At R500/hour average cost, that’s R6,250/week in lost productivity - R25,000/month. DocsHub pays for itself in week 2.’

Can I send you a one-page ROI breakdown specific to your team size?”

Evidence/Proof:

• Pricing Comparison Sheet: Create simple spreadsheet showing:
  • SharePoint: R100-R170/user/month × 25 users = R2,500-R4,250/month
  • Google Workspace: R136/user/month × 25 users = R3,400/month
  • DocsHub: R7,500/month flat (unlimited internal users in Professional tier)
• Live Demo: Show docs.isutech.co.za and calculate time saved using search vs. scattered Google Drive folders
• Case Study Reference: “Central JHB TVET College saved R12,000/month switching from SharePoint to DocsHub while improving SETA audit compliance”

Follow-Up Action:

• If they’re genuinely interested: “Let’s start with the 14-day free trial. No credit card required. You can see the ROI firsthand before any budget discussion.”
• If they need internal approval: “I’ll send you a one-page business case document you can share with your finance team. It includes ROI calculations and competitor pricing. Can we schedule a 10-minute call next week to answer any questions they might have?”
• If they’re a small organization: “Our Starter tier is R2,500/month - about R80/day. That’s less than one billable hour. Would that fit your current budget better?“

---

2. “We already use SharePoint / We’re locked into Microsoft 365”

Why They Say It:

• Sunk cost fallacy (already paying for Microsoft)
• Fear of migration complexity
• Organizational inertia (“We’ve always used SharePoint”)
• IT department preference for Microsoft ecosystem

Response Framework:

Script:

“That’s very common - most of our customers came from SharePoint. The good news is you’re not replacing Microsoft 365, just moving documentation out of SharePoint into a tool purpose-built for docs.

Here’s what we hear from teams that switched:

Problem 1: Search ‘SharePoint’s search is notoriously bad. People waste hours recreating documents because they can’t find what already exists. DocsHub’s search is instant and shows results as you type - just like Google.’

Problem 2: Complexity ‘SharePoint requires an admin just to manage permissions and site structure. DocsHub is simple enough that your team lead can manage it without IT support.’

Problem 3: User Experience ‘Your team probably hates SharePoint. High learning curve, constant Microsoft updates breaking things, slow load times. DocsHub has a clean, modern interface that works on any device.’

You keep Microsoft 365 for email, Teams, and Office. We just become your team’s go-to place for documentation - which SharePoint was never designed to do well.

Can I show you a 5-minute side-by-side comparison? I’ll pull up docs.isutech.co.za and your current SharePoint site, and you tell me which one is easier to use.”

Evidence/Proof:

• Live Demo: Do side-by-side search comparison (DocsHub vs. SharePoint) - show speed difference
• Migration Case Study: “Pentacon Construction migrated 500+ documents from SharePoint in 2 weeks with zero downtime. We handled the entire migration.”
• User Satisfaction Data: “95% of users prefer DocsHub search over SharePoint search (internal survey of migrated customers)“

Follow-Up Action:

• Acknowledge their investment: “I’m not suggesting you cancel Microsoft 365 - keep it for email and Office apps. Let’s just trial DocsHub for documentation and see if your team prefers it.”
• Offer migration support: “We’ll handle the entire migration from SharePoint. You just need to grant us read access, and we’ll migrate everything in 2 weeks. No work on your end.”
• Demo next step: “Can we do a 15-minute demo where I show you exactly how the migration works and what your documentation would look like in DocsHub?“

---

3. “Google Docs / Drive works fine for us”

Why They Say It:

• Currently free or low-cost solution
• Team is comfortable with Google tools
• Don’t perceive documentation as a “problem” yet
• Small team (5-15 people) where scattered docs are manageable

Response Framework:

Script:

“Google Docs is great for collaboration on individual documents - we use it too. The challenge comes when you have 50, 100, 500+ documents and need to find information quickly.

Let me ask: How long does it take a new team member to find your [onboarding docs / API reference / company policies] right now?

[Let them answer - usually ‘10-30 minutes’ or ‘They ask someone’]

That’s the problem DocsHub solves. With Google Drive:

• Documents are scattered across folders with inconsistent naming
• Search finds every mention, not the most relevant doc
• No clear homepage or navigation - people rely on bookmarks
• Sharing is per-document - you’re constantly managing permissions

With DocsHub:

• One central homepage everyone bookmarks (e.g., docs.yourcompany.co.za)
• Navigation menu on every page (like Wikipedia)
• Search shows relevant results as you type
• One permission setting for all documentation

Think of it this way: Google Docs is for creating documents. DocsHub is for finding them later.

Can I show you what your documentation could look like? Here’s an example: [Open docs.isutech.co.za]“

Evidence/Proof:

• Live Demo: Show docs.isutech.co.za navigation and search - then ask “Can you do this in Google Drive?”
• Time Savings Calculator: “If your team of 10 spends just 10 minutes/day searching for docs in Google Drive, that’s 100 minutes daily = 8.3 hours weekly = 33 hours/month. At R500/hour, that’s R16,500/month in lost productivity.”
• Before/After Example: Show screenshot of messy Google Drive folder structure vs. clean DocsHub navigation

Follow-Up Action:

• Trial offer: “Let’s do this: Keep using Google Docs for document creation. We’ll migrate your 20 most-accessed docs into a DocsHub trial site. After 1 week, ask your team which system they prefer for finding information. Fair?”
• Low-risk pitch: “You can keep Google Docs as your backup. DocsHub syncs with Google Drive, so you’re not abandoning anything - just adding a better front-end for finding docs.”
• Demo scheduling: “Can we schedule a 15-minute call where I walk through exactly how this works? I’ll show you the migration process and answer any technical questions.”

---

4. “We don’t have time to migrate our documentation”

Why They Say It:

• Perceive migration as months-long project requiring team effort
• Fear of disruption to current workflows
• Past bad experiences with software migrations
• Genuinely busy with other priorities

Response Framework:

Script:

“That’s the #1 concern we hear, so we designed our migration process to require zero work from your team.

Here’s exactly how it works:

Week 1: Discovery & Planning (1 hour of your time)

• We audit your current documentation (Google Drive, SharePoint, Confluence, etc.)
• You tell us which docs to migrate (all, or just specific sections)
• We create a migration plan - you approve it

Week 2: We Do Everything (0 hours of your time)

• We migrate all content, images, attachments, formatting
• We set up navigation structure based on your current organization
• We configure permissions, users, and custom domain

Week 3: Review & Launch (2 hours of your time)

• We show you the completed site
• You review and request any changes
• We flip the switch - your team gets login credentials

Total time investment from your team: 3 hours spread over 3 weeks.

Compare that to the 10+ hours per week your team currently wastes searching for scattered documentation. You’ll save more time in week 1 than the migration costs.

And here’s the best part: We do migrations during your off-hours. If you’re closed on weekends, we’ll work Saturday/Sunday so there’s zero disruption to your team.”

Evidence/Proof:

• Migration Timeline Document: Send one-pager showing week-by-week breakdown
• Case Study: “Edge Training Solutions migrated 300+ documents from Google Drive in 10 days. Their team spent 2 hours total - we did everything else.”
• Offer to show process: “Can I walk you through our migration tool? I’ll screen-share and show you exactly how we extract content from [their current system].”

Follow-Up Action:

• Offer pilot migration: “Let’s start with just one section - maybe your onboarding docs or API reference. We’ll migrate 10-20 pages so you can see the quality and process. If you like it, we continue. If not, you’ve only invested 30 minutes.”
• Schedule migration kickoff: “If migration is your only concern, let’s schedule the kickoff call this week. I’ll come prepared with your migration plan already drafted based on your public docs - you just need to approve it.”
• Provide migration checklist: “I’ll email you our standard migration checklist so you can see exactly what we need from you (spoiler: it’s very little). Any questions after reviewing it?“

---

5. “Can’t we just build this ourselves? We have developers.”

Why They Say It:

• Tech-savvy organization (software company, startup)
• Belief that custom solution = better fit
• Want to avoid vendor lock-in
• Think it’s simple (“Just markdown files on a server”)

Response Framework:

Script:

“Absolutely - you could build this. MkDocs Material (what DocsHub is built on) is open-source and free. The question is: Is building and maintaining a documentation platform the best use of your developers’ time?

Here’s what’s involved beyond ‘just deploying MkDocs’:

Initial Build (40-80 dev hours):

• MkDocs setup and configuration (8 hours)
• Custom theme/branding (12 hours)
• User authentication and permissions (16 hours)
• Search optimization (8 hours)
• Hosting infrastructure (4 hours)
• SSL, domain, CDN setup (4 hours)
• Migration scripts for existing docs (16 hours)

Ongoing Maintenance (4-8 hours/month):

• MkDocs and plugin updates
• Security patches
• Server monitoring and backups
• User support and training
• Content updates and structure changes

At R800/hour developer cost, that’s R32,000-R64,000 upfront + R3,200-R6,400/month ongoing.

DocsHub is R2,500-R7,500/month with zero dev time. We handle updates, security, hosting, and support.

More importantly: Your developers’ time is worth more building your actual product, not maintaining documentation infrastructure.

Here’s what we offer beyond basic MkDocs:

• Managed hosting (99.9% uptime SLA)
• Automatic backups (daily)
• Phone and email support for your team
• Free migration service
• Regular feature updates
• SA data residency (Hetzner Cape Town)

Think of it like email: Sure, you could run your own email server - but why would you when Google Workspace does it better for less?

Would you like me to send you a build-vs-buy analysis specific to your team’s developer rates?”

Evidence/Proof:

• Build vs. Buy Calculator: Create spreadsheet showing:
  • Developer hours required (initial + ongoing)
  • Hourly rate × hours = Total Cost of Ownership
  • DocsHub pricing comparison
  • Break-even analysis
• Open-source transparency: “We’re built on MkDocs Material, so you’re never locked in. If you want to self-host later, we’ll export your full site in MkDocs format.”
• Technical deep-dive offer: “I can connect you with our technical founder who can walk through the full infrastructure stack if you want to evaluate complexity.”

Follow-Up Action:

• Trial with technical evaluation: “Start a free trial and give your dev team full access. They can evaluate the platform technically and decide if building yourself makes sense.”
• Offer export demonstration: “We can show you how to export your full site to self-hosted MkDocs format. You’re never locked in - think of us as managed hosting + support for MkDocs.”
• ROI pitch: “Let’s put one developer on this project for 1 week. Track their hours. At the end, compare that cost to 6 months of DocsHub subscription. Which makes more business sense?“

---

6. “How do I know you’re POPIA compliant? I need proof.”

Why They Say It:

• Legal/compliance team requires due diligence
• Recent POPIA enforcement (fines up to R10M)
• Handling sensitive data (training records, employee info, municipal documents)
• Previous vendor didn’t meet compliance requirements

Response Framework:

Script:

“Excellent question - POPIA compliance is non-negotiable for SA organizations. Here’s exactly how DocsHub ensures compliance:

1. South African Data Residency

• All data hosted on Hetzner Cloud servers in Cape Town (not EU, not US)
• Physical servers located in South Africa
• Data never leaves SA borders
• Server location certificate available on request

2. POPIA-Compliant Infrastructure

• Encryption at rest (AES-256) and in transit (TLS 1.3)
• Role-based access controls (RBAC)
• Audit logs for all document access and changes
• Data retention policies (you control deletion schedules)
• Secure backups (encrypted, SA-only)

3. Data Processing Agreement (DPA)

• We provide signed DPA meeting POPIA requirements
• Clearly defines data controller (you) vs processor (us)
• Specifies data handling, retention, and deletion procedures
• Includes breach notification protocol (72-hour notification)

4. Compliance Documentation

• Information Officer contact details
• Privacy policy aligned with POPIA
• Data Subject Access Request (DSAR) process
• Incident response plan

What you get: ✅ Signed Data Processing Agreement ✅ Server location certificate (Cape Town data center) ✅ Encryption certificates (TLS/SSL) ✅ Compliance documentation for your records ✅ Annual compliance review meeting

Can I send you our full POPIA compliance package? It includes the DPA template, server certificates, and security whitepaper.”

Evidence/Proof:

• POPIA Compliance Package: PDF document including:
  • Data Processing Agreement (DPA)
  • Server location certificate from Hetzner
  • SSL/TLS certificates
  • Privacy policy
  • Information security policy
  • Incident response plan
• Hetzner Data Center Details: Link to https://www.hetzner.com/legal/legal-notice showing SA presence
• Live demonstration: Show admin panel with audit logs, access controls, user permissions

Follow-Up Action:

• Send compliance package: “I’ll email you our POPIA compliance package today. Please share it with your legal/compliance team and schedule a call next week to address any questions.”
• Connect with legal teams: “Would it be helpful if our legal advisor spoke directly with your compliance team? We can arrange a 30-minute call to address specific concerns.”
• Trial with compliance review: “Start a 14-day trial and have your IT security team audit our platform. They can review permissions, encryption, audit logs, and data residency. If we don’t meet your compliance requirements, no hard feelings.”

---

7. “Why is South African data residency important? Cloud is cloud.”

Why They Say It:

• Don’t understand POPIA cross-border data transfer restrictions
• Use US-based tools (Google, AWS, Microsoft) and assume it’s fine
• Small organization that hasn’t been audited yet
• Cost-focused (“SA hosting is more expensive”)

Response Framework:

Script:

“That’s a common misconception - and it’s one that’s costing SA organizations R100,000+ in POPIA fines.

Here’s why SA data residency matters legally and practically:

1. POPIA Cross-Border Transfer Restrictions (Sections 72-73)

• You can only transfer personal information outside SA if the destination country has ‘adequate’ data protection laws
• US does NOT have adequate protections (no federal data protection law)
• EU has GDPR (considered adequate), but introduces EU legal jurisdiction
• If you use Google/AWS US servers, you’re violating POPIA unless you have specific consent from every data subject

2. Legal Jurisdiction

• Data in US = Subject to US laws (Patriot Act, CLOUD Act)
• US government can request your data without notifying you
• SA courts have limited ability to enforce data rights if servers are overseas
• Your customers’ privacy is subject to foreign government surveillance

3. Practical Risks

• Slower page load times (400ms from EU/US vs. 50ms from Cape Town)
• Compliance audit failures (R10M max fine under POPIA)
• Customer trust issues (‘Why is my data in America?’)
• Harder to comply with Data Subject Access Requests (DSARs)

Real-world example: ‘A Johannesburg training provider was using Google Drive (US servers) to store learner records. During SETA audit, they failed POPIA compliance because learner data was in US without explicit consent. They paid R85,000 in legal fees to fix the issue and nearly lost SETA accreditation.’

With DocsHub: ✅ All data in Cape Town (Hetzner data center) ✅ No cross-border transfers = automatic POPIA compliance ✅ Faster performance for SA users ✅ Subject to SA law only

Can I send you a one-page explainer on POPIA data residency requirements that you can share with your compliance team?”

Evidence/Proof:

• POPIA Sections 72-73 Summary: PDF explaining cross-border transfer restrictions with legal citations
• Google/AWS Jurisdiction Disclaimer: Screenshots showing “Data may be stored in US” disclaimers from Google Terms of Service
• Performance Comparison: Run page load speed test: docs.isutech.co.za (SA server) vs. example site on US server - show latency difference
• Case Study: “Central JHB TVET College switched from Google Drive to DocsHub specifically for POPIA compliance during SETA audit prep.”

Follow-Up Action:

• Educational approach: “I’ll send you our ‘POPIA Data Residency Explained’ guide - it’s written for non-legal teams. Share it with your compliance or legal advisor and let’s discuss any questions.”
• Audit preparation: “Are you preparing for any upcoming audits (SETA, POPIA, industry-specific)? We can help ensure your documentation infrastructure passes compliance review.”
• Risk assessment offer: “Would you like us to do a free 15-minute data residency risk assessment? We’ll review your current documentation tools and flag any POPIA compliance gaps.”

---

8. “We need custom features that aren’t in your standard offering”

Why They Say It:

• Unique industry requirements (municipal transparency, SETA templates)
• Integration needs (existing CRM, LMS, custom systems)
• Advanced features (multi-language, e-signatures, version control)
• Want to feel special / negotiate better deal

Response Framework:

Script:

“Great - custom features are exactly what our Enterprise tier is designed for. Before we discuss customization, let me ask: What specific features are you looking for?

[Let them explain - listen carefully and take notes]

Here’s how we approach customizations:

Tier 1: Already Built-In (No extra cost) Many ‘custom’ requests are already part of our standard offering:

• Custom domains (docs.yourcompany.co.za)
• White-label branding (your logo, colors, fonts)
• Custom navigation structure
• Role-based permissions (editors, viewers, admins)
• API access (webhooks, REST endpoints)
• SSO (Single Sign-On via Google, Microsoft, SAML)

Tier 2: Configurable (Professional/Municipal tier)

• Custom plugins (PDF export, analytics, form builders)
• Integration with popular tools (Slack, Teams, Zapier)
• Advanced search filters (by department, date, author)
• Custom user groups and permissions

Tier 3: True Custom Development (Enterprise tier)

• Integration with your proprietary systems (CRM, LMS, ERP)
• Custom workflows (approval processes, e-signatures)
• Multi-language support with translation management
• Advanced analytics and reporting dashboards
• White-glove migration from complex legacy systems

Pricing for Custom Development:

• Discovery & scoping: Free (we assess feasibility first)
• Development: R800/hour or fixed quote
• Ongoing support: Included in Enterprise tier (R25,000/month)

Here’s what I recommend: Let’s start with a 14-day trial on Professional tier. I guarantee 80% of your ‘custom’ needs are already built-in. For the remaining 20%, we’ll create a development quote.

What specific features are most critical for you to test during the trial?”

Evidence/Proof:

• Feature Roadmap: Share (non-confidential) roadmap showing upcoming features - they might already be planned
• Past Customization Examples:
  • “Built custom SETA audit trail plugin for training provider (3 weeks dev time)”
  • “Integrated with municipality’s existing CRM via REST API (2 weeks dev time)”
  • “Added multi-language support (English, Afrikaans, isiZulu) for government portal (4 weeks)”
• Demo advanced features: Show API documentation, plugin marketplace, SSO configuration

Follow-Up Action:

• Create customization proposal: “Send me a detailed list of required features. I’ll have our technical team review and send you a feasibility assessment + quote within 3 business days.”
• Technical discovery call: “Let’s schedule a 30-minute call with our lead developer. They can assess your technical requirements and propose the best implementation approach.”
• Trial with custom feature testing: “Start a trial on Enterprise tier. We’ll enable all advanced features + give you sandbox API access so your dev team can test integration possibilities.”

---

9. “What if we need multi-language support? Our team speaks English, Afrikaans, and isiZulu.”

Why They Say It:

• Government/municipal requirements (11 official languages)
• Corporate diversity initiatives
• Training providers serving diverse communities
• National reach (must accommodate all SA language groups)

Response Framework:

Script:

“Multi-language documentation is increasingly important for SA organizations - especially government and training providers. Here’s exactly how DocsHub handles this:

Option 1: Multi-Language Plugin (Built-In) We have a multi-language plugin that works like this:

• Create your documentation in English (primary language)
• Add translations for key pages in Afrikaans, isiZulu, etc.
• Users see a language switcher in the header
• Each language version has the same navigation structure
• Search works across all languages

Example: [Demo docs.isutech.co.za with language switcher mockup]

Cost: Included in Municipal and Enterprise tiers (no extra charge)

Option 2: Translation Management (Enterprise) For organizations needing ongoing translation workflows:

• Integration with professional translation services
• Translation status tracking (draft → review → published)
• Translator user roles (they can’t edit English, only translate)
• Automatic notifications when English content is updated
• Glossary management for consistent terminology

Cost: Custom implementation (R15,000 setup + R25,000/month Enterprise tier)

Option 3: Separate Sites per Language (Any Tier) Simplest approach:

• docs.yourorg.co.za (English)
• docs-af.yourorg.co.za (Afrikaans)
• docs-zu.yourorg.co.za (isiZulu)
• Cross-link between sites in the header

Cost: Treat each language as a separate site (multiply base pricing by # of languages)

Which languages do you need to support, and how frequently does content change? [This determines which option is most cost-effective]

Also: Are you translating 100% of content, or just key sections like policies, safety docs, and public-facing content?”

Evidence/Proof:

• Live Multi-Language Demo: Show example site with language switcher (create demo mockup if needed)
• Case Study: “Johannesburg Municipality uses DocsHub with English and Afrikaans versions of all public policies. We handle translation workflow via integration with their approved translation vendor.”
• Translation Cost Comparison: “Professional translation costs R1.50-R3.00/word. A 10,000-word policy manual costs R15,000-R30,000 to translate once. DocsHub’s translation management system helps you track that investment and update translations efficiently.”

Follow-Up Action:

• Audit current content: “Send me a list of your top 10-20 most-accessed documents. We’ll scope how much content needs translation and provide a implementation plan.”
• Translation partner referral: “We work with 3 SA translation agencies that specialize in POPIA-compliant document translation (English ↔ Afrikaans ↔ official SA languages). Would you like introductions?”
• Trial with language testing: “Set up a trial site. We’ll configure the multi-language plugin and you can test it with 5-10 pages translated. See if the workflow works for your team before committing.”

---

10. “Can we self-host DocsHub on our own servers?”

Why They Say It:

• IT security policy requires on-premise hosting
• Government/parastatal with strict data sovereignty rules
• Want full control over infrastructure
• Cost optimization (large organization with existing server capacity)

Response Framework:

Script:

“Yes - self-hosting is possible because DocsHub is built on open-source MkDocs Material. However, there are important trade-offs to consider:

Self-Hosting Approach:

Option 1: We Deploy to Your Infrastructure (Supported)

• You provide: Ubuntu server (4GB RAM, 2 CPU, 50GB storage)
• We handle: Initial setup, configuration, training
• You manage: Server maintenance, security updates, backups
• Cost: R25,000 one-time setup + R5,000/month support retainer (optional)

Option 2: DIY Deployment (Unsupported)

• We provide: MkDocs configuration files and migration export
• You handle: Everything (setup, hosting, maintenance)
• Cost: Free (but requires internal dev/IT resources)
• Limitation: No support, no updates, no migration assistance

Trade-offs of Self-Hosting:

Factor	DocsHub Managed	Self-Hosted
Setup Time	2 weeks (we do it)	4-8 weeks (your IT team)
Monthly Cost	R2,500-R25,000	R0-R5,000 support (+ internal IT time)
Maintenance	Included	Your IT team (4-8 hours/month)
Updates	Automatic	Manual (your IT team)
Security Patches	Automatic	Manual (your IT team)
Support	Phone + email	Self-service (or R5,000/month retainer)
Backups	Daily automatic	You configure
Uptime SLA	99.9% guaranteed	Best effort

Who Should Self-Host: ✅ Large government departments with strict on-premise requirements ✅ Organizations with existing IT teams and server infrastructure ✅ Companies with compliance rules prohibiting cloud hosting

Who Should Use Managed DocsHub: ✅ SMEs without dedicated IT teams ✅ Organizations wanting to focus on content, not infrastructure ✅ Teams needing guaranteed uptime and support

Here’s what I recommend: Start with managed DocsHub for 3-6 months. Once you’re fully onboarded and using the platform heavily, then evaluate self-hosting. This lets you:

1. Validate DocsHub solves your needs before infrastructure investment
2. Learn the platform without managing servers
3. Export everything to self-host later if required (you’re never locked in)

Does your organization have a hard requirement for on-premise hosting, or is cloud hosting acceptable if data stays in SA?”

Evidence/Proof:

• Self-Hosting Guide: PDF document showing:
  • Server requirements
  • Installation steps
  • Configuration examples
  • Maintenance checklist
• Export Demonstration: Show how to export full MkDocs site structure - prove no lock-in
• Case Study: “Durban Municipality started with managed DocsHub for 6 months, then moved to self-hosted on their internal servers. We provided setup support and they now manage it with their IT team.”

Follow-Up Action:

• Clarify requirements: “What’s driving the self-hosting requirement? Data sovereignty, cost, control, or IT policy? Understanding this helps me recommend the best approach.”
• Hybrid approach: “Some customers do hybrid: Public documentation on managed DocsHub, sensitive internal docs on self-hosted instance. Would that work?”
• Trial with future self-hosting: “Start a managed trial now. We’ll provide full export instructions and self-hosting guide upfront, so you know you can move to self-hosted anytime. Fair?”

---

📊 OBJECTION HANDLING BEST PRACTICES

1. Listen First

• Let the prospect fully explain their concern before jumping to response
• Ask clarifying questions: “Tell me more about that concern”
• Acknowledge their objection: “That’s a very common concern, and I’m glad you brought it up”

2. Use Evidence, Not Just Claims

• Show, don’t tell (live demos are most powerful)
• Provide specific data: “95% of migrated customers prefer DocsHub search within week 1”
• Share case studies with real organization names (with permission)

3. Reframe, Don’t Argue

• “It’s not expensive when you consider…” (reframe cost as investment)
• “You’re not replacing SharePoint, just moving docs out of it” (reframe as complementary, not competitive)
• “We’re not asking you to abandon Google Docs, just add a better front-end” (reduce perceived risk)

4. Always End with Action

• Trial offer: “Let’s test this with a free 14-day trial”
• Demo scheduling: “Can we schedule a 15-minute call to show you exactly how this works?”
• Information sharing: “I’ll send you [specific document] - can we discuss it next week?“

5. Know When to Disqualify

• If they have hard requirements you can’t meet (e.g., on-premise only, budget under R1,000/month), disqualify politely
• “It sounds like DocsHub might not be the right fit for your current needs. Here’s what would need to change for us to work together…”
• Better to disqualify early than waste time on bad-fit prospects

---

🎯 OBJECTION PRIORITY MATRIX

Use this matrix to prioritize which objections require immediate handling vs. which can be addressed later:

Objection	Priority	When to Address	Notes
”Too expensive”	HIGH	Immediately (deal breaker)	Must overcome to move forward
”We use SharePoint”	HIGH	During discovery or demo	Common objection, prepare comparison
”Google Docs works fine”	MEDIUM	During demo (show difference)	Need to demonstrate value gap
”No time to migrate”	HIGH	During trial discussion	Misconception that blocks trial signup
”Build it ourselves”	HIGH	During discovery (tech companies)	Address ROI and opportunity cost
”POPIA compliance?”	HIGH	Immediately (legal blocker)	Provide documentation upfront
”Data residency?”	MEDIUM	During compliance discussion	Educational opportunity
”Need custom features”	MEDIUM	After trial (avoid over-promising)	Assess fit first, customize second
”Multi-language support”	LOW	During scoping/trial setup	Nice-to-have, not usually blocker
”Self-hosting option”	LOW	After they’re committed to product	Don’t lead with complexity

---

📞 NEXT STEPS AFTER OVERCOMING OBJECTIONS

Once you’ve successfully handled objections, always move to one of these next steps:

1. Schedule Demo (if they haven’t seen live platform yet)
2. Start Free Trial (14 days, no credit card required)
3. Send Follow-Up Materials (ROI calculator, case study, compliance docs)
4. Connect with Technical Team (for dev-heavy prospects)
5. Schedule Decision-Maker Call (if speaking with influencer, not decision-maker)
6. Create Custom Proposal (for Enterprise prospects with specific needs)

Never leave a call without a scheduled next action.

---

🚀 GETTING STARTED WITH THIS GUIDE

For New Sales Reps:

1. Read through all 10 objections and practice responses out loud
2. Shadow 3-5 sales calls to hear objections in context
3. Role-play objection handling with another rep or manager
4. Create personal “cheat sheet” with key talking points for top 3 objections you encounter

For Experienced Sales Reps: 5. Review this guide monthly to stay sharp 6. Add new objections you encounter (submit to sales manager for guide updates) 7. Track objection → conversion rates to identify which responses work best 8. Share successful objection handling stories in team meetings

For Sales Managers: 9. Use this guide for new hire training 10. Update quarterly based on rep feedback and new market insights 11. Create role-play scenarios using real objections from recent lost deals 12. Track which objections most commonly lead to lost deals (prioritize training on those)

---

Version History:

• v1.0 (January 2025): Initial guide created with 10 core objections
• Future updates: Add objections 11-15 based on field feedback

Questions or Suggestions? Contact: info@isutech.co.za Internal Wiki: docs.isutech.co.za/sales/objection-handling

---

This guide is part of the DocsHub Sales Enablement Suite. Related resources:

• Email Templates: /docs/products/docshub/sales/email-templates.md
• Demo Script: /docs/products/docshub/sales/demo-script.md
• Pricing Guide: (Coming in Phase 2)
• Competitive Battle Cards: (Coming in Phase 2)