4. “FULLY AUTOMATED”
IT INFRASTRUCTURE (HASSLE) SHOULD DISSAPEAR
“NO OWNERSHIP” “NO HUMAN
(IT ENGINEER)
INTERACTION”
“PAY WHEN I USE IT”
“GET THE JOB DONE”
“MONITOR SERVICE
STATUS/UTILIZATION”
“SIMPLE TO SETUP & TO MODIFY”
“PREDICTABLE COST”
5. CHALLENGES WITH TODAY’S SOLUTION
1. MANUAL AND ERROR-PRONE PROCESS DURING END-TO-END WORKFLOW
2. LONG TIME TO GET SERVICES (USERS) AND TO GET REVENUE (PROVIDERS)
3. LOW PROFIT MARGIN FOR PROVIDERS DUE TO HIGH HUMAN COST
7. Source: Cisco Business Technology Architecture Group based on averages across mobile, cable, Telco and data center service providers
OPEX OPTIMIZATION WITH IT AUTOMATION
CONFIG
VALIDATION
93%
OPEX
REDUCTION
SERVICE
PROVISION
90%
OPEX
REDUCTION
NETWORK
CONFIGURE
78%
OPEX
REDUCTION
CONFIG
VALIDATION
94%
OPEX
REDUCTION
RE-
PROVISION
90%
OPEX
REDUCTION
CONFIG
VALIDATION
93%
OPEX
REDUCTION
SERVICE
PROVISION
90%
OPEX
REDUCTION
NETWORK
CONFIGURE
78%
OPEX
REDUCTION
CONFIG
REMOVAL
93%
OPEX
REDUCTION
SERVICE DE-
PROVISION
90%
OPEX
REDUCTION
NETWORK
CONFIGURE
78%
OPEX
REDUCTION
8. CUSTOMERS AND USERS NEED AUTOMATION
Jawdat IT Automation Engine
1. FULLAUTOMATION FOR END-TO-END SERVICE PROVISIONING WORKFLOW
2. SERVICE AGILITY TO REDUCE TIME FOR PROVIDING AND GETTING SERVICES
3. COST REDUCTION FOR PROVIDER BY REMOVING HUMAN OPEX
12. HOW
TO BUILD IT?
IDENTIFY SPECIFIC
PROBLEM TO BE
SOLVED WITH
SPECIFIC SOLUTION
NETWORK MODELING
EVENT CORELATION
ON-PREM AUTOMATION
PLATFORM
LATER:
INTEGRATE ALL
MODULES INTO
ONE PLATFORM
NETWORK
AUTOMATION
AS SERVICE
ON CLOUD
15. POTENTIAL MAJOR RISKS & RESPONSES
Providers are not willing to buy from us
Response: Reduce
Provide free demo unit, show the business benefits
Our platform is not scalable for X no of offices
Response: Reduce
Scalability testing, architecture re-design overtime
New Indonesian tech startup emerges
Response: Accept
Focus on our own strengths and customer relationship
Competitor (Cisco) is going price war
Response: Avoid
Approach customers using values to business outcomes
20. KEY METRICS
Metric Themes Metrics Data Source
Business # of new office activation / year
# of current office renewal / year
Backend Logs
Churn % Users who stop subscription
% Customers who switch provider
Backend Logs
Platform Health # incoming tickets / product usage
# bug counts / product usage
Ticketing/Support System
System Productivity Time to provision new office
Time to execute task
Backend Logs
Portal Engagement # visit / user / week
# of task success / total tasks
Frontend Logs
Customer Satisfaction CSAT or NPS score
Open-ended feedbacks
Customer Survey
28. BUILDING SDN PRODUCT IN 10 STEPS
ü Step 1: Identify problem to solve
ü Step 2: Define if the problem is worth solving
ü Step 3: Plan enough (Lean Canvas)
ü Step 4: Create roadmap and prioritize what to build
ü Step 5: Identify product risk and prepare mitigation
ü Step 6: Build MVP for Frontend and Backend
ü Step 7: Demo and use metrics to capture feedbacks
ü Step 8: Acquire paying customers
ü Step 9: Continuous improvement to Engineering
ü Step 10: Scale the product and build the company
29. “ NO ONE KNOWS
HOW TO DO WHEN
THEY BEGIN. IDEAS
DON’T COME OUT
FULLY FORMED.
THEY ONLY BECOME
CLEAR AS YOU
WORK ON THEM.
YOU JUST HAVE TO
GET STARTED.”
“THE IDEA OF A
SINGLE EUREKA
MOMENT IS A
DANGEROUS LIE.”