We build the boring half of hosting.
InviteFox exists so the person organising an event can stop being a spreadsheet. Describe the event in a sentence; get back an invitation page, an RSVP form, a QR code and a live head count.
Why we made it
Most people organising an event are not event professionals. They are a parent booking a party room, a volunteer running a fundraiser, an office manager confirming numbers for a caterer. The tools available to them are either a free form that produces a pile of rows, or event software priced for a conference. Both leave the host doing arithmetic in a spreadsheet the night before.
So InviteFox is built around the two outputs a host genuinely needs: something to share, and a number to act on. Everything else — themes, questions, exports, invitation artwork — exists to serve those two.
Four decisions that shape the product
The guest should never have to sign up
Every account you ask a guest to create costs you replies. Guests open a link, answer on one screen and leave. No app, no password, no profile.
A count beats a list
Hosts do not need a transcript of who said what. They need a number they can hand to a caterer. Party sizes, declines and maybes are tracked as numbers, not as messages to interpret.
Printed things should not go stale
Invitation links and QR codes are permanent. Change the venue, the time or the questions after the cards are printed, and every scan still lands on the current page.
AI drafts, you decide
Describing an event in a sentence is faster than filling in a form. But nothing is published from a prompt — you review the draft, edit anything, then publish.
Who uses it
Weddings and showers, birthday parties and graduations, school fundraisers, church gatherings, team offsites and family reunions. The common thread is not the occasion — it is a host who needs a reliable count from people who will not create an account.
Start with pricing, browse the guides, or read how we handle your data in the privacy policy.
Plan your next event in a sentence
The free plan is enough to publish a real event and collect real replies.
