A catering website.
Ready for your next event.

Menus people can read on a phone

A catering menu often starts as a print document. That document may work well at a tasting but be difficult to use on a small screen. Tiny columns, scanned pages and image-only prices ask the visitor to zoom before they can understand the food. An HTML menu gives headings, dishes and notes a readable order. It also lets your team update a description without replacing a whole brochure.

We can organise the agreed menu content by service style or occasion. A seated wedding dinner needs different information from a corporate lunch delivered to an office. Dietary labels must come from your team and reflect how the kitchen actually handles ingredients. A website should not promise an allergy-safe service unless you have approved that exact statement. A downloadable PDF can remain as an optional take-away version.

Common patterns worth checking

Some catering sites offer one general contact box for every event. The resulting message may omit the date, guest count, venue or service style. A short structured enquiry can ask for those details and leave room for questions. It should distinguish a preferred date from a confirmed booking and tell the visitor what happens after submission.

Other sites list weddings, private parties and corporate catering without showing how those services differ. A person arranging an office reception may need delivery and staffing details; a wedding planner may need tasting, setup and venue coordination information. Separate sections can explain these differences within an agreed page scope.

Repeated photographs can make a gallery hard to interpret. A plated dish, a staffed buffet and a room setup answer different questions. Use approved images with descriptive captions, consistent crops and accurate credits. Avoid presenting stock photographs as evidence of an event your business catered.

Service areas and practical limits also deserve a clear place. Visitors need to know whether you travel to their venue, whether travel is quoted separately and who supplies equipment. These are business decisions supplied by you, not assumptions we make from a map.

What we build around your service

The agreed informational website can include mobile menus, occasion sections, a service-area explanation, a curated gallery and real authorised review highlights. The enquiry form can collect event date, approximate guest count, venue location, service style and dietary notes. We keep required questions focused so someone who is still planning can explain what they know.

For example, a private dinner enquiry might offer a guest-count range and a field for the address or area. A corporate enquiry might ask whether the event needs delivery only or staff on site. You approve the wording and the recipient before launch. Collecting a request does not confirm availability, a menu price or a booking.

If weddings, corporate events and private events need full separate pages, we agree how they fit within the three-page Launch scope or quote extra pages. Menus and galleries should support the visitor’s decision rather than become an unbounded content project. You provide current offerings, licensed photographs and approved business facts.

Connecting the enquiry to your team

An enquiry should arrive in an account your business controls. The confirmation tells the visitor the request was received and explains the next step your team has agreed. It should not promise a response time that nobody can maintain. We test missing fields, malformed email addresses and delivery failure with synthetic details before launch.

Existing event-management software can remain the place where staff build proposals and confirm work. A website link, embedded supported form or separately scoped integration can connect the journey. We inspect the software’s available options before promising that every enquiry will appear in a dashboard. Provider subscriptions and integration maintenance are separate costs.

From first draft to your live website

We start with a draft concept so you can review the proposed structure and visual direction. You approve the design, pay the first 50% of Launch, and we finish the agreed website using your approved content. The final 50% is due before production launch. A free concept request is reviewed for fit; it is not a promise of a complete free website or a confirmed project.

The three-business-day first-draft target begins after the required brief, content and access are available. A launch-ready website in as little as five business days depends on agreed informational scope and timely consolidated feedback. Complex menu systems, cinematic assets and operational integrations have separate schedules. Website Plan uses its own setup and monthly payment schedule, not Launch’s two project payments.

Useful additions for catering teams

An atmospheric hero or scroll film can show a food and event setting when asset rights, production brief and mobile performance are agreed. It starts from $499 and is separately scoped; the detailed concept film is not automatically included at that starting price.

A bounded enquiry workflow or staff dashboard starts from $1,200. It can help a team review defined event fields and track a limited process, but is not a full CRM. An AI missed-call receptionist can collect enquiry details when your team cannot answer, subject to forwarding, consent and an agreed minutes allowance. Review request automation can follow completed jobs without filtering unhappy customers.

Choose a website plan

Launch: $899 one-time, 50% after design approval and 50% before launch. Three months of Website Care from production launch, then $69/month with recorded agreement or $690/year only with express annual selection. Opt out at kickoff. Website Plan: $299 setup plus $149/month, 12 paid monthly instalments, $2,087 minimum before applicable taxes and approved extras. Care is included.

Compare website pricing and add-ons ↗