Website for event planners: prices, galleries and enquiries

en 2026-09-19 7 min read

An event planner's website costs EUR 600 to 900 as a single page, EUR 900 to 1.500 as a mini-site, and EUR 1.500 to 3.500 as a full business website with a CMS. Add a client login, a dashboard or online payments and you are at step 04, EUR 3.500 to 7.500.

What moves you along that line is not only the page count but the gallery, and what you need the photographs to do once they are on screen.

What you are actually buying

Two things carry an event planner's site: the evidence and the enquiry. A visitor wants to see a room at the scale they are planning, then ask you one question without hunting for a way to ask it. So the budget question is a gallery question and a form question.

Where galleries start costing real money

Six photographs in a row on one page cost nothing extra, and that is step 01 work. The money appears when the gallery has to behave like a tool instead of a decoration.

• Who adds the next event. If the images sit in the build, every new event is a developer task. If they sit in a CMS, you add the event yourself, and that structure has to be built first. That single decision is the difference between step 01 and step 02.
• What happens to a full-resolution camera file. Files straight off a camera are far heavier than a web page should carry. The site needs resized versions, modern formats, dimensions in the markup so the layout does not jump while images load, and lazy loading below the fold. That pipeline is invisible once built, so cheap quotes can drop it.
• Whether the grid is uniform. A square grid is quick to build and quick to fill. Mixed portrait and landscape shots in an editorial arrangement need rules for every screen width, and writing those rules is the work.
• What a click does. Opening a bigger image sounds trivial until it needs arrow keys, a swipe on a phone, a close that returns you to the same scroll position, and a link that opens one specific image.
• Filtering. Weddings, corporate, private, by venue, by season. A filter is a field on every record, so the structure has to exist before the filter can.
• Video. A showreel is not a photo. It needs a poster frame, a decision about muted autoplay, captions, and something sensible for a phone on a weak signal.
• One portfolio, or an archive. A single portfolio page is step 02. An archive where every event has its own page, its own gallery, credits, venue and supplier list is step 03, because each event is now a record with fields.

None of that is exotic. It is the difference between images on a page and a portfolio you can run without calling anyone. How it gets built is on design and engineering.

The five steps, and what each one buys a planner

The same five steps are on packages. A fixed quote always follows scoping, so these ranges tell you which step you are on, not what the invoice will say.

The enquiry form is the other half of the price

A gallery that impresses someone and then hands them a bare name, email and message box wastes the impression. The fields that make a planner's enquiry answerable are the date or month, the type of event, a guest count, the venue or city, and a budget band. That is five fields and a message, and each one you add after that is a reason to close the tab.

Behind the form sits the part nobody sees: where the enquiry lands, who gets notified, an automatic reply so the sender knows it arrived, spam protection that does not block real people, and a thank-you page so analytics can count an enquiry instead of guessing. That plumbing is included from step 01 upwards. Taking a deposit online is a different thing entirely: that is payments, and payments are step 04.

Process and timeline

Scoping call first, then a fixed quote. Structure and copy next, because the layout follows the words. Then design, build, content load, your review, and launch with a check that the form and the analytics are both recording.

A single page is 1 to 2 weeks, a mini-site 2 to 3 weeks, a business website 3 to 6 weeks, an advanced site or web app 6 to 12 weeks. The part that waits on you is the content: the photographs, the credits, and one honest paragraph per event. Bring those to the scoping call and the timeline holds. Builds run on Next.js, set out on our Next.js page.

When to spend less

If your enquiries arrive through venues and word of mouth and you have one strong set of photographs, buy step 01 at EUR 600 to 900 and put the difference into a photographer. A single page with real pictures, a clear enquiry form and a fast load beats a thin seven-page site.

Three more ways to keep the number down:

• Do not buy a client portal before a client has asked you for one. Email handles it until email starts to hurt, and then a client login is an add-on at EUR 1.500 to 4.000, confirmed by the quote.
• Take SEO foundation as the one-off it is, EUR 450 to 750, covering Console, analytics, indexation, technical hygiene, titles, internal links and a 3 to 6 month plan. SEO growth at EUR 500 to 800 a month is for when there is something to grow.
• Care at EUR 100 to 300 a month is updates, monitoring, backups and small fixes. It is not a redesign and it is not new features, so do not buy it expecting either.

Questions planners ask before signing

Can I add a new event myself after launch?

From step 02 upwards, yes. A basic CMS is part of that step, so adding an event means uploading the photographs and filling in the fields, and the image handling takes care of itself. Step 01 has no CMS by design, so changes there are a small paid job or part of a care plan at EUR 100 to 300 a month.

Do I need a booking system?

If what you mean by booking is a structured enquiry with a date in it, that is step 03 work inside EUR 1.500 to 3.500. A system that holds a slot and takes money is payments, which puts it in step 04 at EUR 3.500 to 7.500. Decide which you mean before anyone quotes, because the gap is a whole step.

Who owns the site, and who hosts it?

You own the code, the repository and the database. That is not a favour, it is the only arrangement that lets you take the site elsewhere without an argument. Hosting is agreed per project: the studio can host it, and that is settled during scoping.

How many events should the portfolio show?

Enough that a visitor recognises their own event in yours. A wedding buyer needs to see weddings rather than scroll past corporate launches, which is the argument for filtering rather than volume. Build the filter when the list is long enough to irritate you, because a filter is a field you then fill in for every event.

Bring the photographs you want to show and the enquiry you want to receive, and we will tell you which step that is. Start at the contact form.