Software for how an event business actually runs

Systems and AI tools

The tools your business runs on, built for your business.

Most event companies run on a spreadsheet, a generic CRM and a lot of memory. We build the system that fits how your work actually flows: where leads come from, how a quote becomes a signed job, what the crew needs on the day, and what the owner needs to see every morning. Then we add assistants that read that data and propose the next action.

In plain English

What does Gray Park build?

CRMs and lead hubs, quoting and signing, operations dashboards and AI assistants, built for one company and owned by that company. The AI reads and proposes; a person approves anything that changes a record, contacts a customer or spends money.

What we build

contacts

CRMs and lead hubs

Leads from every form, call and inbox into one record, with statuses that match your sales process and reminders that do not rely on memory.

draw

Quoting and signing

Line items, versions, e-signature and deposits, so a quote becomes a booked job without a PDF round trip.

dashboard

Operations dashboards

Read the tools you already run (field service, scheduling, accounting, call tracking) and show the queue that matters today.

psychology

AI assistants

A daily brief, scored calls, drafted replies and proposed changes, each waiting for a person to approve.

sync_alt

Integrations

Your website forms, your accounting, your calendar, your ads: connected so data is entered once.

lock

Owned by you

Your repository, your hosting, your database, your accounts. Credentials encrypted, access you can revoke.

A production team at a laptop during load-in

Systems we have built

Two are our own products. Two are client systems, described without names.

request_quote

Quotes, signatures and leads for event companies

A platform for event rental and production companies: leads by rep, quotes with versioned line items, client signing with a deposit, invoices, and a client portal. Built as a product we run ourselves.

smart_toy

Gray Park Operator

Our own marketing system: twenty-five specialist roles, an approval queue, a change log with rollbacks, client portal and weekly scorecards. The same discipline we bring to client systems.

engineering

An operations chief of staff for a service contractor

Reads the contractor's field-service platform and call tracking every ten minutes: estimates awaiting answers, unpaid invoices, missed calls scored and texted back by a person, permits and crew credentials, a daily brief for the owner. Agents recommend, humans change.

hub

A lead hub for two event brands

Inbound leads from two websites into one CRM with statuses, files, receipts and PDFs, then forwarded to the marketing system so follow-up and reporting share one record.

How a system project runs

  1. 01

    Discovery

    How the work flows today, which tools hold the data, which decisions are made by hand every day. A short document you sign off.

  2. 02

    First slice

    The one piece that removes the most manual work, live in weeks, in your own accounts, with real data.

  3. 03

    Rules and approvals

    What the assistants may propose, what only a person may change, who approves. Written down before any AI touches a record.

  4. 04

    More slices

    Each next piece is scoped from what the last one taught us. You can stop after any slice and keep everything.

  5. 05

    Running

    Monitoring, a change log with rollbacks, and the Operator roles that keep documentation current.

Why an agency builds software

Because the marketing has to land somewhere. A lead that arrives at a spreadsheet dies there. When the system and the marketing share one record, the Friday scorecard can say which campaign booked which job.

Questions

The tools an event business runs on but cannot buy off the shelf: a CRM that matches how your leads actually arrive, quoting with e-signature and deposits, operations dashboards that read the software you already use, and assistants that turn that data into a daily brief and proposed actions.

You do. Every system lives in your own accounts: your code repository, your hosting, your database. We work through access you grant and can remove. Nothing is a tenant of someone else's platform.

No. Assistants read, summarise and propose. A person approves anything that changes a record, contacts a customer or spends money. Every applied change is logged with a before, an after and a way back.

A short discovery: how the work flows today, which tools hold the data, what decisions are made by hand every day. Then a scoped first slice that goes live in weeks, and more slices as each one proves itself.

It can be either. Some clients start with a system because the leads were already there and the follow-up was the problem. Others add one later so the marketing has somewhere good to land.

Tell us how the work flows today.

A short call about where the hours go, then a scoped first slice. No platform fees, no lock-in.