Certainly! Below is a clear and professional write-up for the Neftaly Prototype/MVP section, detailing expectations for prototype or MVP submissions. This can be used in Neftaly’s competition guidelines, submission instructions, or innovation programme briefs.
Neftaly Development Royalty
Innovation Prototyping & Technical Evaluation Unit
Section: Neftaly Prototype / MVP Submission
Theme: From Concept to Creation – Demonstrate What You’ve Built
Neftaly Prototype / MVP
If Applicable, Participants Must Submit a Working Prototype or MVP (Minimum Viable Product)
To demonstrate the feasibility and functionality of proposed solutions, Neftaly requires all applicable participants to submit a working prototype or MVP (Minimum Viable Product) as part of their project submission. This practical demonstration showcases the real-world potential of the innovation and provides judges with evidence of its development stage.
???? What is a Prototype or MVP?
- A prototype is a physical or digital model that simulates the function, design, or interaction of the final product.
- An MVP is a simplified version of the product with enough features to be tested by users or demonstrate its core function.
⚙️ Applicable Project Types
Prototype or MVP submission is required for:
- Technology, hardware, or engineering projects
- Software, mobile app, or digital tool innovations
- Any solution involving physical devices, platforms, or tangible outputs
For conceptual projects, clear visual models or simulations may be accepted in place of a working unit.
✅ Submission Requirements
Participants must provide one or more of the following, depending on project type:
For Physical Prototypes:
- Photos of the prototype from different angles
- Demonstration video showing how it works
- Schematics or blueprints (optional but encouraged)
- Description of key materials and how it was built
For Digital/Software MVPs:
- Live demo link (web/mobile app, software dashboard, etc.)
- Executable file or download link (APK, EXE, etc.)
- Screenshots and system architecture diagrams
- GitHub or code repository (if open-source)
For Simulation-Based Models:
- Video walkthrough of simulation
- Model file or dataset
- Explanation of parameters and results
???? Format & File Guidelines
- File types: MP4 (video), PDF (visuals), ZIP (bundled files), URL (demo links)
- File size limit: 100MB per file
- Naming convention:
[TeamName]_[ProjectTitle]_Prototype.zip - Ensure all files are clearly labeled and accessible
???? Evaluation Criteria
| Category | What Judges Will Assess |
|---|---|
| Functionality | Does the prototype/MVP demonstrate key features effectively? |
| Usability & Design | Is it easy to understand, use, or navigate? |
| Technical Soundness | Is it built with appropriate tools, methods, or coding practices? |
| Innovation & Impact | Does it successfully reflect the intended solution and benefits? |
???? Best Practices
- Test your prototype thoroughly before submission
- Use captions or narration in videos to explain functionality
- If submitting an app, ensure the link is public or provide access credentials
- Clearly describe what’s functional vs. in development
???? Need Technical Support or Review?
Neftaly’s Prototype Review Team can assist with testing, feedback, or submission formatting.
???? prototype@saypro.online
???? www.saypro.online
???? +27 (0) 87 265 0012
Neftaly – Show Us What You’ve Built. Prove Your Potential.
Would you like this as a checklist, submission guide PDF, or editable form for entrants?