Salesforce Sales Cloud Reviews

We are primarily using it for tracking sales opportunities. Our company has done some things where we've plugged in some resources that it taps into, such as some databases of install base and LinkedIn information about different influential executives that we might reach out to. Those are probably the three primary things that I use.

I assume I am using the latest version.

It helps the company, or at least executives, with forecasting.

It is nice to have the install base information at your fingertips when you look up a company.

We have a very broad set of products at our company. The process to get that information accurately into the Sales Cloud system could use improvement. It shouldn't take weeks of time. The process of identifying products that are being sold for forecasting purposes and sales tracking purposes is too hard.

We're starting to prepackage new product builds that address replacing the install base. If we can get that to be really smooth, it would be great. If a storage array is going to end of service/life, I am looking at something that not only tells me that but also says, "You should replace it with this, and here's the build for it." This way, you don't have to go through the process of throwing up what the new array would look like to get it over to the customer.

I have been using this solution for two years.

I don't really have problems with it. It seems to work when I access it.

I don't perceive any problem from where I sit. 

We probably have 5,000 people who are using this solution. They range from salespeople to management. It is being used extensively. I don't know what the corporate plans are to expand its usage.

I did not contact their support.

I would rate it a five out of 10. The reason is that I'm not using it for myself. I'm using it for other people to get information because I have to do it for my job. It helps me with that, but it is not particularly useful for me in my sales tracking.

I am fundamentally a consultant to businesses exploring CRM solutions. My first choice, subject to the customer's budget, is Salesforce. At my office, we have been using Salesforce primarily for lead management, sales cycle management, renewal management, and sales performance management. We have also integrated it with our help desk and our HRMS. 

We use the Salesforce Platform edition with 300 objects which gives us a phenomenal ability to develop specific functionalities that we need for our unique requirements.

An integrated approach to CRM always helps in streamlining activities across all the departments. We have been able to better our response times, reduce our sales cycles, and have increased overall sales revenue. Similar results have been observed for all our customers who have implemented and adopted SalesCloud in the right manner. 

We have developed a module for integrating our digital marketing tool with Salesforce. The campaign ROI monitoring ability has helped us to increase our marketing effectiveness to a great extent.

There are many extremely useful features. Lead scoring is useful for automatically signaling the importance and urgency of acting on any particular lead. Website integrations are useful for getting in the lead data into Salesforce along with auto-tagging of the customer's point of interest. The automation rules that have been set up across all modules deliver tremendous value by speeding up things, ensuring process compliance, and increasing productivity. 

The customized and role-based dashboards help our team to make the right decisions.  

Featurewise, the product almost has all CRM features that one can think of. Beyond CRM, if the integration with MS Office can be made tighter and smoother, that could be great value for customers. Especially integrating MS Word and MS Excel would be really useful. 

If a lighter version of CPQ is made available, it would help many midsize customers. As of now, Salesforce is the most expensive CRMs out there - making it a bit more affordable will help them in a big way. 

There are also certain restrictions on the reports in terms of the number of records. Ideally, that should be removed.

I've used the solution for more than seven years.

The solution is extremely stable. We haven't seen any nasty surprises. trust.salesforce.com is a great place to check the stability and dependability of Salesforce.  

Irrespective of the number of concurrent users, the automation rules, reporting requirements, workflows etc, the system performance remains the same. There is no performance degradation by additional of number of users or increase in data or increase in automations or functionalities whatsoever. 

trust.salesforce.com gives a real-time view of all salesforce datacentres and the various clouds in terms of their health, availability, uptimes, maintenance status, security and compliances. There is a lot more indepth information if one really wants to dig deeper. 

It is highly and seamlessly scalable. it is very robust at any scale.

This is not applicable to us. However, the back-to-back support from Salesforce has been pretty good.

Positive

We have used a homegrown application earlier. Switching to Salesforce was due to the capabilities provided by the Salesforce platform. It practically molds itself as per an organization's working style. 

It wasn't complex for us as we are ourselves are implementation partners. For customers, it can turn out to be pretty overwhelming. 

There are so many features and so many possibilities, it is very easy for anyone to keep asking for more. That is often the biggest pitfall. A step-by-step phased approach is usually more successful.

We have a highly skilled implementation team.

We've seen an ROI of at least 20%.

