Presentation about Software as a Service to the IT students of Kaunas University of Thechnology in Lithuania

1. SAAS IS HOT
Laurynas Antanavičius
Product Manager @ Data Dog
2014.10.14

2. ABOUT US
• Custom web development and support
• Cloud-based application and software development
• B2B, B2C eCommerce solutions
• Specialised in PHP
• Over 35 developers
• Wide base of clients: UK, US, UAE, Canada, Luxembourgh,
France…

3. http://vimeo.com/107405318

4. OUR TEAM
• Crypto-Currency exchange / Forex market
• 6 members in the development team
• Agile - Scrum, TDD, CI, CD
• PHP & GO
• Write tests before each line of code (TDD & CI)
• Ship the feature as soon as it is ready (CD)
• Focus on performance & quality

5. EVERYTHING IS A SERVICE
Shouldn’t I be talking about tools?

6. We’re actually using tools everyday.
AND
We’re creating and learning how to create tools.

7. An eShop is a tool to generate sales by selling
products.
A Website is a tool to present your company.
An forex trade platform is a tool for traders to buy
and sell currency,

8. WHO HAS RECENTLY
BOUGHT A STANDALONE MS
OFFICE?

9. Google docs is free!
We can use it on all of the devices!
It has all of the most important features!
It does not crash!

10. SAAS | PAAS | IAAS

12. Point and click for what you need.
Tweak parts and configuration
Pay for what you use.
Examples: Amazon Web Service (AWS), Microsoft Azure, Google
Compute Engine (GCE)
Infrastructure as a Service

13. Manage the whole platform.
Configure individual instances, and settings.
CLIs / Point-and-Click / Ready made connections / SaaS
integrations
Examples: Heroku, AWS Elastic Beanstalk, Google App Engine,
Salesforce.
Platform as a Service

14. Mostly subscription based
Centrally managed code base
‘On-demand’ access through browser
Single configuration with all user data
Examples: Gmail, Facebook, Youtube, Google Docs, Github
Software as a Service

15. Standalone vs Cloud based
Standalone might be more intuitive to use for a specific system
Standalone might perform better on a specific system
Cloud based can be accessed from any device
New devices can access all data and use the software
It is about convenience

16. Premium / Freemium / Subscription
Premium allows access only after a payment has been made
(usually with trial periods)
Freemium allows access only to a specific functionality, full
access can be given after a payment has been made
Subscription allows access for a specific period after a payment
has been made (monthly / yearly)
It is about cost.

17. And now it's about devices and agility.
We access software on our phones and tablets
We interact with the same functionality and have access to the
same data
We need the ability to have access to the software if we change
the device completely

18. A wide array of different payment schedules and plans
Should I pay $1000 dollars now?
Or pay $40 for as long as I use it?
Or should I pay $10 for each feature separately?
Or use less features for free?
Which is better?
Cost vs productivity.

24. CAN’T FIND ONE?

25. https://www.youtube.com/watch?v=b_mVb-G1v1I

26. DON’T BE A SCUMBAG CAT
Make one!

27. DEVELOP A TOOL

28. The same on a feature level
Identify critical features
Defined in more detail only for the critical features
PLANNING
SaaS vs Traditional

29. SOA architecture
Continuous integration
Continuous delivery is really really important
Pay for what you use
DEVELOPMENT
SaaS vs Traditional

33. Gather feedback
Updating
Hotfixing
SUPPORT
SaaS vs Traditional

35. WHY ARE WE
FOCUSING ON IT?

36. Centrally managed
Feature rich
Integrated
Constantly evolving
Our software

37. Higher customer satisfaction
Stable inflow of payments for clients
Faster time-to-market
Our clients

38. ANY NEGATIVE?

39. https://www.youtube.com/watch?v=6QI4KmlcQr4

40. WHY SHOULD I DO IT?

41. Ride the wave
New things everyday
Lower risk to get stuck with legacy software
Staying up-to-date

42. Open up your work
Go for open source
Large base of developers
More software architecture decisions
Knowledge growth

43. Faster feedback
Again more growth
Visible results
More $
Short development life-cycles

44. TAKEAWAY

45. CHOOSING TOOLS
Consider standalone and cloud based alternatives
Consider the convenience it provides vs costs
Consider one-time vs subscription fees

46. DEVELOPING TOOLS
Consider time-to-market for a product
Consider working with a larger community of developers
Open up your work
Think about the development life-cycle

47. WAIT FOR IT..
Questions?