When Aldus shipped PageMaker in 1985, anyone with a Mac and a laser printer could produce something that looked, at first glance, professional. What followed was less the explosion of beautiful documents the marketing promised, and more an explosion of badly designed ones. Newsletters in twelve typefaces. Memos with clip art. Annual reports where every heading was a different colour. The cost of producing a page had vanished. The judgment required to produce a good one had not been distributed alongside the licence.
The vibe-coding stack is the PageMaker moment for software.
The Gap That Opened
A founder today is not short on ideas. They are not short on tools to build the idea. They are not short on tools to make it look credible. Cursor and Claude Code, Lovable, v0, Bolt, Figma Make, Supabase, Vercel: three layers that used to be expensive have become cheap in months.
What this exposes is the work between the idea and the build. Who is this for. What does success look like. What are the trade-offs. What might break. What needs to be left out. What are the failure modes the idea is going to walk into without realising. Builds were so expensive, for so long, that nobody could afford to build the wrong thing, and that economic pressure imposed a discipline on the layer above. When the build became cheap, the discipline disappeared with it. Founders now ship the idea straight into the build, skipping the middle, and the result lands somewhere on the spectrum between “looks right but does not work” and “works in the demo but fails in production.”
The Reddit threads have a name for the failure mode: the spaghetti loop. Two months in, the founder has shipped twenty versions and learned almost nothing about whether anyone wants what they are building. The cost of being wrong did not vanish. It moved. It now shows up in time, in attention, and in the steadily growing market for what is being called rescue engineering.
The hard part, it turns out, was never the build. It was the work between the idea and the build.
What the Hard Part Looks Like
The hard part has four faces, and most founders touch one or two of them and assume they have covered the territory.
Strategy: who is this for, what does success look like for them, what does it have to do exceptionally well, what can it afford to do badly. Pathways: the order in which features get assembled into a journey from arrival to value, which AI tools do not produce because the prompt rarely specifies it. Engineering judgment: the failure modes nobody listed, the edge cases that show up in week three, the trade-offs between speed and reliability and cost that cannot be retrofitted. And underneath all three, the surfacing of things the founder did not know to think about. The unknown unknowns. The questions that should have been asked.
That last face is the most defensible piece of the territory, because it is the only one nobody else is offering. Strategy templates exist. Pathway frameworks exist. Engineering checklists exist. What does not exist, anywhere in the current stack, is something that contributes the patterns, risks, and capabilities a founder did not bring to the conversation.
The Layer Above the Build
None of this is a critique of the build layer. v0 and Lovable, Cursor and Claude Code, Bolt and Figma Make have done their job. The next problem is the one their success exposed. The middle layer was always the harder part. It is now the only part that is left.
Producing the artefact for that middle layer is the kind of work Zynkex is built for. The build is the downstream artefact. The strategy, the pathways, the engineering judgment, and the unknown unknowns are the upstream context that decides whether the build is worth doing.
A Zynkex session does not transcribe what you bring. It challenges it. Every turn surfaces something you did not bring: a pattern from a comparable product, a failure mode you had not considered, a question that exposes an assumption you had not noticed. What comes out is a Strategy Plan with a prominent Decision Log capturing every call made and why, plus a Build Brief any of the build tools above can consume directly. The middle layer that used to live in the head of a senior strategist a founder could not afford to hire now runs as one session, priced at $99.
The build is the easy half now. The thinking that decides whether the build is worth doing is the hard half. That work used to be forced by the cost of typing. It has to be installed deliberately now that the typing is free, and that is where the next decade of product value sits.
