Digital Transformation Platform Migration & Modernization

Slack Is Not a Chat Tool

Slack Is Not a Chat Tool

“But I use it to chat with my entire organization every day!”

You sure do. In fact, if your company uses Slack, you likely use it as a chat tool hundreds or even thousands of times per week. 

You also likely have an iPhone or Android device within two feet of you right now that you use hundreds or even thousands of times per week. How much do these devices have in common with a rotary telephone? 

Breaking Paradigms

One of the iPhone’s core, foundational use cases is basic calling. If the iPhone didn’t do that core use case well, it never would have replaced the Motorola Razr that lived in my pocket in 2009. Its initial value, to me as a consumer, was that not only could it replace my Razr, but it could also replace my iPod and provide a superior SMS experience. 

That was 2012. Do you think my personal paradigm around my iPhone has shifted since then?

Of course it has. Like everyone else, I’ve come to rely on the iPhone to manage my day-to-day life. But what does this have to do with Slack?

One of Slack’s core, foundational use cases is basic chat. If Slack didn’t do that core use case well, it never would have replaced GChat within our organization in 2018. Its initial value, to me as a business owner, was that not only could it replace GChat, it could also replace “internal Green Irony” SMS messaging, add logical channel groupings for focused collaboration, and, of course, add Giphy animated gifs to the mix. Mix in some basic integrations like Google Calendar and it was a no-brainer.

That was 2018. Do you think my personal paradigm around Slack has shifted since then? 

More importantly, do you think Salesforce CEO Marc Benioff shelled out $28 bil for a chat tool with animated gifs? 

The Adoption Problem

Just like starting with calling and text got the iPhone into pockets and at-scale usage to unlock more valuable use cases, Slack started with a chat tool, obtained at-scale usage, and is now at the beginning of the innovation curve where it will unlock much more valuable use cases. Slack will become a staple in putting needle-moving enhancements in the hands of users as quickly as possible to impact key business drivers. It will give users the tools they need to do their jobs much more effectively by providing in-context actions paired with the targeted, rapid collaboration that already takes place within its “chat tool.”

Doesn’t Salesforce already do all this stuff? 

It sure does. In 2017, we wrote that Salesforce is not a CRM. We’ve always seen it as a world-class platform for delivering key business workflows. With five additional years of Salesforce-specific digital transformation experience under our belts since then, what we’ve found is that our biggest challenge in delivering on these promises isn’t the technology platform, it’s adoption. And we’re not alone in this observation.

Within the last month, Gartner has applied a heavy focus on the CRM adoption and data problem with a keynote titled “CROs: It’s Time to Solve the CRM Data Problem.” My key takeaway from this presentation re-enforced what I’ve seen in the field: there’s a “spiral-like” impact between CRM data quality, user experience, and adoption. Poor UX drives low adoption, which drives poor data quality. Poor data quality further magnifies UX challenges, driving even lower adoption. The problem feeds upon itself. And with the CRM more and more connected to the rest of the IT system landscape, the problem is only getting worse. 

The dollars and cents to the business here are immense. This adoption problem exists outside of the CRMs as well, but we’ll narrow the focus to CRMs for this blog. Let’s examine a few examples of the impact of this problem: 

  • Lost rep productivity from sub-optimal tooling and manual workflows, resulting in lower deal size per rep, win rate per rep, and overall revenue per rep. 
  • Poor revenue attainment due to loss of basic or advanced CRM capabilities, depending on severity of issues. 
  • Poor employee experience across key CX-impacting sales and service reps with long-term impact on overall brand equity

No matter the industry, all of these are clearly high-impact areas to a business.  

Salesforce and other CRMs have become more like Systems of Record, catering to “thick work”  like sales forecasting, opportunity management, and complex product support. “Thin work” like collaboration, appointment scheduling, basic task automation, and data entry can pivot to a more natural, in-context usage pattern, solving the adoption issue. 

The Future of Work

We see “thin work” being forced onto users in “thick work” systems is the #1 driver of this adoption issue. We see Slack as THE key technology platform for solving it.

