Consistency across projects
Every client site needs a form. Building a custom component each time is slow. Using Typeform or Tally means dealing with their branding and styling on every project.
Guide · Framer
If you build client sites in Framer, you've solved the contact form problem more than once. Here's a setup that works across projects — consistent, rebrandable and requiring zero custom code per site.
The agency form problem
Every client site needs a form. Building a custom component each time is slow. Using Typeform or Tally means dealing with their branding and styling on every project.
Clients need to be able to see their submissions. A form that emails to their inbox is simpler than giving them access to a third-party dashboard they won't understand.
Every client has different fonts, colors and layout. A form that inherits the project's typography and accepts a theme config saves restyling time on every project.
The agency workflow with Quiet Form
Add QuietForm.tsx to your Framer assets once.
It's available across all projects on the same account — no re-importing per client site.
Open the visual builder for each project. Match the client's colors in the theme panel. Set their form provider endpoint. Copy the JSON — that's the entire form setup for that client.
Drop QuietForm into the client's Framer project, paste the config JSON. Typography inherits automatically. Done in under 5 minutes per project.
Use Web3Forms with the client's email to send submissions directly to them. No third-party dashboard to explain, no access to manage.
Related guides
Quiet Form
One purchase, unlimited Framer projects. Rebrandable via JSON config, no code per site.