Salesforce surely is one of the most expensive CRMs out there. However, if implemented in the right manner and adopted extensively, it does deliver a great value to the organization. 

While deploying Salesforce, I would generally suggest engaging a consultant for optimizing the license costs. Salesforce sales team may try to oversell. A 3rd party consultant like us can help you with an unbiased opinion. 

We did not evaluate others while choosing for ourselves. However, as a consultant, we frequently need to show customers comparisons with Navision, SAP, and Oracle.

I use Sales Cloud quite often through an apprenticeship I am doing at a non-profit organization. I do utilize Sales Cloud often, and practice using Trailhead. I also use Sales Cloud with the Nonprofit Success Pack, or anything pertaining to that. We also make use of the Education Data Architecture. I have used Sales Cloud in the past as an administrator.

Sales Cloud really helps to point out different numbers for our company in terms of what converts or what doesn't. Different leads and fields can be utilized inside of Salesforce, using Sales Path to follow those specific leads, and it demonstrates what leads convert over into opportunities. The leveraging of fields help to track progress on the user interface. I think that's fundamental, especially for users or individuals that don't know how to use Salesforce. It's easier to track. The page layouts are pretty good for users as well, to track those numbers.

I would say Sales Path is something that I do like to use to track leads and opportunities. It's a pretty cool feature to use inside of Sales Cloud. Different fields inside of Sales Cloud have pretty cool features in Salesforce too.

There are different applications that can definitely help leverage Salesforce when it comes to data management. Importing and exporting different applications can be used to help that process. 

In addition, applications that can help with migrating data over from the sandbox to production would make it easier because sometimes changesets can be bulky and they're not always as effective. This can be frustrating when you make a lot of changes and try to put those changes into production.

Sometimes uploading and making changes to processes can be a little slow.

The implementation of automated processes could be a little bit better understood.

It is a scalable solution. 

We previously used a Microsoft platform. 

It wasn't easy. The difficulty was in tracking the changes that were made inside of the Sandbox, and then trying to put all the changes into a changeset into production. There were certain fields that you needed to have inside the changeset that wasn't there, so it made it a hassle to deploy.

It took a couple of days to deploy. 

It was implemented in-house. There were about three people that were involved with deployment.

We track changes inside of the platform and they are major programs that help the non-profit to run and complete their mission and vision. 

Salesforce Sales Cloud is reasonably priced. 

I would recommend getting assistance from people that know what they're doing in Salesforce. They should get a good idea of what the client wants and take it from there. 

I would rate it an eight out of ten. The implementation of automated processes could be a little bit and better understood.

Our main use cases for the solution are B2B directions, some presale activities, and some of our service manager activities, which are mainly requests for supplies, certain products.

We do re-house implementation, sales calls for our B2B segment, so it's business to business. We are actually covering all of our sales interactions with our clients within Sales Cloud, just trying to keep the information in one place and all of the activities, according to the sales cycle, within the Sales Cloud, within the certain records inside Salesforce.

The main way the solution has improved the organization is by giving a good understanding of how the salespeople should be tracked, how to restructure their work. Normally salespeople can be disorganized, so we have people who do something which is very difficult to track. However, some people won't do anything until the deadline is tomorrow. So all of the directions, all of the processes should be tracked and sales will give you the understanding. If a salesperson is working to discover a relationship with a client and is trying to sell something, it can be very easy, very intuitive, with very few fields. 

Then you can see if something is moving on or still at the same place for months or even years. You can easily identify it by creating the opportunity and seeing whether you made progress or not. As long as you understand how it should be tracked, the only thing is left to go to sales and say that you expect anything you do to be reflecting this in a certain record, and either I see the progress there, or I can see there's no progress at all. You can say that you're doing something, but if I do not see it within the system, it does not exist.

One of the most valuable features is with management within Salesforce. This is one of the important parts of the process we have right now in place. 

First of all, the point of view that Salesforce gives you on certain object models normally satisfies the biggest parts of the business. In a lot of business scenarios, because the sales process is more or less at a high level the same, in different areas, it's been changing. On the high level, it's all about managing the clients, managing the opportunities around those clients, managing the tasks, calls, activities, all those things are already pretty fine on Salesforce. 

