Cognito Forms review

Cognito Forms is an online form builder built for teams that need more than a contact form. Beyond standard field collection, it handles automatic calculations, payment processing through Cognito Pay or other partners, and electronic signatures collected inside the form itself.

The bigger pitch is workflow: forms can route to approvers, generate documents from submitted data, and track the whole thing through a client portal. Per the pricing page, it also covers HIPAA, GDPR, and CCPA compliance, plus SSO and encryption on higher plans.

One Reddit thread in r/Scams confirms the basic trust question gets asked a lot: a commenter notes Cognito Forms is a legitimate company whose forms get embedded on plenty of business websites without users realizing it, so the brand itself isn't the red flag — what you're asked to submit is.

The feature set goes well past typical form builders, and the pricing page backs that up with specifics rather than vague claims:

• Calculations and data lookups run inside the form, useful for quotes, pricing tables, or conditional logic.
• E-signatures and document generation are built in, not bolted on through a third-party app, available starting on the Pro plan.
• Workflow and approval routing plus a client portal land on the Team plan ($49/mo annual), aimed at small teams rather than enterprise buyers only.
• Compliance coverage (HIPAA, GDPR, CCPA) and SSO show up on Enterprise ($149/mo annual), which matters for regulated industries that usually pay more elsewhere for this.
• It connects to Zapier, Make, and Microsoft Power Automate for things it doesn't do natively, like SMS notifications — confirmed by a Cognito Forms team reply in one r/CognitoForms thread pointing a user toward those three integrations.

A free Individual plan with 100 entries a month and payment support gives smaller users a real way to test the product before committing to a paid tier, backed by a 14-day trial on paid plans.

The published plans look reasonable until you add people. Every tier beyond Individual charges $5 per extra user per month, and guest access is a separate paid tier starting at $25/mo for up to 50 guests, scaling to $250/mo for 2,500 guests, then $100 per additional 1,000. Teams with lots of external reviewers or clients in approval workflows will feel this fast.

Entry limits are tight at the bottom: Individual caps at 100 entries/month, Pro at 2,000. Storage is also capped per plan, from 100 MB on Individual up to 100 GB on Enterprise, with overages on Enterprise billed at $25/month per extra 50 GB.

Native SMS isn't supported; per one Cognito Forms team reply on Reddit, it requires routing through Zapier, Make, or Power Automate. A Zapier user in another thread also noted some uncertainty about how quickly field changes in Cognito Forms sync to an existing Zap, suggesting integration updates aren't always instant or obvious.

The free Individual plan caps out at 100 entries a month and keeps Cognito Forms branding on every form. Fine for testing, not for a real intake form.

Pro starts at $19/month billed annually ($24 if you pay monthly) and removes branding, adds e-signatures, and bumps the limit to 2,000 entries. That's the plan most freelancers will actually use.

The jump to Team is steep: $49/month annually for workflows, approvals, and a client portal, plus 10,000 entries. Business then triples that to $99/month for API access and audit logs. Enterprise tops out at $149/month annually for unlimited entries and HIPAA compliance.

Watch the add-ons. Extra users run $5/user/month on every paid tier. Guests are worse: $25/month just to get above the included five, scaling to $250/month for 2,500 guests, then $100 per extra 1,000. If your use case involves lots of outside submitters, the sticker price on the pricing page is not the price you'll pay.

Cognito Forms' selling point is depth: calculations, document generation, and approval workflows built into the form itself. That depth is also the lock-in risk. Forms with nested logic, calculated fields, and multi-step workflows don't translate cleanly into simpler builders like Google Forms or Jotform, so migrating out later means rebuilding logic by hand, not just reimporting a CSV.

Moving in from another tool is more straightforward if your existing forms are simple, since most builders export field lists and response data you can map manually. The harder part is workflow and approval logic, which the pricing page confirms only exists on Team plans and above — so teams coming from a workflow-heavy tool like a dedicated BPM platform will likely rebuild those steps from scratch.

The guest and per-user fees are the detail that catches people off guard after they've committed. Anyone running client intake at volume should model those costs before migrating data over, not after.