Hunt for early adopter

540 views

Published on

How a tiny Thai niche B2B startup
attracts hundreds of beta users in global market?

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
540
On SlideShare
0
From Embeds
0
Number of Embeds
66
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Hunt for early adopter

  1. 1. The Hunt for The Early Adopters How a tiny Thai niche B2B startup attracts hundreds of beta users in global market?Kulawat WongsarojCEO & Agile Coach Barcamp Bangkok 5proteus-agility.com 20-Oct-2012
  2. 2. Eidos - Agile Tool that Doesnt Suck!
  3. 3. Eidos Team
  4. 4. Who are Eidos customers? Early Adopters customers Agile Tech Lead Agile Practitioners Global IT Professional
  5. 5. Early Adopters, where are they? I had no idea!
  6. 6. Wave 1 : Friends and Local Fan Agile66 Fans
  7. 7. Spam but dont make it to spammy
  8. 8. Wave 2&3 : Community Spamming LinkedIn Agile66 Groups Meetup.com Fans Spam Groups Spam
  9. 9. Quora, the secret source!
  10. 10. Wave 4 : Quora LinkedIn Agile66 Groups Meetup.com Fans Spam Groups Spam Quora
  11. 11. Source Groups
  12. 12. proteus-agility.com4 months75 countries2,517 Unique Visitors376 Beta Signup15% Conversion
  13. 13. Tip #1Dont collect just email in your beta signuppage. What is your pain points? Pivotal Tracker (increasingly popular among small to medium teams) ● Epics and story hierarchy are almost non-existent. ● x-project visibility ● Notifications and searching ● Distributed team, would like better estimate tool and projections based trends... ● summary view point. ● Pivotal Tracker is great for developers and product managers, but pretty much kills my ability to manage the design department. GreenHopper (the most popular one from Eidos beta registrants) ● It doesnt yet have What If analysis or Evidence Based Scheduling. ● Difficult to implement flows. My team members cant get it to a user friendly flow ● Feels like the tool hinders more than it helps; ● Hour burndown doesnt update the initial value if tasks are added after the sprint has started. ● Poor hierarchy in the planning: after the sprint components are created, the hierarchy cannot be edited; ● No possibility to filter out time tracking if the subtasks are part of several "sprint" placeholders;
  14. 14. Tip #2:Share signup responses with your whole team● Google Form can script to send email out
  15. 15. Tip #3Spamming fades away, Q&A doesnt LinkedIn Agile66 Groups Meetup.com Fans Spam Groups Spam Quora
  16. 16. Tip #4 : Infomercial● Blog● DZone ○ send traffic● InfoQ ○ thumbup/thumbdown review ○ personal editor ○ several revisions ○ establish credibility
  17. 17. Tip #5Invest in a decent designer
  18. 18. Thank You
  19. 19. Sources

×