KonaWare

A Company That Bet on the Truck Cab

There is a genre of technology company that never becomes a household name and yet turns out to be right about almost everything, and KonaWare belongs to it. Founded in 1999 in Menlo Park - a few years and a few miles from where the smartphone would later be born - it decided that the most interesting place to put enterprise software was not on a desk, but in a delivery truck. This was, at the time, an eccentric position.

The eccentricity is worth dwelling on, because it explains the whole company. In 1999 the phrase "mobile app" did not mean what it means now. Mobile meant a laptop with a modem, or, if you were ambitious, a PDA - a small monochrome slab that could hold your contacts and, on a good day, sync them. The idea that a field worker driving an eighteen-wheeler across Nebraska might run a piece of mission-critical enterprise software on a handheld device, and that the software would keep working when the signal dropped somewhere past the last cell tower, was less a product roadmap than a leap of faith. KonaWare made the leap.

The founders were Jim DiSanto, who ran the company as CEO, along with Gary Portney and Wesley Cheng. Their pitch, translated out of the enterprise-software dialect, was this: your company's most important employee is often the one furthest from a computer. The driver. The technician. The inspector on the loading dock. These people generate the events that the rest of the business is desperate to know about - a package delivered, a repair completed, a truck that failed inspection - and yet, in 1999, they mostly recorded those events on paper, on a clipboard, to be keyed into a system hours or days later by someone else. KonaWare wanted to close that gap to zero.

The Unglamorous Frontier

What KonaWare actually built was two things stacked on top of each other. Underneath was the KonaWare Mobility Platform, a standards-based development and deployment framework - the plumbing that let a company build a mobile application once and run it across a range of devices, from laptops to PDAs to the early smartphones, without rewriting it for each. On top of that platform sat the application suites, which is where the company got specific about its favorite industry. The Mobile Transportation & Logistics Suite handled dispatch, proof-of-delivery, intermodal moves, electronic driver logs, and vehicle inspections. There was asset and shipment tracking for fleet operators. There was a field-service suite for the technicians who fix things in the wild.

None of this is the kind of thing that gets demoed on a stage to applause. It is, however, the kind of thing that a 300-truck freight operation genuinely needs, which turns out to be a better foundation for a business than applause. And the specificity mattered in a subtler way too. A platform that can build "any mobile app" is easy to describe and hard to sell, because the buyer has to imagine the app themselves. KonaWare instead handed logistics companies a suite that already knew what a proof-of-delivery was. The platform was the moat; the suites were the reason anyone signed a check.

The Hard Part Was the Boring Part

If you had to name the single engineering idea that defined KonaWare, it would be an unglamorous phrase: connected or disconnected. The company's applications were built to keep data intact whether or not the device had a network - to let a driver in a dead zone record a delivery, capture a signature, flag an inspection failure, and trust that all of it would reconcile cleanly the moment the truck rolled back into coverage. This is the sort of feature that sounds like a footnote and is, in fact, the entire product. Software that loses a driver's work when the signal drops is software the driver stops using, and once the field worker abandons the tool, the whole promise collapses. Reliability, at KonaWare, was not a feature. It was the strategy.

The company also understood the edge of its own product, which is a rarer discipline than it sounds. Rather than try to become a routing-and-scheduling company as well as a mobile-apps company, KonaWare partnered with ORTEC, a specialist in advanced planning and scheduling, to deliver an end-to-end solution: ORTEC planned the route, KonaWare ran the cab. Knowing what not to build is a form of maturity that plenty of better-funded companies never acquire.

Proof in the Parking Lot

The evidence that this worked shows up not in headlines but in fleet yards. Land Air Express of New England, a less-than-truckload carrier, selected KonaWare's Mobile T&L Suite for something on the order of 200 to 250 units. Dependable Highway Express, a division of Dependable Logistics, put a KonaWare application into a 300-truck LTL operation. These are not billion-dollar logos, and that is precisely the point: a mid-sized carrier trading its clipboards for KonaWare handhelds is a more honest signal of product-market fit than any launch-day fanfare, because that carrier had to actually retrain its drivers and bet its dispatch operation on the thing working.

Being Early Is Indistinguishable From Being Wrong - Until It Isn't

KonaWare raised venture money along the way - its backers included Draper Richards and Western Technology Investment, with a reported round in the neighborhood of $2 million dated to July 2006, and press at the time noting the company was close to securing significant additional capital. This was never a company that raised at frothy valuations or generated splashy funding headlines. It was a company grinding away at a real problem slightly before the market was ready to reward it, which is the oldest and most thankless position in technology. The entire thesis - offline-capable, device-portable, mission-critical mobile software for the people who do physical work - would become conventional wisdom only after Apple and Google turned the smartphone into a platform. KonaWare had the idea; it simply had it before the hardware caught up.

The exit was quiet, as these things often are. In 2008, KonaWare's field-service assets were acquired by ServicePower, a mobile-workforce and field-service management company - the acquisition is recorded as dated March 26, 2008. There was no live-tweeted celebration, no nine-figure number to gawk at. The technology was absorbed into the infrastructure of field service and kept doing its job, which is a genuine, if understated, kind of success. Today the konaware.com domain sits for sale as a "premium" name, the common afterlife of an early-2000s startup whose ideas outlasted its letterhead.

The lesson KonaWare leaves behind is not a tidy inspirational one. It is closer to an observation about markets: the least glamorous corner of an industry - the part still running on paper, the part nobody wants to demo - is frequently the part where the durable business is hiding. KonaWare spent its years on dispatch tickets and driver logs and vehicle inspections while the rest of Silicon Valley chased consumers. It turned out there was a real economy in the things that aren't fun to show off. There still is.