1-1 Skill Mentoring Platform
SkillHop
A concept-stage startup case study translating an EdTech opportunity into a two-sided mentor marketplace, MVP scope, learner journey, and validation plan.
At a glance
- Role
- Project Lead, Learner Experience Designer, Business Model Contributor
- Team
- 5 members, Group 16
- Context
- Entrepreneurship course
- Stage
- Business concept and interactive prototype
Product thesis
SkillHop explores the space between scalable but impersonal video courses and highly personal but fragmented one-off mentoring calls.
My contribution
I led the team, designed the learner-facing experience, and contributed to service definition, market analysis, revenue projections, refinement, and presentation.
Evidence boundary
This is a concept-stage startup case study. It separates documented material, product hypotheses, and future validation work.
01 · Startup context
SkillHop began as a startup brief, not a conventional UX project.
Our team explored whether short, live mentoring sessions could occupy the space between asynchronous course platforms and fragmented one-off calls arranged through video and community tools. The case study focuses on how a broad EdTech opportunity became a two-sided marketplace concept, an MVP, and a learner journey.
Opportunity
Recorded courses scale, but they do not respond to the learner's immediate context.
Marketplace model
The product had to serve both demand and supply.
Portfolio role
This case is about 0 to 1 product strategy.
- 2
- Marketplace sides
- 3
- Prototype roles
- 5
- Team members
- 0-1
- Case focus
Learner demand and mentor supply
Guest, learner, and mentor
Academic startup group
Product strategy and MVP thinking
02 · Problem framing
The gap was not access to content. It was access to timely feedback.
Recorded courses are scalable and affordable, but they cannot respond to a learner's specific blocker. Direct mentor calls are personal, but discovery, trust, scheduling, payment, learning tools, and follow-up are often scattered across separate platforms.
Positioning
Live learning gap
Asynchronous
Live
Asynchronous + structured
Udemy / Coursera
Live + self-organized
Zoom / Meet + groups
Live + structured, language-focused
Preply / Cambly
Live + structured, multi-skill mentoring
SkillHop
Evidence
Insight
Design response
SkillHop is not a video-call feature wrapped in an EdTech interface.
03 · Assumptions
The honest version separates evidence from hypotheses.
Because the original project did not include completed primary user research or a live-market pilot, the case study should not pretend that behavior was validated. Its credibility comes from being precise about what was documented, hypothesized, and still untested.
Documented
- Startup brief
- Competitor landscape
- Market segmentation
- Product and service model
- MVP definition
- Three-role prototype
Hypothesized
- Learners will pay for short live sessions
- Vietnamese mentors can create enough differentiation
- Mentors will maintain reliable availability
- Integrated tools improve learning outcomes
Not validated
- Booking conversion
- Willingness to pay
- Mentor supply
- Session usefulness
- Repeat booking
- Retention
| Weak claim | Better wording | Why it matters |
|---|---|---|
| Research showed learners need short sessions. | We hypothesized that learners would value short live sessions for specific goals. | It avoids claiming primary research that was not completed. |
| We validated the market. | Market reports indicated a relevant category and adjacent alternatives. | Market size does not prove willingness to pay. |
| The design improved booking. | The booking design aimed to reduce coordination uncertainty. | The prototype was not tested against live conversion. |
04 · Product model
A mentoring marketplace has to create trust on both sides.
SkillHop cannot work as a single-user learning app. Every learner decision creates a mentor obligation, and every mentor service has to be understandable enough for a learner to compare and book.
Learner
Needs fast, relevant guidance.
Mentor
Needs clients, tools, and reputation.
Learner
Search, compare, book, learn, review
SkillHop
Matching, trust, scheduling, payment, session infrastructure
Mentor
Create services, set availability, teach, follow up, earn
Marketplace flywheel
Trust compounds into liquidity.
- 01
More relevant mentors
- 02
Better matching
- 03
More completed sessions
- 04
More credible reviews
- 05
Greater learner trust
- 06
More bookings and mentor earnings
| Side | Gives | Receives |
|---|---|---|
| Learner | Payment, time, context, preparation, and feedback. | Expertise, guidance, confidence, and next steps. |
| Mentor | Expertise, availability, preparation, and follow-up. | Income, audience, reputation, and personal brand. |
05 · Focus
The first market should be narrower than the full vision.
The business plan named several learner segments and mentor types. For a stronger startup narrative, I reframed the first launch wedge around final-year students and early-career professionals facing near-term career milestones.
Launch wedge
Career milestone sessions.
Final-year students and early-career professionals have clear deadlines, practical problems, and a strong reason to pay for targeted feedback.
Service 01
Mock interview
Service 02
CV review
Service 03
Portfolio critique
Service 04
Code review
Service 05
Career consultation
Service 06
English interview practice
06 · Strategy
The product problem became a tree of risky assumptions.
The desired outcome is not total accounts or page views. SkillHop first needs more useful completed mentor sessions per active learner, then evidence that learners want to return.
Desired outcome
More useful completed mentor sessions per active learner.
Opportunity 1
Learners struggle to identify the right mentor
- Goal-based search
- Service-specific listings
- Mentor comparison
- Verified expertise
Opportunity 2
Booking requires too much coordination
- Live availability
- Duration options
- Clear timezone
- Immediate status feedback
Opportunity 3
Learners are uncertain about quality
- Verified profiles
- Structured reviews
- Completed-session count
- Clear service outcomes
Opportunity 4
Continuity disappears after the call
- Session summary
- Shared notes
- Recommended next step
- Follow-up booking
07 · Prioritization
The MVP should prove the transaction, not implement every EdTech feature.
The original vision included video, group classes, whiteboard, notes, recording, chat, community, AI, subscriptions, advertising, B2B, and native apps. I reorganized that ambition into Now, Next, and Later so the startup can learn before adding operational weight.
Now
Prove the transaction
- Mentor profile and service
- Goal-based discovery
- Availability and booking
- Booking confirmation
- Basic video session
- Post-session summary
- Reviews
Next
Improve the learning experience
- Shared notes
- Whiteboard
- Screen sharing
- Session packages
- Progress tracking
- Rescheduling and refunds
Later
Expand the ecosystem
- AI chatbot
- Complex community
- Group classes
- Recording library
- B2B marketplace
- Advertising products
The MVP should prove that a learner can find the right mentor, complete a useful session, and want to book again.
08 · Core flow
One scenario keeps the product story from becoming a screen gallery.
Minh has a technical interview in five days. He needs a 45-minute mock interview with a senior backend engineer who is available after work. The case study follows him from goal definition to rebooking.
- 01
Define a goal
- 02
Discover mentor services
- 03
Compare expertise, price, and availability
- 04
Select a session
- 05
Book and prepare
- 06
Join the live session
- 07
Receive a recap
- 08
Review or rebook
- 01
Make the goal explicit
The discovery flow starts from the learner's outcome, not a generic list of people.
- 02
Compare services instead of profiles alone
A mentor card should package expertise into a service with audience, outcome, duration, price, and availability.
- 03
Close the loop after the call
A recap, action items, resources, review, and follow-up booking turn a call into a learning relationship.
09 · Deep dive
Learners are not looking for a person. They are looking for an outcome.
A marketplace can easily collapse into name, job title, rating, and price. SkillHop needed service-specific listings so learners could understand what problem the mentor could solve tonight.
Nguyen An - Senior Backend Engineer
45-minute Backend Mock Interview
Linh Tran - Technical Recruiter
CV Review for Junior Developers
Minh Pham - Product Designer
Portfolio Critique Sprint
Evidence
Insight
Design response
10 · Deep dive
Booking has to distinguish requested from confirmed.
The MVP plan described learners choosing from mentor availability and sending a request for mentor confirmation. If the interface treats that as a completed booking too early, it creates coordination anxiety and false certainty.
Booking card
Backend Mock Interview
Nguyen An, Senior Backend Engineer. GMT+7, Ho Chi Minh City.
Session type
Available times
Requested is not confirmed.
The learner should see the booking request state until the mentor accepts or the request expires.
- 1Draft
- 2Requested
- 3Confirmed
- 4Session started
- 5Completed
- 6Reviewed
| Question | Design response | Risk reduced |
|---|---|---|
| What am I booking? | Show service name, mentor, duration, outcome, and preparation brief. | Poor fit |
| Is it confirmed? | Use explicit Requested, Confirmed, Rescheduled, Cancelled, and Completed states. | False expectations |
| What happens next? | Show timezone, payment timing, cancellation policy, and pre-session checklist. | Coordination anxiety |
11 · Deep dive
The live session is before, during, and after the call.
The case should not present video call as the innovation by itself. The product value comes from helping the learner prepare, stay oriented during the session, and leave with usable next steps.
Before
Prepare the context
- Learning goal
- Questions
- Files or links
- Device check
- Recording consent
During
Keep the session oriented
- Video
- Screen sharing
- Shared notes
- Agenda
- Remaining time
After
Turn the call into next steps
- Mentor summary
- Action items
- Resources
- Review
- Follow-up booking
12 · Supply experience
Mentors should package expertise into services, not vague profiles.
The mentor side was not my sole design ownership, so it stays secondary. It is still strategically important because marketplace supply quality determines whether learner discovery can work.
Mentor service journey
Supply has to be productized.
- 01
Create profile
- 02
Package expertise into a service
- 03
Set price and availability
- 04
Receive booking request
- 05
Review learner brief
- 06
Conduct session
- 07
Share recap
- 08
Receive payment and review
13 · Quality
Trust is a product surface, not a policy appendix.
Mentoring marketplaces carry risks: false expertise, no-shows, poor fit, recording concerns, disputes, biased reviews, and off-platform leakage. The interface has to make the quality system visible before the learner pays.
| Risk | Learner concern | Product response |
|---|---|---|
| False expertise | The mentor may not be qualified. | Verified identity, verified expertise, evidence links, and completed-session count. |
| No-show | The learner loses time and money. | Reminders, request expiry, cancellation windows, refund rules, and visible response time. |
| Poor fit | The session may not solve the expected problem. | Service scope, preparation brief, expected outcome, and private quality report. |
| Review quality | Ratings may be misleading. | Completed-session-only reviews, review distribution, and report controls. |
14 · Monetization
Monetization should be treated as a design constraint.
The original plan included learner premium, mentor plans, featured placement, business advertising, and B2B opportunities. In a case study, this works best as a set of monetization hypotheses rather than a full pricing catalogue.
Hypothesis
Mentor subscription
User value
Better tools and visibility
UX risk
Pay-to-rank may reduce trust
Hypothesis
Learner premium
User value
Notes, recordings, and advanced tools
UX risk
Core learning may feel artificially restricted
Hypothesis
Featured placement
User value
More mentor exposure
UX risk
Search relevance may be compromised
Hypothesis
Business ads
User value
Additional revenue
UX risk
Ads may distract from learner goals
Hypothesis
B2B services
User value
Employee learning
UX risk
Expands scope too early
15 · Measurement
The north star is useful completed mentor sessions.
The business plan used AARRR for marketing. For product strategy, I reframed it as a measurement system for the learner, mentor, and marketplace loops.
North-star metric
Useful completed mentor sessions per active learner per month.
Learner
- Time to relevant mentor
- Profile-to-booking conversion
- Show-up rate
- Helpfulness score
- Repeat booking
Mentor
- Time to first service
- Request acceptance rate
- Calendar utilization
- No-show rate
- Repeat learners
Marketplace
- Match rate
- Time to match
- Completed-session rate
- Supply-demand ratio
- Dispute rate
16 · Validation plan
A concierge pilot can test the marketplace before full automation.
The plan proposed testing the MVP over about two months with 100 to 200 target users through school or community demos, then collecting survey, interview, and behavior data. Since that pilot was not completed in the source material, this belongs as a planned experiment.
Experiment 1
Problem signal
Hypothesis
Early-career learners need fast expert feedback.
Method
Landing page with three bookable services.
Evidence
Waitlist conversion and selected service.
Experiment 2
Booking usability
Hypothesis
Learners can confidently select and book a mentor.
Method
Moderated prototype task.
Evidence
Task success, hesitation, and status comprehension.
Experiment 3
Concierge pilot
Hypothesis
A small curated marketplace can complete useful sessions.
Method
5 mentors, 15 to 20 learners, manual matching, existing video tools.
Evidence
Time to match, completed sessions, helpfulness, and repeat booking.
First test the transaction. Then decide how much product to build around it.
17 · Reflection
A large market and a broad feature set do not automatically create a focused product.
SkillHop strengthened my ability to connect user experience, marketplace mechanics, product scope, monetization, and business risk inside one product narrative.
Produced
A concept-stage marketplace package.
Unvalidated
The riskiest assumptions remain behavioral.
Next iteration
Narrow, test, then expand.
SkillHop explores how learners can discover, trust, book, and continue learning with the right mentor.