Flexibility is the second point I would like to mention. The flexibility is pretty high and we can set up different scenarios. We can use different pools, both with developer experience and with development experience, making things automated within Salesforce. So it gives you an opportunity for not just a flexible set up, the processes you would like to set, but also to automate the things and make the automation for different scenarios, like providing emails, assigning leads, assigning the right clients to the right people. And also automate that during the sales cycle, if we're talking about providing the resources and providing the information resources.

And I would say the interface isn't perfect, but it's much better than the other CRM systems can provide. So it's not 100% modern if they're talking about making it 21, but compared with the competitors, you can see that Salesforce is way better in terms of user experience. Working the system, it's much more intuitive, it's more user-oriented, user friendly than the other systems I had in my previous experience.

One area where the solution could improve is with handling feature requests. Salesforce has its own community all over the world and people submit ideas saying, okay, that's what's needed. The number of requests is pretty high, and all of these requests are stored for years, but people need these. These features that I requested really sound obvious, but they're still for five, four, six years remaining just the same. When you search for a feature and find that someone created a request years ago, and 6,000 or more are saying, "yes, of course, we need this," it's an obvious feature. It's not that difficult to implement but the waiting line can be up to 10 years long.

One of the features I'd like to see in a future release is a way to see the updates of all the records that I follow. Not an email notification, but a single page to see the information for all the records I'm following. There is a solution that can partially satisfy this need in Salesforce Classic, but it's also classic and old-fashioned, and we would not like to promote the initial sales software within our firm. We are trying to keep Salesforce Lightning as the main tool. Rather than asking the commercial director to switch to Salesforce Classic, just to see a part of the information, but if you need both, we'll be able to give it.

The other area that is definitely a waking point for me is the integration with Slack. Slack is pretty popular and we're trying to launch it as well. The basic integration that is out-of-the-box is pretty small. Having both of these products in the product portfolio in the same company, we actually really expect to have it highly integrated for different scenarios, like task assignments, following notification, so even the same balance can be done within Slack and assigned to a certain account record in Salesforce. There is a huge field for improvement; right now these two products are pretty separated, despite the service.

And the third thing I would say is a Salesforce strategy. A lot of countries, all over the world are trying to protect personal data. And the limitations are increasing here and in new territories, like China, Russia, India, Arabic countries, GDPR regulation, European Union, all of these things that you require the new response from the platforms that are actually dealing with this personal data, personal information. Salesforce itself, its data is a GDPR compliance system, out of the box. The only funny thing is it's two digital compliance until you start entering the personal data there. As long as you are entering personal data there, so they can do some GDPR compliance, in terms of Russian regulation, Chinese regulation, Arabic countries' regulation. It's definitely something that we expect to be improved.

I've been working with Salesforce Sales Cloud for three and a half years.

The stability and performance of Sales Cloud itself, which is provided by Salesforce, is pretty good. We are pretty satisfied with it. We didn't have any huge lags in months with Salesforce downtime; some certain tools that we actually implemented ourselves, were not the level of reliability of Salesforce, though. But that was something we implemented in our own home. The problem was not with Salesforce, but really the tools, the way we actually implemented it.

Ease of scalability depends on where we actually are scaling, and if we had a certain predicted behavior, such as we have a new region to sell, we have a new person in the new region or have a new account, etc. It definitely requires not just some maintenance, but some developments as well. 

We have approximately 100 users in our company. We're using the solution more and more often. Initially, it was a certain form where sales just gave everyone the opportunity. Then we came to the decision, we want this as a system to direct those people on a regular basis. Now we have a regular meeting and the information from Salesforce is checked by the commercial director. We're trying to introduce the solution to see the broader picture, the full pipeline for targeting the client, and finishing the client when you've closed the case.

Technical support has been pretty helpful, in those rare cases I actually use it. During my previous experience, which was also connected with Salesforce, we had some strange cases escalated to Salesforce, and the answer was, okay, we will fix this in one of our upcoming releases. But that was a matter of half a year, and we had a business stopping issue. But after a certain escalation, we actually managed to do this fix earlier. However, we expected it to be faster.

Previously, I've worked with this SAP, and I was working with a custom regionally developed CRM system based on the Microsoft platform. Salesforce has better flexibility and orientation to the user. SAP has perfect functionality and it's really powerful. However, I wasn't fulfilled with the SAP for five years before I actually left SAP. It was like people who developed it just forgot about the end-users. So the interface, how the end-users actually interacted with the system, was horrible. Salesforce is way better. However, SAP also had the best effort in giving data during the later five years.

