SalesForce Vs SharePoint

I have personal aversion on SharePoint and special appreciation on SalesForce. Why? I like the things done in the right way.

SalesForce has a strong and aggressive “sales force”, and this is something I do not like too much, but they have a very good product. Their platform is built with a clear projection on the future, it’s a real SaaS from the basis till the last feature. And the most important thing: it works.

SharePoint: it does not work, that’s all I can say.

I have seen decisions done at corporate level about the implementation of Office 365, and when these programs start to operate they have thousand issues, delays, lack of adoption by the community, etc.

The corporate level though that they were going to save money: jajajaja!!!! poor guys.

You start using SalesForce and it’s like Facebook, you do not need to read the user manual. The SharePoint users start working with libraries and instead of use metadata, they work with folders, so they are making a wrong decision and they do not know it. Microsoft should think about the way of removing the folders in the sense of the architecture design.

Give me a penny every time there is a failure in a workflow done on SalesForce and I will be poor, give me a penny if a workflow fails on SharePoint and I will be rich in less than 5 minutes.

Thanks Microsoft, as SharePoint fails a lot I have customers that pay me because your product fails. In addition your poor service support has gave me the arguments to demonstrate that my team is not guilty or under prepared to deliver the support: the limit is the product!!! and then, they do not blame us.

There are large number of SharePoint support teams, and none support teams on SalesForce.

If you work on SalesForce as developer you will be always working on projects. If you work on SharePoint as developer, you will be always fixing the first product you installed on production.

Are you implementing SharePoint and migrating from Lotus Notes? I’m so sorry about you.

You see how the solution clearly evolves: winter, spring, summer, winter, spring summer… how much time has been Microsoft denying and ignoring issues of SharePoint 2010? and now they recognize and “suggest” to all people to move to SharePoint 2013; come on!!! this is not serious.

I have had a lot of discussions with people from my company and outside my firm that has the same opinion. Some of them loves SharePoint, but those do not know SalesForce.

They are different things, you do not want to pay all the storage at the SalesForce rate to just to have the documentation there: SalesForce is not a document management system, that’s clear. But SharePoint… what is really SharePoint? I still do not know.

I was talking to a CIO some weeks ago and he still told me that SalesForce is more expensive. He still has Lotus Notes in his organization and I was explaining all the issues he was going to face. He is re-assessing the situation.

Linkedin for SalesForce

Linkedin for SalesForce, this is other business development activity done between these two companies that have demonstrated how to leverage new niches of collaboration and partnership.

SalesForce offers its customers the way to improve their sales, Linkedin offers the access to probably the bigger data warehouse of professional people.

LKDN sfdcSales people use to have a big bunch of cards with their contacts. One of the issues some companies have is that one a sales person leaves the company the some customers go behind him, and they suddenly find that there is not any information about the people behind the portfolio of customers they have. Yes, this still happens.

So, why to purchase it? You can enable that your commercial people link their contacts to your CRM. So at least you have the name of the people.

For sure, this not ensure commitment, trust and other things, but it is another step to have the ownership of your sales process.

Migrating Lotus Notes Apps on the Cloud with Force.com

Here a tutorial video of 16 minutesthat is so helpful to understand this migration process.

The steps for moving the application are:

  1. Re-create data model
  2. Create Forms
  3. Move data
  4. Create Workflow
  5. Create complex business logic

For step #3, they propose 3 tools

  • Apex Data Loader (through CVS conversion)
  • Cloud Converter (LN, Access, Oracle)
  • Detachlt (focused on attanchments)
  • DIY: build your own library

Ok, it’s a 16 minutes tutorial, but I missed:

  • Mentions related to security.
  • A quick demo of the migration kit.

Who is Who?

I work in a place where there are so much people working with different projects technologies, industries…

I would like to focus on 2 guys.

Both implement solutions with a well known platforms.

  • One of them is always advancing with respect the project plan, the other is always delay.
  • One of them does not invest any time on maintenance of the production place, the other typically invest 2 days after a wave on support activities.
  • One implements based in a clear object-based model with a clear MVC, the other implements clicking without know the architecture behind and the platform.
  • One implements independently of the end-user front-end (IE, firefox, mobile…), the other implements just for navigators.
  • One works without paying attention to the server, the other is always looking at the server performance.
  • One has the ability to access to a clear defined log and the other just receives a generic error on the console.

Do you want that I continue?  Just one more:

One implements solutions with SalesForce and the other with Microsoft SharePoint. Just imagine who is who.

Behind the Cloud

…The Untold Story of How Salesforce.com, nice book for summer time, some of the chapters are really good, specially the ones related to marketing and sales, some other chapters are a little bit boring.

behind-the-cloudWhat I liked the most has been:

  • V2MOM model to create alignment: Vision, values, method, obstacles, measures.
  • Marketing tactics.
  • Clear vision about where to go.
  • Partnerships done and why they have been done.
  • How they have been able to attract talent.