TOOLZAGDocumented facts. Clear limitations.
ToolZag

Choose by the task.
Keep the evidence in view.

Start with your requirements
ABOUT THIS SITE

Methodology

How requirements, evidence and costs become a result.

Editorial review 2026-11-10 · ToolZag editorial · Public-document research, not account testing.

Scope and evidence

We cover online form builders for collecting inquiries and gathering information or files. Public official documents support individual facts; we do not claim logged-in account tests, a complete market database or specialist compliance advice. Every displayed fact has an ID, scope, unit and evidence record. The three covered tools have comparable facts for some conditions. Check each plan for costs that still need confirmation.

The six visible states

MATCH means the assessed required conditions and known necessary costs fit. NEEDS_CONFIRMATION means a relevant fact or cost remains unknown, conditional, conflicting or expired without an independent hard failure. NO_MATCH means a documented hard requirement fails.

OUT_OF_SCOPE means the full task is broader than this site. INPUT_INCOMPLETE means required input is missing or invalid. LOAD_ERROR means the data request, schema or release compatibility failed; it is never shown as an empty shortlist.

Natural ordering and cost

We separate states, then monthly and annual commitments. Known matching necessary costs determine order within a group, with stable IDs for ties. Role, industry, sponsorship and commissions are absent from the evaluation function. Pending cheaper alternatives stay visible.

Costs use integer USD cents. Base, required seats, add-ons, applicable excess fees and one-time charges are considered. First payment needs independent timing evidence. Missing thresholds and rates remain unknown. A real excess fee does not establish permission to exceed included usage.

Time and correction

Evaluation takes an explicit UTC time. At fourteen elapsed days a fact warns; at thirty it no longer supports a definite relevant conclusion. Conflict can downgrade it immediately. A build or source fetch does not renew verification.

Read the dated facts and report the public field ID if you find an error. No automated cloud source checks run in this local stage.

Evaluation and published changes

Research observations and implementation changes are not vendor announcements. Pending research, failed checks and conflicting extracts do not count as published changes. Task names are display labels; saved conditions use stable task IDs.