This document provides an overview of developing an MVP (minimum viable product) including pitching the product idea, validating product-market fit, building the initial product, measuring user engagement, and scaling the product. It emphasizes the importance of getting started quickly with an MVP to test assumptions with real users rather than waiting. The document also discusses tools and best practices for each stage of development including landing pages, analytics, APIs, and collaboration with developers.

1. MVP
do McGyver
@matleroux

2. “The critical ingredient is getting off your butt and doing
something. It’s as simple as that. A lot of people have
ideas, but there are few who decide to do something
about them now. Not tomorrow. Not next week. But today.
The true entrepreneur is a doer, not a dreamer.”
Nolan Bushnell, Atari Founder

3. Product pitch
Product / Market fit
Build & Scale
Roadmap

4. Product pitch
Product / Market fit
Build & Scale
Measure

5. Product Pitch

6. Target
User typical profile / 1st segment?
Pain
What does he suffer from ?
Solution
What’s my value proposition ?

7. Deezer

8. airbnb

9. Product / Market fit

10.
Activation
Revenue
Retention
Referral
Acquisition

11. Landing page
Clear proposition value
Clean design
Call-to-Action
CRM first milestone

12. Landing page tools

13. No rules
Coupons / partnerships
Newsletters
Follow & ping prospects
Whatever it takes…

14. Paid ads
Upload emails on FB-ads
Create look-alike audiences

15.
Activation
Revenue
Retention
Referral
Acquisition

16. Set metrics
-
+
Likes, followers
Emails
Pre-orders

17. Vanity metrics
Overall likes
Likes / week
vs.

18. Emails

19. Traffic

20. Bounce rate

21. Utm-ize every URL

22.
Activation
Revenue
Retention
Referral
Acquisition

23. How many of your users are still
here after 1 week?
After one month?
After three months?
Right metrics
Retention

24. Use or
to measure it

25. Flurry

26. Retention at 90 days,
33%31% 48% 77% 98%
Flurry

27.
Activation
Revenue
Retention
Referal
Acquisition

28. Right metrics
NPS App Ratings Retention

29. Right metrics
NPS = Net Promoter Score

30. 9 10
promoter
7 8
passives
6543210
detractors
Right metrics

31. NPS = (% of Promoters) - (% of Detractors)
Right metrics

34. Right metrics

35. Right metrics
App Ratings

36. Right metrics

37. Prototyping

38. MVP
Must
Validates
(customer)
hyPothesis

39. MVP
is not
a demo of your ability to
build the best product/UX
not yet…

40. Famous MVP

41. Front-end languages

42. CSS frameworks

43. Github Pages

44. External services

45. Web-forms

46. Newsletter

47. Measure

48. World of APIs
In computer programming, an application programming
interface (API) is a set of routines, protocols, and tools for
building software applications. An API expresses a software
component in terms of its operations, inputs, outputs, and
underlying types. An API defines functionalities that are
independent of their respective implementations, which allows
definitions and implementations to vary without compromising
each other. A good API makes it easier to develop a program
by providing all the building blocks. A programmer then puts
the blocks together.
wikipedia
humm…

49. Web-101

50. Web-101

51. Web-101

52. Web-101

53. Human interface
Readable content
HTML / CSS

54. Programming interface
Structured data
{"richestPeople":[
{"firstName":"Bill", “lastName":"Gates", “value":"81"},
{"firstName":"Carlos", “lastName":"Slim", “value”:"79"},
{"firstName":"Warren", “lastName":"Buffet", "value":"72"}
]}

55. API

56. Http

57. Http

58. They know you’re not devs
(yet)

59. Look for embed button!

60. Support tools

61. APIs connector

62. APIs connector

63. APIs connector

64. Scale

65. Go Fullstack

66. Go Fullstack

67. 2 options
Find a CTO
Build it yourself

68. Collaborate
Product pitch will help you
write user stories to define
your MVP

69. Collaborate
I want to build a social app with geolocation so that
anyone, at any moment, can organize real-time
dinners and then receive analytics on expenses.. I
see this as a connected shopping list for friends.. or
more like a blablablabla…
— Some web-entrepreneur in the wrong direction
Developers don't understand blablabla.
Developers do understand user stories.
to assess complexity & time cost.

70. Collaborate
• As a visitor, I can create an account
• As a user, I can create groups
• As a user, I can add existing friends on a group
• As a user, I can invite new friends on a group
• As a organizer, I can create dinners on a group
• As an invitee, I can comment on a dinner
• As an invitee, I can accept/decline a dinner
• As an invitee, I can tell what I bring to a dinner
• As an invitee, I can tell how much I paid for that
• etc..

71. Go further
www.lewagon.com/SP

72. Merci :)
mat@lewagon.org