Because its first use case was chat, Slack is already ingrained within users’ day-to-day workflows. It serves as the communication lifeblood of an entire organization. Adoption of productivity-enhancing workflows for users will be a much lesser challenge. These workflows will all produce clean business data, powering more advanced workflows, and, in the future, AI.

Does anyone’s sales organization have a Slack adoption problem? If you’ve heard of one, please reach out and let me know. You’d be the first.

If the key inhibitor to the value proposition of the CRM is adoption, moving pieces of our workflows to a platform with sky-high adoption rates and allowing users to perform actions in-context seems like an area with massive potential. 

A few key questions to ask yourself as a business leader:

  • How could our user productivity and happiness be impacted when we can automate common pain points within our critical revenue-driving and customer-impacting processes? Imagine the at-scale impact of being able to automate the build of a first-call deck so that a rep only has to spend 5 minutes validating and fine-tuning the output.
  • How will our sales KPIs like deal velocity and close rate benefit from our additional rep productivity? Imagine the business impact if reps saved an hour per-day on poor CRM UX and applied that time savings to relationship building, prep, and additional prospecting.
  • How will key EX metrics across reps be impacted by eliminating annoying tooling issues? Everyone’s CRM has a workflow that is hated by every rep because of how much time it wastes. Imagine the morale boost of eliminating it with in-context time-savers in Slack.
  • How will the increased data quality as a result of adoption allow me to better analyze and fine-tune my key business workflows? All of the promises of a fine-tuned CRM that are rarely realized due to adoption and bad data can be realized when these challenges are overcome.

Finally, a question from the blog author: why are very few companies taking advantage of this huge opportunity?

Perhaps we’re just early in the innovation curve and it’s only a matter of time. Or perhaps another reason is a challenge we are all too familiar with: Integration.

Integration Drives Innovation

Through the lens of a CIO charged with innovation, if Slack allows me to design user workflows that impact key business drivers and adoption is no longer a huge challenge, what’s my next challenge?

It has to be integration.

On the technical side, the biggest implication to this type of shift is an even greater strategic need for a scalable integration strategy focused on business agility. We’ll have a need to touch a large number of systems within our technology landscape in order to design the best possible workflows to impact these key business drivers. 

Slack is simply the user control panel, allowing users to perform work in-context more easily. It places an even greater emphasis on what’s happening “behind the scenes” to make the in-context work actionable. We’ll get into the nuts and bolts of what’s required to build custom integrations in Slack in a future blog from Green Irony’s engineering team, but suffice it to say, APIs become much, much more important in this sort of environment. If our goal is to avoid the negative impact of our users wasting time in systems to perform specific in-context actions, we must have a well-designed API network. Without one, the one-off integration requirements levied to the engineering team will kill our delivery timeline and derail our key business priorities. 

This means we need a scalable integration strategy focused on delivering reusable assets that can be used to create a composable business and automating key business processes across the IT landscape. 

Doesn’t this sound like the value prop of something else you’ve seen Marc Benioff acquire in the past five years? 

Betterer Together

We’ve seen the “Better Together” MuleSoft and Salesforce campaign for a few years now. We fully believe in it ourselves, having created a fictional story to highlight the concept at a high-level technically

It’s our view that Slack and MuleSoft are even “Better Together” than the previous pairing. The reason for this is because Slack’s #1 use case in every organization is always going to be chat. But that doesn’t mean it’s a chat tool. It means that savvy organizations with control over their API strategy can leverage this “chat tool” to ensure they conquer the adoption problem that impacts all businesses. Conquering this problem is going to be a bigger and bigger competitive advantage in today’s digital world.  

We’ve written ad nauseum about MuleSoft’s ability to shine in key areas and won’t repeat them here. Some reading for interested parties can be found below:

In a nutshell, MuleSoft allows technology departments to create reusable API assets that model the company’s core business. These assets can be composed into critical business processes and orchestrations of the behind-the-scenes technology interactions required by these processes, dubbed an “Application Network.” These processes can then be surfaced in the exact way necessary for a consumer to interact with them.

