The pre-Figma ideation landscape: where teams design before they design
Most product teams in 2026 spend more time on the work *before* a Figma file exists than on the file itself. The brief gets written in Notion, debated in Slack, sketched on a whiteboard, re-sketched in a wireframing tool, copied into Figma, and only then refined into something pixel-correct. By the time the designer opens Figma, three weeks of compounding ambiguity are already baked into the decision. The Figma file ends up being a downstream artifact of choices that were made — or avoided — somewhere else. That somewhere else is its own category now. Calling it "ideation" undersells how operationally heavy it is. It's where the actual shape of the product gets decided. And it's where AI-coder workflows have made the cost of getting it wrong measurable in tokens: every ambiguity you carry into Cursor or Claude Code costs you thousands of refactor turns. The pre-Figma stack matters because the stuff that happens in it determines what your engineering team builds, how fast, and how often it's the wrong thing. This is a map of that stack as of mid-2026. ## Why this category is having a moment Three things shifted at once and made the pre-Figma work go from "PM problem" to "actual tool category." **AI coding assistants made ambiguity expensive.** A vague brief used to cost you a few designer hours. Now it costs you Cursor and Claude Code generating the wrong app, you reviewing it, prompting again, generating slightly less wrong, and so on. The ratio of design-time-saved to r