Notes on building, from inside the work.
How we think about the studio, plus the founder's writing on product, AI, and the operating models behind companies that actually ship.
Notes from Crossroads.
Why we build at the Crossroads of America
Indiana is the Crossroads of America — and we build here on purpose. The idea that great software only comes from a few coastal zip codes is a habit, not a law.
Building here keeps us close to the operators we actually serve: the restaurants taking delivery orders, the maintenance crews keeping buildings running, the dance studios filling auditoriums on a Saturday. These are the customers most software was never built for — and you understand them better standing in the room than reading a market map from two thousand miles away.
It changes the math, too. A studio can run six companies on what a single coastal seed round burns in a year. That efficiency isn't a constraint — it's what lets us build a portfolio instead of a single bet.
A studio, not a startup
Most teams build one company and pour everything into it. We build many, on a shared engine, and operate them.
AI-native building changed the unit economics of starting up. Work that took a full team a year now takes a small, focused studio months. When the cost of building collapses, the right move isn't one careful bet — it's a portfolio that compounds, where each launch makes the next one faster.
A studio isn't an accelerator (advice) or a fund (capital). It builds. Crossroads originates the idea, ships the product, and runs the company.