What do you use today instead of Html (https://html.contact/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Html better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

Archie Langworthpositive

Right now, I'm basically just using simple SMTP settings to send form data to a shared Gmail inbox. When a form breaks or a client changes their email, I have to manually go in and update the paths. This product, html.contact, sounds like it could be a real time-saver. Being able to just paste a URL and have submissions go straight to email or Slack would be sweet. It would definitely be better than my current setup because it promises more reliability and less of my direct involvement. The only thing that might keep me on my current setup is if the cost gets too high, but it says it's free to start, which is nice. I'd be willing to pay around $20 per month, maybe up to $30 if it really handles everything smoothly and reliably.

Simulated interest: 85/100

Verna Waelchineutral

Currently, I'm using Webflow for most campaign landing pages and hand-coded HTML for experiments. Form submissions go to HubSpot, Slack, and a few Zapier automations. Html.contact's promise of turning plain HTML forms directly into email and Slack updates without a backend is appealing, especially for partner campaigns where I often use simple HTML. It could simplify things significantly compared to managing Zapier flows, which sometimes fail silently. The ability to integrate directly with Slack is key. The Google Sheets pilot feature is interesting, but I'd need to see how it performs. I'm hesitant about anything that requires extensive setup or adds more manual auditing. I'd pay $15 per month.

Simulated interest: 60/100

Mahesh Khannapositive

Currently, for our marketing site forms, we're doing it manually or through some basic integrations we've set up ourselves. The idea of just pasting a URL and having submissions sent to email or Slack is appealing, especially since our static site is on Cloudflare Pages. It would be better than our current approach by saving us development time and simplifying the process. What would make it worse is if the spam filtering isn't robust, or if the integration with our internal systems isn't as smooth as described. I'd be willing to pay around $15 per month for this service, provided it handles a reasonable volume of submissions without issues and the spam protection is effective.

Simulated interest: 75/100

Lisann Bolmpositive

Currently, we manually track where each client's form submissions should go – emails, Slack, or CRM via webhooks. It's prone to errors, and developers sometimes implement forms without considering the integration, which creates extra work. Your service, Html, sounds like it could automate this by turning plain HTML forms into email notifications, Slack updates, and webhooks. The idea of "no backend to build" is appealing, as it would save us development time. However, I'm curious about how robust the webhook integrations are, especially for more complex CRM workflows. If it handles all our current destinations reliably and simplifies the process, that would be a significant improvement. I'd be willing to pay up to $15 per month for this service, provided it truly streamlines our current manual tracking and reduces errors.

Simulated interest: 75/100

Nora Schillerneutral

Right now, we're using a shared inbox and a Google Sheet to manage volunteer sign-ups and event registrations. It works, but it's quite clunky and involves a lot of manual sorting. The idea of having form submissions go straight to email or even Slack, as your product offers, sounds like a significant improvement for efficiency. I'm particularly interested in the Google Sheets pilot you mentioned; that could really streamline our data. The main thing that would make me hesitant is ensuring it integrates smoothly and doesn't add more complexity than it solves, given our limited resources. I'm willing to consider paying up to $15 per month.

Simulated interest: 70/100

Marty Moorepositive

Right now, I'm manually checking emails and Discord for form submissions from my personal sites. The current process is functional but cumbersome, especially when I'm trying to focus on my side projects. Html.contact seems like a much more streamlined approach. The idea of turning plain HTML forms into email notifications or Slack updates is appealing, especially since I already host on GitHub Pages. It would definitely be better than what I'm doing now if it reliably funnels everything into one place without me having to constantly monitor multiple channels. The Slack integration is particularly interesting. What I'm not clear on is the actual volume limits on the free tier and how that scales with paid plans – is it per form or for all my projects combined? Given the convenience, I'd be willing to pay up to $10 per month for this service, assuming the volume limits are reasonable for a couple of small personal projects.

Simulated interest: 75/100

Emilia de Boerneutral

Currently, we handle form submissions by directly wiring them to email, Slack, or a webhook tool. This is a manual but reliable process that ensures our clients get their leads. Html.contact's main appeal is the ease of setup; it simplifies the integration significantly. However, the key concern for us is the reliability and scalability of their "Free" tier. If the "accepted submissions" limit is too restrictive for our smaller clients, it would be a major drawback. We'd need to see robust spam filtering and clear performance metrics before considering it a better alternative. I'd be willing to pay up to $30 per month, but only if it proves more efficient and reliable than our current setup.

Simulated interest: 70/100

Andrew Nitzscheneutral

Right now, I use simple HTML forms that route directly to shared mailboxes. For a few things, I have custom webhook scripts. What Html.contact offers is basically taking over the backend processing I currently handle myself or through simple scripts. The main benefit would be less maintenance on my end. The integration with Slack sounds useful for getting inquiries into a team channel faster. What I'm not clear on is the pricing for higher volumes. I'd be willing to pay $15 per month, but that depends on the submission limits and features included at that tier.

Simulated interest: 40/100

Estelle Weissnatneutral

Essentially, my current process involves our website's HTML forms feeding directly into Outlook and a shared spreadsheet, which is quite manual to sort through. The main issue is the time I spend cleaning that data and the risk of leads falling through the cracks. Html.contact could be better if it seamlessly integrated with Slack for urgent leads, as it already offers. What would keep me on my current option is if the cost became prohibitive, especially since we've recently decided against a more expensive CRM. I'd be willing to pay up to $15 per month, provided it handles our current lead volume efficiently.

Simulated interest: 75/100

Gajbaahu Ahluwalianeutral

Today, I use a mix of custom HTML with form submissions going directly to email, or I set them up in Airtable or Slack. If `html.contact` could seamlessly handle conditional logic in forms without needing any backend code on my end, that would be a definite plus. The ability to integrate directly with Slack and potentially Google Sheets without extra setup is also appealing. What worries me slightly is the "Limited pilot" status for Google Sheets; I'd need to know if that's stable. Given my focus on minimal dependencies and cost, I'd be willing to pay around $10 per month for a solid, reliable service that saves me significant setup time and maintenance.

Simulated interest: 60/100