This is exactly what’s needed technologically to capitalize on the immense business value unlocked by the Slack platform. This pairing was meant to be.

Are You Prepared for the Future of Work?

All visionary executives must ask themselves one critical question: am I prepared for what’s to come with the future of work? 

If the answer is no, you are essentially relying on your competition to be equally unprepared. Because if they are, you’re toast, aren’t you? Your competition will be ahead of you in several key areas:

  • They will have the business agility to competitively differentiate themselves rapidly under new market conditions such as pandemics, geopolitical situations, or inflationary impacts.
  • They will have a superior set of data upon which to make actionable business decisions and drive future AI scenarios.
  • Their workforce will be much more productive than yours, dollar for dollar.
  • They will be able to continually improve high-impact metrics like revenue, CX, EX, and cost of sale by making the employee workflows and communications that drive these metrics more effective. 
  • They will be able to quickly open new revenue channels and attack new business models without the friction of user adoption.
  • They will see the business results that get organizations to buy into these types of technology platforms and 8-figure “digital transformation” or “modernization” initiatives.

Does this sound like a competitor you want to deal with from your current position, or do you want to win by planning, executing, and evolving?  Talk to us today about gaining your competitive edge through a scalable integration strategy tied to your business outcomes.

Green Irony News

Green Irony’s Commercial Revamp

A Common Sense Approach to Digital Transformation Backed by a 60-year-old Framework

Green Irony has always aligned our organization’s success to our customers. I started the company with a bet that Salesforce provided a superior technology platform that would allow our highly-skilled engineering teams to attack digital transformation initiatives more quickly and effectively. Having to deal with fewer “moving parts” with technology would enable our teams to focus more on other critical factors for delivering successful digital transformation outcomes.

Five years later, I can say that Salesforce’s platforms have not disappointed. Marc Benioff continues to evolve his technology vision and software offerings on the fly, giving organizations better tools than they have EVER had at their disposal for accomplishing their business objectives. Our team at Green Irony, effectively trained on these platforms, is capable of delivering scalable business value FAR faster and with fewer problems than we were without these platforms at our disposal.

There’s a but.

But, we’ve found that it isn’t enough to just be the best at delivering business outcomes using Salesforce and MuleSoft. There was another key set of variables limiting our success, and Green Irony needed a set of well-defined offerings to better address these inhibitors to successful outcomes. 

Digital Transformation Isn’t Just Technology

At its core, digital transformation is about transforming a “normal” corporate entity to operate more like a tech company. Ideally, this transformation merges the advantages of the existing corporate brand with the scale advantage of tech “disruptors.” A well-executed transformation results in the business having fine-grained control over processes that drive critical business metrics impacting revenue and profitability. These goals involve more than merely bringing in software platforms. Does creating a world-class mobile app alone make you Uber? And why do 70% of digital transformations fail?

The answers to these questions lie within the common sense of a 60-year-old framework.

The PPT Framework that was created in the 1960s says, to paraphrase: People, Process, and Technology must live in harmony for an organization to operate at a high level. People do the work and processes govern how they do it. If technology “levels up” significantly through “Tech Modernization,” it stands to reason that the other two elements of the PPT framework would need to support this change.  

Too many enterprises embarking on Digital Transformation ignore this common-sense wisdom.

Customers bring in modern technologies like Salesforce and MuleSoft and expect to wave Marc Benioff’s magic wand over their existing technology landscapes, perform anIT project, and deliver a business outcome fit for Marc’s next Dreamforce keynote. They parachute these shiny new platforms into their existing IT operating environments, say phrases like, “let’s do a base implementation,” and tell their teams to go. Chaos erupts. 

This approach is counterproductive to the organization’s goals.

Under this “strategy,” implementations are executed by People trained to enhance and support the existing legacy Technology. These People, with minimal training, set out to deliver capabilities on new Technology platforms using IT Processes that were defined for the older Technologies. These legacy Processes were also designed with different goals in mind than what’s necessary to succeed at digital transformation. 

