Technology independence
Compare outcomes, not logos
Technology selection should start with requirements, constraints, total cost, portability and operational fit. These guides expose the decision criteria rather than awarding a universal winner.
CRM
A detailed decision framework is already published.
Cloud
AWS vs Microsoft Azure vs Google Cloud
Compare workload fit, skills, identity, data gravity, resilience, governance, portability and total cost
Avoid moving workloads merely to standardise a logo
Automation
Power Automate vs Zapier vs Make vs n8n
Compare governance, connectors, self-hosting, observability, maintainability, licensing and citizen-development controls
AI platform
Compare model quality for the actual task, data handling, tool support, evaluation, latency, resilience, portability and cost
Use multiple providers where the business case justifies avoiding a single critical dependency
Decision rule
Document requirements first
Score must-have constraints before preferences
Model three-year TCO
Test migration and exit
Disclose commercial relationships
Record why the selected option won