slide 1/11. apps 1.lack of information flow 2.no easy way to share 3.hard to find / retrieve...

22
Slide 1/11

Upload: audrey-nelson

Post on 26-Mar-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description

Slide 1/11

Page 2: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description

apps

Page 3: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description

1. Lack of information flow2. No easy way to share3. Hard to find / retrieve information4. Capturing employee’s Knowledge

Problem description

Page 4: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description

Real-time Collaborationfor the Enterprise.

Page 5: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description
Page 6: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description
Page 7: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description
Page 8: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description

Slide 8/11

Page 9: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description

How Flowr works?1. Users collaborate and share information

(Ideas, content, videos, links...)

2. Flowr engine analyze the content (Semantic)

3. Flowr returns “rich” content (related, user “rich”)4. Flowr store it into knowledge database repository5. Knowledge is accessible for all enterprise

Page 10: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description
Page 11: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description
Page 12: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description
Page 13: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description
Page 14: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description

Business model• Flowr is SaaS (software as a service) • 2 pricing models (Free & Premium)

o Freemium (limited with users, basic feature set)o Premium (subscription per user / month)

• Hosted solution (behind the firewall for large Enterprises)

Page 15: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description

Business model / pricing

Page 16: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description

Marketing / sales strategy• Viral (Freemium) go-to-market strategy• Direct marketing activities (large Enterprises)• Strong online presence / advertising• Sales strategy– Monetization of Freemium Premium (SME) – Appliance direct sales to CIO/CEO (large enterprises)– Step 1 - Global market SaaS, Gain first traction in EU:– Step 2 – Q1 2011 reach out of EU with focus on USA– Step 3 - Q1 2012 focus on enterprise (monetized) sales

Page 17: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description

Round A Investment• 1.5M€ for next 12-18 months– Product launch– Sales & marketing activities– Additional team members– Further product development

Page 18: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description

Status / Timeline• Product is in private beta (10 clients, +200 testers)• Public product launch in Q2 2010• Close Round A financing by Q2 2010• Mobile apps (iPhone, Android, BB) Q2 2010• Flowr HQ / Sales office (London, UK) Q2• Cash flow positive in next 20 months (Q1-2012)• 9 new (international) team members in 2010

Page 19: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description

About us• Flowr is a start-up founded in 2009• Location: London, UK (Sales), R&D Slovenia• History: spin-off from Intera, succesful regional web

application company and Red Herring 100 Europe Winner 2009

• People: 4 full time + some external co-workers• Product status: private beta, product launch in Q2

Page 20: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description

Slide 20/27

TeamDavorin Gabrovec, co-founder and CEO • Experienced and serial entrepreneur (Intera.si, Refresh.si…)• Slovenian young executive member CEED Top Class 2008 • Red Herring 100 Europe Winner (Intera, May 2009)

Matjaz Lipus, co-founder and CTO• Social web geek with 8 years experiences managing development teams• Specialities Ajax, WOA, real-time web, RDF, OWL

Vlada Petrović, architect• Software architecture enthusiast with 10+ years experience in web dev• Specialities in Ruby, PHP, C# and JavaScript

Page 21: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description

Slide 21/11

Advisory Board

Suresh Patel Jennifer Hicks Verdexus, UK Ink Communications, USA IBM, HP PR, media

Matt MayfieldHermes Softlab, SLOSales, Business dev.

Page 22: Slide 1/11. apps 1.Lack of information flow 2.No easy way to share 3.Hard to find / retrieve information 4.Capturing employees Knowledge Problem description