The landing page is a test suite

The service is “casi casi casi casi” ready ▸ 0:35: terms and privacy pages exist, login shows a project manager, there’s even a logout button. What remains is the landing page, and the decision recorded back in seed 51-1 is now playing out on camera: the landing is being designed inside Divo itself.

Dogfooding immediately starts paying in the currency it always pays: product findings. Juan asks how sections work in the reference tool Julia is copying from; Divo doesn’t have sections yet, so the workaround is improvised aloud, build each section as its own canvas, save them, join them at the end ▸ 8:21. Julia pushes further: she wants one element to straddle two consecutive sections, and Divo can’t do that either. Her verdict is the purest dogfooding sentence in the diary so far: “acá no se puede, pero en el código sí, claro, pero estoy hablando en cámara” ▸ 9:04. She could drop to code, but the whole point of the exercise is to feel what a customer feels.

cada fricción del landing es un ticket del producto →

The same session grows the MVP checklist a third time. Listing what’s left, Julia floats a profile page, and Juan connects it to billing: if someone wants to cancel their subscription, they need a way to do it, so the profile has to ship with the MVP, not after ▸ 9:49.

None of this came from a planning meeting. It came from being your own first user on the most demanding real task available, your own launch page. The landing was supposed to be marketing work; it turned out to be the cheapest QA pass the product will ever get…