Elements vs Typeform
Typeform is a hosted form and survey builder. A business builds forms, surveys, quizzes and applications in Typeform's editor, shares them at a link or embeds them on a site, and collects the answers in Typeform, where it can view, analyze and send them on to other tools. Typeform describes its forms as "beautiful design and conversational logic that adapts to every response." It connects to other apps through webhooks and integrations, including "+500 integrations with Zapier." Typeform has a free plan with a limited number of responses, and paid plans priced by responses and users. Basic, Plus and Business are billed monthly or yearly, and each allows more responses and users than the one below it. Plus is the lowest plan that lets you "Remove Typeform branding" (pricing).
Elements is not a form builder. It builds web apps with an AI agent, and a form tool comes down to parts it already has: a Postgres database for forms and responses, pages and server functions to collect them, file uploads, live updates for response tables and charts, and email sent through an SMTP provider such as Postmark. Describe the forms you need to an agent, and it can build them into an app on your own server.
Typeform is a form tool you rent by the response; forms you build are yours. On Typeform, the editor, the response limits and the integrations belong to Typeform, and the price rises with the responses and users you need. Forms you build are part of your own app, at a fixed monthly cost, and the answers land in the same database as the rest of your work: your CRM, your email list, your bookings. What you give up is Typeform's polished respondent experience, its templates and its editor, which anyone on your team can use without asking for a change. A form tool on its own costs less than running an app, so the case for building is consolidation, not the form.
What Typeform Gives You That Is Hard to Build
Typeform is more than a page of inputs. Some of what it does takes real work to match in an app you build.
- The respondent experience. Typeform's forms are designed to be filled in one question at a time, with logic that adapts to each answer. Typeform says that design is "doubling the completion rate vs. traditional forms." That polish takes design time to reproduce.
- An editor for everyone. Anyone on the team builds and changes forms without a developer. In an app you build, a new form is either something the app lets staff create or a change you ask your agent for.
- Templates and logic. Typeform includes templates, quizzes with scoring, calculations and multiple endings based on form logic (pricing).
- Integrations. Answers flow to hundreds of other apps through Zapier and native integrations. In your own app, the answers are already in your database, but a connection to an outside tool is code you write.
- No upkeep. Typeform hosts the forms, stores the answers and keeps it running. With your own forms, upkeep becomes your job, even with an agent handling most of it.
What Building It Looks Like
A form tool is a small set of parts: forms, fields, responses, files and notifications. Each Typeform feature has a counterpart, or a gap:
| Typeform feature | In an app you build with Elements |
|---|---|
| Forms at a public link, in your colors | Pages in Elements HTML, rendered on the server, with forms and fields stored in your Postgres database (html, database) |
| Required fields and validation | Rules checked in the browser as people type and again on the server, which has the final say (form validation recipe) |
| Submitting a response | A typed server function the form calls directly (rpc) |
| File uploads | Files sent with the form's other fields and stored in your database (file upload recipe) |
| A response table and summary charts | Rows that appear in every open browser as answers arrive, using a LiveTable (livetable) |
| An email for each new response | An email template sent through an SMTP provider such as Postmark, from a background job (email, jobs) |
| Accounts for the people who build forms | Sign-in and sessions, with your users as rows in your own database (authentication recipe) |
| Sending answers to a CRM or email list | No connector needed when they are tables in the same app; a query reads them (sql) |
| Payment on a form, such as an order or a deposit | Stripe Checkout, with the response saved when the webhook confirms payment (payments) |
| The one-question-at-a-time format, templates and the integrations catalog | No equivalent out of the box. A one-question-per-screen flow is a design you build; the template library and integrations stay with Typeform. |
Because forms, contacts and subscribers can all be tables in the same database, a person who fills in an application, a lead in your pipeline and a newsletter subscriber are the same kind of row, in one list of people.
The Demo: Fieldloft
Fieldloft is a form builder built with Elements by an AI agent from one prompt. Users build forms with nine field types (short text, long text, email, number, single choice, multiple choice, date, rating and file upload), each optionally required with help text, reorder fields by dragging and preview the form. They publish it at a public link with a theme color and a thank-you message. Responses fill a table with a column per field and a summary view with charts for choice and rating fields, both updating live, with CSV export and an email to the owner for each new response.
Fieldloft shows all of a form's fields on one page. It does not show one question at a time, the way a typeform does. That format is something you can ask your agent to add, and it takes design work to get right.
The prompt is on the demo page. Your agent turns it into the same app on your computer, a starting point for your own forms. For where the answers go next, Dealwren shows a CRM with contacts, deals and follow-up tasks, and Letterhearth shows an email list with scheduled posts. All three can be one app.
Adding It Up
Every business is different, so this section shows how to make the comparison for your own rather than making it for you.
This is an example, not a customer. A small consultancy collects client applications and intake forms in Typeform without its branding, tracks prospects in a CRM with two seats and emails a list of clients and prospects. It pays for:
| Subscription | What it charges by |
|---|---|
| Typeform | By plan, priced by responses and users |
| HubSpot | Sales Hub Starter, per seat |
| Mailchimp | By plan, priced by the number of contacts |
To compare, add up what you pay for these each month, billed the way you actually pay, and set it beside the cost of your own app:
- $100 a month for Elements, which is two licenses: the computer the app is built on and the server it is deployed to (pricing).
- A server from DigitalOcean.
- An email provider such as Postmark, priced by the number of emails sent.
Where it usually turns:
- Plans priced by responses and users grow with you. Typeform's higher plans add responses and drop-off rates; an app you build sets no response limit of its own and needs no licenses for the people who use it.
- Several flat subscriptions add up. A form plan, CRM seats and an email plan are each modest, and together they can pass the cost of one app. Yearly billing lowers each of them, so compare at the billing you would choose.
- A single cheap tool is usually cheaper to keep. A form tool on its own costs less than running an app.
The case for building is what one database does. The application form, the prospect it creates and the email they receive are rows in one app, with no integration between three vendors to set up or keep working. The subscriptions overview works through other cases.
When to Keep Typeform
- The free plan covers you. A free form tool is free, and nothing here beats it.
- Forms are all you would replace. A Typeform plan on its own usually costs less than running your own app.
- Completion rates matter more than anything. Typeform's one-question-at-a-time design is its product, built for completion.
- People without a developer build forms every week. Typeform's editor and templates let them do it on their own.
- Your answers feed many outside tools. Typeform's integrations save you writing those connections.
Questions
How much does Typeform cost?
Typeform has a free plan with a limited number of responses. Basic, Plus and Business are billed monthly or yearly and priced by responses and users; Plus is the lowest plan that removes Typeform branding. The current figures are at typeform.com/pricing.
Is building my own forms cheaper than Typeform?
Not for forms alone. Your own app costs $100 a month for Elements, plus a server and an email provider such as Postmark. The case for building is replacing several tools at once, such as a form tool, a CRM and an email list, with one app and one database.
Does the Fieldloft demo show one question at a time like Typeform?
No. Fieldloft shows a form's fields on one page. A one-question-per-screen flow is something you can ask your agent to build, but the demo does not include it.
Can forms in my own app accept file uploads and payments?
Yes. Elements apps send files with a form's other fields and store them in the app's database, and take payments through Stripe Checkout, with Stripe's own fees listed at stripe.com/pricing.
Where do I start comparing my subscriptions?
List every tool one app would replace, at the plan you pay for, and add them up. The subscriptions overview at /vs/subscriptions works through several examples.