1. Integration and API development (With MuleSoft Anypoint Platform)
Quick seamless integration between multiple systems

2. Why Integration needed ?
What is Integration?
Adding two or more system or software mono directionally or bi- directionally so that data flows between those system is called Integration
Why Integration needed ?
Integration is required for complete automation of any process system. For example let say our organization bought HR management system for HR operation and that is built on ServiceNow. For employee attendance we have Biometric attendance system which developed in Java. HR System’s payroll module is depend on Employee attendance. So if we want complete system to be automated then Attendance system must talk with HR system. That’s why integration is required

3. What is API?
API – Application Programming Interface. A set of function which exposed to outer world so that other system can use easily those functions and leverage the benefits of those functions in their own programming language. Example: ServiceNow HR module required adding of employees. If ServiceNow expose a function “ADDEMPLOYEE” and that function can be called from Bullhorn application that’s means that is an API of ServiceNow.
What is ESB?
A service-oriented architecture (SOA) is a style of software design where services are provided to the other components by application components, through a communication protocol over a network.
An enterprise service bus (ESB) implements a communication system between mutually interacting software applications in a service-oriented architecture (SOA).

4. What are the different tools available in Market for Integration
MuleSoft Anypoint Platform
IBM Enterprise BUS
Dell Boomi
APIGEE
Jitterbit
WSO2
FUSE ESB

5. Why MuleSoft Anypoint Platform
MuleSoft eliminates point-to- point integration and provides an integration platform for connecting any application, data source or API, whether in the cloud or on-premises. MuleSoft’s Anypoint Platform is built as an integrated set of individual products such as Anypoint technology, CloudHub, Mule ESB, Anypoint connector etc.
Mule has a large collection of different connectors to connect and integrate diverse systems. It is said like it can almost connect anything.
Mule is very lightweight and easy to use compared to other ESB. Since it is mostly Java based, so, it becomes very easy to use and build custom components.
Most important is that, Mule is a pure ESB, where other products comes with other functionality and platforms and ESB is one of the part of the product.
Mule is graphical based unlike most of other ESB, where the flows are mostly configured in XML (Apache Camel or Spring integration).

6. Who can you sell this to? - Initial Target audience
It can be sold to any organization, who used multiple systems/ software and wants to automate / connect those system or process:
Customer needs Multiple Data entry into multiple systems
Customer spends lot of time / man power to maintain the data in multiple system
Due to Multiple systems human interaction chances of mistakes are more
Data doesn’t flow timely manner from one system to another
Customers wants data reflect in other system quickly or frequent basis
Customers wants their customers to use their systems (API & Connector can be sell to them)
Customer has Complex business domain like Finance, banking, insurance, Travel, Healthcare, Telecom and Retails etc. Complex domain has more chances of integration than simple domain like Education and Entertainment

7. Ask these questions to understand pain points - Discovery questions/ Common pain points
Are you using multiple software/ system in your business?
If yes, then there will be chances of integration
Are those applications are from same vendor?
If vendors are different then there will be more chances of integration
Do your employee need to do duplicate work due to entering data into multiple system?
If answer is yes then Integration is required
Does your customers need to interact with your system and they wants to integrate your system with their system or do you want to develop mobile app for your system?
If answer is Yes, then API & / or Connector development is required
If customer says their systems are integrated but its very slow and not seamless, downtime is more, information is not secured that’s means they need strong Integration Tools like Mule

8. Talk about relevant parts of the solution based on their pain points - Our Platform benefits / Differentiators
Integration
Development time is less so systems can be integrated easily
Seamless and Secured integration can be done in very less time
Zero data loss during integration
Investing on In-house infrastructure is not required as application can be deployed in cloudhub

9. Few our Work Customer’s Problem
Product entry / update has to be created by each distributor’s side. Which is a rework.
Sales order created in system and the same sales order has to be created in in Distributors side, which is duplicate of work.
Once Sales order status change then the status has to be updated in another system
After our Solutions:
Reduced Man Power
Quick Happy Path solutions
Cost Effective and Re-usable solutions
Data accuracy and efficiency between multiple systems
Seamless integration between multiple distributors systems in same country and across the world
Quick Rollout time for each market

10. Few Our Work Customer’s Problem Big Learning curve
Directly consuming via Mule HTTP Connector is difficult for the developers as they used different Authentication Mechanism
Directly consuming via Mule HTTP Connector is difficult because input and output structure is very complex and developer has to do lot of struggle due to lack of DataSense
Business Results
Reduced the learning curve.
Reusable connector.
Supports their custom Authentications.
DataSense helps their developers to finish the integration easily and quickly.

11. Based on leads we can define:
How to filter leads
Steps to follow after initial discovery
General costs and time estimates based on type of requests
These sometimes can be easily defined but most likely will be case by case basis so we can see the kind of leads and define these