The initial deployment can take time. We started the project in February, and the deployment was in June, end of June. Five months, and we are not talking about the prerequisites, because we gathered the business scenarios we need to finish the analysis. So if you're talking about the analysis and prerequisites as well, so it will three months more.

Update deployment prevents a lot of issues, as it gives you the opportunity to change the things that can be badly influencing the production system. So you invest some time to get a deployment done. It still takes hours to deploy and there is a certain benefit behind this. The more time spent on deploying, the fewer issues on production. However, there is certainly fuel for improvement there.

The initial deployment was a group of about 20, involving people from different parts, both development, quality assurance people, admins, business analysts, business representatives, salespeople, pre-sales people department. So this group was much broader than future deployments.

There is only one person who actually doing update deployment for us. However, the more we grow, the more people will be involved in the deployment. And we work with the vendor because certain parts of our implementation require the help of Salesforce authorized companies which help us to do this. And there were more people than one to do the deployment because different groups of people were involved in the development. To merge the codes of different groups of development, we required the efforts of recruiting people. Either two or three people were involved in the deployment; they were not only our internal team working with the development.

Right now I'm operating on the Russian market, and in terms of investment value and return of the investment, Salesforce right now is pretty good in the Western markets where the price of the employees is pretty high.

Here in Russia, the country has a cheaper workforce, so the investment into Salesforce Solution is questionable, in terms of the return on the investment. The price model, is oriented on the best markets and there is a certain sense of investment in Salesforce there; but here in Russia, prices for the workforce can do the same thing easily. It's the 21st century, probably manual work should be reduced each day. We think if we look at this problem in terms of the investment, it will be a big question if it's worth the money, as Salesforce is pretty expensive.

The biggest advice that I can give to anyone considering Sales Cloud is to develop a good pre-analysis before the implementation and don't overload the stages of the opportunity. Think what the main purpose of these stages is. The best way to make it work for salespeople and for the commercial department is to structure it that way, that it will now reflect the stages of the penetration to the client. Pursue methodology, when we have targets, interact, propose, close. It's not just throwing the opportunity between the different departments, but it's complete and clear and simple, which is very important. You don't have 20 stages, but you have five certain career stages, which actually reflect the steps when you're closer and closer to the deal. Not in terms of working with the documents, but in terms of structuring the sales process in terms of the penetration to the clients.

Also, very close to the implementation, the final day of the goal, dedicate as much time as possible to the data migration. Dedicate as much time as you have, consider doing data migration; it will be difficult. We will have a lot of migrant issues rolling the data from the previous system to the new one. So two or three weeks is the shortest period that should be dedicated to that purpose.

I would rate the solution a seven out of ten.

A client was running the sales and marketing operations in a spreadsheet, and they wanted to have everything in one place. So, they migrated to Salesforce, and we helped them out with:

• Creating the object structure
• Mapping their objects with native Salesforce objects
• Putting together the page layout for the team
• Adding the data from the sheet into the instance

In terms of deployment, it was on the Salesforce cloud. The users had to log into it through a browser.

It enabled them to centralize the location of all the information. For example, everyone could enter the lead information in the central location, and then the higher management had a high-level overview of all the leads that came in. They could see how long it was taking to process leads and close them from the time leads come in. It keeps track of the close date as well. 

You can set up automation for following up and sending emails to the rep when the leads first get assigned. You can also run automation where if there is no activity on a certain lead for 30 days or so, the lead owner gets the notification. 

The ability to work on it from anywhere is most valuable. All you need is a computer, a browser, and an internet connection to access your instance. It can be accessed from anywhere, which is pretty cool and user-friendly. 

Its licensing can be improved to accommodate small companies. They provide a certain number of licenses in a set or batch, and you have to buy the set. For example, if they have 20 licenses in a set, you have to get the whole set, even if you need just three licenses, which could be a barrier for small companies. There is no option to buy fewer licenses. So, small companies have to go for a smaller CRM, such as HubSpot.

It has been pretty stable. When they have any maintenance, they usually send a notification saying that the system is going to be unavailable from a certain time, which is usually over the weekends. Usually, no one uses the system at that time.

It seems to be pretty good. It provides the ability to use different types of automation. If you want to create complex solutions or automation, you can do that. You can also start with simple ones and then go into the more complicated ones.