People and Process misalignment in digital transformation have caused me to personally witness the following Corporate IT Horror Stories:

  • Customer buys MuleSoft for agility; Enterprise Architecture carves up processes for taking the “Donkey Work” in-house, increasing cost and eliminating MuleSoft’s agility
  • Customer purchases MuleSoft to accelerate development; IT does not train staff on MuleSoft and continues to unknowingly build its own in-house MuleSoft “competitor” on AWS
  • Customer acquires Salesforce to move fast; PMO leverages legacy KTLO processes that stifle innovation and grind the Software Supply Chain to a halt.
  • Customer hires high-end, dedicated platform consulting experts; point-and-click Salesforce administrators call the shots on architectural strategy

These stories will be explored in more detail at a later date, but they all have one thing in common: they have nothing to do with technology. They arise because the Technology leg of the three-legged PPT stool has significantly “outgrown” the other two legs when Salesforce and MuleSoft enter the equation in a technology modernization effort.

So no, we can’t be Uber just by virtue of having a compelling mobile application. Uber has evolved its People, Processes, and Technology in TANDEM to BECOME Uber and OPERATE like Uber. And transformations, even with a great technology platform strategy, fail without the appropriate People and Process to bring that Technology platform strategy into motion the RIGHT way. 

A Modern IT Operating Model

Building world-class People & Process capabilities to match the Technology capabilities of Salesforce and MuleSoft does not happen overnight. At Green Irony, our objective is to help our customers maneuver around this constraint, accelerate their Digital Transformation goals, and EVOLVE these other two legs of the stool as we move through the roadmap.

A well-run digital transformation engagement focuses on getting new business value in the hands of customers as quickly as possible, analyzing data, and rapidly evolving the technology based on the analysis. A successful process for delivering on these goals needs to be agile and it needs to be capable of getting right-sized capabilities to the market quickly. We need fast Software Supply Chain cycle times, continuous feedback on metrics that matter, and continuous evolution of the technology product with capabilities delivered to the end customer regularly.

This type of model is much more Silicon Valley than it is Corporate IT.

Existing Corporate IT operating models are geared toward keeping core day-to-day operations running smoothly and minimizing risk from even small changes. Resources are deployed on siloed projects with rigid schedules and limited visibility into upstream or downstream implications in the software supply chain. There is very little in common between the objectives or operating models used here and those that are used in well-run digital transformation engagement. 

The core operation must keep running smoothly as digital transformation capabilities are released quickly. Therefore, both portfolios of processes are required, each with specific purposes for the organization. 

Green Irony’s Market Response

Green Irony is already delivering exponential value using MuleSoft Anypoint Platform and Salesforce. We’re evolving our offerings and our messaging to fully embrace what we’ve always been: a bridge between your existing IT operation and the business. We operate like Silicon Valley because it’s in our DNA to do so. We provide the People and Processes required to fuel your digital transformation goals while you mature your own internal operating models to match the needs of technology product development. This evolution doesn’t happen overnight, and our offering strategy is focused on ensuring it happens in a way that fuels technology innovation, protects the in-flight technology investment, and sets our customers up for ongoing success.

Our refined commercial offerings and messaging will focus on several key areas:

  • Creating a repeatable Software Supply Chain that rapidly delivers business value to our customers’ customers
  • Measuring, analyzing, and shortening the cycle time of this supply chain, fueling rapid delivery of on-demand capabilities to customers
  • Leveraging technology platforms and tooling that enable the rapid rollout of high-impact business use cases at scale
  • Optimizing future data access using MuleSoft, increasing the “clock speed” of the business by reducing the critical path of the Software Supply Chain

Our mission at Green Irony is to change the way that our customers think of delivering technology and to level up their organization’s ability to accomplish the main goal of digital transformation: Operate like a tech company and combine the advantages of that operating model with their own. These offerings will help our customers do just that.

