NSF Skills Development Platform - Action Plan

Date Created: November 23, 2025 Opportunity: Monitoring & Reporting Platform for NSF-Funded Skills Development Organizations Market Validation: CONFIRMED - High urgency, minimal competition

Phase 1: Discovery & Validation (Weeks 1-2)

Week 1: Deep Dive with Your Contact

Meeting 1: Excel Templates & Data Analysis

Objectives:

Obtain actual Excel templates used by NSF-funded organizations
Understand current data structure and workflow
Identify pain points and failure modes

Questions to Ask:

1. About the Excel Templates:

Can you share the actual Excel templates organizations use for NSF reporting?
What are the different tabs/sheets in these templates?
How many data fields are tracked per learner?
What formulas/calculations are built in?
How often are these templates updated?

2. About the Workflow:

Walk me through a typical reporting cycle from start to finish
Who enters the data (roles/titles)?
How many people touch the spreadsheet in one reporting cycle?
How is data validated before submission?
What happens when errors are found?

3. About Pain Points:

What are the top 3 reasons organizations miss reporting deadlines?
Can you share examples of compliance failures due to poor tracking?
How much time per month do organizations spend on manual reporting? (hours/days)
What are the most common data errors or issues?
Have any organizations lost funding due to reporting failures?

4. About NSF’s Monitoring:

What does NSF actually check when reviewing reports?
How often does NSF request updates from funded organizations?
What triggers NSF to flag a project as “at risk”?
What data does NSF struggle to get from organizations?

Deliverables from Meeting:

Copy of Excel templates (anonymized if needed)
Sample reports organizations submit to NSF
List of common compliance violations
Timeline of typical project lifecycle

Meeting 2: Stakeholder Mapping & Market Access

Objectives:

Understand decision-making structure in funded organizations
Identify target customer profile
Map network for pilot customers

Questions to Ask:

1. Organization Profiles:

What types of organizations did you work with most? (NPOs, NGOs, private providers, cooperatives)
What’s the typical size? (staff count, budget, number of learners)
Which organizations struggle most with current Excel system?
Which organizations would be most eager for a solution?

2. Decision-Making:

Who decides to purchase new systems in these organizations? (CEO, Finance Director, Project Manager)
What’s the typical approval process for software purchases?
What budget range do they have for operational tools?
Do they prefer monthly subscriptions or annual licenses?

3. Buying Triggers:

What would make an organization urgently need this solution? (audit, funding loss, expansion)
Are there seasonal buying patterns? (before April 30 deadline, after funding awards)
What would be the #1 feature that would make them say “we need this NOW”?

4. Network & Introductions:

Can you introduce me to 3-5 organizations currently using Excel for NSF reporting?
Which organizations would be good pilot partners? (willing to test, provide feedback)
Are there any industry associations or forums where these organizations meet?
Do you maintain relationships with former colleagues at NSF who could provide insights?

Deliverables from Meeting:

List of 10-15 potential pilot organizations with contact details
Stakeholder map (decision-makers, users, influencers)
Budget range expectations
Introduction to 3-5 organizations for interviews

Meeting 3: Competitive Landscape & Positioning

Objectives:

Understand what solutions organizations have tried
Identify differentiation opportunities
Validate pricing assumptions

Questions to Ask:

1. Current Alternatives:

Do organizations use any software currently? (MYCITO, Learnership Tracking, etc.)
Why are they still using Excel despite these options?
What do existing solutions fail to address?
Have organizations built custom Access databases or other homegrown solutions?

2. NSF’s Technology Plans:

What do you know about NSF’s delayed ICT system?
When it launches, what will it require from organizations?
Will it replace what organizations do, or supplement it?
Are SETAs planning similar systems?

3. Pricing Intelligence:

What do organizations currently pay for software/systems? (LMS, accounting, etc.)
What would be considered “cheap” vs “expensive” for this type of tool?
Would they pay per learner, per project, or flat subscription?
Is there budget allocated for “compliance” or “reporting” tools?

4. Value Proposition Testing:

If I said “never miss a compliance deadline again,” is that compelling?
If I said “reduce reporting time by 80%,” would they care?
If I said “increase grant success rate,” is that valuable?
What benefit would make them switch from Excel tomorrow?

Deliverables from Meeting:

Competitive analysis grid
Feature prioritization (must-have vs nice-to-have)
Pricing model recommendations
Positioning statement draft

Week 2: Customer Discovery Interviews

Target: Interview 5 NSF-funded organizations currently using Excel

Interview Script Structure:

A. Current State (10 min)

Tell me about your organization and the programmes you run
How many learners/beneficiaries do you currently support?
What funding sources do you manage? (NSF, SETA, other)
Walk me through your current reporting process

B. Pain Points (15 min)

What’s the hardest part about NSF/SETA reporting?
Have you ever missed a deadline? What happened?
How much time do you spend on reporting each month?
What keeps you up at night about compliance?
Can you share an example of when the Excel system failed you?

C. Ideal Solution (10 min)

If you had a magic wand, what would the perfect system do?
What features would make your life dramatically easier?
How would you measure success of a new system?
What would prevent you from adopting a new system?

D. Buying Process (10 min)

Who would need to approve purchasing a new system?
What’s your budget for operational software?
When do you make purchasing decisions? (time of year)
Would you be interested in piloting a solution if it solved your top 3 pain points?

E. Network Effect (5 min)

Do you know other organizations with similar struggles?
Would you be willing to introduce us if the pilot goes well?
Are there forums/associations where you discuss these challenges?

Deliverables:

5 completed interview summaries
Pain point frequency analysis
Feature demand ranking
2-3 committed pilot partners

Phase 2: Solution Design (Weeks 3-4)

Data Model Mapping

Input: Excel templates from contact Activities:

Map all data fields across templates
Identify relationships (learner → project → funder → reports)
Design normalized database schema
Plan data migration strategy from Excel

Deliverables:

Entity-relationship diagram
Database schema (initial)
Data dictionary
Excel import specification

MVP Feature Definition

Based on Research + Interviews, Define:

Core Module 1: Learner Management

Learner registration (demographics, eligibility)
Enrollment in programmes/projects
Progress tracking (milestones, attendance)
Document storage (ID, certificates, agreements)

Core Module 2: Project/Programme Tracking

Project setup (funding source, budget, timeline)
WBLPA generation
Milestone tracking
Deliverable management
Budget vs actual spend

Core Module 3: Compliance Dashboard

Deadline tracker (WSP, ATR, NSF reports, NPO annual reports)
Alert system (30 days, 14 days, 7 days before deadline)
Compliance status (green/yellow/red by requirement)
Missing data indicators

Core Module 4: Reporting Engine

NSF narrative report generation
NSF financial report generation
Export to Excel (for SETA portal uploads)
Pre-filled WSP/ATR templates
Custom report builder

Deferred for Later:

Full SETA portal integration (start with export)
QCTO assessment scheduling
Mobile app (start with responsive web)
Advanced analytics/AI
Multi-stakeholder portals

Deliverables:

MVP feature list with acceptance criteria
User stories (as a Project Manager, I want to…)
Wireframes for key screens
Technical architecture diagram

Prototype Development

Tool Options:

Figma for clickable prototype (no code)
Bubble.io for functional prototype (low code)
Custom build (if development team ready)

Screens to Prototype:

Dashboard (compliance status, upcoming deadlines, project overview)
Learner registration form
Project setup wizard
Report generation interface
Alert/notification center

Deliverables:

Clickable prototype (Figma/Bubble)
Demo script (5-minute walkthrough)
Feedback collection form

Phase 3: Validation & Pilot (Weeks 5-8)

Prototype Testing

Test with:

Your contact (expert validation)
3-5 interview participants
1-2 new organizations (fresh eyes)

Test Scenarios:

“You just enrolled 20 new learners. Show me how you’d enter them.”
“NSF WSP deadline is in 2 weeks. Generate the report.”
“Find all learners who haven’t attended in 30 days.”
“Your audit is tomorrow. Show me proof of compliance.”

