That works. If the screen recording clearly demonstrates the product, your written explanation can carry the “what I built and why” story.

Here’s a polished version you can use for your Contra challenge submission:

What I built & why

I built PawRoute, a smart booking and automation experience for a fictional solo mobile dog groomer, Maya, based in Austin, Texas.

I chose mobile dog grooming because booking isn't as simple as finding an empty calendar slot. Every new inquiry can require the owner to check the customer's location, understand the dog’s needs, recommend a service, calculate pricing, find a time that works with the driving route, confirm the appointment, send reminders, and handle cancellations.

I wanted to answer one question:

How can I turn “Can I book?” into “You’re booked” with as little work from the business owner as possible?

So I designed PawRoute around a simple 3-step customer booking experience. Customers provide their location and dog details, receive a recommended service with clear pricing, and choose from available appointment times.

I also created Best Route Match, which prioritizes appointments when Maya is already working nearby instead of treating every available time equally.

Behind the customer experience, PawRoute handles the repetitive work: booking confirmations, reminders, customer information, route updates, rescheduling, and automation activity.

I also designed an owner dashboard where Maya can see appointments, customers, her driving schedule, and what PawRoute has automated.

Finally, I added a cancellation-recovery workflow. When an appointment opens up, PawRoute can help identify suitable waitlisted customers and refill the slot instead of requiring Maya to manually message people.

The goal wasn't simply to build another booking website. It was to design a system where the customer sees simplicity while the complexity is handled behind the scenes.

3 steps for customers. Less scheduling work for Maya.

Built with Lovable for the Lovable Challenge.

Loved how you focused on reducing the work for the for the business owner, not just making the booking page look good. Great concept.

🏢 The Business & The "Greasy Hands" Dilemma: We built DockFlow (Biscayne Marine OS) for Elena "Rico" Rossi, a solo mobile boat engine mechanic operating "Biscayne Mobile Marine" in Miami, Florida. Elena drives a mobile workshop van to marinas and canal slips to repair high-performance boat engines (Yamaha, Mercury). But she faced a brutal daily dilemma: The Greasy Hands Barrier: When working, both of her hands are covered in black engine grease inside noisy boat engine compartments. She physically cannot pick up her phone to answer customer calls. The Traffic & No-Show Trap: Over 35% of boat owners would cancel after Elena had already driven 45 minutes across Miami bridge traffic in her work van. Logistics Chaos: Between texting back and forth for marina security gate PINs, boat parking slip numbers, and checking if ocean tides were too shallow to run boat engines, Elena was losing 14+ hours every week just playing phone tag.

⚡ What We Built in Lovable:

We completely rebuilt the moment an inbound customer inquiry turns into a confirmed, paid booking without Elena ever touching her phone:

Marketing Landing Page (/): An executive business homepage with an interactive 3-slide hero carousel explaining the service, problems eliminated, and dockside repair guarantees.

Customer Fast-Track Booking (/book):

Elena's Mission Control (/owner):

Realtime Auto-Healing Waitlist Waterfall:

Miami Localization & Enterprise Polish:

📈 Measurable ROI: ⏱️ 14 Hours Saved Weekly in manual scheduling and phone tag. 🛡️ Zero No-Shows thanks to upfront card deposits. 🚗 2+ Hours Saved Daily in Miami bridge traffic via neighborhood clustering.

🔧 No Wasted Parts Runs with van inventory pre-flight matching. Live App: https://dockflow-biscayne.lovable.app/

Amazing! Love the backstory and a female boat mechanic with greasy hands. Well done.