[NDA] – Building a Custom MVP Team for a US-Based EdTech Startup

[NDA] – Building a Custom MVP Team for a US-Based EdTech Startup

Industry: EdTech / Online Learning Market: United States Engagement model: Outstaffing Client type: Early-stage startup validating its product concept

---

MVP Goal

To validate whether users find it convenient to go through micro-learning modules, track their progress, and interact with instructors in real time.

---

What Osmium Did

We assembled a tailored MVP team within days, selecting specialists based on the project’s complexity and time-to-market priorities. All team members were mid- or senior-level professionals.

Team composition:

• Business Analyst – Full-time for the first month, then part-time
• Backend Developer (Node.js) – Full-time
• iOS Developer (Swift) – Full-time
• UI/UX Designer – 1.5 months full-time
• Manual QA Engineer – Part-time first month, full-time from then on

---

Tech Stack

• Backend: Node.js
• Mobile Frontend: Swift (iOS)
• Infrastructure: AWS

---

Development Focus

The MVP was designed with the following priorities:

• Fast and responsive interface
• Intuitive UX for non-technical users
• Secure storage of personal and academic data

The team delivered a highly functional learning platform that included:

• Modular courses across various subjects
• User programs, milestones, feedback, and quiz features
• Communication between students and instructors
• A knowledge base with personalized course recommendations
• Monetization features (paid courses, subscriptions, in-app payments)

---

Timeline

The full cycle—from assembling the team to MVP launch—took 4 months. The platform required multiple user portals (student, teacher, admin) and complex billing features, which added to the challenge.

---

Outcome

• Launch date: February 2025
• Adoption: Over 300 active users within the first month, driven by a strong marketing campaign and a pragmatic MVP-first mindset
• Feedback: Users shared valuable insights—some critical, some confirming usability—which helped prioritize the next steps
• Next steps: Scale infrastructure, add core features, launch a web version, and expand the team to support growing demand