When we think of enterprise SaaS companies today, just about every startup in the space aspires to be a platform. That means they want peopl...
When we think of enterprise SaaS companies today, just about every startup in the space aspires to be a platform. That means they want people using their stack of services to build entirely new applications, either to enhance the base product, or even build entirely independent companies. But when Salesforce launched Force.com, the company’s Platform as a Service, in 2007, there wasn’t any model.
It turns out that Force.com was actually the culmination of a series of incremental steps after the launch of the first version of Salesforce in February, 2000, all of which were designed to make the software more flexible for customers. Company co-founder and CTO Parker Harris says they didn’t have this goal to be a platform early on. “We were a solution first, I would say. We didn’t say ‘let’s build a platform and then build sales-force automation on top of it.’ We wanted a solution that people could actually use,” Harris told TechCrunch.
The march toward becoming a full-fledged platform started with simple customization. That first version of Salesforce was pretty basic, and the company learned over time that customers didn’t always use the same language it did to describe customers and accounts — and that was something that would need to change.
Customizing the product
from TechCrunch https://ift.tt/2JyrcGi
via IFTTT
COMMENTS