There's this formality to RSVP's that I took very seriously in my development.
Little things like allowing guests to be reordered in the guest list - when I first showed that to my friends, it didn't seem like a big deal, but once I explained that certain guests could be offended by being at the bottom of the guest list (considering they're only at the bottom because of the way the host entered them), it made sense to those I was showing.
Another big thing was the ease of use in filling in the form for the guests. In my [example RSVP page](https://www.rsvpkeeper.com/rsvp/08c084c7-ecf2-4aed-8cfc-4fe6...) you can see how that works if you haven't already visited it.
I really focused on making it as simple and clean as possible. I don't even allow theming just yet because I felt that would just distract and confuse the guest filling out their form. This is all done to the benefit of the host of course - so they can capture the highest number of RSVP's for their event.
Thanks for your insight and comments.
To put it another way, an RSVP tool occupies a niche where the host does not follow convention for their own convenience but requires guests to follow convention in an unconventional and perhaps inconvenient way...setting up logins, filling out forms etc.
I'm already married, so I doubt I would use it. That's the problem with solving wedding problems...brides and grooms don't create repeat business.
Good luck.