NSTF - Objection Handling Guide

NSTF Objection Handling Guide

How to Use This Guide

Purpose: Equip team with confident, evidence-based responses to NSTF concerns

Format: Objection → Response → Proof Point

Best Practice: Listen first, acknowledge concern, then respond (don’t be defensive)

Budget & Pricing Objections

”This is too expensive for a nonprofit organization”

Response: “I understand budget constraints are real for NSTF. Let’s look at this differently - what’s the cost of the current manual process? If your awards team spends 40 hours managing nominations, adjudication coordination, and data entry at an average cost of R500/hour, that’s R20K per awards cycle just in staff time. Our platform eliminates 60-70% of that, saving R12K-R14K annually. Over 3 years, the ROI is 200-300%.”

“We also offer:”

Pilot option (R150K-R250K to prove concept)
Phased payments (spread over 12-24 months)
Outcomes-based pricing (pay more only if we deliver results)
Technology Alliance model (ecosystem referrals offset your investment)

Proof Point:

MGSLG case study: R400K investment, saved R180K annually in admin costs (2.2-year payback)
SACE: Similar nonprofit, found budget through efficiency gains in other areas

”We can’t commit to multi-year contracts”

Response: “Totally reasonable. Let’s start with the awards pilot (8-week delivery, R150K-R250K). No long-term commitment. If it works well for your Nov 2025 cycle, we discuss expanding. If not, you have a functional awards platform with no further obligation.”

Proof Point:

“90% of our pilot clients expand to comprehensive platforms within 12 months because the value is proven"

"We need board approval and that takes months”

Response: “We understand governance processes. Here’s how we can help:”

Provide board-ready materials (one-pager, ROI analysis, risk mitigation summary)
Present at board meeting if helpful
Lock in pricing now while board deliberates (3-month price guarantee)
Structure contract with board approval contingency clause

“What’s your next board meeting date? Let’s work backward from there.”

Proof Point:

SACE experience: Board approval took 8 weeks, we supported with presentation materials and Q&A session

Change Management & Adoption Objections

”Our nominators and adjudicators aren’t tech-savvy”

Response: “Great point - that’s exactly why we designed this to be simpler than email. Consider: currently, nominators have to navigate email attachments, Word documents, file naming conventions. Our platform is point-and-click with drag-and-drop file uploads - like online shopping, which everyone does.”

“For adjudicators:”

Mobile-friendly (review on tablet or phone)
Video tutorials (3-5 minutes)
Support helpline during adjudication period
We train NSTF team to support users

“In similar programs, 95%+ users complete submissions without technical support.”

Proof Point:

MGSLG: Worked with rural schools (low tech capacity) - 98% successful submission rate after video tutorial
User testing shows our interface is easier than Gmail for most tasks

”We’ve tried technology projects before and they failed”

Response: “I’d like to understand what went wrong - was it the technology, the implementation, or the vendor?”

[Listen to their story]

“Here’s how we’re different:”

Agile delivery: You see working software every 2 weeks, provide feedback, adjust course
User-centered design: We involve nominators, adjudicators, administrators in design (not just build what IT wants)
Training & change management: Included, not an afterthought
Phased approach: Start with pilot (low risk), expand based on success
Local team: We’re in South Africa, available when you need us (not offshore support)

Proof Point:

Reference case study where previous vendor failed, we recovered project and delivered successfully

Everlytic & Current Systems Objections

”We already use Everlytic - why do we need this?”

Response: “Everlytic is great for what it does - email campaigns and basic forms. We integrate with and enhance Everlytic, not replace it. Here’s what Everlytic can’t do:”

Multi-stage workflows (nomination → adjudication → shortlisting → winner selection)
File management (organizing 100+ documents per awards cycle)
Adjudicator collaboration tools (scoring rubrics, panel discussions)
Advanced analytics (diversity metrics, trend analysis)
Integrated database (nominees, winners, historical archive)

“Think of it this way: Everlytic handles communications, our platform handles the awards lifecycle. They work together.”

Proof Point:

Show integration diagram: NSTF platform triggers Everlytic emails automatically
NSTF official confirmed “Everlytic can only do so much” - we fill the gaps

”Can’t we just build this in-house or use Excel?”

Response: Excel: “You certainly could continue with Excel, but consider:”

No real-time collaboration (version control nightmare)
No automated workflows (manual copy-paste between sheets)
No user access controls (everyone sees everything or complex sheet protection)
No audit trail (who changed what, when?)
Breaks at scale (500+ rows = slow, error-prone)

In-house development: “You could build in-house if you have:”

Dedicated developer team (R80K-R120K/month x 6 months = R480K-R720K)
Project manager
Ongoing maintenance and security updates

