SANSA Email Templates - Revised (Formal Communication)

January 2026 Re-Engagement Strategy

Purpose: Formal email templates for professional communication with SANSA Note: Email is preferred over WhatsApp for government/parastatal communication in South Africa

Email 1: January Re-Engagement (Send: January 6-7, 2026)

Subject Line Options

Option 1 (Recommended): SANSA Partnership Follow-Up - Vision 2030 Collaboration Proposal

Option 2: Following Up: Educator Platform for Vision 2030

Option 3: iSu Technologies - Ready to Support SANSA Vision 2030

Email Body

Dear Dan and Thandile,

Happy New Year! I hope you both had a restful holiday break with family and friends.

I'm following up on our productive meeting from December 3rd regarding SANSA's Vision 2030 initiative. Your framework for producing 450,000 STEM entrepreneurs through educator transformation continues to resonate with our team.

Since our meeting, we've been developing our thoughts on how to best support Thandile's quarterly CETA workshop initiative and Dan's broader Vision 2030 tracking needs.

I've attached a Partnership Proposal outlining our approach. A few key points:

1. Working Software, Not Promises
Rather than presenting slides, we propose building a working prototype demonstration of the educator platform - complete with SANSA branding, EBSI model tracking, and Four Accelerators integration. You'll see exactly what you're buying before committing.

2. Proven Capability
Our flagship platform AssessFlow demonstrates our ability to build enterprise-grade software with ML analytics. Additionally, our active partnership with Dube TradePort for government cloud infrastructure shows we understand public sector requirements.

3. Next Steps
We suggest a discovery call to clarify requirements, after which we'll develop a working prototype for your review. This approach minimizes risk and ensures alignment before any investment commitment.

Discovery Call Availability:
- Tuesday, January 14: 10:00 - 14:00
- Wednesday, January 15: 09:00 - 12:00
- Thursday, January 16: 10:00 - 16:00
- Friday, January 17: 09:00 - 13:00

Please let me know which date and time works best for you and your team, and I'll send calendar invitations.

I'm happy to answer any questions before then - please feel free to call or email.

Looking forward to exploring how we can make Vision 2030 measurable and achievable together.

Kind regards,

Nhlanhla Mnyandu
Director
iSu Technologies (Pty) Ltd

Email: nhlanhla@isutech.co.za
Mobile: [Your Mobile Number]
Website: www.isutech.co.za

Attachment: SANSA Partnership Proposal - iSu Technologies (January 2026).pdf

Email 2: Follow-Up If No Response (Send: January 13, 2026)

Subject Line

Re: SANSA Partnership Follow-Up - Vision 2030 Collaboration Proposal

Email Body

Dear Dan and Thandile,

I hope this message finds you well. I wanted to follow up on my email from last week regarding our proposed partnership for Vision 2030.

I understand January can be a busy month with planning and budget cycles. If the timing isn't right for a discovery call this week, I'm happy to work around your schedule.

Alternatively, if it would be helpful, I can:

1. Provide a brief summary of our proposal via email (5-minute read)
2. Schedule a shorter 30-minute introductory call instead of the full 90-minute discovery
3. Answer any specific questions you have before committing to a meeting

Please let me know what works best for you. I'm flexible and want to make this as convenient as possible.

Kind regards,

Nhlanhla Mnyandu
Director, iSu Technologies (Pty) Ltd
nhlanhla@isutech.co.za | [Mobile Number]

Email 3: Confirm Discovery Call (After They Respond)

Subject Line

Confirmed: SANSA-iSuTech Discovery Call - [Date] at [Time]

Email Body

Dear Dan and Thandile,

Thank you for confirming the discovery call. I've sent calendar invitations for:

Date: [Day, Date]
Time: [Time] (South African Time)
Duration: 60-90 minutes
Location: [Virtual/In-person at SANSA offices]
[If virtual: Meeting Link: [Zoom/Teams link]]

Agenda:
1. SANSA Vision 2030 requirements review (20 min)
2. iSu Technologies capability overview (15 min)
3. Prototype approach discussion (20 min)
4. Next steps and timeline alignment (15 min)
5. Questions and discussion (10 min)

Before Our Meeting:
I've attached a brief overview document for your reference. No preparation required on your end - we're there to listen and understand your needs.

