Brand New Colors ← All reports

This is a Business Nervous System report — the core deliverable of the Foundation. The Foundation produces this kind of document for your business, scoped to what it actually needs.

Business Nervous System Report
Ridgeline Charter Group

Six drivers. Forty events a month.
One person holds it together.

IndustryPrivate Event Transportation
Revenue~$1.4M
Team9 (owner + 6 drivers + 2 admin)
Operating7 years
Report DateApril 2026
Section I

Business nervous system diagnosis

Sensing
Absent
Vehicle utilization, driver availability, booking lead time, and seasonal demand sit untracked in any format that supports planning. The owner reads the next two weeks because they personally manage the bookings; past that window the picture goes dark. The business cannot see itself at a distance.
Signaling
Degraded
Drivers reach the owner directly by text, with no shared channel, no standard pre-event briefing, and no post-event report. Every on-the-road problem routes to one person who is the only one positioned to act on it. Admin staff run bookings and billing but stay outside the driver loop, so day-of issues still wait on the owner.
Processing
Degraded
Event logistics hold up at normal volume and compress under concurrent demand. Three events on a football Saturday squeeze the owner’s coordination bandwidth, and prep quality slips across all of them. A second processing tier — a dispatcher, or a lead driver with coordination authority — would carry that load; today every event-day decision flows through one point regardless of volume.
Deciding
Absent
Drivers carry no documented authority over anything touching the client experience or the firm’s liability. A last-minute pickup change, a mechanical issue mid-route, an intoxicated client requesting an unplanned stop — each routes to the owner, and each has a correct, repeatable answer that lives only in the owner’s head. The owner is the real-time decision layer for a fleet spread across a 30-mile radius.
Regulating
Absent
Seasonal spikes — football season, Greek formals, graduation weekend — are known months ahead yet go unplanned structurally. Driver schedules are built late, and booking availability stays open past real capacity, so the business learns it is overbooked only once it already is. Maintenance follows the same reactive pattern, with vehicles serviced after a failure rather than ahead of peak season.
Section II

Primary structural failure mode

On the busiest days the owner is the dispatcher, the sales desk, the conflict resolver, and the capacity manager at once — four roles competing for one person’s attention exactly when each is needed most. A football Saturday with four concurrent runs is the predictable failure point of a business that grew its revenue ahead of its structure.

The owner is competent and the drivers are experienced; the gap is architectural. An operating model built for three vehicles and two drivers has carried a tripled business without a structural update. What held implicitly at $400K strains at $1.4M, and the strain shows at the moments of highest demand, which are also the moments of highest revenue.

The business runs on my presence and judgment. I am the system, and I can feel it.

That reading is accurate, and the question is where to start. The answer holds across businesses: begin where the system fails most visibly, most predictably, and most expensively. Here that is peak-event scheduling.

Pricing is the second leak. Every event is priced about the same regardless of demand, lead time, or complexity, while the market would carry a 25–40% premium on peak dates. The premium goes uncaptured because no pricing rule encodes demand.

Section III

Where the margin is leaking

Last-minute bookings drive overtime and routing inefficiency that erode margin on otherwise profitable events. Events confirmed inside 48 hours force reactive reassignment, which often means overtime or calling in an unscheduled driver. That cost lands as a general operating expense and never traces back to the booking that caused it. Same-week bookings should carry a premium and currently do not.

Peak-date pricing stays flat while demand justifies 30–40% above standard rates. Football Saturdays, Greek formal weekends, and graduation are capacity-constrained by definition: vehicles and drivers are finite and demand reliably outruns supply. A client booking homecoming six weeks out pays the same rate as a Tuesday corporate dinner.

Vehicle maintenance costs swing because maintenance is reactive. At least one vehicle needed emergency service during an active booking window in the last year — a substitute vehicle, a client reimbursement, and a repair bill landing together. A maintenance calendar by vehicle, tied to mileage and season, turns unpredictable large costs into predictable small ones.

Section IV

Decision and escalation map

The owner is the terminal point for every decision above “drive to the pickup.” Drivers are skilled with clients but work without a decision framework, so their working rule is to call the owner whenever a situation is uncertain. That default made sense at a smaller size and now strains under current volume.

Most driver escalations land in four buckets: a route change requested day-of, a vehicle issue that may or may not abort the run, client behavior that may or may not breach policy, and a timing slip that cascades into the next booking. Each carries a correct answer that lives only in conversation.

Admin owns bookings and invoicing but has no view of the operational schedule. When a client modifies a confirmed event, admin updates the booking system without seeing whether the change collides with a driver or vehicle. The owner catches those collisions during prep, if at all.

Section V

The structural moves

1
Build a 30-day rolling master event calendar with driver and vehicle assignments locked two weeks out — visible to drivers and admin, not only the owner.
The schedule lives in two disconnected places today: the owner’s head and the booking system. Pull it into one shared, visible format — event, date and time, vehicle, driver, client contact, pickup. A shared sheet or Google Calendar covers it. The two-week lock means changes inside that window need owner approval, which stops admin from quietly creating conflicts. In 30 days: every event in the coming month carries a named driver and vehicle, and the owner fields no scheduling question already answered on the calendar.
2
Write the driver authority matrix — five situations, five rules, laminated in every vehicle.
Spell out what a driver settles without calling: a route change under 15 added minutes — approve; one unplanned stop under 10 minutes — approve and log; an intoxicated, disruptive client — pull over and call admin; a vehicle warning light — check against a defined list before calling; a timing slip into the next run — contact the next client directly from the run sheet. Laminate it and keep it in the vehicle.
3
Set peak-date pricing on a published surge calendar — applied to every new booking immediately.
Name the 12–15 peak dates across the next year — home football games, Greek formal weekends, graduation, homecoming, New Year’s Eve — and attach a 1.3x to 1.5x multiplier. Update the booking confirmation template and hold the rate without negotiation. Margin widens on the highest-demand events, and price-sensitive clients self-select out, freeing capacity for full-rate work. In 30 days: the surge calendar is live internally and the next peak event books at the new rate.
Section VI

What this business is ready for

Ready now
The shared event calendar, the driver authority matrix, and the surge-pricing structure. Each goes in this month without a new tool or a new hire. They turn decisions made on the fly into decisions made once and written down, so drivers gain clarity and admin stops making changes that create invisible conflicts.
90 days
A named lead-driver role — one experienced driver with explicit authority to coordinate day-of logistics across concurrent events. This formalizes something likely already happening informally; a defined scope and a modest rate premium create a second tier of operational decisions and ease the owner’s event-day load.
Not yet
A transportation-management or dispatch platform. The scheduling model these tools assume does not exist yet, so buying first means configuring an expensive system around a broken process. Give the shared calendar and driver matrix 60 days to prove out. A second admin hire also waits, since admin’s constraint is visibility rather than headcount.

This is what the Foundation produces.

The Foundation reads your business and delivers a report like this one, then leaves you with your books current, a deployed workspace, and a compliance calendar. It starts with a 20-minute fit call.

Book a 20-minute fit call → Start with the Foundation