“Our solution costs less, delivers faster, and includes ongoing support. Your IT team can focus on NSTF-specific priorities, not reinventing awards management.”

Proof Point:

Total cost of ownership comparison: In-house development R800K+, our solution R300K-R500K (40% savings)
Speed: 12 weeks vs. 6-9 months for in-house build

Timeline & Urgency Objections

”November 2025 awards cycle is too soon”

Response: “Let’s look at the timeline:”

Today: December 2025
Registration opens: November 4, 2025
We have 11 months

“Our 12-week comprehensive delivery means we’d be done by March 2025 - 8 months before registration opens. That gives you:”

6 months for thorough testing
Time to create training materials
Pilot with internal team (mock nominations)
Refinements based on testing

“If we start by end of Q1 2025, we’re very comfortable hitting Nov 2025 deadline.”

Alternative: “If Nov 2025 feels risky, we can deliver pilot by Q2 2025, test it with a smaller program (discussion forum registration?), then deploy for full awards cycle in 2026. You decide based on comfort level.”

Proof Point:

SACE: 10-week delivery, live within 3 months, ran full program 6 months later without issues

”We need to focus on other priorities right now”

Response: “I completely understand competing priorities. A few questions:”

“When is the next awards cycle less busy for planning?” [Identify window]
“What if we handle the heavy lifting?” (Requirements, development, testing - NSTF reviews and approves)
“Could we lock in pricing now, start implementation when you’re ready?” (3-6 month deferral)

“The risk of waiting: if you defer to mid-2025, Nov 2025 awards cycle is off the table. Then you’re running 2025/2026 awards the old way (one more ‘arduous’ cycle).”

Proof Point:

Opportunity cost: One more manual cycle = R20K+ in staff time, nominator frustration, limited analytics

Vendor & Trust Objections

”We’ve never heard of iSu Technologies”

Response: “Fair concern - trust is earned. Here’s our background:”

South African company, based in [location]
[X years] in business, specializing in nonprofit/public sector platforms
Clients include MGSLG (education sector), SACE (training providers), [others]
POPIA-compliant, security-certified

“What would help build confidence? Options:”

Reference calls with current clients (MGSLG, SACE)
Visit our office, meet the team
Pilot approach (small commitment, prove ourselves)
Escrow code arrangement (if we disappear, you get source code)

Proof Point:

Share client testimonials (video or written)
LinkedIn profiles of leadership team (established professionals)
Portfolio of delivered projects

”What if you go out of business?”

Response: “Legitimate question. Here’s how we protect you:”

Code escrow: Source code held by third party, released to you if we cease operations
Data portability: Your data is exportable anytime (not locked in proprietary format)
Open standards: Built on widely-used technologies (easy for another vendor to support)
Financial stability: [Share company stability indicators if appropriate]

“Also consider: manual Excel process is 100% dependent on institutional knowledge. If your awards manager leaves, knowledge walks out. Our platform documents the process and training is transferable.”

Proof Point:

Include code escrow clause in contract (standard practice, minimal cost)
Show export functionality (all data to CSV/JSON in minutes)

Scope & Requirements Objections

”This doesn’t do [specific feature we need]”

Response: “Great catch - tell me more about that requirement.”

[Listen and understand the need]

If it’s a reasonable addition: “We can build that. It would add [X weeks] to timeline and [R amount] to cost. Alternatively, we could include it in Phase 2 enhancements after initial launch. What’s the priority - must-have for Day 1, or nice-to-have for future?”

If it’s edge case / low value: “That’s an interesting need. In our experience with similar programs, [that feature] is rarely used. How about we launch without it, and if you find it’s actually needed in practice, we add it in a future update? Keeps initial project lean and on-budget.”

Proof Point:

Show customization examples from other clients
“80% of features get 95% of usage - we focus there first, add edge cases later"

"Our awards process is unique and complex”

Response: “Every organization says that - and they’re right! Here’s how we handle uniqueness:”

Discovery session: 60-90 minutes, we map your exact process (every step, every stakeholder)
Configurable platform: We don’t force you into a template, we configure to your workflow
Examples of ‘unique’ we’ve handled:
- Multi-stage nominations (registration → full submission)
- Category-specific criteria (different scoring for research vs. engineering)
- Panel conflict of interest management
- Special theme awards (your Quantum Science 2025)
- Integration with existing databases

“The core framework is proven, the configuration is customized to NSTF.”

Proof Point:

SACE had 12 different training provider types, each with unique requirements - we configured for all
Show configuration interface (demonstrate flexibility)

Ecosystem Partnership Objections

