The product story
The calendar was empty. The business wasn't available.
Mia does not need another calendar or chatbot. She needs to know whether Little Wild can actually deliver the party — and she needs the admin around that decision to keep moving when she is asleep, setting up another event or living her life.
Problem-solving impact
Turns “can I book?” into a real operational decision, not a calendar guess.
Owner effort removed
Messages, feasibility, holds, branded emails, balance chasing and recovery move without Mia.
Craft & execution
One connected system for customers, operations, money, team and owner alerts.
Proof
Facebook + Instagram live, branded email live, booking engine live, PWA owner alerts and command centre live.
Mia’s side of the story
What running Little Wild used to look like — and what changed when the routine admin stopped depending on her.
Before Little Wild
The invisible admin behind one “yes”
The customer only sees a party. Mia sees people, vans, kit, travel, setup windows, payments and promises.
The after-hours walkthrough
What happens after a parent messages while Mia is asleep
A customer messages Little Wild
Facebook Messenger and Instagram are connected directly. Website enquiries use the same customer pipeline. Little Wild can respond after hours and send the customer into the booking journey without waiting for Mia.
The customer gives Little Wild the information it actually needs
Date, party time, package, guest count, add-ons, exact Jersey location, access notes and contact details — plus what the child is into and their favourite colours. These creative details arrive with the enquiry and stay on the confirmed booking for Mia to see, separate from general notes. Instagram and Facebook bookings keep their source attribution too.
The system asks a harder question than “is the calendar empty?”
It checks staff skills and approved time off, drivers, vehicle capacity, equipment quantities, existing holds, setup and pack-down, cleaning/reset time, parish travel, travel between jobs, lead time and daily job limits.
If the requested time cannot really be delivered, it does not sell it
Little Wild explains the constraint and calculates alternatives that pass the same operational checks. The customer sees a real option instead of Mia promising a time that later creates a logistics problem.
A workable slot is held while the customer decides
Crew, vehicle and equipment are provisionally protected for 30 minutes. The price and payment requirement are calculated server-side: normal bookings take a deposit; last-minute bookings within four days require full payment.
Payment turns the enquiry into an operational booking
After the deposit or full payment succeeds, Little Wild re-checks feasibility, confirms the booking, reserves crew, van and equipment, schedules payment follow-up, sends the parent a branded booking + payment confirmation email, and notifies Mia that the payment step is complete.
The balance chases itself
If a balance remains, Little Wild sends the branded balance email automatically four days before the party. If it is still unpaid 24 hours later, the parent gets a polite follow-up and Mia is escalated by dashboard alert, owner email and PWA notification.
When payment is recorded, everyone is updated automatically
A completed balance records the payment, clears the overdue state, cancels unnecessary reminders, emails the parent a branded receipt and notifies Mia that the booking is recorded as paid.
The customer can manage their own booking
Parents open My Little Wild with their booking reference and phone number to see their celebration, payment status, balance and existing extras. They can update safe party details, including guest count and access notes, and add compatible extras. Little Wild recalculates the balance where needed and tells Mia what changed. Extras affecting equipment, timing or capacity go to Mia for approval before they are added.
A cancellation becomes a recovery opportunity
Cancelling releases the crew, vehicle and equipment. Little Wild immediately identifies the next waitlisted family whose requested window fits and shows Mia the freed date, time and location with a suggested recovery action instead of letting that capacity disappear.
The freed slot is offered one family at a time
The selected family gets a branded email showing the exact date, time, location and package, with a 30-minute accept/decline link. Accepted, declined and expired states are tracked, and Mia is notified of the response.
A booking, end to end
What Little Wild can finish before Mia even opens the app
This is the point of the product: not another dashboard Mia has to operate, but a chain of decisions and follow-up that keeps moving on its own.
Instagram or Facebook DM arrives
Little Wild receives the message directly, recognises a booking enquiry and replies with the route into Check my date.
The customer shares the party brief
Saturday at 11:00 for Theo, turning 4: Monster trucks, with black, lime green & orange styling. Little Wild keeps those details with the enquiry and booking for Mia while checking staff, vans, kit, travel and timing — not just an empty calendar square.
11:00 cannot genuinely work
Little Wild does not sell it. It calculates the next feasible option using the same operational rules and offers that instead.
The customer pays
The system re-checks feasibility, converts the hold, reserves the real crew, vehicle and equipment, records the payment and confirms the booking.
The parent gets the branded booking + payment email
A Little Wild confirmation shows the booking reference, deposit or full payment, date, time, location, package and what remains to pay. Mia sends nothing manually, and her PWA is notified that the payment landed.
The parent changes the booking themselves
They open My Little Wild, update a safe party detail or add a compatible extra. Little Wild recalculates the balance where needed and tells Mia what changed. Extras affecting equipment, timing or capacity wait for her approval.
The balance chases itself
Four days before the party, the branded balance email goes out automatically. If it remains unpaid 24 hours later, the parent gets one polite follow-up and only then does Mia get an owner-action alert.
The system closes the loop
Payment is recorded, redundant reminders stop, the parent gets a branded receipt and Mia is told the money arrived.
The empty capacity becomes an opportunity
Crew, van and kit are released; Little Wild suggests the next fitting waitlist family and shows Mia the freed date, time and location. One click sends a branded 30-minute offer, then tracks accepted, declined or expired and surfaces the next safe action.
Owner intervention
0 — unless Little Wild reaches a genuine exception.
That is the design rule behind the whole build: automate the routine, surface the exception, and make the next safe action obvious.
The decision engine
What Little Wild checks before it ever says yes
Crew
Required skills, team lead needs, drivers, approved time off, existing jobs and max jobs per day.
Vehicles
Load capacity, current assignments, travel windows and whether a driver is actually available.
Equipment
Required kit, quantities, existing holds, booking reservations and the reset/cleaning time before reuse.
Travel
A twelve-parish Jersey travel matrix, outbound/return buffers and travel between consecutive jobs.
Timing
Setup, party duration, pack-down, turnaround and the full operational window — not just the party start time.
Lead time
Package and add-on lead times so the system does not sell work the team cannot prepare in time.
A calendar tells you whether a time is empty.
Little Wild tells you whether the business can actually deliver the booking.
Payment without chasing
The money workflow runs itself
Branded emails are part of the product, not an afterthought
Booking + deposit confirmation, full-payment confirmation, balance due, overdue follow-up, balance receipt and waitlist recovery all use the Little Wild identity. The parent experience stays consistent even when no one is manually sending the message — and every payment state is written back into Mia's command centre.
Mia's command centre
Little Wild is installable as Mia's own PWA
Mia can install the studio dashboard on her phone like an app. Push notifications bring meaningful changes to her instead of making her keep checking the admin: new booking enquiries, deposits or full payments, balances paid, overdue balances that now need action, waitlist responses and team leave.
The command centre separates money that is simply scheduled from money that is overdue and now needs Mia. Paid bookings clear themselves; overdue balances only become owner work after the automated customer follow-up has already run.
The dashboard answers one question first:
“What actually needs me right now?”
Example morning view
Mia should be able to understand the business in under a minute
Paid overnight
Isla · deposit received
No action
Balance workflow
Freddie · reminder sent automatically
No action
Needs Mia
One balance is now overdue after follow-up
Open exact booking
Recovered capacity
Holly accepted the freed Saturday slot
Complete recovery
This example shows how the live dashboard uses actual booking, payment, waitlist, team and operations state to decide what belongs under “needs you”.
Exceptions, not admin
Mia only gets pulled in when judgement is genuinely useful
A genuinely ambiguous enquiry
Mia gets Approve / Decline instead of searching the system.
A real operations clash
The Copilot explains the conflict and, where safe, shows the exact internal hold-time fix before Mia approves it.
A cancellation or reschedule request
The request lands against the exact booking with the relevant actions.
An overdue balance after automation has tried
Only then does it become a human follow-up.
A staff time-off request that overlaps booked work
Approval is blocked until the affected work is reassigned.
Recover lost capacity
A cancellation does not have to become lost revenue
When a booking is cancelled, Little Wild releases the resources and finds waitlisted families whose requested date window fits. Mia sees the suggested match with the freed date, time and location, then can send a one-family-at-a-time 30-minute offer.
The customer accepts or declines from the branded link. Declined or expired means the next suitable family can be offered the space.
Team self-service
Time off stops being another spreadsheet job
Mia adds a team member once. Each person gets a branded self-service time-off link. Requests land in Mia's Copilot, are checked against booked work, and only approved time off removes that person from future booking allocation.
A day before approved leave begins, Mia gets a reminder so the absence is not forgotten.
Copilot + marketing intelligence
The system does more than store data — it tells Mia what to do with it
Operations Copilot
If Little Wild spots an internal equipment overlap, it distinguishes a stale reservation window from a real customer conflict. Where the fix is safe, Mia sees exactly which equipment hold will change, from what time to what time, before she approves it.
Marketing
Source parameters track Facebook, Instagram and website booking journeys. The booking form also asks “How did you hear about us?” so Mia can compare tracked acquisition with what customers remember, then see enquiries, conversion and confirmed value by channel.
What this removes from Mia's day
How Little Wild works
This is not a prettier booking form. It is the small-business operating layer behind the booking.
Facebook Messenger and Instagram are live-connected. Website, social and booking activity share the same operational data. Branded booking, deposit, balance, overdue, receipt and waitlist emails run from the same workflow. The owner dashboard is installable as a PWA and pushes meaningful events to Mia instead of asking her to keep checking. The payment state, reminder logic, resource allocation, recovery workflow, team availability and owner-action logic are real.