Two islands

The analogy he gave the team meeting does the deciding: we’re in the middle of the ocean, “nadie nos va a venir a salvar”, and there are two islands, one apparently richer but farther, one closer where survival starts sooner ▸ 3:47. The far island is the phone menus. Its pain is the most validated thing they own, they lived it themselves all week, menus that feel designed on purpose to give bad service ▸ 5:50, bad enough that one wrong maze makes customers cancel the underlying service ▸ 6:08. But reaching it requires a salesperson knocking on corporate doors and climbing hierarchies to whoever owns the phone system ▸ 6:42. The near island is Piqui: the architecture is already half-built from his earlier work ▸ 4:12, reframed by validation week into a CRM for the small, hyper-personal places where the owner is the system ▸ 4:46, and a restaurant owner can be sold to directly, even by word of mouth ▸ 7:01.

no se escoge la isla más rica; se escoge la que alcanzas a nado →

A Friday validation fail sharpened the segmentation. A restaurant they took for a neighborhood spot turned out to be an 11-location chain, and the person available was a manager whose honest answer was that he has no problems: “ya todo está estandarizado acá”, anything unusual gets escalated ▸ 15:58. Managers execute a system someone else owns; only owners feel the pains worth paying to remove ▸ 16:22. And one artifact from that visit sketches the roadmap anyway: the chain’s table-map software runs on rented point-of-sale hardware, slow machines with maintenance contracts like internet modems, and he can’t understand why none of it just runs on a phone ▸ 17:33, which is exactly the cheap end Piqui could enter from, the restaurant that’s just starting and can’t buy machines ▸ 18:21…