Talk about building product flow for early stage startup company

1. Build your winning
product in two weeks
Quan MT
quan@beeketing.com

2. About Me
Quan MT
Founder & CEO Beeketing
Batch 15

3. Increase
REVENUE
Increase
RETENTION
LEARN RECOMMEND ENGAGE
customers buying habits right products to customers slipping away customers

4. Do you have a working product?

5. Companies & time to build first version
• Start 08/2014
• Launch 08/2014
• 55,000 business users
• 30% revenue month
over month growth
• Raised ~$400,000
• Start coding 04/2012
• First launch 03/2013
• Next big update 06/2013
• Acquired 01/2015
• Start 01/2014
• Launch 03/2014
• 06/2014 - 20 users
• Closed 07/2014
1 year 3 months 1 week
Time to build first version:

6. “Almost all startups that died
has a product”

7. A Good Product
Product
Marketing Sales Attract talents …
is foundation of the company success

8. Why and when we need to build a MVP?
• Because all we have when stared is an idea with a lot
of assumptions.
• Build MVP to validate your assumptions.
• You don’t want to waste your time and money.
• Build product customers want faster.
• Excite your team with small wins.
• Ideal time for a MVP?
• 1 day ~ 1 week … don’t take more than 1 month.

9. Beeketing Big Platform Problem

10. What make startup delay on the MVP?
• Question: What technology to use?
• Should we use the trendy AngularJS or the plain old
PHP? Aged Mysql or Highly Scaleable MongoDB?
• Answer: What you already know best… you can always
change later, and you gonna change it anyway.
• Question: User need these features, we have to build them
before launching.
• Answer: Keep only features that can be built within a
week.

11. LEAN STARTUP
Customers don’t care about your solution. They
care about their problems.
—Dave McClure, 500 Startups

12. Lean Canvas

13. Building MVP - the Beeketing way
1.Identify right problem
2.Proposal solution (Build P/S canvas)
3.Mock up, flow (Review all tasks, build wireframe for
them)
4.Schedule
5.Code / Design
6.QA
7.Deploy
8.Measure

14. Pick 1 or more assumptions then test in 2 weeks

15. 1. List all problems, then shortlist

16. 2. Problems Solutions Canvas

17. Building time
Mock up, flow, Schedule, Code / Design, QA, Deploy

18. What’s next after deployed?
1.Get users to your product daily / weekly to measure
1.Google, Facebook Ads
2.Forum seeding
3.Facebook group
4.Many more if you read “traction” book
2.Integrate with more focus analytics system (not
Google Analytics)
1.e.g.: Mixpanel

19. 7. Measure
• User usage, behaviors
• Funnel analytics
• Churn analytics

20. 7. User behavior analytics
Screen 1 Screen 2 Screen 3
Page 1 Page 2 Page 3
Metrics Hub
(Mixpanel / ModeAnalytics / In house)

21. 7. User behavior analytics

22. 7. Measure conversion funnel

23. 7. Measure conversion funnel

24. 7. Measure churn / retention
Gross MRR Churn
= Churned MRR / Beginning of Period MRR
1.Split churn group to many segments as you grow
1.Second-month churn
2.By user group (Hanoi, Saigon user)
2.Focus more into churn than growth if it cost you a lot
to grow and vice versa.

25. 7. Measure churn / retention

26. 7. Find the reason why user churn
1.Call / meet / interview user
2.Use Mixpanel explore to find what churn user group
have in common
1.List all churned users
2.View their parameters, behaviors with Mixpanel
profile
3.Fix this in next sprint

27. http://appcues.com/blog/6-growth-experiments-sidekick-ran-to-improve-retention/
Google: “6 growth experiments sidekick ran”

28. 1. Identify the right problems
1.OMTM: One metric that matter - MRR, Churn rate
2.Set goal for that metric
e.g.: Grow MRR 50% m.o.m (month over month)
3.Find the real issue if we didn’t reach goal
e.g.:
1.If revenue grow slower than our goal
2.Found that churn rate lead to growth rate get slower
1.~> Fix churn rate
4.Plan tasks for next sprint to fix that issue
5.Then repeat this process for next sprint

29. Pick 1 or more metrics then improve in 2 weeks

30. Product team structure to run fast
1.Try to automate everything
1.Build new version with Jenkins instead of FTP, Git
pull so you can update your product many times
daily.
2.Use test frameworks like Selenium IDE to
automate testing
2.Be simple
1.No trendy micro-service when you just started
2.Recommended tools: Trello, Slack
3.Use Feature Switch (Learnt from Zalora, Spotify)

31. Feature Switch
1.Add If … Else statement to ALL new features
2.Admin backend dashboard to easily turn this feature
off if it breaks something

32. Fail-friendly environment

33. Useful quotes
1. Không sợ dẫm shit
2. Build half a product, not a half-assed product
3. Smart people know when to stop and when to stick

34. Must read books

35. Thank you
quan@beeketing.com
Quan MT