”We’re not comfortable referring members to a vendor”

Response: “I appreciate that concern - NSTF’s relationship with members is sacred. Here’s how we protect it:”

No pressure approach: Free technology consultations, no obligation to buy
Member benefit framing: “NSTF negotiated exclusive member discount” (positioning NSTF as advocate)
Quality guarantee: Poor service damages both our brands - we’re incentivized to deliver excellence
NSTF control: You decide which members to introduce, when, and how
Transparency: Members know this is a partnership, not hidden agenda

“Think of it like NSTF’s South32 partnership - you’re not ‘selling’ South32, you’re partnering for mutual benefit and member value.”

Alternative: “If referrals feel uncomfortable, we can do technology partnership without revenue share - just deliver great platform for NSTF, build credibility organically. Members see NSTF’s success, inquire on their own.”

Proof Point:

Professional association case study: 40% of members adopted recommended platform (high conversion because trusted source)

“What if members don’t convert to clients?”

Response: “Then we don’t earn referral revenue - that’s our risk, not yours. Here’s the beauty of the model:”

Option A (Revenue Share):

NSTF gets platform at standard price (R300K-R500K)
IF members sign contracts, NSTF earns commissions (bonus, not expected)
If no members convert, NSTF still has awards platform (no downside)

Option B (Member Discount Model):

NSTF members get 20-30% discount
iSu absorbs cost (betting on volume)
NSTF provides member value, no financial risk

“We’re betting on our ability to deliver value - if we can’t convert warm leads from NSTF, that’s on us.”

Proof Point:

Similar ecosystem play with [organization]: 60% of warm referrals converted within 12 months

Data Security & Compliance Objections

”How do you handle POPIA compliance?”

Response: “POPIA compliance is built into the foundation, not bolted on later. Specifically:”

Consent Management:

Explicit consent checkboxes (nominators opt-in to data processing)
Clear privacy policy accessible during registration
Right to access and delete data (self-service portal for nominators)

Data Minimization:

Only collect what’s needed for awards process
Automatic purging of non-shortlisted nominations after 24 months (configurable)

Security Measures:

Encryption in transit (HTTPS/TLS) and at rest
Access controls (role-based: nominators, adjudicators, admins see different data)
Audit logs (who accessed what, when)
Regular security updates and penetration testing

Data Residency:

Hosted in South Africa (data doesn’t leave country)
Compliant with POPI Act Section 72 (cross-border transfer restrictions)

Proof Point:

POPIA compliance certificate (if available)
Show GDPR compliance (higher standard than POPIA - if we meet GDPR, we exceed POPIA)
Reference clients in healthcare/education (highly regulated sectors)

“What if there’s a data breach?”

Response: “We take this extremely seriously. Here’s our approach:”

Prevention (Best Defense):

Encryption, firewalls, intrusion detection
Regular security audits and penetration testing
Staff training on security protocols
Vendor security assessments (all third-party tools vetted)

Detection:

24/7 monitoring and alerts
Automated anomaly detection
Regular log reviews

Response (If Breach Occurs):

Incident response plan (notify NSTF within 24 hours)
Forensic analysis (identify scope and impact)
Remediation (patch vulnerability immediately)
Notification to affected individuals (POPI Act Section 22 compliance)
Post-incident review (prevent recurrence)

Insurance:

Cyber liability insurance (covers breach costs)
Professional indemnity insurance

Proof Point:

“In [X years] of operation, zero data breaches” (if true)
Show security certifications (ISO 27001, SOC 2, etc. if applicable)
Share incident response plan summary (demonstrates preparedness)

Competition & Alternatives Objections

”We’re evaluating other vendors”

Response: “Smart approach - you should evaluate options. To help your comparison, here’s what makes us different:”

vs. Big 4 (Deloitte, PwC, etc.):

Us: R300K-R500K, 12-week delivery, ongoing support included
Them: R2M-R5M, 9-12 month delivery, change requests cost extra
Why us: Right-sized solution, not enterprise overkill

vs. Generic Platforms (Submittable, Award Force):

Us: Customized to NSTF process, local support, POPIA-compliant hosting
Them: Template-based, offshore support, monthly subscription fees add up
Why us: Built for you, not adapted to you

vs. In-House Development:

Us: Proven platform, delivered in 12 weeks, includes support
Them: 6-9 months, R800K+, ongoing maintenance burden
Why us: Faster, cheaper, less risk

“Happy to provide detailed comparison matrix. Who else are you considering?”

Proof Point:

Comparison spreadsheet (feature-by-feature, cost-by-cost)
Win/loss analysis (where we’ve beaten competitors and why)

“Why shouldn’t we just use Google Forms?”

