SANSA January 2026 Engagement Strategy

Comprehensive Preparation Guide for Vision 2030 Partnership

Status: Ready for Execution Last Updated: December 20, 2025 Author: iSu Technologies

Executive Summary

The December 2025 discovery meeting did not occur due to SANSA year-end closure. The December Vision Document was not sent. This creates a strategic opportunity to approach January 2026 with a refined, budget-first strategy rather than leading with pricing that may not be profitable.

Key Strategic Shifts

Original Approach	Revised Approach
Send Vision Doc → Wait → Send Investment Doc	Budget Discovery First → Tailored Proposal
Fixed pricing tiers (R650K-R1.2M)	Flexible pricing based on actual budget
90-minute formal discovery call	Informal WhatsApp re-engagement → Discovery
Lead with features	Lead with relationship and understanding

Intelligence Summary

SANSA Budget Context

Metric	Value	Source
Annual Parliamentary Grant	~R350 million	Engineering News
Additional Contract Revenue	~R160 million	SANSA FY2024/25
Total Annual Budget	~R510 million	Combined
Space Infrastructure Hub SIP 22	R4.47 billion	Investor funding attracted

Key Contacts Intelligence

Thandile Vuntu

Role: Science Engagement Manager (Hermanus)
Focus: STEM outreach, educator workshops, youth engagement
Philosophy: “STEM is Inclusive and has no gender limits”
Active in: GLOBE.gov collaboration, Women’s Month events
Source: LinkedIn

Dan Matsapola

Role: Science Engagement Manager
Focus: Career guidance, space awareness, EBSI wealth creation model
Media: Motsweding FM appearances (June 2024)
Quote: “Space science and technology were no longer the exclusive preserve of rich countries”
Active in: World Space Week, rural school career days

SANSA Strategic Plan 2025-2030 Priorities

Increasing national space capabilities
Enhancing space-relevant knowledge for development
Increasing South Africa’s share in global space market
Augmenting international collaborations
Using space applications for socioeconomic development
Impelling Africa’s involvement in global space agenda

Alignment Opportunity: Vision 2030 (450,000 STEM entrepreneurs) directly supports outcomes #2 and #5.

January 2026 Re-Engagement Timeline

Week 1: December 30 - January 5 (Pre-Return)

DO NOT contact during this period. SANSA officially closed.

Internal Preparation:

Finalize all preparation materials
Test SACE demo environment
Prepare WhatsApp message drafts
Review December 3 meeting notes

Week 2: January 6-10 (First Week Back)

Monday, January 6:

SANSA returns from closure
DO NOT contact Day 1 (let them settle)

Tuesday, January 7 (Target: Re-engagement)

Morning (9:00 AM): Send WhatsApp to Thandile (warmer relationship)

Hi Thandile,

Happy New Year! Hope you had a wonderful break with family.

I've been thinking about your educator workshop initiative since our December meeting. Still excited about supporting the CETA accreditation tracking.

When things settle this week, I'd love to reconnect briefly - even just 15 minutes to understand how your planning for 2026 is shaping up.

No rush - I know first week back is always hectic!

Nhlanhla

Wednesday-Thursday, January 8-9:

Wait for Thandile’s response
If no response by Thursday afternoon, send similar message to Dan

Friday, January 10:

If responses received: Schedule informal call for Week 3
If no response: Wait until Monday January 13 for follow-up

Week 3: January 13-17 (Discovery Conversations)

Objective: 15-30 minute informal calls to understand:

What’s their actual budget situation for FY2026/27?
What’s their timeline pressure (when do workshops need to start)?
Is this going to tender, or can it be direct appointment?
Who else is involved in the decision?

Key Questions to Ask (Natural Conversation):

“How’s the planning going for the quarterly workshops? Any timeline pressures?”
“Have you had any conversations internally about technology support for this?”
“Is there a budget allocated for this, or is that still being determined?”
“Would this typically go through a tender process, or is there flexibility for smaller projects?”
“Who else would need to be involved in making this happen?”

