Suite gravity and app sprawl
The appeal of a suite is one vendor and shared data. The risk is that you end up running several applications to do one job, each with its own settings and its own learning curve. Count the applications you will actually use before you count the ones you could.
The size of business each assumes
Both serve small and mid-sized businesses, but suites reward organisations with defined functions: someone in finance, someone in support, someone in sales operations. A ten-person business where three people do everything gets less from that structure.
Breadth versus depth
Breadth is genuine here, and depth varies by module. The module you care about most may not be the strongest one in the suite. Evaluate the sales application on its own merits, as though the rest of the catalogue did not exist, then add the suite benefit back afterwards.
Implementation and administration effort
A suite is a programme rather than a purchase, especially if you deploy several modules at once. Decide who owns configuration and whether that ownership is realistic. Unowned modules drift out of use quietly and still appear on the invoice.
Channel coverage
Ask specifically what is native for calling and WhatsApp in the edition you would buy, rather than what exists somewhere in the catalogue. In India that answer decides whether your busiest sales channel is on the record or on a personal phone.