If there are specific questions you'd like us to address, please send them in advance and I'll prepare accordingly.

If any other stakeholders should join (IT, Finance, other team members), please let me know and I'll update the invitation.

Looking forward to our conversation.

Kind regards,

Nhlanhla Mnyandu
Director, iSu Technologies (Pty) Ltd
nhlanhla@isutech.co.za | [Mobile Number]

Email 4: Post-Discovery Call Thank You

Subject Line

Thank You - SANSA Discovery Call Follow-Up

Email Body

Dear Dan and Thandile,

Thank you for taking the time to meet with us today. It was valuable to hear more about:

[Personalize based on call - examples:]
- Thandile's plans for the quarterly educator workshops
- Dan's vision for tracking EBSI progression nationally
- The specific challenges around [topic discussed]
- Your timeline expectations for [specific initiative]

Key Takeaways:
Based on our discussion, we understand that:
1. [Key requirement 1]
2. [Key requirement 2]
3. [Key requirement 3]

Please correct me if I've misunderstood anything.

Next Steps:
As agreed, we will:
1. Develop a working prototype demonstration by [date]
2. Include [specific features discussed]
3. Schedule a prototype presentation for [proposed date range]

We'll share progress updates as we build, and you're welcome to provide feedback at any point.

If you need anything before then, please don't hesitate to reach out.

Thank you again for the opportunity to support Vision 2030.

Kind regards,

Nhlanhla Mnyandu
Director, iSu Technologies (Pty) Ltd
nhlanhla@isutech.co.za | [Mobile Number]

Email 5: Prototype Ready - Presentation Request

Subject Line

SANSA Educator Platform Prototype Ready for Demonstration

Email Body

Dear Dan and Thandile,

I'm pleased to share that we've completed the prototype demonstration for the SANSA Educator Professional Development Platform.

What We've Built:
Based on our discovery call, the prototype includes:

- Educator Dashboard: Personal profiles, EBSI journey tracking, Four Accelerators assessment
- Workshop Management: Registration, attendance, CETA compliance, certificate generation
- Analytics Dashboard: Provincial comparisons, EBSI distribution, trend analysis
- Sample Data: 50,000 educator profiles demonstrating scale capability
- SANSA Branding: Your visual identity throughout the platform

The prototype is live and ready for demonstration whenever you're available.

Proposed Demonstration:
- Duration: 45-60 minutes
- Format: Live walkthrough with Q&A
- Attendees: Whoever you feel should see this (Dan, Thandile, IT, others)

Available Times:
- [Date 1]: [Times]
- [Date 2]: [Times]
- [Date 3]: [Times]

Please let me know which works best, and I'll send calendar invitations.

This is working software, not slides - you'll see exactly what we're proposing to deploy for SANSA.

Looking forward to showing you what's possible for Vision 2030.

Kind regards,

Nhlanhla Mnyandu
Director, iSu Technologies (Pty) Ltd
nhlanhla@isutech.co.za | [Mobile Number]

Email 6: Post-Demonstration Follow-Up

Subject Line

SANSA Platform Demonstration - Next Steps

Email Body

Dear Dan and Thandile,

Thank you for attending the platform demonstration yesterday. We appreciated your engagement and the thoughtful questions from your team.

Demonstration Summary:
We showed you a working prototype of the SANSA Educator Professional Development Platform, including:
- Educator registration and EBSI journey tracking
- Workshop management with CETA compliance workflows
- Analytics dashboard with provincial and district views
- Predictive analytics for early intervention
- Mobile-responsive design for educator access

