Sanjay Tools: a shared customer view across more than 14 business verticals
Sanjay Tools and Accessories needed customer information to work across a complex distribution business. Different verticals needed ownership of their activity, while management needed a broader view of the customer relationship.
Client and business problem
The Pune based industrial distribution business operated across more than 14 business verticals. Its previous Salesforce setup provided the context for a review of application fit and licence procurement costs. The challenge was to support vertical level work without losing the consolidated customer picture.
What Fristine built
Fristine's published case describes a Zoho One implementation centred on shared customer visibility and business vertical ownership. The configuration connected information needed by the operating teams with management's view of the relationship.
The approach matters where one customer may interact with several product or service groups. Record ownership and reporting need to reflect that structure, so that a common customer database does not obscure the responsibilities of individual teams.
Reported result
The case reports a 60% reduction in licence procurement cost compared with the previous Salesforce setup. The figure concerns the historical licensing comparison in this project. It does not represent a 60% reduction in total implementation cost or a general price comparison between every Zoho and Salesforce configuration.
Plan a comparable review
For a multi vertical business, a useful starting point is a map of customer ownership, reporting needs and licence eligibility. Fristine can use those facts to assess application design and the total cost of the proposed scope.
Book a sessionFrequently asked questions
What type of business is Sanjay Tools?
Sanjay Tools and Accessories is described in the published case as a Pune based industrial distribution business with more than 14 business verticals. That operating structure is central to the project: individual teams needed to manage their activity while the organisation retained a consolidated view of customers and business relationships.
What was the main design requirement?
The project needed to balance vertical level ownership with a shared customer view. This is relevant when several teams serve the same organisation through different products or services. The implementation approach addressed how records and reporting should support that structure, rather than treating every team as a completely separate customer database.
Which Zoho offering was implemented?
The published case identifies Zoho One as the chosen platform. The value of a comparable implementation depends on the applications, processes and users included in the agreed scope. Licence eligibility and application fit should be reviewed for the new business rather than inferred from the product name in this historical case.
What does the 60% saving mean?
It is the reported reduction in licence procurement cost against Sanjay Tools' previous Salesforce setup. It is not a measure of total project return, productivity improvement or every recurring technology expense. Any new comparison needs current vendor pricing, the required editions and a clear statement of which costs are included.
Does this show that Zoho always costs less than Salesforce?
No. It describes a particular historical licensing comparison. Current costs depend on edition, user numbers, negotiated terms, applications and implementation needs. A purchasing decision should compare the functionality and total cost of the proposed configurations, including integration, support and administration, rather than applying this project's percentage to another organisation.
How should a multi vertical rollout be phased?
Begin with shared customer definitions and the ownership rules that every vertical needs. Then select a manageable first group, test access and reporting, and expand once the process is accepted. The project plan should identify migration dependencies and business approvals so individual teams can adopt the system without losing the common customer view.
Which businesses may find the case relevant?
The case is useful for distributors and other organisations where several business units share customers but need distinct ownership and reporting. A similar structure does not automatically require the same configuration. The first review should establish account relationships, data responsibilities and management requirements before choosing an implementation approach.
How should a similar project measure success?
Agree measures that reflect the problem being solved, such as the quality of shared customer records, reporting effort or licence cost under the chosen model. Establish the baseline before implementation. The Sanjay Tools result provides a reference point for discussion, while the new project's acceptance criteria and expected benefits must be defined separately.