ReasonWhat is this and who should come?
Event website design and registration systems
Make the event clear. Make the next step easy.
I build event websites that explain what is happening, take registrations or payments and give the organiser a useful record for this event and the next one.
£1,400 - £2,200typical complete project2 to 4 weeksusual build time
Registration openexample flow
Saturday 18 OctoberThe Makers ForumLondon · doors 09:00
£35Choose a ticket
GeneralSelectedStudentAvailable
Capacity checked before paymentConfirmation follows the completed registration.
The organiser receives a structured registration record.
£1,400 - £2,200typical event project
2 to 4 weeksusual delivery
£600registrations from
2UK event references shown
The short answer
Sell the decision. Then handle the detail.
An event visitor needs five answers quickly: what it is, who it is for, when and where it happens, what it costs and how to take the next step.
Behind that simple decision, the organiser may need ticket types, capacity, payment, confirmations, practical questions, attendee exports and a reliable launch. I design those as one joined journey.
Start with the constraint
What is making the event harder to sell or run?
Choose the closest problem. The recommended route and useful starting price change with it.
The sales page has a job
Give each question one obvious answer.
A visitor should not need to hunt through posters, social posts and PDFs before deciding. The page order follows the decision they are making.
CommitmentWhen, where, duration and price
ConfidenceProgramme, people, access and practical details
ActionRegister, pay or make the right enquiry
ChooseTicket type, date or session
RegisterOnly the details the organiser needs
PayConnected payment route where required
ConfirmUseful next steps for attendee and organiser
Registration without the muddle
One journey. Several possible outcomes.
Free registration, paid tickets, different sessions, group bookings, capacity limits and sold-out states can be designed around the event rather than forced into one generic form.
- Payment does not count as complete until the system confirms it
- Booking references and exports are agreed before launch
- Refund, transfer and cancellation wording stays visible
Use the actual contract
What could a percentage fee mean across the year?
Enter the event’s own numbers. This is a comparison aid for a percentage-based platform charge, not a claim about any named provider.
Illustrated annual comparison
£31,500ticket value processed
£1,890percentage charge illustrated
Compared with the typical complete projectabout 9 to 14 months
Send me this comparisonIllustration only. Check the provider agreement. It excludes fixed charges, card processing, VAT, attendee-paid fees, refunds, chargebacks, failed payments and the cost of operating a direct system. A direct website does not remove every payment cost.
Launch day is a pattern, not a slogan
Prepare for the moment people actually arrive.
A steady conference booking period and a limited release announced to a large list are different technical problems. I ask for the expected pattern before choosing hosting or integrations.
The next event starts with this audience
Keep the relationship without blurring consent.
Operational messages about a booking are not the same as marketing. I can connect clear consent, lawful list management and post-event journeys without treating every attendee as an automatic subscriber.
newsletter system for websiteBuilt around the event operation
Useful parts. No decorative feature list.
Programme and sessions
Timings, speakers, performers or activities arranged for scanning on a phone.
Tickets and capacity
Free or paid types, limits, availability and honest sold-out states.
Travel and access
Location, arrival, accessibility and practical information before the attendee asks.
Payments and records
A tested transaction route and a registration record the organiser can use.
Attendee communication
Confirmations, practical updates and separately consented future marketing.
Measurement
Track the important journey without pretending every click is a completed sale.
Relevant UK work
Event project references. No borrowed result.
The current UK archive contains the projects below. I am showing the names as relevant references, without attaching performance numbers that the records do not support.
0102
UK event project reference
↗Events Nation
UK event project reference
✓Lime Star Promotions
Preliminary investment
Price the event route before adding extras.
The quote depends on ticket types, capacity rules, payment provider, content readiness and what must connect to an existing system.
See how website pricing works →A focused website with the event information, registration journey and launch checks agreed in scope.
Ask for an event quoteEvent proposition, information structure and enquiry route.
Ticket or registration logic scoped to the event.
List setup and an owned sending route.
Performance work after measuring the real route.
Usually 2 to 4 weeks
From event brief to tested booking route.
Decide
Audience, offer, capacity, ticket types, policies and launch pattern.
Structure
Pages, programme, practical detail and registration data.
Connect
Payment, confirmation, exports and communication routes.
Rehearse
Mobile booking, failure states, capacity and launch-day handoff.
Different events, one clear principle
The website should match how this event works.
The same structure does not suit every organiser. A timed run, multi-session conference and public festival need different booking decisions and operational detail.
If the event has unusual access, age, waiver, group or session rules, include them in the first brief so the route can be scoped correctly.Before the event website build
Event website questions.
Can people register and pay on the event website?
Yes. The route can combine registration, capacity checks and a connected payment provider where the project requires it. The final scope depends on ticket types, currencies, tax treatment, refunds and the records the organiser needs.
Can the website limit ticket numbers and show when an event is sold out?
Yes. Capacity can be set for an event, ticket type, session or timed slot where that logic is included. The sold-out, waiting-list and release rules should be agreed before sales open so the public message matches the organiser’s process.
Can it send confirmation emails or event tickets?
Yes. A completed registration can trigger a useful confirmation and booking reference. Downloadable tickets, QR codes, scanning and a staffed check-in workflow are separate requirements and are scoped according to how entry will operate.
Can one event website handle free and paid tickets?
Yes. Free registration, paid admission, invitation-only access and different ticket types can use separate rules. The page should explain what each choice includes before the attendee enters personal details.
Can an attendee book several places in one order?
Yes, where group booking is part of the scope. We first decide whether the organiser needs one buyer with a quantity, every attendee’s details, named tickets, group discounts or the ability to change names later.
Can registration collect dietary or accessibility requirements?
It can collect information that is genuinely necessary to support attendance, but these fields need careful wording, restricted access and an agreed retention period. Health-related answers can be sensitive personal data, so the form should not collect more than the organiser can justify and protect.
Can the website connect to an existing ticket platform?
Often, yes. Depending on the provider, the website may link, embed, import, export or connect through an available API. I check the provider’s current documentation, account tier and data access before promising a particular integration.
Do I have to replace the ticket platform I already use?
No. A working platform can remain in place while the website improves the sales page and route into it. Moving registration directly onto the site only makes sense when the control, cost, data and operational responsibilities justify the change.
Can an event website cope with a busy ticket launch?
It can be prepared for a forecast launch pattern through suitable hosting, lean critical pages, caching, payment-provider checks and testing. Capacity is not unlimited, and third-party services also have limits, so I ask for audience and release estimates rather than giving an unqualified traffic promise.
Who owns the attendee list?
The organiser controls properly collected registration records on the agreed system, subject to data-protection duties and the terms of connected providers. Booking messages and marketing are treated separately, so attendance does not automatically make someone a newsletter subscriber.
How much does an event website cost?
A typical complete event project is £1,400 to £2,200. The website foundation starts from £900 and registrations or ticketing from £600. Ticket types, payment logic, capacity, content, integrations, check-in requirements and launch preparation affect the final quote.
How long does an event website take to build?
Most focused event projects take 2 to 4 weeks once the event proposition, dates, programme, ticket rules, policies and payment-provider access are ready. Complex schedules, migrations or check-in systems can extend the schedule.
Start with the event operation
Show me what the attendee must decide and do.
Send the event type, date, expected capacity, whether it is free or paid, the current website or ticket route and the planned launch date.
- I inspect the current booking route before recommending a replacement
- I reply within 24 hours - much faster on WhatsApp
- Do not send attendee personal data in this first enquiry
Sent
Got it. I reply within 24 hours - much faster on WhatsApp. Check spam if nothing arrives, then message me there.