Build logs · series
Studio Build
Build logs about how Sandcastle Labs itself is built: marketing site, brand voice, infrastructure decisions.
- Audience
- Agentic studios and indie founders
- Rhythm
- Weekly while shipping site or brand work
Arcs that include this series
Posts (16)
-
Is AI visibility only for SaaS companies? No
Engines route on the problem, not the vertical: a local fitness studio went from 0 of 8 to 5 of 8 AI answers in four weeks. In July we still sold to SaaS first. By October our pricing page named four kinds of company. Here is what we can and cannot show about why.
-
How do teams get started with an AI visibility agency?
With us, it starts with a free scan, then a 30-minute call, then a manifesto that opens the 90-day sprint. The scan is proof of the problem. It is not proof that we can fix it, and here is what to ask for instead.
-
Which AI crawlers visit a young site, and what do they read?
Five named AI crawlers made 209 fetches on our site in 30 days. What they read, what we changed, and what to check on yours.
-
How do you find what AI assistants get wrong about your website? Read it the way they do
An assistant reads every page you ever published, old posts included, plus files a buyer never sees. We audited our own site that way on October 13 and found 12 verified problems, nearly all sentences we wrote ourselves. Here is the checklist, the fixes that took a day, and the one step you cannot skip.
-
How an Agent-Native Studio Found Its Own Broken Links
A link-graph sweep of Collimer's 35 guides found 8 orphans, 6 of them the newest, most expensive content on the site.
-
Last Week's Bet Was Tested, and It Held
Last week's post was a decision: split the Chronicle from a second, buyer-facing content pipeline before there was evidence it would work. This week is the evidence.
-
A Pipeline Isn't Built Until Someone Else Runs It
Chase ran our chronicle-and-PR pipeline solo, extended it into new territory, and went back to fix a gap in his own earlier work along the way.
-
An operating scorecard that runs itself
We moved the studio's operating scorecard onto a Neon database and a scheduled tick, and a traffic anomaly proved why that mattered.
-
Warming up a days-old domain: the cheap SEO that compounds
A low-token SEO audit of two days-old sites found a 3-hop redirect, a dateless sitemap, a thin page, and short guide descriptions.
-
The audit right after the rebuild
We rebuilt sandcastlelabs.ai on a new brand system, then audited it the same day and caught a leftover internal codename still live.
-
Running an agent-native studio like a series of small bets
We built the agent-native studio workflow behind our operating plan and scoreboard before hiring anyone, so progress gets measured, not guessed.
-
Lookout: a marketing analytics scorecard that refuses to fabricate trends
We built Lookout, an operator analytics scorecard for both marketing sites. It reads PostHog, assesses what's working with volume-aware confidence, and renders a graph-rich HTML report. Its one design principle: if the numbers are too small to say something real, it says nothing.
-
Minimum viable legal, deferred lawyer
Privacy Policy and Terms for two static marketing sites, built without a lawyer. Here is the threshold we think we hit, and what would change that.
-
Launching Collimer's marketing site in a week
Collimer went from a coming-soon page to a full marketing site in five days. Then we deleted a third of it. That was the right call.
-
We sent back 59KB of react-dom for a hamburger menu
Astro 6, Tailwind v4, Motion, PostHog reverse-proxied through Vercel, and a three-package monorepo underneath. Every piece has one line of defense. Here is what it is.
-
Week one: V1 of the site, and the parts that are not done
What shipped in week one of sandcastlelabs.ai: aurora hero, mobile nav, brand tokens, PostHog A/B. And the parts we left visibly unfinished on purpose.