Founder-led management consulting

Luna SolGroupOperator-led transformation
Local site index

What decision are you trying to move?

Suggested starting pointsUse ↑ ↓ and Enter
Curated index · no query leaves this browser
Start a conversation
Luna Sol GroupManagement consulting
Start a conversation →Founder-led · Confidential · Evidence-aware
6-minute case studyConsulting engagement · 2026
HopSkipDrive logoHopSkipDrive

The operating system behind safe, scalable growth.

Connecting dispatch, compliance, risk, technology, and executive control for a rapidly scaling student transportation platform.

Sources checkedOfficial product, expansion, newsroom, and distributed company materials
A HopSkipDrive CareDriver seated in a vehicle
Operating contextPeople, technology, regulation, and live service—moving at once.
30+Metropolitan markets
17Coverage geographies
10Integrated workstreams

Scale could not come at the expense of control.

Rapid national growth required an operating model capable of supporting regulated transportation of minors across multiple U.S. markets—without losing the evidence and escalation discipline needed in live operations.

Role
Senior Operations & Technical Project Manager
Mandate
Design the scalable operating foundation
Operating posture
Safety-critical and compliance-led
Primary deliverable
A deployable operating system

A national footprint multiplies every handoff, exception, and control.

Dispatch, compliance, risk, vendors, incidents, product requirements, and executive governance could not operate as separate workstreams. In a live service involving minors, the operating model had to preserve rider-specific needs and escalation logic across markets.

The engagement treated frontline execution, policy, technology, and executive control as one connected system—not a collection of independent process documents.

Ten workstreams, edited into three operating pillars.

01

Operating architecture

Established the current-state fact base, then designed how dispatch, frontline execution, SOPs, and decision rights should work as one multi-market system.

  • Current-state assessment
  • Enterprise operating model
  • Dispatch workflows
  • SOP library
02

Control and governance

Embedded compliance, incident response, vendor accountability, executive KPIs, and named ownership into the operating cadence.

  • Compliance controls
  • Incident pathways
  • Vendor standards
  • Executive governance
03

Implementation enablement

Translated operating needs into technical requirements, sequenced delivery, and equipped internal teams to carry the system forward.

  • KPI framework
  • Technical requirements
  • Implementation roadmap
  • Knowledge transfer
Explore the 17-geography engagement footprintOpen map +
Map of the United States with HopSkipDrive engagement coverage marked
Selected coverageWashington

Pacific Northwest coverage

Coverage reflects the engagement scope provided by Luna Sol. Base map: CC0 public-domain U.S. map via Wikimedia Commons.

Signature interactive

One control thread across every handoff.

Select a stage to see how customer demand connects to dispatch, CareDrivers, compliance evidence, rider protection, verified completion, and executive visibility.

Active controlStructured intake

Demand enters with rider needs, service commitments, timing, and eligibility requirements.

The output was an implementation-ready control system.

One architectureEnd-to-end operating model

Connected daily execution to enterprise decision-making.

Built inCompliance by design

Placed policy, evidence, and thresholds inside the workflow.

Named controlGovernance and KPIs

Clarified owners, cadence, thresholds, and corrective action.

Ready to sequenceTechnical roadmap

Translated operating needs into implementation requirements.

Evidence boundary: This case describes Ryan Miller’s consulting scope. Company scale, products, expansion, and safety claims are attributed to HopSkipDrive’s public materials; public articles are not presented as validating personal contribution.

Company context, clearly separated from personal-work attribution.

View all 4 checked sources and notesOpen +
Next case study

Maid of the Mist

Moving the guest-planning decision upstream—before the queue.

Read the next case
Selected work

Compare the complete case portfolio.

Review all three engagements with their scope, public context, and attribution boundaries intact.

View all case studies
Start a confidential conversation

Bring the operating decision the current system cannot resolve.

Ryan reviews every inquiry directly and will respond with fit, the evidence needed, and the smallest useful next step.

Start a conversation