Currently, we have around 10 to 15 users who use this solution. They are usually into business development. There is also a leadership team with around five or six people. There are two different divisions of the company. One is marketing, and one is sales, and then there is also a business development section. So, each team has a number of people associated with it.

It is being used extensively. If we onboard new people, it'll probably scale.

They're fairly responsive. They usually respond within half a day. They send the details or instructions about how to resolve an issue. If it's something that belongs to a future release, they redirect us to the post mentioning that.

Its deployment was fairly straightforward. It wasn't too complicated for this use case. The complicated part was figuring out and mapping the existing objects and data structure with the Salesforce data structure.

For deployment, we had a team of three people. This team included a project manager, a developer, and me. We didn't really need the developer. We had him in case we had any complicated deployment. It was a smaller implementation, and it took about two months.

Its maintenance depends on the scale. If it is a big deployment, you would need an admin. For our internal instance, currently, we don't have an admin, but in the next few months, we'll probably be looking for a dedicated internal admin because we want to implement a few data projects. We're trying to create a partner portal, and we are thinking of hiring a dedicated admin for that.

It is alright for now because we ended up getting a discount off the base price. So, for now, it is okay. We may have to renegotiate when we get more users, and I don't know if the price would stay the same or increase.

It has just a standard licensing fee. If you end up hiring a consultant for implementation, you will have to pay for the implementation. Other than that, there are no additional fees.

You should know what your use cases are. Try to figure out if you will be extensively using automation or not. If you're not, you can use the lower licensing versions that are pretty cheap. The basic model was about $25 a month per user, and you can probably have three users for that, but it doesn't give you extensive automation capabilities. You will have to do a cost comparison for your specific use case to see if the basic license fits the needs of your business.

I would rate it an eight out of 10.

We are using Salesforce Sales Cloud to develop sales processes. For example, from the lead creation, submitting the contract, and sending the contract via DocuSign for the user to sign it. We use principle objects, such as opportunity, lead, account, and contact, and some process automation to automate the process of sales.

The automation of Salesforce Sales Cloud makes the process very easier to focus on leads and converts them automatically to accounts, contacts, and opportunities.

Salesforce Sales Cloud could improve by allowing some customization of the processes with coding to avoid the problem of memory. When we use only flows in the process, which can become large flows, they are more complicated to debug and also for maintenance. It's better to invoke some Apex classes to make the process better.

I have using Salesforce Sales Cloud for approximately three years.

Salesforce Sales Cloud is stable.

We have approximately 100 users using this solution in my organization. 

Salesforce Sales Cloud has the ability to scale to large numbers.

We are using this solution on a daily basis.

I have been satisfied with the technical support of Salesforce Sales Cloud.

We deploy the solution using many different tools. The process is simple because you only need to create the package and component and choose the sandbox.

The time it takes to deploy the package depends, it could take a few minutes. However, when we use GitLab or another tool, it takes more time than changeset.

The amount of people involved in the implementation depends on many factors. I have worked with many managers, such as GitLab managers, and we created a branch and later deployed it.

There are some releases that need to be updated and some packages that are necessary for maintenance.

I have found Salesforce Sales Cloud to be expensive. However, it is the number one CRM solution in the world. It is worth the money.

I would recommend this product because it can give a company a chance to have new clients. There is a lot of functionality that can increase the number of clients they have.

I rate Salesforce Sales Cloud a nine out of ten.

I'm using it to track opportunities and keep track of customer relations.

It's fast. It's accurate. I can access it anywhere. I can log calls live, keeping the information fresh in my mind. It has really helped expand our customer base.

I can see activity per customer. I can find out quickly and easily who was the last person I talked to, when it was, and what we were talking about.

I like its reporting.

Sometimes, it is difficult to integrate it with my emails. I've had trouble integrating it with my emails. There were a couple of things I did try as well, but I wasn't able to do so. 

I've had difficulty in other areas too with integration. It was related to syncing my calendars. I want the tasks that I put in to automatically sync to my calendars and update my calendars, but I couldn't figure out how to do it.

I have been using this solution for three years now.

I haven't had any issues so far.

I'm only using a small portion of it. You can do a lot more than I'm using it for, but I haven't gone into that yet.

