EventWorks is the platform we built for the way event agencies, venues and caterers run. From first enquiry through to the final invoice, it covers contacts and accounts, quotes and purchase orders, costing and forecasting, diary and resource management, document generation and storage, sales reporting. The kind of work most teams in the industry currently piece together from spreadsheets, shared docs and email threads.
We’ve been building it since 2015. It runs as a multi-tenant SaaS, so each customer gets their own isolated MySQL database, their own subdomain, their own admin. No shared data, no noisy-neighbour problems. The platform sits on SOC 2 and ISO 27001 certified infrastructure.
The integration surface has grown over the years. Customers don’t want to give up the tools they already use, so we’ve built bridges to most of them: Xero, Sage, QuickBooks, FreeAgent and NetSuite for accounting; HubSpot for CRM with bidirectional sync; MailChimp for marketing contact sync; Signable for e-signatures; and a full Zapier app that connects EventWorks to the thousands of other apps Zapier supports. Stripe and GoCardless handle payments.
Behind all of that sits a fair amount of our own packaging work: around fifty internal Laravel packages we’ve built over the years for things like media handling, notifications, reporting, audit logging and admin UI. Those packages are why we can ship the next bespoke client project quickly. Most of what a business app needs, we’ve already built once.
EventWorks is in production, used by event businesses around the world, and worked on nearly every day. It’s the project that taught us the most about running software for the long haul: what to invest in early, what to leave alone, what to rip out and replace.
