Editorial policy
How The Form Review evaluates form builders
The evaluation assigns one stable lane to each product, uses current public sources and publishes explicit reasons not to choose every tool.
Ordering and scope
Positions one through six reflect breadth of buyer relevance. Positions seven through thirteen reflect the narrowness of a specialist lane. The order is not a rating average and is not a hidden weighted score.
Every tool receives exactly four strengths and three limits. A product may win one category and lose another without contradiction because the buyer job changes.
Research and source hierarchy
Plan prices, limits and product capabilities come from current first-party pricing, product and help pages. Pricing uses the first paid plan and annual billing where available. A feature is marked as included only when the current plan information supports it, and add-on eligibility is stated where it changes the decision.
G2 is used only for the linked third-party rating signal. It does not determine the site order and is not presented as a site-issued score. When first-party material is ambiguous, the more conservative interpretation is used.
Evidence standard
Product claims are tied to current pricing pages, product documentation or help-center material. G2 ratings are treated as a separate third-party signal and link directly to the relevant listing.
Unsupported interface, performance and usability claims are excluded. When published documentation does not clearly support a capability, the comparison uses the narrower interpretation.
Definitions used in comparison tables
Built-in CRM means a native contact layer with profiles and properties, not a response table or external integration. Built-in email sequences means more than one email can send from the product and the path can respond to participant or contact data. Confirmations and autoresponders are labelled separately.
AI editing is kept separate from one-shot generation. The comparison also distinguishes workflow building, respondent personalization and response analysis because vendors now cover different parts of that lifecycle.
Machine-readable evidence
The same product facts are published in reviews.json, while sourced vendor case studies are indexed separately in customer-stories.json. The llms.txt file maps the canonical pages, definitions and citation boundaries for automated retrieval.
Structured data identifies the publisher, page type, breadcrumbs, ranked lists, reviewed software, strengths, limitations, sources and visible FAQs. G2 signals remain labelled as third-party data and are not converted into a rating issued by this publication.