Week 4: January 20-24 (Tailored Proposal Development)

Based on Week 3 intelligence:

Develop proposal tailored to actual budget
Determine if Vision Doc or Investment Framework is appropriate
Prepare for formal discovery meeting or proposal submission

Week 5: January 27-31 (Formal Engagement)

Schedule 60-90 minute discovery call/meeting
Share tailored proposal
Demo SACE platform
Discuss next steps toward contract

Revised Pricing Strategy

The Profitability Problem

Original R920K “Professional Platform” pricing may not be viable because:

Scope is massive: 460,000 educators, 25,000 schools, CETA integration
Timeline is aggressive: 6-9 months to national rollout
Ongoing costs: 3 years hosting, 12 months support included
Hidden complexity: SACE integration, ML model training, multilingual

Pricing Options Based on Budget Discovery

Scenario A: Budget is R500K-R800K

Offer “Pilot Program” (limited scope)
5,000-10,000 educators in 2-3 provinces
6-month implementation
Phase 2 expansion negotiated separately
Your Price: R650K-R800K (profitable at reduced scope)

Scenario B: Budget is R1M-R1.5M

Offer “Foundation Platform”
Full workshop management + basic tracking
9-month implementation
ML and advanced analytics as Phase 2
Your Price: R1.2M-R1.4M

Scenario C: Budget is R1.5M-R3M

Offer “Professional Platform” (full Vision Doc scope)
All Phase 1 features including ML
12-month implementation
Your Price: R1.8M-R2.5M (properly scoped)

Scenario D: Budget is R3M+

Offer “Enterprise Platform” with Phase 2 elements
Full customization, white-label, mobile apps
Your Price: R2.5M-R4M

Tender vs Direct Appointment

If Going to Tender:

Pricing becomes competitive
Focus on technical capability and SACE proof
Include B-BBEE advantage
Expect 60-90 day procurement cycle

If Direct Appointment (Preferred):

Threshold for direct appointment typically R500K-R1M
Position as “specialized service” not commodity
Emphasize urgency of Q1 2026 start
Push for single-source justification based on SACE experience

Competitive Landscape Analysis

Potential Competitors

Competitor	Strength	Weakness	Threat Level
Synrgise	SA-based LMS provider	Generic platform, no educator-specific experience	Medium
SchoolNet SA	Education sector credibility	Non-profit, may not bid on contracts	Low
VVOB	DBE/SACE partnership already	International NGO, not commercial	Low
Moodle Service Providers	Low cost, open source	Generic, no ML, no EBSI model capability	Medium
Big 4 Consultancies	Government relationships	Expensive, outsource development	Medium-High
International EdTech	Advanced platforms	No SA presence, no B-BBEE	Low

Your Competitive Advantages

SACE Proof Point: 400,000+ educators already tracked - exact scale SANSA needs
ML Capability: Predictive analytics proven, not theoretical
Local Presence: SA-based, understand government procurement
B-BBEE Compliant: CSD registered, ready for tender
Relationship: Already met Dan and Thandile, WhatsApp rapport
Vision Alignment: Understand EBSI model and “flip the script” philosophy

Differentiation Messaging

“While others offer generic learning management systems, iSu Technologies has already proven we can track 400,000+ educators at national scale with predictive analytics. We don’t need to build capability - we need to adapt what’s already working.”

SACE Demo Environment Concept

What to Prepare

Option A: Live SACE Demo (If Permissible)

Anonymized/sample data from actual SACE platform
Show real dashboards, real ML predictions
Most credible but may have confidentiality concerns

Option B: SANSA-Branded Prototype

Clone SACE interface with SANSA branding
Populate with sample educator data
Show “what it would look like” for their use case
Takes 2-3 days to prepare

Option C: Video Walkthrough

Pre-recorded demo of SACE platform
Narrated explanation of how it works
Can share via WhatsApp before call
Lowest effort, still effective

Recommended: Option B + Option C

