SANSA January 2026 Execution Plan

SANSA January 2026 Execution Plan

Revised Strategy: Honest Positioning + Working System

Document Status: Final Last Updated: December 20, 2025 Strategy: Formal email communication + Prototype demonstration

---

Strategy Summary

Core Approach

Element	Approach
Communication	Formal email (not WhatsApp)
Positioning	Honest - real proof points only
Demonstration	Working system (built as production-ready)
Investment Discussion	After prototype demonstration

Key Documents

Document	Purpose	Type
05-INTERNAL-application-specification.md	Technical spec for prototype build	Internal
06-revised-partnership-proposal.md	Main document to send to SANSA	External
07-revised-email-templates.md	Formal email templates	Internal
08-january-2026-execution-plan.md	This execution plan	Internal

---

Timeline Overview

Phase 1: Build (December 20 - January 15)

Objective: Develop production-ready application (presented as “prototype”)

Week	Dates	Activities
Week 1	Dec 20-27	Repository setup, scaffolding, database schema, SANSA branding
Week 2	Dec 28 - Jan 3	Educator dashboard, workshop management, API development
Week 3	Jan 4-10	Analytics dashboard, EBSI tracking, Four Accelerators
Week 4	Jan 11-15	ML predictions, polish, demo data (50K educators), testing

Deliverable: Fully functional platform with 50,000 educator records

Phase 2: Engage (January 6-17)

Objective: Re-establish contact and schedule discovery call

Date	Action
Jan 6-7	Send re-engagement email with Partnership Proposal
Jan 13	Follow-up if no response
Jan 14-17	Discovery call (if scheduled)

Deliverable: Discovery call confirmed and completed

Phase 3: Demonstrate (Late January - February)

Objective: Present working system, gather feedback

Activity	Timing
Prototype presentation	Late Jan / Early Feb
Feedback incorporation	1 week after presentation
Investment discussion	Following week

Deliverable: SANSA impressed, investment discussion initiated

Phase 4: Contract (February - March)

Objective: Formalize agreement and begin deployment

Activity	Timing
Investment proposal (detailed)	Post-demonstration
Procurement process	February
Contract signature	March 2026
Pilot kickoff	Q2 2026

---

Week-by-Week Execution

Week 1: December 20-27

Development Focus:

• Create GitHub repository: sansa-educator-platform
• Set up Next.js 14 project structure
• Set up FastAPI backend structure
• Create PostgreSQL database schema
• Implement SANSA branding (colors, logo, typography)
• Build base UI components

Deliverables:

• Working development environment
• Database with all tables created
• Basic frontend layout with SANSA branding

Week 2: December 28 - January 3

Development Focus:

• Educator profile pages
• Educator dashboard (personal view)
• Workshop list and detail views
• API endpoints: educators, workshops
• Demo data generation script (10K educators)

Deliverables:

• Educator can view their profile
• Educator can see workshop list
• Basic data in database

Week 3: January 4-10

Development Focus:

• Analytics dashboard (admin view)
• EBSI journey tracker visualization
• Four Accelerators assessment forms
• Provincial/district charts
• Workshop management CRUD
• CETA compliance workflows

Business Focus:

• Send re-engagement email (Jan 6-7)
• Prepare for discovery call
• Follow up if no response (Jan 13)

Deliverables:

• Full analytics dashboard working
• EBSI progression visible
• Discovery call scheduled (goal)

Week 4: January 11-15

Development Focus:

• ML predictions display
• Early warning indicators
• Complete demo data (50K educators, 200 workshops)
• Performance optimization
• Mobile responsiveness testing
• Deploy to Railway (demo environment)

Business Focus:

• Conduct discovery call (if scheduled)
• Document requirements from call
• Adjust prototype based on feedback

Deliverables:

• Production-ready platform
• 50,000 educator records
• Live demo URL

Week 5+: January 17 onwards

Focus: Demonstration and engagement

• Schedule prototype presentation
• Conduct live demonstration
• Gather feedback
• Prepare investment proposal
• Begin contract negotiation

---

Email Communication Plan

Email 1: Re-Engagement (January 6-7)

Purpose: Restart conversation after holiday break Attachment: Partnership Proposal (06-revised-partnership-proposal.md as PDF) Template: See 07-revised-email-templates.md - Email 1

Key Messages:

1. Happy New Year
2. We’ve been thinking about Vision 2030
3. Our approach: working software, not promises
4. Propose discovery call

Email 2: Follow-Up (January 13)

Purpose: Gentle reminder if no response Trigger: No response to Email 1 within 5 business days Template: See 07-revised-email-templates.md - Email 2

Email 3: Discovery Call Confirmation

Purpose: Confirm meeting details Trigger: They agree to discovery call Template: See 07-revised-email-templates.md - Email 3

Email 4: Post-Discovery Thank You

Purpose: Summarize call, confirm next steps Trigger: Within 24-48 hours of discovery call Template: See 07-revised-email-templates.md - Email 4

Email 5: Prototype Ready

Purpose: Request demonstration meeting Trigger: Prototype completed Template: See 07-revised-email-templates.md - Email 5

Email 6: Post-Demonstration

Purpose: Follow up with investment details Trigger: Within 24-48 hours of demonstration Template: See 07-revised-email-templates.md - Email 6

---

Prototype Requirements Summary

Must-Have Features (Demo Essential)

1. Educator Dashboard

   • Profile display
   • EBSI journey visualization
   • Workshop history
   • CETA credits summary

2. Workshop Management

   • Workshop list view
   • Enrollment capability
   • Attendance tracking
   • Certificate view

