How we choose

Last updated: 31 August 2026

This page explains exactly how tools end up on Project Stack, and what our recommendations are and aren't based on. If anything here seems vague, email us and we'll clarify it.

What we don't do

We don't run a testing lab. We haven't put twenty tools through six weeks of controlled trials, and any site claiming that at our size probably hasn't either. Some tools we've used ourselves; most we haven't.

We don't accept payment for placement. No tool has paid to appear here, to rank higher, or to be called a top pick. If that ever changes, this page changes with it.

We don't score things out of ten. A single number implies a precision we don't have. "Best for teams under ten" tells you more than "8.4/10" ever could.

What we actually do

1. Read the pricing page properly

Most of the useful information is in the parts written to be skimmed. For every tool we cover, we note:

The real entry price, including seat minimums
Which features are locked behind which tier
Usage caps, and what happens when you hit one
Whether add-ons are metered or flat
What the free plan genuinely includes

This is where most comparisons stop at the headline number and get it wrong. A tool advertised at $9 a seat with a three-seat minimum and no automations until the next tier up is not a $9 tool.

2. Read what users say months later

Launch-week reviews are useless. We look for what people say six to twelve months in, when they've hit the limits - forums, community threads, review sites, and support discussions.

We're looking for complaints that repeat. One person finding an interface confusing is noise. Forty people describing the same slowdown as their workspace grows is a finding, and it goes in the article.

3. Work out the real cost

For each tool we calculate what a realistic team or solo user would actually pay, not the advertised figure. That means including seat minimums, the tier where the features you need actually live, and any per-use charges.

Where two tools are close, we show the maths rather than asserting a winner.

4. Match tools to situations, not to a leaderboard

There is no best project management tool. There's a best one for a five-person agency juggling client work, and a different one for a solo consultant, and a different one again for a field team that needs a visual board.

Every recommendation on this site carries a "best for" label. If a tool doesn't fit anyone in particular, we leave it out rather than padding the list.

5. Name the downsides

Every tool has something wrong with it. If a page here doesn't tell you what you're giving up, it's incomplete and you should treat it with suspicion.

6. Re-check quarterly

Software pricing in this category changes constantly - tiers get restructured, free plans shrink, products split into separately-priced lines. Every page shows the date we last verified it. If a date is more than three months old, treat the numbers as indicative and check the vendor's page.

When we get it wrong

We do. Pricing sources contradict each other, vendors change terms without announcement, and we're one person working from public information.

When we find an error we correct it and update the date. When a reader finds one first, we're grateful and we'll fix it.

Email: projectstack.info@gmail.com

We'd rather be corrected than confidently wrong.

How money affects this

Project Stack earns affiliate commissions when readers sign up through our links. Some tools we recommend pay well, some pay a little, and some pay nothing at all.

We recommend free tools regularly - they're often the right answer, particularly for solo users and small teams. If the honest recommendation is "use the free plan and don't pay anyone," that's what the page says.

The practical test: if commissions were shaping our rankings, the free options would quietly disappear from the top picks. They haven't, and you can check.

Page updated

Google Sites

Report abuse