Create 3-5 minute video walkthrough of SACE (shareable via WhatsApp)
Build lightweight SANSA-branded prototype for live demo
Use video for initial re-engagement, prototype for discovery call

Demo Script Outline

Dashboard Overview (2 min)
- National view: educators by province
- Progress toward targets
- Alert indicators
Educator Journey (2 min)
- Individual profile
- Workshop completion
- CETA credits
- EBSI progression
ML Early Warning (1 min)
- At-risk educator identification
- Intervention recommendations
CETA Compliance (1 min)
- Accreditation workflows
- Automated reporting

Custom SANSA Mockups Specification

Mockup 1: SANSA Educator Dashboard

Header:

SANSA logo + “Vision 2030 Educator Platform”
Welcome message: “Welcome, [Educator Name]”
Quick stats: Workshops Completed | CETA Credits | EBSI Level

Main Content:

Progress wheel showing journey from Employee → Investor
Four Accelerators self-assessment scores (A1-A4)
Upcoming workshop calendar
Recommended next steps

Sidebar:

My Profile
My Workshops
My CETA Credits
Community Forum
Success Stories

Mockup 2: SANSA Admin Analytics Dashboard

Header:

SANSA logo + “Vision 2030 Analytics Hub”
Date range selector
Export button

Key Metrics Row:

Total Educators Enrolled: 52,431 / 460,000 target
Workshops Delivered: 24
Average Completion Rate: 87%
EBSI Progression Rate: 23%

Charts:

Provincial map with heat indicators
Trend line: Enrollments over time
Bar chart: Workshop attendance by district
Pie chart: EBSI level distribution

Alerts Panel:

3 districts below 70% completion
2 upcoming CETA renewal deadlines
5 educators at risk of dropout (ML prediction)

Mockup 3: Workshop Management Interface

Header:

SANSA logo + “Workshop Management”

Upcoming Workshops Table:

Workshop	Date	Venue	Capacity	Enrolled	Status
CETA Q1 - Gauteng	Feb 15, 2026	Pretoria	200	187	Open
CETA Q1 - KZN	Feb 22, 2026	Durban	150	150	Full
CETA Q1 - WC	Mar 1, 2026	Cape Town	175	89	Open

Quick Actions:

Create New Workshop
Send Reminders
Download Attendance
Generate Certificates

Design Notes

Use SANSA color palette (blue/white/green)
Include SANSA logo prominently
Show realistic data volumes (not 10 records, show 52,431)
Make it look like a real system, not a wireframe

FAQ: Common Objections & Responses

Budget Objections

“This is too expensive for our budget.”

“I completely understand budget constraints. Let me ask - what range are you working with? We’ve designed this in phases specifically so organizations can start with what’s achievable now and expand later. Would it help if I showed you what we could deliver within your current budget?”

“We need to go to tender for this amount.”

“That’s completely appropriate for an investment of this scale. We’re tender-ready - CSD registered and B-BBEE compliant. Would it help if I provided technical specifications you could use for the tender document? We’d also be happy to participate in a briefing session if that’s part of your process.”

Capability Objections

“How do we know this will work at our scale?”

“That’s exactly why our SACE experience is so relevant. We’re already tracking 400,000+ educators nationally with 85% compliance improvement. SANSA’s 460,000 educator target is nearly identical scale. We’re not proposing to build something new - we’re proposing to adapt what’s already proven.”

“We’ve had bad experiences with IT projects before.”

“Government IT projects often fail because vendors underestimate complexity. Our approach is different - we start with a pilot cohort (say, 5,000 educators in one province), prove it works, then scale. You only commit to national rollout after seeing it succeed. Would that approach reduce your risk concerns?”

Timing Objections

“We’re not ready to start this in Q1.”

“No problem at all. When do you anticipate being ready? I’d rather we take time now to properly scope this than rush into something. Would it be helpful to use the next few months for detailed requirements gathering so we’re ready to move quickly when budget is approved?”

“Thandile’s workshops don’t start until Q3.”

