Back to Home
Case Studyridecrew.rentals

Web App + Automation Pipeline

How we built a headless automated booking sync system for a local rental fleet

Ride Crew is a Columbia, SC based premium vehicle rental fleet. They operate across both private direct bookings and a third-party peer-to-peer rental platform, but that platform locks its API, making calendar sync impossible out of the box. Every confirmation email had to be manually entered. One missed email meant a double-booked car. We fixed that, and added a direct booking channel on top.

0%Platform fee on direct bookings
<800msEnd-to-end pipeline latency
8 carsManaged without manual scheduling
100%Brand-owned customer experience

The Problem

  • No direct booking channel. Customers had to go through a third-party P2P platform even when they found Ride Crew first
  • Every platform confirmation email required a manual calendar entry; a missed email meant a double-booking
  • Two booking streams (direct calls + P2P platform) with no unified calendar; conflicts were a constant risk
  • Generic Carrd.co template: no brand presence, no conversion path, no ownership of the customer relationship

What We Built

  • Direct Booking EngineCustomers can now book privately through the site. No third-party platform required, no fees on those transactions
  • Platform Email ParserSince the P2P platform locks its API, we intercept their confirmation emails, extract the booking data, and auto-block the calendar. Zero manual entry
  • Unified Fleet CalendarBoth direct and platform bookings feed into one live calendar automatically. One source of truth, no conflicts
  • Custom Branded Web AppReact storefront built for conversion and direct customer ownership: fast, on-brand, reservation-ready

The MaD Avenue Approach

When the platform does not open the door, we find another entrance.

Peer-to-peer rental platforms intentionally limit third-party integrations, which is understandable from a security and business perspective. Most agencies see that limitation and stop there. We look for legitimate integration points that are already available: what data is the platform already sending the client? In this case: confirmation emails. Every booking the platform processes sends a structured notification to the fleet owner. We built a parser that reads those emails the moment they land, extracts vehicle, dates, and renter info, and syncs the fleet calendar automatically. We found a legitimate integration point most agencies miss.

This is how we approach every integration challenge: not by bypassing security, but by working with what the platform already exposes to the client. The constraint becomes the brief. The legitimate integration point becomes the feature. And our clients end up with custom infrastructure that fits their workflow without breaking platform rules.

The Results

Numbers that matter

15 min → 2 min

Reservation completion time

From phone-call back-and-forth to instant online booking

40%

Increase in direct bookings

Within the first 60 days of the new site launching

0

Double-bookings since launch

Previously happened 2–3 times per month

100%

Platform emails auto-parsed

Every confirmation email synced to calendar without manual entry

Under the Hood

Two booking channels. One calendar. Zero manual work.

The P2P platform doesn't expose an API. So we built around it.

sync-pipeline.ts

// Channel 1: direct booking via site

on("direct.booking.submitted", async (req) => {

const booking = await parseDirectRequest(req)

await calendar.block(booking.vehicle, booking.dates)

});

 

// Channel 2: P2P platform (no API, parse email instead)

on("email.received", async (msg) => {

if (!isPlatformConfirmation(msg)) return

const booking = await platform.parseEmail(msg)

await calendar.block(booking.vehicle, booking.dates)

});

// 0 double-bookings since launch

Direct bookings via the site

Customers can book privately through ridecrew.rentals. The form submits, the calendar blocks, and a confirmation fires. No third-party platform involved.

The platform workaround

The P2P platform doesn't allow third-party API access. So when their confirmation email arrives, our parser reads it, extracts the vehicle and dates, and auto-blocks the shared calendar.

One unified calendar

Both channels write to the same fleet calendar in real time. There's no gap window where a double-booking can sneak through.

Zero manual entries

What used to be: owner reads email → opens calendar → manually enters booking. Now: email arrives → calendar blocks automatically. Every time.

The Transformation

From generic template to conversion machine

Before
Ride Crew before: generic Carrd template

Generic Carrd template. No brand identity, no booking engine, no direct customer ownership.

After
Ride Crew after: MaD Avenue custom build

Custom React storefront. Direct booking engine, branded experience, unified fleet calendar with automated sync.

Want this for your business?

We build the same custom infrastructure for any industry. No templates. No platform dependency. Just software that works for you.