Skip to main content
Back to Work

Site, dashboard, CMS — one sprint.

4

repos shipped

Sprint · 8-week build · ongoing · 2025

cambrian.org

The Problem

Cambrian Network is decentralized financial intelligence for autonomous AI agents. The launch story has to land before the protocol does. Cambrian had a launch window measured in weeks, not quarters.

A working go-to-market needed four things at once. A marketing site that did justice to the technical depth. A dashboard for API key issuance and Stripe-backed plan management. A CMS so the team could ship content without engineering on the loop. And cross-browser transparent video for the hero — Safari requires HEVC with alpha, the rest of the world wants WebM.

The Approach

Fixed-scope sprint with a focused team running parallel tracks. Built marketing site and dashboard side-by-side with a shared design system and feature parity (blog, pricing, auth on both). Set up the CMS once, modeled content with Article / Author / Category / Global / About, then handed off. 2 commits, then it ran itself.

Marketing pitches the protocol with a hero that runs in every browser — Safari included. The dashboard issues API keys and bills against Stripe plans on day one. The content team publishes from the CMS without an engineer in the loop. Underneath: Next.js 15, Clerk auth with signed Svix webhooks, Drizzle on Postgres, Strapi 5 on Strapi Cloud.

The Outcome

8wk
build window
3
surfaces (marketing, dashboard, CMS)
2 commits
to hand off the CMS

4 repos in scopeshipped in 1 sprint

2 production Next.js apps on Vercel and 1 Strapi instance on Strapi Cloud, all live. Pre-launch waitlist, full Stripe checkout, and a blog the content team publishes to without engineering on the loop. The CMS handoff stuck — 2 commits, then no engineer has touched it.

Start a similar project.

Talk to us