Scaffolds

A website-planning product: sitemaps, page structures, wireframes, requirements and implementation plans in one model of a site.

Ownership

  • StatedHis own product, originated and run through Merlin Studio. Not Tonic's or any client's.

Stage

  • DocumentedLive and on sale at scaffolds.design (free for one project, paid Pro and enterprise tiers).

Origin

  • StatedRepeated first-hand exposure to the same workflow across many large website programmes: briefs kept turning into the same sitemaps, wireframes, requirements and plans. It began as the tool he needed for that consulting work.
  • StatedHe uses it in client work: wireframe sets for several Tonic engagements (Baker Hughes, Imperial Brands, Open Society Foundations) were built in it.

His role

  • StatedDesigned and built it end to end (Next.js, Firestore, Postgres, Stripe, an MCP server with OAuth). The repository was not reviewed for this record; the stack is as Merlin's page states it.

Decisions

  • StatedNo model inside the product. Instead, people connect the AI they already use (Claude, ChatGPT, Gemini or an editor) through MCP, so the product is the structure and the AI is the user's.

What this demonstrates

  • InferenceThe clearest instance of productisation: solve the instance (each brief) → recognise the pattern → understand the category (website planning) → build something that addresses the category.
Full case study on Merlin Studio ↗Product ↗Fullest account: merlinstudio.io/ventures/scaffolds

Each line is labelled by the evidence behind it. Documented: checkable in code, a live product or a primary artefact. Stated: his own account. Attributed: a wider team's or client's. Inference: a reading of the evidence, not a fact. Unknown: not established. No outcome or metric is documented for any of this work. The same record is published for AI assistants at /llms-full.txt.