Platform Migration & Modernization

The Modern Solution to P&C Third Party Data Provider Integration

The Importance of Data To P&C Insurance Carriers

To evaluate the risk of writing a new policy on a property, insurers rely on a vast array of third-party data providers that supply information on important factors like flood risk, replacement cost estimation, potential liabilities like swimming pools, policyholder creditworthiness, and the likelihood of catastrophic events like hurricanes. With a rapidly growing pool of new data providers, the number of data points that can be mixed and matched to increase a carrier’s ability to accurately assess policy risk is growing by the day. 

Proper estimation of risk is a make-or-break proposition for an insurance carrier since it directly impacts the carrier rating, overall profitability, and long-term financial stability. Carriers who underwrite policies with poor risk-to-premium ratios don’t stay in business for long; on the other hand, carriers who invest in a data strategy that allows them to be nimble and leverage risk data to its fullest advantage have a clear leg up on their competition. The evolving availability of data provides a tremendous opportunity for carriers to not only upgrade their ability to estimate risk but also to harness data to detect fraudulent claims, identify risk of policyholder attrition before it happens, surface customer insights, and handle nearly limitless other scenarios.

The ability to properly leverage this data is of the utmost importance to carriers. Unfortunately, carriers are held back by legacy integration approaches that prevent them from maximizing the impact of this data on their bottom lines.

The Traditional Integration Approach

Carriers have been using third-party data to automate portions of the underwriting and risk assessment process for over a decade by wiring services like Melissa Data, Core Logic, and LexisNexis directly into their policy management systems (PMS). The PMS is a monolithic center of the universe in this approach, handling connectivity to the third party providers, aggregating data, applying business logic, and remediating any errors that occur within the transaction before ultimately leveraging the data for its purpose.

In the example below, the Duck Creek PMS consumes data from five different third-party providers and uses custom-developed code to implement the necessary logic within the PMS:

Traditional Integration Approach for Policy Systems

Please note that Duck Creek was chosen for this example and this problem exists for all other policy management systems such as Guidewire. 

This approach silos application and business logic within customizations that live on the Duck Creek PMS. It has several pitfalls from a technology perspective that hamstring business initiatives to more effectively use this data:

    • Critical business logic is siloed and not reusable to other consumers like additional policy management systems, customer-facing portals, or third-party comparative raters, meaning this logic would need to be written, maintained, and governed for each of these additional consumers.
    • Replacing or augmenting a problematic provider results in an IT project that is developer-intensive, slow to market, and costly with an outage risk to the mission-critical PMS.
    • Monitoring and problem determination are challenging, error-prone, and time-consuming since they involve custom code that lives on the policy management system.
    • Legacy third-party data providers have cumbersome interfaces that are difficult to integrate with and troubleshoot, resulting in one-off spaghetti code. 
    • No ability to scale services independently based on throughput needs since they live within a monolithic policy administration system. 
    • Much greater barrier to entry to adding new best-of-breed 3rd party data providers.
    • Decreased ability to intelligently cache and meter pay-per-use 3rd party APIs, resulting in increased spending with these vendors.

These pitfalls result in a severe challenge for carriers looking to leverage available data for making the best business decisions. Because this approach is how things have always been done at most carriers, their mindsets have been molded to believe that this is simply the way things are and that they must live with it. But there is a better way to handle managing these integrations that allow carriers maximum agility, reuse, and speed to market while also mitigating outage risk to the PMS.

The Modern Approach: API-led Integration

The API-led approach to integration is just what the doctor ordered for solving this technology challenge and fueling the next level of intelligent data usage at carriers. API-led Connectivity decouples integration logic from the policy management system, alleviating the challenges with the legacy approach.

Insurance Three-Tiered Architecture

