I'm starting a build-in-public journey, and step one was this site. The brief I gave myself was short: don't claim the positioning, prove it. If the pitch is "SaaS founder who makes AI agents behave", then the site itself has to be evidence.
The concept
I kept coming back to one storytelling site I love — a scroll-driven story where a 3D phoenix carries you through chapters. I wanted that cinematic feel, but a phoenix means nothing to my work. What does mean something: signal over noise.
It's earned, not decorative. Roasproof sells clean conversion signal pulled out of tracking noise. Parsemend turns error noise into merged pull requests. Building in public is the discipline of staying worth hearing through the feed. So instead of a phoenix there's one particle system — 40,000 points, one draw call — living behind the whole page. It starts as static. Then it becomes my face. Then the three products. Then a workflow graph with guardrails. Then a broadcast wave. At the end it collapses into a beacon with my email under it.
The guardrail graph is real
My favorite part is chapter three. The lattice you see behind "I make agents behave" isn't a metaphor — its nodes are the mechanisms that run inside Parsemend in production. Hover them and they introduce themselves:
- a confidence gate — below the threshold, the agent stops and asks a human
- human stopping points — per-project checkpoints an agent cannot cross alone
- draft-PR only — agents never merge; every change arrives as a reviewable PR
I didn't invent those for the website. The website borrowed them from production.
Things almost nobody will notice
- Every word is real DOM text. The canvas is decoration — screen readers, crawlers and reader mode get a normal page.
prefers-reduced-motiongets composed static frames instead of a broken experience.- No WebGL? The site quietly falls back to a plain dark page with a duotone photo.
- The whole thing exports to static files and deploys anywhere that can serve a folder.
Storytelling sites usually sacrifice all of this. Refusing to was the most "guardrails" decision in the project.
How it was built
Honestly: agents wrote most of it. I set the concept and the design system — a palette where color temperature encodes signal strength (cold blues for noise, amber for action), four typefaces with one job each — and then directed an agent fleet through the phases: scaffold, the six-chapter narrative, the WebGL engine, the portrait sampler, the tooltips. Empty repo to what you're scrolling now took about two days.
Stack, for those who ask: Next.js 16, Tailwind v4, GSAP + Lenis for the scroll choreography, React Three Fiber with a custom GLSL morph shader for the Signal.
Numbers so far
- 3 build phases shipped in ~2 days
- 40,000 particles on desktop, 14,000 on mobile, always 1 draw call
- 18 real dated ships backfilled into the ship log
- 0 visitors — the domain isn't even pointed yet
Next
Cloudflare deploy, OG cards, this RSS feed. Then the actual rhythm starts: one ship-log roundup and one note per week — what shipped, what broke, what it cost. If you want the transmissions, the newsletter form is below.