What Tool Is Right?

Gabriel Marechal

12/12/20251 min read

What Tool Is Right?

Over my career, Iโ€™ve probably had to use and/or recommend hundreds of different tools to a disturbing variation of success.

So whenever I get asked for a Revenue Tech Stack recommendation, I always say that the individual tool matters less than the way it actually functions within your org's existing ecosystem โ€“ process, platforms, and people.

And so, to me, the single most important thing to look out for in your RevTech is its integration capabilities โ€“ both technical and otherwise.

Here are the 3 questions I would ask and the scenarios where Iโ€™ve seen the most and least success:

๐—–๐—ฎ๐—ป ๐—ถ๐˜ ๐—ถ๐—ป๐˜๐—ฒ๐—ด๐—ฟ๐—ฎ๐˜๐—ฒ ๐˜„๐—ถ๐˜๐—ต ๐˜†๐—ผ๐˜‚๐—ฟ ๐—ฐ๐—ผ๐—ฟ๐—ฒ ๐—ฑ๐—ฎ๐˜๐—ฎ ๐˜€๐˜†๐˜€๐˜๐—ฒ๐—บ๐˜€ ๐—ฎ๐—ป๐—ฑ ๐—ต๐—ผ๐˜„ ๐—ฒ๐—ฎ๐˜€๐—ถ๐—น๐˜†?

๐Ÿ‘ Best case scenario: Itโ€™s a native tool to that data source or at least has a native integration.

๐Ÿ‘Ž Worst case scenario: The connection requires an additional 3rd-party app or a Frankensteining of code in order to work properly.

๐—›๐—ผ๐˜„ ๐—ฑ๐—ฒ๐—ฒ๐—ฝ๐—น๐˜† ๐—ฐ๐—ฎ๐—ป ๐—ถ๐˜/๐˜€๐—ต๐—ผ๐˜‚๐—น๐—ฑ ๐—ถ๐˜ ๐—ถ๐—ป๐˜๐—ฒ๐—ด๐—ฟ๐—ฎ๐˜๐—ฒ?

๐Ÿ‘ Best case scenario: The data access requested by the new tool maps neatly with the tool's purview, and data permission requests can be easily explained.

๐Ÿ‘Ž Worst case scenario: An unnecessary/seemingly unconnected level of data access is requested for basic functionality (for example, requires system admin-level permissions to read one field... ๐Ÿ˜ตโ€๐Ÿ’ซ). High levels of data have to be sent between platforms and/or at a high frequency.

๐—–๐—ฎ๐—ป ๐—ถ๐˜ ๐—ถ๐—ป๐˜๐—ฒ๐—ด๐—ฟ๐—ฎ๐˜๐—ฒ ๐˜„๐—ถ๐˜๐—ต ๐—บ๐—ถ๐—ป๐—ถ๐—บ๐—ฎ๐—น ๐—ฝ๐—ฟ๐—ผ๐—ฐ๐—ฒ๐˜€๐˜€ ๐˜‚๐—ฝ๐—ต๐—ฒ๐—ฎ๐˜ƒ๐—ฎ๐—น?

๐Ÿ‘ Best case scenario: Automations and safeguards are built-into initial implementation to circumvent manual checks and balances (beyond an audit phase).

๐Ÿ‘Ž Worst case scenario: Manual intervention is required to ensure basic functionality (i.e proper data flow), multiple platform training sessions needed.

Youโ€™ll know when youโ€™re in a worst case scenario when the implementation process starts to drag on and on, and the post-implementation checklist gets longer and longer.

And the best-case scenario for the best case scenario?

Having an empowered RevOps team that can oversee the bigger picture of that ecosystem and make high-level decisions as to what is added/removed/altered.

ForecaaS Software

The Recurring Revenue Specialists for Salesforce

Questions?

ยฉ 2025. All rights reserved.