The result is a solution that allows carriers to move much more quickly in replacing or adding new data providers without outage risk, simplifying a very complex and costly scenario:

    • Changing or adding additional 3rd party data providers becomes much less costly and faster without the outage risk to the PMS of the legacy integration approach.
    • Business and application logic becomes reusable to other consumers like additional policy management systems, external comparative raters, and policyholder portals.
    • Robust data monitoring and problem determination capabilities allow IT to rapidly identify and remediate production issues.
    • Each service can be independently scaled to handle its own unique needs.
    • New best-of-breed providers can be added and incorporated into the architecture quickly.
    • Increased governance and metering of pay-per-use data providers.
    • Full ownership and control of data
    • Increased ability to rapidly scale new product lines and regions


As technology continues to evolve with new InsureTechs emerging daily, the need for insurance IT organizations to be nimble and give themselves the ability to leverage best-of-breed data will continue to become more critical to remain competitive. Legacy approaches to integration of these data providers have saddled carriers with IT infrastructure that is slow to adapt, costly, rigid, and poses needless outage risk to mission-critical, revenue-driving policy management systems. API-led connectivity solves the problems posed by this legacy architecture in an elegant way, giving carriers the tools they need to succeed in today’s data-driven landscape.

Need help modernizing your integration strategy? Want to learn more about how API-lead connectivity helps your business? Contact us to start the conversation.

Digital Transformation Platform Migration & Modernization

The Best Toolset for Your Digital Transformation

The Beginning

In early 2016, Salesforce really caught my attention. At the time, I was leading high-dollar digital transformation technology efforts fueled by mobile and web requirements. These projects were built with the user interface on whatever the current sexy JavaScript framework flavor of the month was—Backbone, Angular, Bootstrap, Foundation, React, and myriad others were in the tool belt at one time or another—and a middleware API tier that was built using technologies and platforms like Java EE, Node, IBM on-prem middleware, and a mixture of AWS services. Prior to investing the time in learning the platform, I thought of Salesforce as just a CRM.

Once I realized what Salesforce had built at a platform level, I couldn’t get enough of it. I’d seen a number of “low code” platforms in the past that didn’t deliver, mostly because they weren’t flexible enough to allow someone with a development background to meet any requirement thrown their way.

Seeing this unfold over a decade of technology experience made me come to the conclusion that low-code platforms just weren’t equipped to handle the types of challenges posed by enterprise digital transformation initiatives. Engineers like myself would always be needed to write the complex code required for fueling great user experiences. 

By mid-2016, I realized that Salesforce and its Lightning Platform had proven the above conclusion wrong. Green Irony was born.

System of User Engagement

Salesforce provides the best possible platform for delivering the user experiences required for digital transformation. Using a sophisticated mix of drag-and-drop tooling, an extensible programming model, and a broad array of on-platform applications, Salesforce provides a vehicle for fueling the user interface side of digital transformation efforts.

With much of the functionality either out of the box or configurable in a short time period, it also cuts down on the grunt work that IT teams would have to do in the past, allowing them to focus more on business value than time-consuming tasks best categorized as reinventing the wheel. 

While Salesforce goes to market with very specific user scenarios, the Lightning Platform that they use to build these scenarios is powerful enough to deliver any user experience need thrown at it:

  • User interface
    • Componentized drag-and-drop controls for building custom page layouts tailored to specific user personas 
    • Ability to extend existing functionality using custom-built components that work with drag-and-drop editor
  • Development acceleration
    • Rapid data modeling tools with built-in foundational functionality like automatically-generated CRUD REST interfaces
    • Formulaic data fields for easy-to-build functionality without writing code
    • Built-in no-code automation tooling with ability to use programmatic Apex language for more complex needs
    • Full support for all common integration patterns, removing typical “low code” limitations
    • Thriving 3rd party ecosystem on the Salesforce AppExchange, offering bolt-ons that layer in value in specific scenarios
    • Integrated JavaScript UI framework similar to other advanced MVC-style frameworks in the market to fuel custom requirements
  • Process control and reporting
    • Data validation enforcement 
    • Visual user workflows to drive standardized processes 
    • Process control and approval workflows
    • Real-time access to all critical workflow data for users, management, and executives
  • Automation
    • Full suite of automation tooling designed to let users focus on what’s important instead of manual data entry
    • Built-in industry-specific applications with out-of-the-box automation for common user workflows like bank referrals or loan origination

