Design without approved content is guessing.

Every website project has a phase nobody owns. The sitemap lives in one tool, the copy lives in nine documents, and the client’s approval lives in an email that says “looks great!” about a version nobody can find any more. Then design starts, and all of it gets renegotiated inside Figma comments at three times the cost.

We run an agency. We got tired of paying for that phase twice — once when we skipped it, and again when it came back as revisions. Lorem ipsum is debt: every placeholder paragraph is a decision postponed to the most expensive possible moment.

The cheapest place to change your mind about a website is before anyone designs it. That phase deserves a proper tool, not a folder.

So Blocky holds the whole phase in one place. The structure is a tree of pages you can drag. Every page is wireframe sections with real words in them — words with an owner, a stage, and a due date. When the words are ready, the client gets a magic link: no password, no seat, no training. They read the site the way visitors will, talk in the same threads as your team, and approve it section by section.

And approval means something here. Every yes is recorded per section, with a name and a timestamp — frozen exactly as approved. If an approved section changes later, it’s flagged and goes back for re-review. Three weeks later, when someone asks “did we agree to this?”, there’s an answer instead of an argument. Sign-off that stands up.

Then the phase ends properly: approved content exports as structured Markdown and JSON — sections in order, statuses intact. Designers start from real words. AI tools like Claude Code can build straight from it. Approved content in, working site out.

That’s the whole pitch. Not a design tool, not a CMS, not a whiteboard — the tool for deciding what the website says, and proving everyone agreed.