Thomas Schmidt

I'm testing an idea for agencies maintaining 10 30 client sites, especially Webflow forms routed through Make into Google Sheets and email. It isn't built or available to buy yet.

The proposed $49/month pilot would cover up to 20 approved form paths: send one clearly marked test each day, check that its matching row reaches the Sheet and its notification reaches a dedicated test mailbox, then alert after two failed attempts with the last verified step.

Example: form accepted, email received, Sheet row missing. That is more useful than a green "form submitted" check, but it still would NOT prove delivery to your client's real inbox.

Setup would need your approval to read the destination spreadsheet as a Viewer (the whole file, not just test rows) and keep marked tests out of sales reporting. Existing Webflow, Make and email costs stay separate; checks consume their usage allowances. The pilot would be for paid Webflow sites, not Starter sites with the 50-submission lifetime limit.

If you run an API or AI product with a free allowance, did requiring a card actually reduce your costs without killing activation?

I m researching whether there s room for a small tool that checks credit grants, rather than another generic signup filter. The part I can t establish from product pages is whether repeat accounts cost enough to justify another integration. A hundred fake signups that never consume credits may matter less than three that do.

I d like to hear about a recent change you made: what was being consumed, what control you tried, and what happened to legitimate users. Rough ranges are fine. If email checks, quotas or an existing service solved it cheaply, which one worked?

I m comparing this with other small software ideas before building. No product to pitch yet trying to understand whether this is a problem worth paying to fix. Please leave customer details and secrets out of replies.