Collect:

Usability feedback (can they complete tasks?)
Feature feedback (what’s missing? what’s unnecessary?)
Pricing feedback (show pricing options, gauge reactions)
Commitment (would you use this if available today?)

Deliverables:

Test results summary
Revised feature list
Updated wireframes
Pilot agreement with 2-3 organizations

Pilot Programme Design

Duration: 3 months

Pilot Partners: 2-3 organizations (different profiles)

1 small NPO (< 100 learners, single NSF project)
1 medium NGO (100-500 learners, multiple projects)
1 private training provider (if possible)

Success Criteria:

Reduce reporting time by 50%+ (measure before/after)
Zero missed deadlines during pilot
100% data migration from Excel
User satisfaction score > 4/5
Willingness to pay validated

Support Model:

Weekly check-in calls
Dedicated Slack/WhatsApp channel
Onboarding training (2 sessions)
Unlimited support during pilot

Deliverables:

Pilot agreement template
Onboarding checklist
Training materials
Success metrics tracking sheet

Phase 4: Build & Launch (Months 3-6)

Technology Stack Recommendation

Option A: Speed to Market (Recommended for MVP)

Frontend: Next.js + React + Tailwind CSS
Backend: Supabase (PostgreSQL + Auth + Storage)
Hosting: Vercel
Why: Fast development, low cost, scales well, modern stack

Option B: Enterprise-Grade

Frontend: Next.js + React
Backend: Node.js + Express + PostgreSQL
Hosting: AWS/Azure
Why: More control, better for government tenders later

Option C: Low-Code

Platform: Bubble.io or Retool
Why: Fastest to market, no dev team needed initially
Tradeoff: Less customization, harder to scale

Recommendation: Start with Option A (Supabase stack) for MVP, migrate to Option B when securing government contracts.

Development Phases

Sprint 1-2 (Weeks 1-4): Foundation

User authentication & authorization
Organization/project setup
Learner registration & management
Basic dashboard

Sprint 3-4 (Weeks 5-8): Compliance Core

Deadline tracking system
Alert/notification engine
Document management
Compliance status dashboard

Sprint 5-6 (Weeks 9-12): Reporting

NSF report templates
WSP/ATR pre-fill
Excel export functionality
Custom report builder

Sprint 7-8 (Weeks 13-16): Polish & Pilot Prep

UI/UX refinement
Onboarding flow
Help documentation
Excel import tool

Deliverables:

Working MVP application
User documentation
Admin documentation
Pilot launch plan

Go-to-Market Strategy

Phase 1: Pilot Success Stories (Months 3-6)

Document time savings, compliance improvements
Video testimonials from pilot partners
Case studies with metrics
Referrals from pilot partners

Phase 2: Network Expansion (Months 6-9)

Leverage contact’s network
Present at NPO/skills development forums
Content marketing (blog posts on compliance tips)
LinkedIn thought leadership

Phase 3: SETA Partnerships (Months 9-12)

Approach SETAs with pilot results
Offer white-label version for SETA portfolios
Attend SETA events and conferences
Build integrations with SETA portals

Phase 4: Government Tender (Year 2)

Position for NSF’s ICT system integration
Respond to SETA RFPs
Partner with larger IT firms for government contracts

Business Model Options

Option 1: Tiered SaaS Subscription

Starter (Small NPOs): R2,500/month

Up to 100 active learners
2 users
Basic reporting
Email support

Professional (Medium Organizations): R7,500/month

Up to 500 learners
5 users
Advanced reporting
Multi-project management
Priority support

Enterprise (Large Providers): R15,000/month+

Unlimited learners
Unlimited users
Custom integrations
Dedicated account manager
API access

Annual Discount: 15% off (2 months free)

Option 2: Per-Learner Pricing

R50 per active learner/month

Simple, transparent pricing
Scales with organization size
No feature restrictions
All users included

Example:

100 learners = R5,000/month
250 learners = R12,500/month
1,000 learners = R50,000/month

Option 3: Hybrid Model (Recommended)

