David Hodge Is Teaching Fleets to Speak Software

The missing piece in David Hodge's first transportation product was the signal. Underground, where a phone could not ask the internet what came next, a rider still needed to know where to change trains. So Hodge and his friends built the answer into the app. Their early iBart software worked offline, carried the local map, and made a complicated physical system feel briefly legible. It was 2008. Hodge was an undergraduate at the University of Southern California, and much of the company that became Embark lived in a dorm room and in two protected work nights each week.

Nearly two decades later, Hodge is still hunting the missing signal. The physical system is now a fleet of cars, and the dead zone sits between what a modern vehicle already knows and what its operator can actually do. Cars report location, charge, mileage, tire pressure, and warning states. Yet a fleet manager may still install a box, chase a key, reconcile a charging receipt, or open another dashboard. Standard Fleet, where Hodge is founder and CEO, is his attempt to close that distance with software.

The line from subway maps to vehicle APIs is not perfectly straight. It runs through Y Combinator, an Apple acquisition, three years managing engineers in Cupertino, a Tesla owner app, and a set of angel checks tilted toward rockets and satellites. Still, the repeated instinct is visible: find an elaborate transportation network, study its rough edges, then give a person a calmer interface for moving through it.

Build for the tunnel

Hodge arrived at the problem through Apple. In high school he sold laptops and worked the Genius Bar at an Apple Store in Marin County. As a USC student, he attended Apple's Worldwide Developers Conference with his friend Ian Leighton. They spent the summer of 2008 making a Bay Area transit app and released an early version before returning to their respective campuses. People used it. The response was enough to keep going.

Embark eventually made 14 transit apps for cities including New York, Chicago, Washington, San Francisco, and London. The choice to build city by city looked inefficient beside a single universal map. It was also the product. Transit has local grammar: entrances, service changes, rider habits, walking pace. Hodge once explained the challenge through a wonderfully specific question: how fast do New Yorkers walk? Good directions required cleaned data, local observation, user feedback, and design tuned to the place.

“To get really good transit results, what you need is you need to be able to focus on a particular city.”David Hodge on Embark's local approach, 2012

The little details accumulated into traction. Embark joined Y Combinator's Summer 2011 batch. Embark NYC won the Metropolitan Transportation Authority's App Quest grand prize in 2012, selected from 42 submissions. The apps attracted more than half a million users. When Apple removed built-in Google transit directions from iOS 6, Embark's downloads surged. The gap in the platform became the startup's opening.

The acquisition began with misdirection of the benign corporate kind. Hodge visited Apple to pitch an API improvement Embark wanted. He later called the meeting an audition. Negotiations consumed three months and $195,000 in legal bills. The company's comfortable 16-month runway fell to eight. Hodge could not explain the process to friends and family. On closing day, one investor signature remained missing while Apple waited.

The signature arrived. The deal closed for an undisclosed amount. Because the news was still private, the team celebrated in a shed and cleared its office without drawing attention. Years later, Hodge described the sale without varnish: expensive, exhausting, lucky. That candor matters. The polished version is a founder selling to the company he admired since his Apple Store days. The lived version includes tense negotiations and a party no one could see.

Inside the map

Hodge spent the next three years at Apple as an engineering manager. He integrated the Embark team and oversaw a group of roughly 25 people working around Maps. At Embark, a small company had tried to understand each city deeply. At Apple, that transportation experience had to fit inside a product used at a far wider scale. Hodge's personal site is terse about the period, but names one point of pride plainly: Transit.

His education had prepared him for both sides of that assignment. Hodge graduated from USC in 2011 with a degree joining computer science and business administration. He has credited deep computer science training with helping Embark solve problems competitors could not, and group engineering projects with creating a network of peers to learn from and hire. Four of Embark's five co-founders came from USC's engineering school.

The builder streak started earlier. At eight, Hodge constructed a 14-foot Eiffel Tower replica from K'NEX. In high school, he wrote code around GarageBand and converted an old computer into a DVR. These are small biographical objects, but they point in one direction: large system, visible parts, invitation to tinker.

The side project knew

After leaving Apple in 2016, Hodge returned to the scale of a single owner and a single car. Nikola, the app he began operating in 2018, gave Tesla drivers access to trip data, efficiency information, and convenience features beyond Tesla's own app. A 2020 podcast appearance went deep on the technical limits of Tesla's API and on patterns visible across Model S, 3, X, and Y data. The consumer product was also an observatory.

