How This Site Is Generated
Notion in,
AI rewrites the site.
All our company info lives in Notion. From there, AI writes the diff; humans review and merge. A semi-automated corporate site.
01 / Why
Most sites peak right after launch.
New cases, new titles, new awards — corporate sites rarely keep up. Every update needs a designer and an engineer, so most companies end up showing "themselves from a year ago."
no plan started by rewriting the company itself into an AI-native structure. Project notes, meeting minutes, case studies, member updates — all consolidated in Notion. From that single source, AI drafts. Humans review. We ship.
Conventional Site
- Updated by
- Designer + engineer
- Freshness
- A year out of date
- Entry point
- CMS editor
- Maintenance
- Recurring cost
no plan's Site
- Updated by
- AI drafts, humans approve
- Freshness
- Moves with each project
- Entry point
- The Notion / Slack we already use
- Maintenance
- Much lower
02 / How
Primary sources → AI → Site, in three steps.
01 / Source
Primary Sources
Notion-first. Logs, notes, and articles already created by everyday work — used as the input.
02 / AI
AI Agents
Read primary sources via MCP and rewrite them in the site's voice.
03 / Site
Site
Diffs land as PRs → preview → review → merge.
Instead of humans typing while AI assists, we run AI typing while humans approve. The order is reversed.
03 / AI Skills
Multiple AIs split the work inside this site.
Rather than one AI writing everything, we split into role-specific skills. Each one reads its corresponding primary source and rewrites only its corresponding surface.
- Skill 01 jisseki-copy-ai
Case-Study Copy AI — drafts the Works page
Bundles meeting notes, Slack, PR Times, media coverage, and social posts, and writes a 5-chapter body — Challenge → Approach → Tech & Ethics → Facts & Resonance → Behind the Scenes. "No self-praise adjectives." "No fabricated anecdotes." Only drafts that pass an 8-point check against the reference case move to review.
- Input
- Notes / Slack / PR Times / Media / SNS
- Process
- 5-chapter rebuild / 8-point review
- Output
- Markdown for
/works/<slug>
- Skill 02 np-corp-update
Site Update Skill — from "update the site" to a PR
Say "update the site" in Slack. The AI branches, edits, opens a PR, and shares the preview URL. Humans look at the PR + preview, then merge.
- Input
- Slack update request / meeting notes / PR Times
- Process
- Branch → PR → preview → review → ship
- Output
- GitHub PR + Cloudflare preview URL
Member-profile sync and news / award ingestion still run by hand. They're next on the skill roadmap.
04 / Outcomes
Days became hours.
- From meeting notes and Slack, AI drafts each Works page in 5 chapters.
- One "update the site" in Slack spins up a PR and a preview URL.
- A member's Slack feedback becomes a diff PR in minutes.
- What took days by hand now takes hours: AI drafts, humans approve.
05 / Stack
The stack.
Sources
Notion-first. Where primary sources already live.
AI Layer
Agents that read primary sources and rewrite for the site
Site / Build
Layer that delivers diffs to production
Skills (built by no plan)
AI skills running inside this site, built in-house
06 / Open to Dig
The whole approach is one of our products.
Built for no plan's own site, but designed to drop straight into client projects. The structure — AI rewriting the site from project info — is itself one of our products.
Want to rewrite your own corporate site to be AI-native, or design AI-driven internal operations? Reach out.