Terminal

Terminal launched with a deliberately narrow MVP: a single API endpoint aggregating GPS and speeding data from three major telematics providers. ​​‌‌‌‌‌‌‌​‌‌​​‌​​​​​​‌‌​‌‌‌​​​‌‌Raghav and Connor shipped this in eight weeks, having spent their previous roles at a Series B neobank wrestling with fragmented payment and banking APIs. They intentionally excluded vehicle diagnostics, fuel data, and driver behavior analytics—features competitors offered but that required exponentially more provider integrations. This constraint forced early customers to validate the core problem: accessing standardized telematics data across incompatible systems. Within six weeks, two insurance tech startups signed pilot agreements, each reporting they'd previously spent three months building custom integrations. That validation signal—customers willing to pay for a solved integration problem rather than build it themselves—justified the stripped-down approach. The narrow scope also meant Terminal could iterate on API reliability and documentation speed rather than feature breadth. However, this minimalism later created friction when customers demanded vehicle diagnostics; Terminal had to rapidly expand their provider network, delaying some enterprise deals by months.