Websitefor your event
An event has a date, and the date doesn't move. So I take these projects outside the general queue and plan backwards from the day itself: first whatever registration can't open without, then everything else.
What's included
Form with confirmation to the attendee and an exportable list
Schedule by day and room, speaker cards
Map, how to get there, where to park
Time left until the event and until registration closes
The page survives announcement day and event morning
It switches to report mode, the links keep working
How the work runs
- 011 day
Scoping the event
Date, venue, expected numbers, and what absolutely has to be captured at registration. That also settles what ships before the announcement and what can land between announcement and event.
- 022–3 days
Registration
First, the thing sign-ups can't open without: form, confirmation email, exportable list. This can go live ahead of everything else — registration matters more than completeness.
- 032–3 days
Programme
Schedule by day and room, speaker cards, map and parking. Programmes change until the last minute, so this section is editable by you without me.
- 043–5 days
Design and build
The look of the event, the countdown, the mobile version. I test load separately: the peak arrives in the hour of the announcement and on the morning itself, and an ordinary page doesn't hold it.
- 051 day + until the event
Launch and standby
Registration opens and I stay reachable right up to the date. Changes to the programme and speaker list during those days count as normal work, not extras.
What moves the price
"from $2,400" is the floor, not bait. Here's what pushes the number up, so you can place your own case before we talk.
Under two weeks means working outside the queue, and that costs more
A hundred people and three thousand put different demands on load and on list handling
A simple form, or ticketing with payment, categories and seating
A single track, or several rooms with parallel talks and personal schedules
Who it's for
- →Conferences, forums, industry meetups
- →Concerts, festivals, showcases
- →Openings, launches, open days
Questions
Can you make it if the event is in three weeks?
Yes, that's a normal timeline for this. A week also works, but then we cut: registration and the essentials go live first, the rest fills in as we go — sign-ups matter more than a complete page.
Do I need to sell tickets on the site?
If entry is paid, usually yes — otherwise you lose a share of the people who said yes: someone ready to pay now rarely comes back to pay tomorrow. I wire up a payment provider and receipts go out automatically. If tickets already sell on an external platform, I don't duplicate it — I send people there and keep the programme and answers on your site.
Will it survive announcement day?
That's a specific piece of work, not something that happens by itself. The page is served pre-built, without a database call per visitor, and that holds thousands of simultaneous arrivals on an ordinary server. The fragile part isn't the page, it's the registration form — so sign-ups go through a queue: at peak, people wait for a confirmation instead of getting an error.
Where do registrations go?
Into a list you can export at any moment, and as an instant notification to you. If you use a CRM or a mailing tool, they go straight there. Attendees get a confirmation with the details — that alone measurably reduces no-shows.
What happens to the site after the event?
It switches to report mode: photographs, recordings, presentations, and a form for the next event. The links keep working, which matters — that page has accumulated search weight and inbound links, and throwing it away means throwing those away too.
Shall we talk?
Half an hour on a call and you'll have an estimate and a plan. Free, and it commits you to nothing.