161–170 of 206 posts
Salesforce is this generation's Lotus Notes. It's incredibly powerful software that when implemented well, can streamline processes, provide easy access to information, and make teams really efficient. However, it rarely seems to be implemented well.
Earlier quoted context omitted.
AirTable is also a relational database editor with a nice UI. I don't know if you could compare the two though.
You can. Airtable is what salesforce would look like if it were built today. Because CRM is so dominated by salesforce though, Airtable's defaults are not CRM and it doesn't market itself as such.
Earlier quoted context omitted.
I’m not sure I understand your point? My understanding is the intended users of Salesforce are most certainly the sales team . And I say this out of experience with using it as part of a sales team at a car dealership I worked at years ago. Every sales person in the company was expected to log all the customers they interacted with, track phone numbers & other info, set reminders to makes sales calls, make notes of w…
> intended users of Salesforce are most certainly the sales team. Alas, intended users are seldom the ones writing checks. As the old saying goes, decision to go with Oracle happens on golf course, not meeting room.
This is a good article and history is Salesforce. Another shorter developer focused perspective: Salesforce is a relational database editor. You can create tables, columns, and relationships, app in a nice UI without writing code. You get automatic views and edit forms for records in the tables. And the whole thing is built on a platform where you can write custom sandboxed code to manipulate those records, or expose…
How’s that really different from MS Access?
This is a good article and history is Salesforce. Another shorter developer focused perspective: Salesforce is a relational database editor. You can create tables, columns, and relationships, app in a nice UI without writing code. You get automatic views and edit forms for records in the tables. And the whole thing is built on a platform where you can write custom sandboxed code to manipulate those records, or expose…
So it's Django?
Earlier quoted context omitted.
I want to add. Not 100% non transferrable. I was able to deliver a project on Service Now without any Service Now training, using my Salesforce architecture background.
Service Now is the bane of my existence. Pray tell if the behind-the-scenes code base is as bad as the experience.
and or
Implement & run
NEVER OPERATE
this is obvious, everybody knows this :)
Earlier quoted context omitted.
Oh I get it. But as I said in another response below, what you're describing is the stage of a contact, not separate objects (in my opinion). You could just as easily have a single object but where the status was "lead" (no company name needed) and "contact" where you add the company information and the ability to add them to an opportunity.
You’re right, it could be done that way, but for the orgs that do use leads, it would mean a lot of repetitive filtering on pretty much every business process. The difference in functional concept between a lead and a contact are great enough that processes (both software and human) between the two rarely overlap. A foreign key does all of this for free. For this reason, I think they made the right choice, especially…