vibecodedevents.com

Send an email.
Wake up to a website.

Most event sites take a month because most of that month is meetings. We skip that part. You send what you already know — the date, the feeling, the colours, what you want people to do — and the site is live before you have finished deciding the rest. The parts you have not decided show up on the page as to confirm instead of being invented.

19h 46m

From a client’s brief email to the site being live. Thursday 2:31 PM → Friday 10:18 AM. Most of that was overnight. It is the slow one — it was the first of its kind. The next one reuses the engine.

Send a brief See what we’ve built
The same engine points at film. This is an invitation — a 40th birthday, Charlotte, April 2026 — built with AI-assisted production, written, scored and cut as a two-minute short, then sent instead of a card. Sound on.
what the night actually looked like

The site is one deliverable. The room is the other.

Virgo Season, Charlotte — the week the site above was built for.

And sometimes the invitation is the production.

The film at the top of this page is the other half of this. Same bargain as the site: you send what the night is supposed to feel like, and the thing people actually open comes back finished. AI-assisted production is what makes that reachable — no crew day, no location hire, no six-week post.

  • A two-minute invitation film — written, scored and cut.
  • Delivered as a file you can text, email or post, and as a link.
  • Pairs with the site, or stands on its own.
Ask about a film Email instead
the build log — jay day 40

What those 19 hours actually looked like

Thu 2:31 PM
The brief arrives as an email

Nine lines. Palette, photography, two pages, a dress code, and one requirement the client called crucial: entry is a donation. No call, no discovery workshop, no deck.

Thu evening
Five domains checked, one picked

The client had listed five he liked. All five were available; the shortest one won.

Fri 10:18 AM
Live on the internet

Four pages, three working forms, a countdown, and every fact he hadn't decided yet showing as a visible 'to confirm' chip rather than a guess.

Same day
Handed back for corrections

Venue, city, beneficiary and payment link were still open. They were knobs in the generator, so each one is a one-line change — not a redesign.

with the right information

Everything a brief needs, and nothing it doesn’t

The email that produced the site above was nine lines long. This is what was in it. If you can answer most of these in one sitting, you have given us enough — and anything you leave blank becomes a visible chip on the page rather than a delay.

What the event is

A 40th. A season of watch parties. A launch. One line is enough.

When and where

Dates you know. The ones you don't become a 'to confirm' chip.

The feeling

“Glamorous, bold, high-end” was one client's whole brand brief. It worked.

Colours

Three or four. If you don't have them, we derive them from the event itself.

The pages

Usually two to four. A night, a main event, a way to say yes.

The ask

RSVP, ticket, donation, door list — what do you want a visitor to actually do?

Photos

Or not. A missing image renders as a designed panel, never a broken one.

shipped & running

Every one of these is live, and ours

Not mockups and not case studies written after the fact. These are sites we built, deployed and still operate — including the one you are reading, which was built with the same generator it is describing.

The Jay Day 40 site as it is live today. A 40th birthday, NYE weekend

Jay Day 40

Brief by email Thursday, live Friday. Door list, group trip and sponsor forms; a live countdown to midnight; every undecided fact visible as a chip.

See it →

The Virgo Season CLT site as it is live today. A five-day birthday week

Virgo Season CLT

Two headline nights and an undercard, a programme card for everything else, a second page for the close circle, and one RSVP form serving both. This site is built in its mould.

See it →

The Dawg Pound Charlotte site as it is live today. A recurring series, every Sunday

Dawg Pound Charlotte

Ticketing wired to Eventbrite, the schedule pulled from the season fixture list, and a printable game-day kit — backdrop, member cards, specials menu — generated from the same source as the pages.

See it →

The Studio 55 site as it is live today. A venue

Studio 55

The room as the argument. Built as a preview, noindexed, handed over before a dollar changed hands.

See it →

The Las Vegas 40th site as it is live today. A five-day trip, delivered the day before

Las Vegas 40th

Day tabs that open on the right day in Las Vegas wherever you are, a checklist that saves to the phone, and a shows page that works out which Cirque productions actually run on each night of the trip. Private, so it carries a real mobile number and a login instead of an index.

Private — password protected at the client’s request.

The Studio 55 Photo Booths site as it is live today. An event service with packages

Studio 55 Photo Booths

Pricing the client hadn't set renders as placeholder pricing — shown as unset, not invented.

See it →

see it talk

The same pipeline, pointed at a person

An avatar we generated, scripted and cut in-house. The event sites and this are the same machine — a brief in, a finished thing out, fast enough that you stop planning around the production time.

the honest answers

What people ask first

Is it a template?

No. Every site here is generated from its own file, and the design argument comes from what the event actually is. A birthday concert week got built like a gig poster. A 40th got built like an invitation. A football season got built like a fixture list. A template would have made all three look the same.

What if I don't know the venue yet?

Then the venue shows as “to confirm” on the live page. That is a deliberate rule and it is enforced in the build: an unknown fact is never filled in with something plausible. You can send a page to people while half of it is still open.

Who owns it?

You do. It is your domain, your forms, your list. Nothing is locked to us.

Can you do the video too?

Yes — films, recap cuts, vertical edits for stories, and presenter-avatar explainers. Most of the sites above have one.

start here

Send the brief

Write it the way you would text a friend about the event. There is no wrong format — the last one was nine lines in an email and it was plenty.

Goes to the person who does the build. You get a real reply, not a sequence.

Or skip the form entirely.

Write to us info@vibecodedevents.com Opens your mail app with the subject filled in. Forward an email you already sent Straight to info@ The last brief was nine lines in an email to a friend. That works.