// 00
Problem discovered
Solo client work moved quickly, but discovery notes, architecture decisions, and execution plans kept fragmenting across tools.
Why this direction
Build a workspace that captures the problem first, then turns reasoning into architecture and execution artifacts in one flow.
Current progress
Previo is live and still evolving as an internal product experiment shaped by real workflow friction.
Tech Stack
The studio system behind these experiments is quietly documented in /system.
Previo started as an internal response to a recurring problem: solo client work moved fast, but requirements, decisions, and architecture notes kept scattering across documents, chats, and memory.
The goal was simple. Build a workspace that helps capture the problem first, map the system clearly, and turn that thinking into execution-ready work before implementation drifts.
It belongs here because it was born from lived workflow friction, not from a polished product brief. The lab is where tools get pressure-tested before they earn a cleaner product narrative elsewhere.
Some of the interaction rules behind this studio now live in the hidden system page for readers who want to inspect the reasoning, not just the output.
The live product is available at previo.iqbalfr.dev. For the broader catalog of shipped work and writing, visit iqbalfr.dev.