Feedback Received:
[Personalize based on their comments]
- [Positive feedback point]
- [Question/concern and how we'll address it]
- [Feature request and feasibility]

Investment Discussion:
As discussed, I'm attaching our Investment Framework document with:
- Three investment tiers (scope-dependent)
- Payment structure options
- Implementation timeline
- What's included in each option

We recommend [specific tier] based on your requirements, but we're flexible and can tailor the approach to your budget reality.

Proposed Next Steps:
1. Review the Investment Framework (attached)
2. Internal discussion with your team
3. Budget/procurement clarification call (if helpful)
4. Contract negotiation and timeline agreement

Please let me know if you have any questions about the investment options or if you'd like to schedule a call to discuss.

We're excited about the possibility of supporting Vision 2030 and making it measurable, achievable, and provable.

Kind regards,

Nhlanhla Mnyandu
Director, iSu Technologies (Pty) Ltd
nhlanhla@isutech.co.za | [Mobile Number]

Attachments:
- SANSA Partnership Investment Framework.pdf
- Platform Feature Summary.pdf

Handling Specific Responses

Response: “Budget is limited”

Dear [Name],

Thank you for sharing your budget constraints - I appreciate the transparency.

We're committed to finding an approach that works within SANSA's reality. A few options to consider:

1. Phased Implementation: Start with core workshop management (lower investment), add analytics and ML features in Year 2

2. Pilot Scope: Launch with 2-3 provinces initially, prove value, then expand with subsequent budget

3. Payment Structure: Spread investment across two financial years (60% Year 1, 40% Year 2)

Would it be helpful to discuss what's achievable within [their stated range]? I can prepare a scaled proposal that delivers maximum value within your constraints.

Let me know how you'd like to proceed.

Kind regards,
Nhlanhla

Response: “We need to go to tender”

Dear [Name],

Thank you for clarifying the procurement requirement - this is completely appropriate for an investment of this scale.

We're tender-ready:
- Registered on Central Supplier Database (CSD)
- B-BBEE compliant
- Can provide all required documentation

How we can help:
1. Provide technical specifications you can use in the tender document
2. Participate in any briefing sessions
3. Submit a comprehensive tender response

Would it be helpful if I prepared a technical specification document that outlines the platform requirements? This could assist your team in drafting the tender.

Please let me know the expected tender timeline and process, and we'll prepare accordingly.

Kind regards,
Nhlanhla

Response: “We’re talking to other vendors too”

Dear [Name],

That's absolutely appropriate for a decision of this importance - you should explore all options.

What I'd ask is this: how many of those vendors will show you working software before you commit?

Our approach is different:
- We build first, then present
- You've seen our prototype - it exists today
- If you proceed, we deploy - we don't start from scratch
- This means faster implementation and lower risk

We're confident in our capability because you've already seen it in action. We welcome the comparison.

Please let me know if you need any additional information for your evaluation process.

Kind regards,
Nhlanhla

Response: “Timeline has shifted to Q2/Q3”

Dear [Name],

Thank you for the update on timing. We're flexible and will work around SANSA's schedule.

This extended timeline actually provides some advantages:
1. More time for thorough requirements gathering
2. Opportunity to refine the prototype based on your feedback
3. Better alignment with budget cycles

Would you like to:
A) Pause until you're ready to re-engage (we'll reach out in [month])
B) Continue discovery discussions now so we're ready to move quickly when budget is approved
C) Keep in touch with monthly updates on our progress

Please let me know your preference. We'll be here when you're ready.

Kind regards,
Nhlanhla

Email Formatting Guidelines

Professional Standards

Subject Lines: Clear, specific, professional (no emojis, no ALL CAPS)
Greeting: “Dear [Name]” - formal but warm
Body: Short paragraphs, bullet points for lists, clear structure
Closing: “Kind regards” (professional), “Best regards” (slightly warmer)
Signature: Full professional signature with all contact details

Timing Guidelines

Day	Best Send Time	Reason
Tuesday	09:00 - 10:00	Fresh week, before meetings
Wednesday	09:00 - 10:00	Mid-week productivity
Thursday	09:00 - 11:00	Before Friday wind-down

Avoid:

Monday (inbox overload)
Friday afternoon (ignored until Monday)
After 16:00 (end of day)

Follow-Up Cadence

Situation	Wait Before Follow-Up
Initial email	5-7 business days
Discovery call request	5 business days
Post-meeting	24-48 hours (thank you)
Proposal sent	7-10 business days
Contract negotiation	3-5 business days

Pre-Send Checklist

Before sending any email:

Attachments actually attached
Names spelled correctly (Dan Matsapola, Thandile Vuntu)
Dates and times correct (check calendar)
Mobile number included in signature
PDF/document properly formatted
Subject line clear and professional
Proofread for typos
BCC yourself for records

Email templates prepared for January 2026 re-engagement Use formal email communication - avoid WhatsApp for initial business contact