Research
Build a feature matrix
How the tools in a space actually compare on the things that decide it.
Fill it in
Which products, one per line.
What actually decides it for you.
Read the docs rather than the marketing page.
Your prompt
Build a feature matrix. [your tools] Compare on: [your compare on] Check every claim against the documentation, not the marketing page. Feature grids assembled from landing pages are wrong in a specific direction: everyone claims everything, and the differences that decide the purchase are in the docs or the limits page. Use three states, not two: yes, no, and partial with a note. A tick that means "technically, via an add-on, on the enterprise plan" is worse than a cross, because it survives into a decision. Put YOUR criteria in the rows. A matrix organised by the features vendors advertise measures who has the best marketing. Date it and cite where each answer came from.
Use Build a feature matrixOpens with everything above already filled in.
Why this works
Feature grids built from landing pages are wrong in one direction: everyone claims everything, and the differences that decide the purchase live in the docs. This checks the documentation, uses three states so a qualified yes cannot pass as a tick, and puts your criteria in the rows.