METHODOLOGY / EVIDENCE MODEL

How Atlas reaches a decision.

Tool Atlas combines attributable product facts with an explicit editorial model. The interface separates facts, judgment, and commercial relationships.

Effective2026-07-30

Official facts first.

Tool Atlas takes pricing, platform support, plan names, billing cadence, and feature claims from vendor pages. Each price snapshot includes a checked date and source. Regional or usage-based prices remain unnormalized when a single number would mislead.

Official product, pricing, and documentation pages
Visible verification dates and billing caveats
No silent conversion of regional or usage pricing

Atlas fit is Tool Atlas’s editorial score.

Tool Atlas scores workflow usefulness, product clarity, platform reach, and trade-offs in the launch dataset. The score excludes customer ratings, star averages, market share, and independent laboratory testing.

No invented review counts or community sentiment
Strengths and trade-offs shown together
Method changes require a visible editorial update

Tool Atlas requires an explicit overlap rule.

A shared broad capability does not make two plans redundant. Each overlap entry names the affected paid plans, classifies the relationship as avoidable or complementary, and identifies a safe Lean action.

Plan-level evidence for each overlap rule
Avoidable and complementary are distinct
The user can inspect and reject the lean route

Team totals follow the billing unit.

Stack Compare models 1 to 100 operators and accepts a separate seat count for each per-member plan. The team count supplies the default; specialist allocations override it for the named membership. Account, site, and channel plans stay fixed. Tool Atlas keeps custom quotes and one-time purchases outside the recurring total. Vendor minimum seats, admin seats, tax, usage, promotions, and checkout terms can still change the invoice.

Billing unit shown beside every selected plan
Specialist seats remain shareable in the stack URL
Fixed plans keep one billing unit as headcount changes
Checkout verification remains required

Role bundles declare who is doing the work.

Bundle Composer separates two purchasing models. Under Hybrid operator, one person performs each selected role, so the system counts a shared per-member plan once at the strongest required tier. Under Team roster, role counts represent distinct people: per-member plans receive the seats assigned to roles that use them, while account, site, and channel plans stay fixed. Stack Compare receives separate seat maps for Professional and Lean routes.

Each scenario uses one composition model throughout
Role headcounts are bounded and shareable in the URL
Professional and Lean seat maps transfer separately
Cross-role overlap requires manual adjustment

Role Stacks assign each release gate to a person.

Professional stacks follow the work sequence from evidence and canonical source through review, delivery, and release. AI can assist at a stage; each workflow names the judgment a person must make.

Current and lean subscription routes
Official-source frontier signals
A human gate at every workflow stage