“That gives us great runway. If we started discovery in February and development in April, we’d have a working pilot ready by August - perfect timing for Q3 workshops. Would you like to map out that timeline together?”

Competition Objections

“We’re talking to other providers too.”

“Absolutely as you should for a decision of this importance. What I’d ask is: how many of those providers have already proven they can track 400,000 educators nationally? Our SACE platform isn’t a proposal - it’s operational. I’d love the chance to show you that difference in a demo.”

“Why shouldn’t we just use an off-the-shelf LMS?”

“Generic LMS platforms are great for course delivery, but they can’t do what you need: track EBSI progression, manage CETA accreditation workflows, predict educator dropout risk, or measure Vision 2030 achievement. Those features don’t exist off-the-shelf - they need to be built specifically for SANSA’s model. And we’ve already built them for SACE.”

Trust Objections

“We need to involve our IT department.”

“Absolutely - they should be part of this conversation. Would you like me to prepare a technical architecture document for them? I’m also happy to schedule a separate technical deep-dive with your IT team while we continue the strategic conversation with you.”

“Can we see references from SACE?”

“Yes, I can arrange a reference call with our SACE stakeholders. They can speak directly to implementation experience, platform reliability, and results achieved. Would that be helpful?”

Risk Mitigation Plan

Risk 1: They Choose a Competitor

Mitigation:

Maintain relationship even if they go to tender
Differentiate on SACE proof point
Offer pilot program at lower risk
Stay engaged as “trusted advisor” regardless

Risk 2: Budget is Too Small

Mitigation:

Have pilot program ready (R300K-R500K scope)
Propose phased approach over 2 fiscal years
Identify co-funding opportunities (DSI, SETA)

Risk 3: Project Goes to Tender

Mitigation:

Ensure all CSD documentation current
Prepare technical specifications in advance
Build relationship advantage pre-tender
Consider consortium if required

Risk 4: Key Contacts Leave SANSA

Mitigation:

Document relationships with multiple stakeholders
Get introduced to IT and Finance contacts
Build institutional knowledge, not personal dependency

Risk 5: Vision 2030 Priority Changes

Mitigation:

Position solution for multiple use cases
Emphasize immediate Thandile need (workshops)
Show value independent of 2030 target

Preparation Checklist

Immediate (By December 31)

Draft WhatsApp message for Thandile (Week 2)
Draft WhatsApp message for Dan (backup)
Review December 3 meeting notes
Identify key questions for budget discovery
Confirm CSD registration is current
Confirm B-BBEE certificate is current

Before January 7

Create SACE video walkthrough (3-5 min)
Design SANSA mockup specifications (3 screens)
Prepare pricing scenarios (A/B/C/D)
Draft pilot program scope (reduced scale)
Review competitor landscape
Prepare reference request for SACE

Before Discovery Call

Build SANSA-branded prototype (if time permits)
Prepare discovery call agenda
Create tailored proposal based on budget intel
Prepare demo environment
Print leave-behind materials (if in-person)

Success Metrics

January 2026 Goals

Metric	Target	Status
Re-engagement with Thandile/Dan	By Jan 10	Pending
Budget range discovered	By Jan 17	Pending
Discovery call scheduled	By Jan 24	Pending
Tailored proposal submitted	By Jan 31	Pending

Q1 2026 Goals

Metric	Target	Status
Contract signed	By Mar 31	Pending
Project kickoff	By Apr 15	Pending
Phase 1 deposit received	By Apr 30	Pending

Contact Information

Internal Reference:

Contact	Role	Phone	WhatsApp	Email
Thandile Vuntu	Science Engagement Mgr	[Stored]	Yes	[SANSA email]
Dan Matsapola	STEM EBSI Lead	[Stored]	Yes	[SANSA email]

Your Details for All Communications:

Nhlanhla Mnyandu Director, iSu Technologies (Pty) Ltd Email: nhlanhla@isutech.co.za Mobile: [Your Number] Website: www.isutech.co.za

Document prepared December 20, 2025 Strategy valid through Q1 2026