Hotels, resorts, planned communities and campus shuttle programs move people and have to prove it to a board, a GM or a student government. 761 grew out of a shuttle company, so we build the rider pages, the live ride dashboards and the operating software from experience, not from a brief.
Ride counts live in one system, wait times in another, and someone pastes them into a deck once a month. By the time the board sees it, the numbers are stale.
The hours, the stops and how to request a ride are in a PDF at the front desk. Guests ask the valet, who guesses.
A scheduling spreadsheet, a group text, a vehicle checklist on paper, applicant emails in an inbox. The manager spends the morning stitching them together.
A property or a city evaluating a shuttle program gets a 30 page PDF with pricing buried on page 22. Nobody reads it, and nobody can share it.
Rides, wait times, busiest hours and stops on a page the client opens on a phone, updated from your ride data without anyone pasting numbers. We built these for FSU Safe Ride and CatawbaGO.
Guest and rider facing pagesA page that says how the shuttle works: hours, stops, how to request a ride, with the app links and a map. Built for a phone held by someone standing at a curb.
An operating hubOne login for schedule, drivers, vehicles, inspections, hiring and support tickets. Replaces the spreadsheet, the group text and the paper checklist with one place managers actually open.
Driver and inspection appsA pre shift and post shift walkaround app with photos and incident documentation, so the vehicle condition record exists before anyone asks for it.
Pitch sites instead of PDFsA proposal that is a website: the route, the fleet, the pricing structure and the dashboard preview, shareable with a link and readable on a phone. Built for a specific property or program.
These are the searches the site is built to answer, one page each.
Yes. 761 grew out of Slidr, an electric shuttle company that has served universities, hotels and planned communities since 2016. The ride dashboards for FSU Safe Ride and CatawbaGO, the hotel shuttle at Cove Inn in Naples and the community shuttle at Tradition in Port St. Lucie all run on software we built for ourselves first.
From the ride data your operation already produces, pulled on a schedule into a page you own. Nobody exports a spreadsheet. The page shows rides, wait times, busiest hours and top stops, and it is designed to be read on a phone by a GM or a dean, not by an analyst.
Yes. The guest facing page, the booking flow and the reporting work whether the vehicles are yours or a partner's. If you are evaluating a shuttle program, we can also build the pitch site that lays out the route, the fleet and the structure so your ownership group can see it on a phone.
The scheduling spreadsheet, the driver group text, the paper vehicle checklist, the applicant inbox and the support emails. One login, with managers seeing their own locations and admins seeing everything. It is the system we run our own shuttle company on, rebuilt for each client.
Start a two minute intake and tell us about the property or the program. We will reply within a business day.
Why a monthly PDF dies in the inbox and a dashboard gets bookmarked: period filters, a KPI row, charts you can hover, a searchable log and a map, in that order.
DesignWhy we pitch hotels, resorts and builders with a private website branded to the prospect, with their logo, colors and a live demo, instead of a PDF proposal.
Running itWhat an operating hub replaces for a company with an office and field crews: scheduling, time off, inspections, handbook, recruiting, support, CRM, a daily brief.