Tool
Stack Compatibility Review
The Stack Compatibility Review helps a company decide what to do with the tools it already uses. The answer is not always a direct integration.
Score one workflow or department at a time. Higher scores suggest the stack is ready for connection, automation, a bridge, a wrapper, replacement, or a custom operating layer.
How to use it
Pick one workflow: campaign handoff, lead intake, appointment booking, quote follow-up, support escalation, reporting, approval, onboarding, or another repeated operating path.
For each signal, score whether the current tools make the workflow easier or harder. The result should point to the right next move: connect, automate, bridge, wrap, replace, build, or leave the workflow human-led.
What the result means
A tool with clean access and clear ownership may be ready for a direct integration. A tool with exports but no good API may need a bridge. A useful tool with a messy user experience may need a wrapper. A tool that blocks the business may need replacement or a custom company app.
If sensitive judgment, unclear consent, or weak data quality is involved, workflow redesign and human approval paths come before automation.
Scorecard
| Signal | Weight | Why it matters |
|---|---|---|
| The tool can share data reliably | 2 | APIs, webhooks, exports, database access, or form paths make connection safer. |
| The workflow owner is clear | 2 | Integration works better when someone owns the next action and recovery path. |
| The tool controls a critical handoff | 2 | Important handoffs justify more careful integration, automation, or wrapper work. |
| The team manually reconciles the tool with another system | 2 | Manual reconciliation is a strong signal for cohesion work. |
| The tool is useful but hard to operate | 1 | A wrapper or operating surface may help without replacing the underlying system. |
| The tool blocks growth or visibility | 2 | Replacement or a custom company app may be better than a fragile integration. |