Building in Public: The FilaForms Roadmap | FilaForms [ ![Filaforms Logo](https://filaforms.app/logo.svg)FilaForms ](https://filaforms.app) [ Features ](https://filaforms.app#features) [ Pricing ](https://filaforms.app/pricing) [ Blog ](https://filaforms.app/blog) [ Documentation ](https://docs.filaforms.app) [ Try Demo ](https://filaforms.app/login) [ Get Started ](https://filaforms.app/pricing#plans) [ Features ](https://filaforms.app#features) [ Pricing ](https://filaforms.app/pricing) [ Blog ](https://filaforms.app/blog) [ Documentation ](https://docs.filaforms.app) [ Try Demo ](https://filaforms.app/login) [ Get Started ](https://filaforms.app/pricing#plans) ![FilaForms](https://filaforms.app/logo.svg) FilaForms InsightsBuilding in Public: The FilaForms Roadmap ========================================= filaforms.app/blog [ Back to blog ](https://filaforms.app/blog) [ Insights ](https://filaforms.app/blog/category/insights) Building in Public: The FilaForms Roadmap ========================================= Manuk Minasyan · August 11, 2026 · 7 min read Six months ago FilaForms had three customers and a landing page I had rewritten four times. Today it has a real customer list, a public blog with two dozen posts, and a backlog longer than I will ship this year. That second part is the uncomfortable one. I'm writing this for two reasons. The first is that I owe the people who paid me an honest read on where the product is going. The second is selfish — I want feedback before I commit to the wrong things in Q4. Building in public only works if the "public" part shows up, which means showing the unpolished plan, not the keynote version of it. This is the keynote-free version. What shipped in Q2 and Q3 ------------------------- Most of what shipped is either in the product or on the blog. I'll keep this honest about which is which. In the product: the webhooks hub, which moved webhook configuration from "a thing you wrote a custom listener for" into the admin. Stripe payments and Google Sheets storage are first-class integrations now, configured from the admin instead of plumbed by hand. Zapier sits next to them — once your form fires events into Zapier, you can wire it to anything Zapier reaches. Honeypot spam protection is in. Signature fields and line items are in. Tags landed, which I had been putting off for longer than I want to admit. On the blog, but not yet in the admin as native integrations: Slack, Notion, Discord, HubSpot, Mailchimp, Airtable, and Microsoft Teams. Each of those posts walks you through the webhook setup end to end. The pattern works, customers are using it in production, and the playbooks are accurate — but the experience is "configure a webhook with the right URL," not "click Connect Slack in the admin." That gap is on the Q4 list. GDPR and WCAG were the other content-led pieces this quarter. The product respects the conventions — the data lives in your database, retention is whatever your application's data policy says, and accessibility lives at the form-render layer — but the bulk of this quarter's work on those topics was writing the checklists that show customers how to use what's already there. A dedicated per-form retention UI and an audit log are on the Q4 list, not in the product yet. The form performance pass cut load and submission latency on public forms. The NPS post is a recipe that uses existing field types and the conditional-logic engine — there is no dedicated "NPS module," and I should be clear about that. The spam protection is honeypot plus Laravel's standard throttle middleware. It handles the obvious stuff and not the interesting bot traffic yet. That is on the Q4 list too. What I'm leaning toward in Q4 ----------------------------- I want to be careful here. "Leaning toward" means I have spent time thinking about it, not that it is shipping. One item below is committed. The rest are honest reads on where my attention is going. **Committed: FAQPage and HowTo schema auto-emission on public forms.** If your form has FAQ-style content, FilaForms will emit the structured data without you writing JSON-LD by hand. This is the one item on the list I'm putting a stake in the ground on for Q4 — the design is settled, the work starts next sprint. **Leaning toward: per-form retention policy with auto-purge.** I wrote about this in the GDPR post and the response was stronger than I expected. The shape is clear — a retention window per form, configurable in the admin, with a scheduled job that anonymizes or deletes on the chosen cadence. What I have not decided is whether anonymization is a separate concept from deletion in the UI, or whether they live on the same control with a toggle. **Leaning toward: native UI for Slack, Notion, and Airtable connections.** Right now the playbook works via webhooks, but the setup means jumping between the blog post and your env file and trusting that you copied the right value. I want a connection screen that handles the OAuth dance and stores the credentials in the admin, the way Stripe and Google Sheets already do. The question is whether I do all three at once or stagger them. **Exploring: i18n for public forms.** It comes up in conversations more than I expected for a single-language product. I do not yet know if the people asking represent the whole customer base or the loudest corner of it. If you would use this, tell me. **Exploring: a theme contrast and a11y dashboard.** I mentioned this in the WCAG post. It would let you check that your form theme passes contrast checks before you ship the form. Useful, but I am not sure it is more useful than two other things on this list. **Leaning toward: Tags as filters in the submissions table.** Tags are live. Filtering submissions by tag is the obvious next step. This is small, and small wins are good for momentum. The one thing I'm not building ------------------------------ I get asked about this most weeks, so I will say it in writing. I am not building a visual workflow builder inside FilaForms. The "Zapier inside your admin" pitch — drag a form event onto a canvas, connect it to a Slack node, connect that to a HubSpot node, branch on a condition. It is a beautiful demo and a maintenance trap. Every node you add becomes a third-party integration you now own, every customer workflow becomes a support ticket waiting to happen, and the abstraction never fits the thing the customer wanted to do. Zapier already exists. I will write the integration that points FilaForms at it. FilaForms will keep doing the boring version: events, listeners, webhooks, and integrations you configure once. If you want a workflow engine, use one of the workflow engines. I will write the integration that lets FilaForms talk to it. I will not rebuild it inside the admin. This is the part of the roadmap I am most sure about. What I'd love your input on --------------------------- There are three places I am genuinely uncertain, and feedback would change what I build next. First, the integrations question. If you have FilaForms in production, which integration would change your week if it had a proper UI tomorrow? Slack, Notion, Airtable, something else. I will read every answer. Second, the i18n question. Is multi-language support on public forms a "would be nice" or a "this is why I haven't moved my client over yet"? Be honest. A "would be nice" pushes it out of Q4. Third, the analytics question. The current submissions analytics covers volume and completion rate. Several people have asked for funnel-style analytics — drop-off per field, time spent per step. Is that real, or is that what people say they want and then never look at? You can email me at hello@filaforms.app or send me a note on Twitter. If a public issue tracker would help, I am open to opening one — tell me if that would change whether you would file something. Close ----- This post exists because I do not want to ship the wrong thing in Q4. The roadmap above is what I would write today if you forced me to commit. The roadmap I want to publish in January is the one shaped by people who use the product. If you are already a customer, thank you for being early. If you are evaluating, [pricing is here](https://filaforms.app/pricing), and the product is closer to what I want it to be than it was six months ago, which is the only direction this is supposed to go. Tell me what I'm missing. Related posts ------------- [ Insights Jul 21, 2026 The Quiet Cost of Rebuilding Forms on Every Project ----------------------------------------------------- Every Laravel agency I know has built 'the form thing' four times. Same admin table, same submissions viewer, same notifications. Here's the math on what that actually costs. ](https://filaforms.app/blog/the-quiet-cost-of-rebuilding-forms-on-every-project) [ Insights Jun 5, 2026 What I've Learned Shipping FilaForms (90 Days In) --------------------------------------------------- Ninety days ago I shipped FilaForms. Here's what's worked, what hasn't, the number I underestimated, and the launch tactic I'd skip if I did it again. ](https://filaforms.app/blog/what-ive-learned-shipping-filaforms-90-days-in) [ Insights Apr 6, 2025 How I built FilaForms: architecture decisions behind a Filament plugin ------------------------------------------------------------------------ The technical and product decisions behind FilaForms — why JSON storage, why SHA-256 analytics, why Custom Fields as a foundation. ](https://filaforms.app/blog/how-i-built-filaforms-architecture-decisions-behind-a-filament-plugin) ![FilaForms Logo](/logo.svg) FilaForms Laravel form infrastructure for Filament. Stop rebuilding forms on every project. ### Product [ Features ](https://filaforms.app#features) [ Documentation ](https://docs.filaforms.app) [ Blog ](https://filaforms.app/blog) [ Pricing ](https://filaforms.app/pricing) [ About ](https://filaforms.app/about) [ Contact ](mailto:hello@filaforms.app) ### Legal [ Terms of Service ](https://filaforms.app/terms-of-service) [ Privacy Policy ](https://filaforms.app/privacy-policy) © 2025-2026 FilaForms. All rights reserved. [ ](mailto:hello@filaforms.app) [ ](https://x.com/MinasyanManuk)