This platform delivers the user experiences necessary to execute on digital transformation efforts much more quickly than the technologies I’d used in my past life. Since Salesforce facilitated the creation of these user experiences much more rapidly, Green Irony would focus on the area that gated most digital transformation efforts, and one that I was intimately familiar with given that my background is in middleware: integration.

Salesforce Integrations

Because the Salesforce platform includes a fully-featured programming language similar to Java (Apex) and an MVC-style UI framework (Lightning, and in the legacy world, Visualforce), the opportunities for customization are not bounded like they would be in a typical no-code or low-code platform.

Anything you’d expect to be able to do from more heavyweight options like JEE or .NET is at your disposal on the Salesforce platform, including integration. These integration patterns are no different than what our engineering team had seen in other enterprise technology solutions, so they were already very familiar to us.

What needed to be learned, then, was how to use Salesforce’s configuration and programming methodology effectively so that our team was equipped to build integrations that delivered not only on the system requirements but also on the user requirements. Integrations built without knowledge of the usage requirements rarely work as intended; therefore, understanding of the Salesforce workflows and their best practices was critical.

We took it upon ourselves to master every aspect of the Salesforce platform so that we could be the best at harnessing its power for integration-heavy digital transformation scenarios. 

When building the integrations, it struck me as odd that we were still using the same techniques we’d always used for enterprise integration. These techniques were effective but created point-to-point connections that were brittle to change, time-consuming to create, and not reusable.

The Salesforce platform had solved the need for a system of engagement that could keep up with the pace of today’s technology needs, but the integrations were still very time-consuming to create and maintain and were always the long pole in every project, gating our ability to accelerate these efforts. 

There had to be a better way. In mid-2018, Salesforce CEO Marc Benioff tipped us off to that better way.

Say Hello to MuleSoft

A little over two years ago in May of 2018, Salesforce completed its acquisition of MuleSoft at a staggering trailing-revenue multiplier of roughly 22x. Prior to the acquisition, we were still thinking of integration in the same way that we had for years: point-to-point. We built custom integrations using Apex in Salesforce for client-driven interactions and leveraged the robust Salesforce API for inbound integration needs.

When requirements dictated the need for additional flexibility in transformation and aggregation, we built out middleware tiers using technologies like Node.js that we, at the time, thought of as rapid enablers for integration. Additional development acceleration could be achieved by adding a platform-as-a-service like Salesforce’s Heroku, which took away many hosting and administrative considerations, allowing my team and I to focus purely on the code needed to integrate Salesforce to other enterprise systems. 

Like Salesforce did in mid-2016, MuleSoft drastically changed my thinking two years later. Its API-led approach, which we cover in great detail in The Value of Anypoint Platform, was something I had not seen before despite being heavily involved in middleware and integration since I started my career at IBM in 2005.

It was a new and different way of looking at integration, and one that would deliver greater speed to market, lower TCO, and more overall value to our customers. The MuleSoft toolset equipped developers with everything they needed, soup to nuts, to deliver using the API-led approach and allow customers to invest in an integration strategy rather than continually burning time and money on tactical approaches. 

MuleSoft was the Salesforce of integration, enabling our development team to move much faster than we could before. Our integration strategy made a rapid shift.

Salesforce and MuleSoft: Better Together

Combining these two platforms drives the needs of digital transformation initiatives much more effectively by giving technology teams every tool they need to move at the speed of today’s digital world. Salesforce provides the ability to handle today’s user engagement needs. MuleSoft ensures that the data that fuels these user experiences can be made available in a very effective way. 

Technology executives who adopt these two platforms to drive their initiatives will enjoy much faster time-to-market and a better total cost of ownership than home growing the solutions using custom code. In the coming months, we will be rolling out a series of blogs and content that describe the multiplier effect of leveraging Salesforce and MuleSoft to tackle complex digital transformation use cases.