The Problem
Arity’s core business was built on insurance risk models. Partners in consumer finance and home safety needed to see what connected-vehicle data looked like inside their own apps. How would the data manifest as insights that add value? My objective was to show the value as an interactive experience rather than static slideware.
The Approach
I designed for Mobile Publishing and served as a design partner to the sales, marketing, and GTM teams. The SDK work solved for problems around consent and permissions, as well as embedding solutions such as crash detection, driver coaching, and predictive mobility marketing offers within existing partner experiences. These solutions were driven through a customized three-stage path from wireframes to branded examples to coded assets.
The Method
The pipeline started with an internal enterprise knowledge layer — strategy documents, raw telemetry definitions, domain context — fed into frontier LLMs to generate the product framing and initial interaction logic. Figma Make supplied visual starting points. Cursor handled the build: data integration, mapping APIs, functional interaction, and iterative refinement against real feedback from product and sales. The first working prototype took roughly two weeks. Major revisions landed in about ten days after that.
In addition to the SDK work, I applied this method to two other domains: a regional traffic-intelligence prototype for public-sector customers, and a trade-area intelligence prototype built on road-level movement patterns. Six-plus functional iterations in sixty days — working software the team could stress-test, not decks they had to imagine.
The Outcome
Three SDK partnerships closed during my tenure — Experian, Alarm.com/ADT, and SiriusXM — representing 196M+ potential monthly active users across consumer finance, connected home, and in-car audio — with solutions spanning crash detection, driver coaching, and predictive mobility marketing. The prototyping method changed how the organization sold: instead of walking a prospect through a slide deck and asking them to imagine the integration, we put working software in front of them and let them react. Sales cycles shortened. Internal alignment happened faster because product, engineering, and analytics were all looking at the same functional artifact. And the method itself spread — other teams adopted the pipeline after seeing what it produced.


