ooh is a lightweight platform for turning AI-generated single-page apps into shareable, collaborative team briefs — live at a named URL in seconds, with a built-in overlay for comments and feedback.
When you want to communicate a product idea, a tool concept, or a business model to your team, you have a few bad options: a wall-of-text Notion doc, a PDF no one reads, or a Figma mockup that needs a 30-minute walkthrough. None of them are interactive, none of them are iterable, and none of them make it easy to gather structured feedback.
The best way to communicate an idea is to show it working. AI can now build that in minutes. The missing piece is a place to put it.
Chat with Claude to flesh out an idea → ask it to build a microsite → it publishes directly to a live URL — with a Google Docs-style overlay on top for your team to highlight, comment and suggest changes.
Develop the idea in a back-and-forth with Claude until it’s ready to share.
Claude generates a polished single-page app — any design, any framework.
One MCP call. Files go to R2, slug goes live. No deploy pipeline, no config.
Team annotates inline — highlights, comments, suggestions — on the live page.
Rebuild with feedback, republish as v2. Old versions preserved, annotations intact.
Every publish is immutable. Rollback is instant — just a pointer swap in KV.
Anything that communicates better as an interactive page than a static document.
Interactive explainer of a new tool, feature, or product direction — with live examples embedded.
Working calculators that let the team stress-test assumptions in real time.
Visual system diagrams with interactive layers — far clearer than Miro or a slide.
GTM plans, competitive analysis, investment rationale — scannable and interactive.
Working UI concepts to pressure-test before committing to a full build in Figma.
Interactive charts and dashboards that make a point, not just display numbers.
It was built by Claude in a single conversation and published via the ooh_publish_inline MCP tool — no local filesystem, no deploy step, no manual upload.
Flesh out the idea in claude.ai. Iterate until it’s ready to communicate to the team.
Claude generates a polished single-page app from the conversation context.
MCP tool sends file contents to the ooh API. Uploaded to R2, version created in D1.
ooh.athick.com.au/[slug] — overlay active, ready to share.
Highlights, comments, and suggestions directly on the live page — no screenshots, no separate doc.
Incorporate feedback, publish a new version. Every version is preserved. Rollback is instant.
Everything runs in one Cloudflare Worker. No Pages, no separate services. All microsites handled within the same deployment.
Shipped in order. Each phase is independently useful — Phase 1 alone is enough to start publishing.
Token-based for CLI/API is obvious. Does the overlay need auth? Are comments attributed to named people, or just “the team”?
Per-version is clean, but context is lost on republish. Recommend: per-version, with archived annotations visible in sidebar.
ooh.athick.com.au works for internal use. If this becomes a product, establish a separate identity early — not after.
Worker + R2 platform first (Phase 1), or CLI/MCP tooling first? Phase 1 is the foundation everything else depends on.
Build the Cloudflare Worker with R2 asset serving and the publish API. That unlocks everything — CLI, MCP, overlay, and the SaaS builder all sit on top of it.