What to bring it
Juukbox answers questions about what software costs, because cost is what our catalog can prove. That makes it very good at a narrow set of decisions and no use at all for a wider set. Both lists are below, and the second one is the more useful of the two.
What should you bring it?
Bring it a decision where the price is part of the answer: what a tool costs at the size you will be, what you give up by choosing the cheaper one, and what the total looks like once the add-ons are counted.
What will this actually cost at the size we will be next year?
List price is per seat and the decision is not. The catalog holds the tiers, the minimums and the bands, so the answer can be computed at your number rather than estimated at theirs.
Which of these is cheapest while still meeting a constraint I cannot move?
A budget per seat, a minimum user count, a billing term you will not sign. Constraints are where a shortlist either survives or quietly stops being true.
What does the add-on do to the total?
The plan price is rarely the price. Guests, extra automations, storage and support tiers are held as their own priced components, which is why they can be added to the sum instead of discovered later.
How do I justify this choice to the person who signs it off?
Every amount traces to the vendor page it was read from and the day it was read. When finance asks why not the cheaper one, the answer is on the page rather than in whatever anyone happens to remember.
What should you not bring it?
These are limits of our data, not of our ambition
Each of these is a question we could answer badly and choose not to answer at all. If one of them is your actual decision, a tool built for it will serve you better than this one.
Which of these has the better feature set?
The catalog does not currently hold structured feature data. It holds what each product costs and where that came from. A feature comparison built on what we have would be assembled from marketing descriptions, which is exactly the sort of thing this site exists to avoid.
Which one integrates with the rest of our stack?
Same reason. Integration coverage is a capability claim and we have no verified source for it, so we do not make it.
Which one will pass our security review?
Certifications, data residency and processing terms change on a different clock from pricing and carry a different cost when wrong. We link to a vendor security page where one exists and stop there.
Anything that is not project or portfolio management.
CRM, payroll, data warehousing, support desks. The catalog does not cover them, so there is nothing here for you and no amount of asking will change that today.
If yours is on the first list
Bring the constraint you actually have rather than the one that is easy to type. The narrower the question, the more the catalog can do with it.