Table & Together
99–100 mobile Performance and 100 Accessibility on every page
Project overview
Marketing site for a Sydney Italian catering business built around live cooking stations — pasta rolled by hand, wood-fired pizza, tableside finishing. Eleven static Astro pages, an enquiry flow and gated menu-guide PDF that fan out to email, Klaviyo and a Google Sheet, and 76 unit tests behind the lead capture.
The challenge
Table & Together cater Italian weddings, corporate events and milestone parties around live cooking stations — pasta rolled by hand, wood-fired pizza, tableside finishing. The site had two jobs that pull against each other: sell an experience that is inherently visual, and qualify leads hard enough that a $1,800 minimum spend does not arrive as a surprise halfway through a conversation. It also had to be fast on a phone at a venue, and every lead had to reach the inbox, the email platform and the spreadsheet the team actually works from.
What we did
- Eleven static pages on Astro with a branded 404 — only the two API routes that receive form submissions opt into server rendering, so everything a visitor reads is served from the CDN
- All copy in content collections (FAQs, packages, gallery, offerings, founders, testimonials) with schema validation, so the team's text lives in data rather than buried in markup
- Lead capture fanning out to three destinations — a notification email, Klaviyo, and a Google Sheet — each called directly rather than through an SDK, so one failing destination cannot take the enquiry down with it
- A gated menu-guide PDF as a second capture point for visitors who are not ready to enquire, running through the same validation and the same fan-out
- Security and cache headers written into the Vercel Build Output manifest by a local Astro integration, so what the platform actually routes with is inspectable after any build
- A full verification pass before launch — 76 unit tests, Lighthouse on all ten pages, and a page-by-page audit that surfaced two real defects: a WCAG AA contrast failure at 3.88:1 and a swallowed space in the pricing copy
The results
Services delivered
Interested in similar services? View all services →
Summary
Publishing the minimum spend on the enquiry page is the kind of decision that looks like it costs leads and does the opposite: catering enquiries that die on price waste the client's time, not the visitor's. The other lesson is procedural — the pre-launch verification pass, run with real numbers instead of a summary, is what caught a contrast failure and a broken sentence that had been shipping unnoticed. Sites are not verified by looking at them.
Want results like these?
Let's talk about your project. Free 30-minute consultation, no commitment.
Start a project