Case study · Events · Richmond, Virginia
Mobile Axe RVA: the system behind it.
A mobile axe-throwing business that books parties, team events and gatherings around Richmond. Studio built its website, booking flow, phone agent, owner dashboard and crew tools.
Mobile Axe RVA is my family's business, which I run. It is not a paying client. It's where I build and test every system before I offer it to anyone else.
The problems
Where the time went.
- 01Inquiries arrive everywhere. Calls, texts, a web form, often after hours. Each needs a date, place, head count and price before anyone can say yes.
- 02Quotes take back-and-forth. Price depends on guests, time and travel, so every quote was worked out by hand.
- 03Money is easy to lose track of. Deposits, balances and what each event actually paid.
- 04The crew needs details on the day. Where, when, how many, without seeing the owner's numbers.
What was built
The pieces.
- Website
- The public site at mobileaxerva.com, with packages, photos and a booking request that asks for date, location, guest count and event type.
- Phone agent
- An AI agent on the booking line. It answers, collects the event details, quotes from the price list and hands the booking to a person to confirm. It doesn't lock in a date on its own.
- Owner dashboard
- Every request, quote and booking in one place, with each booking's money read from its invoices. One tap copies a customer's payment link.
- Team portal
- The owner puts a coach on an event and it shows up as their shift. Coaches see the event details; only the owner sees what it's worth.
- Paperwork
- Waivers that print or download as a PDF on a phone, event signage, game sheets and the QR codes they use.
A customer's path
From first click to the event.
Finds Mobile Axe and opens the site on a phone.
Requests a quote with the date, location, guest count and event type, or calls and talks to the phone agent.
The request lands in the owner dashboard as one record.
Gets a quote and a payment link. A deposit confirms the date.
A coach is scheduled and sees the event in the team portal.
The event happens; the booking's balance and receipt come from the same records.
Evidence and limits
What's measured, and what isn't.
Implemented, and you can check it: the website is live at mobileaxerva.com, and the phone agent is set up on the booking line listed there.
Not measured: I don't have a clean before-and-after on bookings, revenue or response time, so I don't publish one. When Studio builds for you, the monthly report tracks what we can count from day one.
Still being improved: recent work added crew scheduling, payment links, invoice-based booking totals and phone-friendly waivers (September 2026).