3. Analytics Dashboard

   • National overview metrics
   • Provincial comparison
   • EBSI distribution chart
   • Trend indicators

4. Demo Data

   • 50,000 educator records
   • 200 workshops
   • Realistic geographic distribution
   • Sample ML predictions

Nice-to-Have Features

• Four Accelerators assessment forms
• ML early warning details
• District drill-down
• Mobile app preview
• Offline capability demo

Technical Requirements

• Response time < 2 seconds
• No crashes during demo
• Mobile responsive
• SANSA branding throughout

---

Discovery Call Preparation

Agenda (60-90 minutes)

1. Opening (5 min)

   • Thank them for time
   • Recap December meeting

2. SANSA Requirements (25 min)

   • Thandile: Workshop workflow details
   • Dan: Vision 2030 metrics priorities
   • Current systems and data sources
   • Timeline expectations

3. iSuTech Capability (15 min)

   • AssessFlow demonstration (brief)
   • Dube TradePort partnership
   • Technical approach overview

4. Prototype Discussion (20 min)

   • What we’ll build
   • Timeline commitment
   • What we need from them
   • Feedback process

5. Next Steps (10 min)

   • Prototype delivery date
   • Demonstration scheduling
   • Any immediate questions

Questions to Ask

For Thandile:

• How many workshops per quarter?
• Target audience per workshop?
• Current CETA accreditation process?
• Biggest pain points in workshop management?

For Dan:

• Which metrics matter most for Vision 2030?
• How do you currently track progress?
• What would success look like in Year 1?
• Who else needs to see the platform?

For Both:

• Budget range for this initiative?
• Decision-making process and timeline?
• Other stakeholders to involve?
• Preference for pilot scope (provincial/national)?

Materials to Prepare

• Partnership Proposal (PDF)
• AssessFlow overview slides (3-5 slides)
• Dube TradePort partnership summary (1 page)
• Prototype mockups (3-5 screens)
• Discovery call agenda (to share in advance)

---

Risk Management

Risk 1: No Response to Emails

Probability: Medium Impact: Delays engagement

Mitigation:

• Follow-up email after 5 business days
• Second follow-up after 10 business days
• Phone call if email contact available
• Final “should we pause?” email after 3 weeks

Risk 2: They Want to Go to Tender

Probability: Medium-High Impact: Longer timeline, competitive process

Mitigation:

• Prototype differentiates from competitors
• Prepare CSD registration proof
• Prepare B-BBEE documentation
• Offer technical specifications for tender document

Risk 3: Budget Lower Than Expected

Probability: Medium Impact: Reduced scope or no deal

Mitigation:

• Prepare phased implementation options
• Pilot program (provincial vs. national)
• Payment spread across fiscal years
• Clear minimum viable scope

Risk 4: Prototype Not Ready in Time

Probability: Low-Medium Impact: Missed engagement window

Mitigation:

• Prioritize must-have features
• Cut nice-to-have if needed
• Daily progress tracking
• Parallel development (frontend/backend)

Risk 5: Contact Leaves SANSA

Probability: Low Impact: Lost relationship, start over

Mitigation:

• Request introduction to additional stakeholders
• Build institutional relationship, not personal
• Document all discussions

---

Success Metrics

Phase 1 Success (Build)

Metric	Target	Measure
Prototype completion	January 15	All must-have features working
Demo data volume	50,000 educators	Database record count
Performance	< 2 sec page load	Measured timing
Stability	Zero crashes	Test runs

Phase 2 Success (Engage)

Metric	Target	Measure
Email response	Within 7 days	Reply received
Discovery call	By January 17	Meeting confirmed
Requirements clarity	High	Documented needs

Phase 3 Success (Demonstrate)

Metric	Target	Measure
Demonstration scheduled	By January 24	Meeting confirmed
Stakeholder attendance	Dan + Thandile + 1	Attendee count
Positive feedback	Verbal confirmation	Meeting notes
Investment discussion	Initiated	Budget mentioned

Phase 4 Success (Contract)

Metric	Target	Measure
Proposal submitted	By February 28	Document sent
Contract negotiation	Started	Discussion ongoing
Contract signed	By March 31	Signed agreement

---

Document Checklist

For External Sharing

• 06-revised-partnership-proposal.md → Convert to PDF
• Investment Framework (to be created post-demo)
• Platform Feature Summary (after prototype)

For Internal Use

• 05-INTERNAL-application-specification.md
• 07-revised-email-templates.md
• 08-january-2026-execution-plan.md
• Development progress tracker
• Discovery call notes template

To Archive (Outdated)

• 01-partnership-vision-roadmap.md - Contains false SACE claims
• 02-partnership-investment-framework.md - Based on false positioning
• email-01-december-vision-document.md - Not sent, outdated
• email-02-january-investment-framework.md - Based on false positioning

---

Contact Information

SANSA Contacts:

Name	Role	Email	Phone
Dan Matsapola	STEM EBSI	[SANSA email]	[Stored]
Thandile Vuntu	Education Programs	[SANSA email]	[Stored]

iSuTech:

Name	Role	Email	Phone
Nhlanhla Mnyandu	Director	nhlanhla@isutech.co.za	[Mobile]

---

Quick Reference: Key Dates

Date	Action
Dec 20-27	Week 1 development
Dec 28 - Jan 3	Week 2 development
Jan 4-10	Week 3 development + email engagement
Jan 6-7	Send re-engagement email
Jan 11-15	Week 4 development + discovery call
Jan 13	Follow-up email (if needed)
Jan 15	Prototype complete
Jan 17+	Demonstration and negotiation

---

Execution plan prepared December 20, 2025 Strategy: Honest positioning + Working system demonstration Communication: Formal email only