Base Platform Fee: R1,500/month

Covers up to 50 learners
Core features included

Plus: R30 per additional learner/month

Scales affordably
Predictable for small orgs
Grows with large orgs

Example:

50 learners = R1,500/month
200 learners = R1,500 + (150 × R30) = R6,000/month
500 learners = R1,500 + (450 × R30) = R15,000/month

Add-ons (Optional):

Advanced Analytics: +R1,000/month
White-label Reports: +R500/month
API Access: +R2,000/month
Dedicated Support: +R3,000/month

Option 4: Success-Based (Alternative)

No Monthly Fee 15% of grants successfully claimed

Pros:

Aligns incentives perfectly
Easy adoption (no upfront cost)
High revenue potential

Cons:

Revenue unpredictable
Requires financial data access
Complex billing

Recommendation: Offer as alternative to monthly pricing for risk-averse NPOs.

Financial Projections (Conservative)

Year 1 Assumptions

3-month pilot with 3 organizations (free)
Launch Month 4
Acquire 2 customers/month (Months 4-12 = 18 customers)
Average: R5,000/month per customer
Churn: 10% annually

Year 1 Revenue:

Month 4: 2 × R5,000 = R10,000
Month 5: 4 × R5,000 = R20,000
Month 6: 6 × R5,000 = R30,000
…
Month 12: 18 × R5,000 = R90,000

Year 1 Total MRR: ~R540,000 (R45,000 average MRR)

Year 2 Assumptions

Acquire 5 customers/month (network effects + marketing)
Average increases to R7,500/month (larger orgs)
Churn: 8%

Year 2 Total ARR: ~R2.5 million

Year 3 Assumptions

SETA partnership secured
10 customers/month
Average: R10,000/month
Enterprise customers: 5 at R25,000/month each

Year 3 Total ARR: ~R8 million

Investment Requirements

Bootstrap Option (Recommended Initially)

Months 1-2 (Discovery): R0

Your time + contact’s expertise
No paid tools needed yet

Months 3-4 (Prototype): R15,000

Figma Pro: R300/month × 2
Domain + hosting: R500
Bubble.io (if used): R2,000/month × 2
Contingency: R10,000

Months 5-8 (MVP Development): R120,000

Developer (contract): R15,000/month × 6 months = R90,000
Designer (contract): R5,000/month × 2 months = R10,000
Infrastructure (Supabase, Vercel): R1,000/month × 4 = R4,000
Tools/licenses: R6,000
Contingency: R10,000

Months 9-12 (Pilot & Launch): R80,000

Developer: R15,000/month × 3 = R45,000
Marketing: R10,000
Sales materials: R5,000
Events/networking: R10,000
Contingency: R10,000

Total Year 1 Investment: ~R215,000

Funded Option (If Seeking Investment)

Seed Round: R1.5 million

Development team (2 devs, 1 designer): R900,000
Marketing & sales: R300,000
Operations: R200,000
Contingency: R100,000

Use of Funds:

Faster time to market (3 months vs 6 months)
Hire full-time team
Aggressive customer acquisition
Build advanced features sooner

Risk Mitigation Strategies

Risk 1: NSF Launches Their Own System

Probability: Medium (delayed since Jan 2024, government IT projects notoriously slow)

Mitigation:

Position as complementary to NSF system (we manage, they monitor)
Build integration capabilities
Expand to SETA market (larger than NSF)
If NSF system is provider-facing, we focus on internal management

Risk 2: Low Adoption (Excel Habits)

Probability: Medium (change management is hard)

Mitigation:

Freemium model for first 3 months
Excel import tool (easy migration)
Show compliance risk/audit failures
Use April 30 deadline pressure as urgency driver
Video testimonials from early adopters

Risk 3: Price Sensitivity (NPO Budgets)

Probability: High (NPOs are cost-conscious)

Mitigation:

Tiered pricing with affordable entry point
Success-based pricing option
Show ROI (time saved = staff cost savings + grant success)
Annual discounts
Pilot proves value before asking for payment

Risk 4: Regulatory Changes

