How forms work on my site (no form plugin, no SMTP plugin)
My good friend and long-time customer Kevin emailed me recently with a good question. He’d read how I built this site, with no WordPress and no page builder, and he wanted to know: what about forms?
Fair question. If you build with WordPress, forms are one of those things you never really think about until you have to. And then there’s quite a lot to think about.
So here’s how the forms on this site work, how that compares with what I used to do, and what I’d suggest if you’re curious about doing the same.
How I used to do it
If you’ve built a WordPress site with a form on it, you’ll know the drill:
- A form plugin, like WS Form (the one I used last), Gravity Forms, WPForms or Fluent Forms. Often a paid licence, renewing every year.
- An integration to get sign-ups into your email marketing platform. Sometimes that’s another add-on, sometimes another licence.
- An SMTP plugin, because WordPress’s own email has a habit of quietly landing in spam (or not arriving at all).
- A transactional email service behind that, like Postmark, Mailgun or MailerSend, with an account, an API key and some DNS records.
Plus the entries piling up in your WordPress database, the spam getting through, and all of it needing updates.
That’s not a dig at any of those tools. They all do their job. It’s just a lot of moving parts for what’s usually “someone typed their name and email into a box”.
What a form actually needs
Strip it back, and a form really only needs three things:
- Somewhere to send the data. Your email platform, your inbox, or both.
- A way for you to find out about it, if it’s something you need to read or reply to.
- Something to keep the spam out.
That’s it. Everything else is how a particular tool happens to do it.
Sign-up forms: straight to my email platform
Most of the forms on my site are sign-ups. Join the newsletter, or register your interest in the AI Agency workshop.
They’re just HTML forms. Kit, my AI web developer, built them as Astro components, with a little JavaScript so they send without leaving the page and show a thank-you message.
The site itself is static and hosted on Cloudflare, for free. Alongside it runs a tiny script called a Cloudflare Worker. When someone sends a form, the Worker:
- checks it came from one of my own pages,
- checks there’s a name and a proper-looking email address,
- sends it straight to Bento, my email marketing platform.
Nothing is stored on the website itself. There’s no database, so there’s no pile of entries to look after.
Along with the name and email, the Worker tells Bento which form it came from and how the person found the page (for example, a link from one of my YouTube videos). Bento takes it from there: it adds the right tags and sends the confirmation email.
So there’s no form plugin and no integration add-on. The “integration” is a short script that Kit wrote, which I can read and change.
Forms I want to reply to: hello, transactional email
Then I built something a bit different.
I’m thinking about some small-group training, and I wrote an open letter asking people what they’d want from it. At the bottom, there’s a reply form with a few optional questions.
The name and email go to Bento, like any other sign-up, and the answers are saved with it. But if someone has taken the trouble to tell me what they think, I want to be able to write back. And Bento wasn’t built for that: it doesn’t tell me when an answer comes in, and I can’t reply from it.
So if someone answers any of the questions, the Worker also emails me a copy, through a transactional email service called Resend. The email arrives in my normal inbox, and I hit Reply. It goes straight to them.
Yes, that’s the same job Postmark or MailerSend would do on a WordPress site. The difference is there’s no SMTP plugin in the middle. The Worker talks to Resend directly. Resend’s free plan is very generous for something like this, and its dashboard keeps a copy of every email it sends.
My part of the setup took about five minutes. I signed up to Resend, and it added the DNS records to my Cloudflare account for me. Then I pasted a key into Cloudflare. Kit wrote the code and tested it on my staging site before it went live.
By the way: if you build sites for clients and you’re curious about working this way, I’m thinking about teaching a small group how to build simple client sites without the ongoing WordPress upkeep. Nothing’s decided yet. Tell me what you’d want →
What about contact forms?
Exactly the same idea. Someone fills in the form, the Worker emails it to me, and Reply goes to them.
And my contact page doesn’t have a form at all. It just has my email address (hidden from the bots that harvest addresses).
For a site like mine, I think that’s fine. People can email me from their own inbox, and nothing can break. If I ever wanted a proper contact form, though, everything I need is already in place.
And spam?
So far, two simple things have been enough:
- A honeypot. A hidden field that people never see, but bots tend to fill in. If it’s filled in, the Worker quietly pretends all is well and throws the submission away.
- Only accepting forms from my own pages, so nobody can post to the Worker from somewhere else.
No puzzles, no “click all the traffic lights”. If spam ever does start getting through, Cloudflare has a free and mostly invisible bot check called Turnstile that I can add.
What would I suggest for your site?
It depends on where your site lives.
If your host can run a little code (Cloudflare Workers, Vercel and so on), I’d do what I’ve done here. A small function that sends the form to your email platform, or emails it to you through a service like Resend. No form plugin, nothing extra to pay for, and you can make it work exactly how you want.
If your host is purely static and can’t run any code, use a form service like Formspree or Basin. You point your form at their address, and they email you the submissions and keep a copy. Very simple.
Either way, you’re not stuck. And you’re not maintaining three plugins to collect an email address.
How much work was it?
Honestly, not much from me. Kit wrote all the code. My part was the decisions: what each form should collect, where it should go, what the thank-you message should say, and what should happen when something goes wrong.
That’s the same pattern as the rest of the site. The AI writes the code. The decisions are still mine.
If you want all the nerdy details of what powers this site, they’re in my colophon. And thanks, Kevin, for the nudge. 🙂