Typeform alternative: a custom form built with Claude Code in under an hour
A team replaced a hosted form tool (Tally in their case, the same category as Typeform) with a 10-field application form that Claude Code generated in one session. It has React validation, a Zod schema, a server action that writes each application to their own Postgres, and an email to the team on every submission.
Setup steps
- In your site's repo, ask Claude Code for the form: fields, validation, a database table and a notification email
- Review the generated React form, Zod schema and server action
- Create the Postgres table and set NOTIFICATION_EMAIL
- Run an end-to-end test, then deploy with the site
- Change questions later with small commits
Steps summarized from the original Blog source ↗. Use “Copy” to grab them with the tools and source link, or copy an AI prompt.
How it went
Built and live in under an hour, including review and testing. In the first week they changed question copy, raised minimum answer length and added character counters, each as a normal commit.
Worth knowing
The writers say to keep the hosted tool if you have no engineer, need branching logic, or need non-technical people to edit the form.
Only what the original source ↗ says, re-read Oct 25, 2026. How we write these
Try it with AI
Paste this into ChatGPT, Claude or your own agent for step-by-step help. Prompt written by AppToBot from this recipe's data, not by the original author. It keeps drafts for your review and asks before anything is sent or paid.
Help me set up this automation using Claude Code + React + Neon Postgres + Resend: "Typeform alternative: a custom form built with Claude Code in under an hour". Goal: replace Typeform/Tally-style hosted forms. How it should work: - Trigger: Someone submits your form - Then: Validated in the browser and on the server - Then: Saved as a row in your Postgres - Result: Application in your database, plus an email to the team Setup steps (summarized from the original source): 1. In your site's repo, ask Claude Code for the form: fields, validation, a database table and a notification email 2. Review the generated React form, Zod schema and server action 3. Create the Postgres table and set NOTIFICATION_EMAIL 4. Run an end-to-end test, then deploy with the site 5. Change questions later with small commits Guide me one step at a time. Ask me for anything you need (accounts, sheet or channel names) before you start. Safety rules: - Build and test with sample data first, and show me a sample result before anything goes live. - Keep anything that goes to other people (emails, posts, replies, record updates) as drafts for my review until I say otherwise. - Never send, post, buy, pay, delete or change records without my approval. - Tell me about any cost (paid plans, API usage) before I'd incur it, and help me set a spending limit. - Keep API keys and passwords out of shared docs and chats. - Privacy: Submissions go to your own database; notification emails go through Resend. Based on: https://www.poolside.co/blog/how-we-replaced-typeform-with-a-single-prompt
Tool names link to each official site (opens in a new tab).
Running cost: Free to run After the one-time build, the source says the cost is zero beyond hosting it already pays for. How we sort costs
Stack: Claude
App vs bot, side by side
| Old app / habit | Bot | |
|---|---|---|
| Tool | Typeform / Tally | A form in your own repo, generated by Claude Code, writing to Postgres |
| Monthly cost | Typeform Basic is $29/mo with 100 responses (per source); their own Tally cost not reported | $0 beyond hosting already paid for (per source) |
| Setup | None (already in use) | Not reported · Intermediate |
| Your time | Baseline | Not reported |
| Maintenance | Handled by vendor/you as before | Question changes are small code commits deployed with the site. |
| Privacy | Data stays with the app vendor | Submissions go to your own database; notification emails go through Resend. |
Full comparison
| Replaces | Typeform / Tally |
|---|---|
| Bot / agent stack | A form in your own repo, generated by Claude Code, writing to Postgres |
| Monthly cost before | Typeform Basic is $29/mo with 100 responses (per source); their own Tally cost not reported |
| Monthly cost after | $0 beyond hosting already paid for (per source) |
| Setup time | Not reported |
| Time saved | Not reported |
| Skill level | Intermediate |
| Reliability | 3/5: firsthand and live, with a narrow scope stated honestly (simple, unbranched forms); no response figures. |
| Maintenance | Question changes are small code commits deployed with the site. |
| Privacy & data | Submissions go to your own database; notification emails go through Resend. |
| Best for | Technical teams with a simple, stable form |
| Not for | Non-technical teams, or long branching surveys |
Pros and cons
Pros
- No response cap or monthly fee
- Data lands in your own database
- Changes are ordinary commits
Cons
- Needs an engineer and an existing repo
- No branching logic or no-code editing for marketers
Source and evidence
Team engineering blog (Sep 2026): built and live in under an hour, including review and an end-to-end test. The form has survived every deploy since launch. They replaced Tally, not Typeform itself.
Read the original Blog source ↗
“Not reported” means the source doesn't say. We never fill gaps with guesses. Numbers marked “per author” or “vendor claim” are the source's own and weren't independently tested. Source last checked Oct 25, 2026.
Our rating is an editorial opinion based on the public source above, not lab testing. Spot an error? Request a correction.
Plain-text summary (for search and AI assistants)
Typeform alternative: a custom form built with Claude Code in under an hour. Replaces Typeform / Tally with A form in your own repo, generated by Claude Code, writing to Postgres. Cost before: Typeform Basic is $29/mo with 100 responses (per source); their own Tally cost not reported. Cost after: $0 beyond hosting already paid for (per source). Setup: Not reported, Intermediate. Time saved: Not reported. Reliability 3/5: 3/5: firsthand and live, with a narrow scope stated honestly (simple, unbranched forms); no response figures. Best for: Technical teams with a simple, stable form. Not for: Non-technical teams, or long branching surveys. How it went (per source): Built and live in under an hour, including review and testing. In the first week they changed question copy, raised minimum answer length and added character counters, each as a normal commit. Worth knowing: The writers say to keep the hosted tool if you have no engineer, need branching logic, or need non-technical people to edit the form. Source: https://www.poolside.co/blog/how-we-replaced-typeform-with-a-single-prompt
Related recipes
- One n8n workflow that replaced 4 SaaS tools (3/5)
- Linear AI triage with n8n: route new issues to the right team (3/5)
- Can n8n replace Zapier? One user's $74/mo to $0 switch (3/5)
- n8n homelab workflows that replaced Zapier on a NAS (3/5)
More: all Operations recipes
Questions, corrections or ideas?
Spotted an error, want a recipe covered, or have a partnership idea? Send us a message and we'll get back to you.
Starting your own newsletter? Try beehiiv ↗
What is beehiiv?
beehiiv is a newsletter platform: you write and send emails, host a newsletter website, and grow and monetize a list from one place. We've used it for our own newsletter.
beehiiv says (vendor claims, not tested by us):
- Free plan with up to 2,500 subscribers and unlimited sends
- Built-in website, recommendation network and analytics
- 0% cut of paid subscription revenue (Stripe fees apply)
Good for: starting or growing an email newsletter. Not ideal for: email automations or removing beehiiv branding on a $0 budget (those need Lite or Pro).
Free plan: $0, no card needed. Paid plans from $49/mo billed annually (Lite, up to 1,000 subscribers). People who sign up through our link get a 14-day trial plus 20% off their first 3 months, per beehiiv's partner page. Facts as of Oct 2026, from beehiiv's own website. More about beehiiv →