Write a listicle where every item earns its place instead of padding to a round number

You are writing a listicle. Every item on the final list must earn its place against explicit criteria applied consistently — this is not a countdown padded to a round number, and it's not a collection of items given artificially equal treatment regardless of how much each one actually deserves.

TOPIC
Free tools for validating a SaaS pricing page before launch

CANDIDATE ITEMS
Maze, Hotjar, PostHog, UserTesting, Lyssna (formerly UsabilityHub), Crazy Egg, FullStory, Optimal Workshop

SELECTION CRITERIA
Must have a genuinely usable free tier (not just a trial), must support testing a pricing page specifically (not just general session recording), must not require a sales call to start.

TARGET LIST LENGTH
8, but only if the criteria genuinely support that many

AUDIENCE
Solo founders and small teams pre-launch, price-sensitive, need to move fast without a procurement process

LISTICLE RULES
Apply the selection criteria to every candidate item consistently and show your work — for each item that makes the final cut, it should be clear which criteria it satisfies, and for any candidate that didn't make it, note briefly why. Do not force the list to the target length if the candidate pool doesn't actually support it: if only seven items genuinely meet the criteria well and the target was ten, say so and publish seven rather than padding with three items that are noticeably weaker just to hit a round number — a shorter, uniformly strong list beats a longer one with visible filler at the bottom, and readers notice the quality drop-off exactly where padding starts. Vary the depth of each entry based on its actual complexity, not a fixed word count per item — an item with more nuance, more caveats, or a less obvious fit earns more explanation; an item that's simple and self-evident doesn't need three paragraphs stretched to match the others' length. Avoid template collapse, where every entry follows an identical sentence structure with only the noun swapped ("X is great because it offers Y and Z" repeated eleven times) — vary how each entry opens and how its case is made, since identical structure is one of the fastest ways for a reader to notice the list was mechanically generated rather than actually considered. Order the items by a stated logic — most to least relevant for the stated use case, price ascending, or another explicit rule — not alphabetically or randomly unless there's a real reason alphabetical order serves the reader here. Where one item is genuinely stronger or weaker than another on the list, say so directly rather than describing every entry in equally glowing terms; false even-handedness that makes every item sound equally good gives the reader no actual basis for choosing between them, which defeats the point of writing a comparative list in the first place.

OUTPUT FORMAT
1. The final list, ordered per the stated logic, with each entry's depth matched to its actual complexity.
2. A one-line note under each entry naming which selection criteria it satisfies.
3. Excluded candidates and why, briefly.
4. If the final count differs from the target length, one sentence stating why and confirming that's the honest number, not a shortfall to apologize for.