I’m spending this week at Alfresco’s Sales Kickoff in Chicago, and having a blast. There’s a lot of energy across the company about our new Digital Business Platform, and it’s great to see how many people instantly and intuitively get how Alfresco’s platform fits into a customer’s digital transformation strategy. When content and process converge, and when we provide a world class platform for managing and exposing both as a service it’s a pretty easy case to make. We have some great customer stories to drive the point home too. It’s one thing to talk about a digital strategy and how we can play there, but it’s another thing entirely to see it happen.
Content management is undergoing a shift in thinking. Analysts have declared that ECM is dead, and content services is a better way to describe the market. For my part, I think they are right. Companies ahead of the curve have been using Alfresco as a content services platform for a long time. I decided to do a little digging and see when Alfresco first added a web API to our content platform. A quick look through some of our internal systems shows that Alfresco had working web services for content all the way back in 2006. It was probably there earlier than that, but that’s one of the earliest references I could easily find in our systems. That’s over a decade of delivering open source content services. Here’s a quick view of the history of content services delivery channels in the product.
I don’t think any other company in the market space formerly known as ECM can say that they have been as consistently service enabled for as long as Alfresco. It’s great to see the market going to where we have been all along.