Working with tens of thousands of EV owners exposed a second user hiding behind the first. Businesses were buying connected cars, but their operational software remained tied to the world of aftermarket trackers and manual routines. An individual wanted to understand a drive. A fleet operator needed to understand hundreds or thousands of vehicles, control access, reduce downtime, assign charging costs, and act on an alert. The data source was similar. The job was larger.

Hodge framed the motivation around adoption. Businesses wanted electric vehicles, he argued, and better tools could make those vehicles easier and more profitable to operate. In 2022, as Standard Fleet came into public view, he made the long-term bet direct: “All vehicle fleets in time will be electric. It's just a matter of time.” The market has since offered a practical complication. A fleet rarely changes all at once.

The future arrived mixed

Standard Fleet began around electric vehicles, then widened to the fleet that operators actually own: EVs, hybrids, and internal-combustion vehicles from many manufacturers. The platform now supports more than 30 automaker brands. It can pull more than 1,000 vehicle data points into a common interface, while integrating third-party hardware for older cars that lack embedded connectivity. The phrase “OEM-agnostic” is technical shorthand for a very human request: please do not make the operator learn a different language for every badge in the parking lot.

The product brings telematics, digital access, and payments together. Location and vehicle-health data make the fleet visible. Digital Key lets an operator grant, schedule, or revoke access through a phone without a physical handoff. Payment tools can connect usage with charges for rentals, tolls, or EV charging. In September 2025, Standard Fleet said its digital keys had powered more than 75,000 trips, including use by DriveWhip across a fleet of more than 2,500 vehicles.

“Our platform connects directly to the vehicle itself, so operators can scale faster, control access in real time, and streamline operations across diverse vehicle types.”David Hodge, September 2025

That month, Standard Fleet announced a $13 million Series A led by Nova Threshold, with participation from WEX Venture Capital, SNR, Garry Tan, Salil Deshpande, and Apoorv Bhargava. Returning investors included Burst Capital, Canvas Ventures, Liquid 2, Night Capital, Olive Capital, UP2398, and Danny Wen. Together with its 2023 seed round, the financing brought disclosed funding to $20 million.

Money gives the company room. It does not simplify the underlying puzzle. Vehicle makers expose different capabilities, policies, and data. Fleets contain old and new cars. A rental operator values fast turnover; an insurer may care about off-trip data; a government fleet has its own controls. Hodge's city-by-city lesson returns in a new form. A universal layer only works when its makers respect the differences underneath it.

A builder with orbit

Hodge's interests extend above the road. He calls himself a space enthusiast and maintains SatRadar, a side project for following satellites. His personal investment list leans into ambitious machinery: Relativity Space, Astranis, REGENT, Inversion, AstroForge, Charge Robotics, and others, alongside software companies such as Fly.io and Taro. Several early bets were later acquired. He lists the shut-down companies, too, another small sign of an unsentimental record.

The connection is less about sectors than interfaces. A satellite is remote, fast-moving, and mostly invisible without data. So is a vehicle spread across a fleet. So is a train somewhere in a tunnel. Hodge keeps returning to systems that are hard to see from the user's position, then builds a window.

Standard Fleet's current ambition is to become a common software layer for connected vehicle operations. The company says it connects more than 100,000 vehicles. In 2026 it continued publishing the practical case for hardware-free telematics, seven-day OEM onboarding, and digital keys that replace counter lines and lockboxes. Hodge has also been recruiting engineers to bring consumer-grade software expectations into fleet work, a corner of business technology where usefulness is often measured in hours avoided.

There is a temptation to read his career backward from Apple: the dorm-room project was destined for Cupertino, and everything since has benefited from the credential. His own acquisition story resists that tidy arc. Embark could have spent its runway on a negotiation that failed. Standard Fleet began not as a grand fleet thesis but as an experiment in connected vehicle software. Nikola found an audience before it found a larger market.

The more practical reading is about attention. Hodge noticed that an underground rider could not fetch the next instruction. He noticed that generic transit results missed local behavior. He noticed that connected cars had already become useful computers while fleet software still began with a box in the mail. Each observation was modest enough to test, then broad enough to become a company.

A fleet is not elegant. It is a row of assets, each with a key, a driver, a payment, a battery or fuel tank, a maintenance schedule, and a different manufacturer's idea of connectivity. The elegance has to come from the layer above. David Hodge has been rehearsing that layer since the tunnel.