why an api? - exec i/o mobile 2014

21
Why an API? Johannes Lundberg twitter.com/johannesl [email protected] 46elks

Upload: johannes-lundberg

Post on 12-Jul-2015

254 views

Category:

Technology


1 download

TRANSCRIPT

Page 1: Why an api? - Exec I/O Mobile 2014

Why an API?Johannes Lundberg twitter.com/johannesl !

[email protected]

46elks

Page 2: Why an api? - Exec I/O Mobile 2014

Classic SaaSBUSINESS TO BUSINESS

End-users CustomersSaaS

company

MoneyValue

LTV > ACQUISITION COST = YOU WIN

MoneyValue

Page 3: Why an api? - Exec I/O Mobile 2014
Page 4: Why an api? - Exec I/O Mobile 2014

Problems with SaaS

1. Solves a specific problem

2. Limited market

3. End-user responsibility

Page 5: Why an api? - Exec I/O Mobile 2014

The API business

End-users CustomersAPI

business

MoneyTools

MoneyValue?

Not knowing the value your customers will create is the true power of an API business.

Page 6: Why an api? - Exec I/O Mobile 2014

Not knowing the value your customers will create is the true power of an API business.

Johannes Lundberg - Exec I/O Mobile 2014

Page 7: Why an api? - Exec I/O Mobile 2014
Page 8: Why an api? - Exec I/O Mobile 2014

SaaS CTA - sign up

Page 9: Why an api? - Exec I/O Mobile 2014

API CTA - understand

Page 10: Why an api? - Exec I/O Mobile 2014
Page 11: Why an api? - Exec I/O Mobile 2014

Characteristics of an API business

1. Community building, not sales

2. Requires long term commitment

3. Can be very low churn, high LTV

4. Often crucial for customers’ success

Page 12: Why an api? - Exec I/O Mobile 2014

The essence of an API

Turning traditional complexity into programatic simplicity.

Page 13: Why an api? - Exec I/O Mobile 2014

46elksTelephony automation

Voice, SMS & MMS for developers

Page 14: Why an api? - Exec I/O Mobile 2014

• High hardware costs • Big monthly fees • Long term contracts • Extensive development time • Requires telecom skills

• No hardware needed • No fixed costs • No lengthy contracts • Fast to integrate • No special skills required

Traditional way 46elks

Page 15: Why an api? - Exec I/O Mobile 2014

- Send & receive SMS - Dynamic Voice call logic - Real time phone number allocation - MMS campaigns

Page 16: Why an api? - Exec I/O Mobile 2014

• Play menu sound file • If 1, connect to sales • If 2, connect to support

Startup IVR concept

Page 17: Why an api? - Exec I/O Mobile 2014

Startup IVR with 46elks

{ ”ivr”: ”menu.mp3”, ”1”: { ”connect”: ”+123456” }, ”2”: { ”connect”: ”+789123” } }

Page 18: Why an api? - Exec I/O Mobile 2014

46elks

Become a part of the Developer’s toolbox!

DeveloperBusiness

Can we solve this problem?

Page 19: Why an api? - Exec I/O Mobile 2014

47 520 developers

Page 20: Why an api? - Exec I/O Mobile 2014

2.6 million developers

Page 21: Why an api? - Exec I/O Mobile 2014

Johannes Lundberg twitter.com/johannesl !

[email protected]

Your API can win!