Research & Insights
Meet the team
The complete organization chart of the Lexy platform, where the roles the founder once staffed with a real newsroom are now seats held by software.
One newsroom, every surface
Lexy launched on Alexa without changing the newsroom's routine, because the architecture makes every new platform a rendering problem instead of a rebuild.
Press one to continue
Voice 1.0 ran on IVR and the dial pad. Everyone hated the menus, but the reach of a plain phone call was the idea that never stopped being true.
The assistant in your pocket
Siri made talking to machines ordinary and put a microphone in two billion pockets. Voice 2.0 built the habit, but not the conversation.
The room becomes an interface
Smart speakers proved people want conversational audio in their routine, and that a voice product is only as durable as the platform underneath it.
Punctuation you can hear
Audio has no typography. How a four-note violin phrase, a one-second beat, and a spoken transition became the punctuation system of the Lexy news brief.
Eliminating race conditions with a single integer
The browser was a state machine fighting the phone call. We fixed it by turning it into a display terminal.
Teaching a browser to detect walking, running, and driving
A locomotion classifier in 200 lines of JavaScript so a trivia game could tell you to put down your phone.
An experiment in unartificial intelligence
Nine years between the theory and the proof. The browser finally caught up to the idea.
One table, seven content types, four languages
The old system stored voice scripts across four tables and eight switch blocks. The new system is one table, two functions, and an INSERT statement.
Word-level karaoke sync at 50 milliseconds
On desktop the timing is perfect. On mobile it is early. An 8-line fix to a fundamental assumption about browser audio APIs.
Rendering multilingual cover art with Java2D inside ColdFusion
ColdFusion ImageDrawText produces garbled Arabic. Java2D renders it perfectly from the same server-side file.
578 strings, 4 languages, zero deploys
Most localization systems require a build step. Ours requires a database insert.
The Walmart greeter problem: GPT before keywords
Keyword matching is like reading aisle signs. GPT is like asking someone who knows every product in the store.
The end of the minimum viable team
For fifty years, building a product meant building an organization first. AI tools collapsed that barrier. The founder who understands the problem can now build the solution directly.
E pluribus unum
The phrase chosen in 1782 to describe a nation now describes what one builder with an orchestrated stack of tools can do.
The invisible interface
Twenty years of building voice products, from feature phone audio to sensor-driven apps, led to one conclusion: the best interface is the one that disappears.
Twenty years to one phone call
From feature phone audio publishing in 2004 to IVR citizen journalism to sensor-driven apps, every product was a fragment. Lexy is the assembly.