Not one invitation for three hundred people — three hundred invitations for three hundred people. What per-guest design actually changes, and why it ends the plus-one problem for good.
For as long as invitations have been printed, they have been printed once: one design, one wording, three hundred identical copies, and a hand-addressed envelope doing all the work of making each guest feel seen. The envelope was always the tell. The one truly personal element of the traditional suite is the one added last, by hand, because the printing press couldn't do it. Now it can — and it changes more than the greeting.
A per-guest suite starts from the guest list, not the artwork. The design is still one design — same palette, same typography, same motif, everything a suite should share. What varies is what the system has always known but the paper could never say:
Every etiquette guide, ours included, teaches the traditional machinery for controlling the guest list: the inner envelope, the carefully worded website FAQ, the reply card with a discreet "we have reserved ___ seats in your honour." All of it exists because the invitation itself was generic and something had to carry the specifics. A per-guest invitation retires the machinery. When the card says Elena and Marcus, and the RSVP that opens from it lists Elena and Marcus as the people it expects answers for, there is no gap for a fourth chair to slip through — and, better, no sentence anywhere telling anyone what they may not do. The boundary is built into the object, which is the politest place a boundary can live. (The wording that remains genuinely necessary is covered in the wording guide.)
A QR code on a wedding invitation is usually a doorbell: everyone rings, everyone gets the same page. The per-guest version is a key. Elena's code opens Elena's page — her household's RSVP, her dietary questions already on file from the engagement party, her table once seating is set, the weekend schedule filtered to the events she's invited to. Three practical consequences follow. RSVPs stop being anonymous form submissions and arrive pre-matched to the guest list. Reminders go only to households that haven't answered — by name, before the deadline, instead of a broadcast nag to everyone after it. And day-of changes (a moved ceremony time, a rain plan) reach every guest through a page they already trust, rather than a phone tree.
Per-guest does not mean screens-only. Printed suites can be issued per household — the greeting and the named-guest line typeset into each card, the variable inserts collated per envelope. Digital suites personalize further and faster, down to the guest's own name in the opening animation. The pairing we design most often: printed invitation with the household's names, per-guest QR behind it doing the logistics. The keepsake stays paper; the moving parts move. (The broader print-versus-digital decision is mapped in the complete guide.)
Honesty requires the cost line: per-guest design runs on a clean guest list. Households defined, names spelled, languages known — the same list the seating chart and the caterer will eventually demand anyway, assembled earlier. That is the real trade: an hour of list hygiene up front buys an invitation that does the etiquette for you and an RSVP season that runs itself. Guests, for their part, notice none of the machinery. They notice their own names, set in the suite's italic, on a card that plainly wasn't printed three hundred times. That — like every detail worth doing — is the point.