Response: “Google Forms is great for surveys, but awards programs need more:”

What Google Forms CAN’T do:

File uploads (limited size, no organization)
Multi-stage workflows (nomination → adjudication → selection)
Access controls (anyone with link can view responses)
Custom branding (looks like Google, not NSTF)
Integration with existing databases
Adjudicator scoring interfaces
Analytics beyond basic charts
POPIA-compliant hosting (Google servers are US-based)

“Google Forms gets you 20% of the way. Our platform delivers the full awards management lifecycle.”

Proof Point:

“Organizations start with Google Forms, hit limitations within 6 months, then come to us”
Show side-by-side comparison (what takes 20 clicks in Google Forms is 2 in our platform)

Risk & Guarantees Objections

”What if it doesn’t work?”

Response: “Let’s define ‘work’ and put guarantees behind it:”

Success Criteria (Contractual):

Uptime: 99.5% platform availability (monitored, penalties if we miss)
Performance: Page load <2 seconds (fast user experience)
User Satisfaction: 85%+ nominator satisfaction (post-awards survey)
Admin Efficiency: 60% reduction in manual tasks (measured pre/post)

If We Don’t Meet Criteria:

Refund clause (proportional to unmet criteria)
Free extended support (until criteria met)
Exit clause (you can terminate without penalty)

Pilot Option: “Alternatively, do 8-week pilot (R150K-R250K). If it doesn’t work, you’ve invested minimally and learned what doesn’t fit. If it works, upgrade to full version (pay differential).”

Proof Point:

“92% of pilots convert to full implementations” (demonstrates confidence)
Client testimonials on reliability and performance

Strategic & Political Objections

”Our Board member’s nephew has a software company”

Response: “Family connections are important. Here’s how to handle this professionally:”

Competitive process: Invite nephew’s company to submit proposal alongside ours
Objective evaluation: Use scoring matrix (functionality, cost, timeline, experience)
Reference checks: Both companies provide client references
Proof of concept: Both demonstrate platform (may be eye-opening)

“The Board’s fiduciary duty is to NSTF’s best interest. Professional procurement process protects everyone - Board member included (avoids conflict of interest perception).”

“We’re confident in competitive evaluation - our platform, pricing, and track record stand on merit.”

Proof Point:

“We win 70% of competitive RFPs because our solution is purpose-built and proven"

"We need to support local/BEE suppliers”

Response: “We are local and BEE-compliant:”

South African company (registered, tax-paying, job-creating)
[BEE Level X] certified (if applicable)
[% Black ownership] (if applicable)
Local team (support calls answered in SA time zone, in person meetings possible)

“Your procurement policy likely prioritizes local BEE - we tick those boxes. Happy to provide BBBEE certificate and company registration documents.”

Proof Point:

BBBEE certificate (if available)
Company registration documents
List of other public sector/nonprofit clients (validates BEE compliance)

Final Objection: “Let us think about it”

Response (Diagnose First): “Of course - this is an important decision. To help your thinking, can I ask:”

“What specific aspects are you considering?” [Uncover real objection]
“Are there concerns we haven’t addressed?” [Surface hidden objections]
“What would make this a ‘yes’ for you?” [Understand decision criteria]
“Who else needs to be involved in the decision?” [Identify stakeholders]

[Based on answers, address real concerns]

If genuinely need time: “Understood. Here’s what I’ll do:”

“Send summary of today’s discussion (key points, pricing, next steps)”
“Include answers to any outstanding questions”
“Propose follow-up call in [X days/weeks] - does [specific date] work?”

“In the meantime, feel free to reach out with questions. I’m here to help you make the best decision for NSTF, whether that’s with us or not.”

Proof Point:

“Most clients take 2-4 weeks to decide after demo - that’s normal. I’m here to support your process.”

Objection Handling Principles

1. Listen First

Don’t interrupt
Let them fully express the concern
Show empathy (“I understand why that’s important”)

2. Clarify

“Tell me more about that”
“What specifically concerns you about [objection]?”
Ensure you understand root cause, not just surface objection

3. Acknowledge

“That’s a valid concern”
“Others have raised that too”
Don’t dismiss or minimize

4. Respond with Evidence

Data, case studies, guarantees
Not opinions or claims
Specific, quantifiable where possible

5. Confirm Resolution

“Does that address your concern?”
“What else would help you feel confident?”
Don’t assume objection is handled, verify

6. Document

Note all objections in CRM
Track which responses work best
Share learnings with team

Guide Owner: iSu Technologies Sales Enablement Last Updated: December 2, 2025 Next Review: Quarterly (incorporate new objections and successful responses)