Siebel Business Process Implementation Guide > Using Siebel Business Processes > Guidelines for Planning a Siebel Implementation >

Customizing Siebel Software


Companies that purchase enterprise software are agreeing to make significant changes to increase their returns and—in the case of CRM—to improve customer satisfaction.

In addition, these companies have determined that purchasing software solutions—rather than building their own software solutions—provides an improved return on investment. What sets a company apart from its competitors is its ability to execute, its culture, or its employees. Some constituents within a company believe, however, that it is the company's unique use of a technology that sets it apart from its competitors. The use of custom-built technology can sometimes be a strategic advantage. However, by using Siebel business-process-based applications, in conjunction with the Siebel Universal Application Network and Siebel Systems' support for Web services, customers can easily combine Siebel applications with other enterprise-class applications that support their unique service or product offerings.

Rather than heavily configure the Siebel application to match your current business processes, it is recommended that you select from the premapped business processes that Siebel applications support. Overcustomization can reduce the efficiency of the software and the business process.

However, there may be compelling business reasons why a company needs to configure its implementation of the Siebel application to the company's business processes. For example:

NOTE:  A company may decide to configure its implementation if the current sequence of tasks does not exactly follow the sequence of tasks provided in the predesigned business process. Before deciding on configurations, you should confirm that the predesigned process (despite the altered sequence of tasks) prevents you from achieving your business goal, and therefore will not work.


 Siebel Business Process Implementation Guide 
 Published: 18 April 2003