There are 10 people in our organization who are using this solution. It is currently not being used extensively in the organization. It could be used more. Right now, we're just scratching the surface.

They were good, and they helped me through my issues.

I used Sage CRM for a while, and it's not very much fun to use. I switched because every time I had to do something, I had to contact our company IT support. It was too cumbersome. They had to get involved every time I wanted to do something, and I needed to be able to do things quickly and without having to go through someone else.

I had to set it up myself. There were some parts of it that took a little bit of learning, but I found the videos and other resources helpful.

My advice to others would be that they should talk to a consultant and tell them everything they want to do beforehand. They should make sure that they have a plan in place to get it set up the way they want to right away.

I would rate it at least a nine because it is really easy to use, and it has helped me a lot.

The primary use case is if you want to update old legacy systems and go into a more mobile way of doing business. One of the main competitive advantages of this solution is that it already offers an 85% solution (out of the box), and you can modify it if you wish.

Salesforce does not offer anything on premise. It's always in the cloud.

No installation of software, or security updates. Easily working together with colleagues.

Salesforce wishes to push for a declarative way of solving IT problems.
As an end user, you can do a lot by yourself, so you do not have to write code. The idea is that they go for low-code and they use flow. It's possible to update records and do things like automation without writing real code. I think this is one of the advantages of the solution.

Also you can easily collaborate with your colleagues. Another main benefit is that you can find a lot of information on websites, and you can learn it yourself through Trailhead. It's a guided way of learning new topics, and it's completely free.

The company has a policy of three releases per year.

One of the advantages of Salesforce is that it's fun. With features like Trailhead, the gamification makes it a joyful environment.

The reporting part is a bit low. You have other possibilities, like Einstein, or Tableau.

The deployment of (meta) data from the sandbox environment to production is also a weaker point because their solution is not powerful (even non-existent).

I have been working with Salesforce Sales Cloud for more than five years. 
I work as a Salesforce functional consultant. My role is to improve the adoption ratio of the client. I help implementing (declarative) and migrating legacy systems towards Salesforce.

The stability of Sales Cloud (and Salesforce in general) is extremely reliable. Ten years ago, we were one of the first Belgium customers that got a massive implementation of Sales Cloud. Servers were in the United States, there were several complaints from customers that it was taking too long. Salesforce acted and invested heavily in data centers in Europe, and now I have never had any issues with reliability or stability.

The solution is extremely easy to scale up because you can go from the Professional Edition to the Unlimited Edition.

You will only have a problem if you wish to downgrade.

If you have a problem, you can open a case with Salesforce. They give it a status, like high, low, or medium. If it takes a bit of time, maybe it's linked to the fact that your case is not crystal clear. If they don't do anything after a while or if you haven't heard back from them, then you can escalate the case.
Of course all is linked to your service contract and SLAs.

Positive

Salesforce doesn't require any specific maintenance. Salesforce works like a hotel. You just rent a room for a particular period, and the rest is done for you.

The main issue is the price. Because it's SaaS, you will have to pay on a monthly basis. It will become very expensive because you'll be thinking, "I have Sales Cloud, and I want to do service and help my customers, so I need another cloud." This is something I have already seen with other customers. They would like to jump into the Salesforce environment, but it can become a hefty price tag, so that's an issue.

There are different licensing models. 
You could have the Essentials, Professional, Enterprise, and Unlimited edition. It is linked to functionality. I only work for multinational clients, so they usually use an Unlimited or Enterprise solution.

If you are a big company, then you have a lot of leverage and more power to decrease the cost of your system per month. A lot of people aren't aware of that. If you go into a full-fledged solution, you can still bargain or discuss the price.

Only one person is required for deployment, and you can automate it if you wish. If you have a good developer who creates that, and you have your deployment street, you can push information into the production environment on a nightly basis.

I would rate this solution a 9 out of 10.

Sales Cloud is suitable for everyone, even a mom and pop shop, if you have the money to invest in it ( I would not recommend it for a very small company that has only one FTE). 
If you have five or 10 SEs, you can definitely use it, all the way up to Fortune 500 companies. Most companies that use Salesforce are Fortune 500 companies.

I would definitely recommend that you try to stick to what Salesforce offers. You should not try to change the native setup of Salesforce, otherwise you will face issues with new releases. You should try to follow the spirit and idea of Salesforce, for example avoid large coding because then you will/can screw up the system.