Probability: High (QCTO just changed, more changes likely)

Mitigation:

Modular architecture (easy to update)
Configuration-driven compliance rules (no code changes)
Advisory board of compliance experts
Charge for major regulatory updates as add-on service

Success Metrics & KPIs

Discovery Phase (Weeks 1-2)

5+ customer interviews completed
3+ Excel templates analyzed
2+ pilot partners committed
Clear MVP feature list defined

Design Phase (Weeks 3-4)

Prototype tested with 5+ users
80%+ positive feedback on core features
Pricing validated (willingness to pay confirmed)
Data model finalized

Build Phase (Months 3-6)

MVP launched on time
3 pilot organizations onboarded
Zero critical bugs
90%+ pilot satisfaction score

Launch Phase (Months 6-12)

Immediate Next Steps (This Week)

Monday

Schedule Meeting 1 with contact (Excel templates deep dive)
Create interview guide for customer discovery
Set up project folder structure

Tuesday

Conduct Meeting 1 with contact
Begin analyzing Excel templates
Draft stakeholder map

Wednesday

Schedule Meeting 2 with contact (stakeholder mapping)
Request introductions to 5 potential interview candidates
Create competitive analysis grid

Thursday

Conduct Meeting 2 with contact
Schedule customer interviews for next week
Draft positioning statement

Friday

Conduct Meeting 3 with contact (competitive landscape)
Compile week 1 findings
Prepare interview materials for week 2
Create Figma account and start wireframe exploration

Decision Points

Go/No-Go Criteria After Discovery (Week 2)

GO if:

3+ organizations commit to pilot
Pain point is validated (real, urgent, expensive)
Willingness to pay confirmed at R3,000+ per month
No major technical blockers identified
Contact remains engaged and supportive

NO-GO if:

Organizations satisfied with Excel (pain not urgent)
Budget constraints make pricing unviable
NSF system launching imminently and comprehensive
Regulatory complexity too high for MVP timeline

Resources & Tools Needed

Week 1-2

Google Docs (interview notes)
Spreadsheet (tracking interviews, feature requests)
Calendar tool (scheduling)
Video conferencing (Zoom/Teams)

Week 3-4

Figma (prototyping)
Miro/FigJam (user journey mapping)
Notion (project documentation)

Month 3+

GitHub (code repository)
Supabase account
Vercel account
Project management tool (Linear/Jira)

Team Requirements

Phase 1-2 (Discovery & Design): Solo + Contact

You: Project lead, customer interviews, business model
Contact: Domain expert, introductions, validation

Phase 3 (MVP Development): Small Team

Full-stack developer (contract or hire): Build core platform
UI/UX designer (contract): Wireframes, visual design
You: Product management, customer success, sales

Phase 4+ (Scale): Core Team

2× Developers (full-time)
1× Customer Success Manager
1× Sales/Marketing
You: CEO/Product
Contact (advisory or co-founder if interested)

Partnership Opportunities

Strategic Partners to Explore

1. Accounting/ERP for NPOs

Partner with Sage, Pastel, QuickBooks resellers
Bundle offering (financial + compliance)

2. Skills Development Consulting Firms

White-label for their clients
Revenue share model
They sell, we provide platform

3. SETAs (Later)

White-label for SETA portfolio monitoring
Government tender partnerships

4. NPO Associations

NASCEE (National Association for Skills Development)
Regional NPO forums
Bulk licensing deals

Contingency Plans

If Pilot Fails

Pivot to consulting (manual WSP/ATR preparation)
Use software internally for consulting efficiency
Learn deeply, rebuild with insights

If Funding Needed

Bootstrap to pilot success
Use pilot metrics for investor pitch
Apply for government innovation grants
Contact as potential co-founder/investor

If Competition Emerges

Focus on NSF niche (they may go broad)
Superior UX as differentiator
Faster feature development
Better customer support

Next Review Date: End of Week 2 (after customer interviews) Decision Point: Go/No-Go for prototype development Success Indicator: 3+ pilot commitments + validated willingness to pay

This is a living document. Update weekly as you learn more.