When Signal Labs came to us with a deadline and a vision, the scope was ambitious by any measure. A full marketing site for an AI company — one with deeply technical content, a headless CMS, meeting scheduling tied to HubSpot, animated data visualizations, a white paper viewer, a blog engine, a glossary, an FAQ, and a page that reads more like a long-form manifesto than a landing page. Two engineers. Two weeks.
We shipped it. Here’s what it actually looked like.
Table of Contents
The Challenge
Building Attention Infrastructure
Signal Labs is building what they call SignalOS — attention infrastructure for institutions. The thesis, articulated by Rajeev Ronanki in their white paper *Attention for Institutions: The Economics of Signals and the Architecture Required to Act in Time*, is that the fundamental problem facing modern organizations isn’t a lack of data or intelligence. It’s the absence of architecture that converts ambient organizational awareness into timely, coherent action.
It’s a dense, rigorous idea. The website had to do it justice — and make it compelling.
The Tech Stack
Putting the Pieces Together
Before getting into the process, here’s what we actually built on:
| Layer | Technology |
|---|---|
| Framework | Next.js 16 (App Router) |
| Language | TypeScript 5.5 |
| UI | React 19 |
| Styling | Tailwind CSS + Styled Components |
| Animations | Motion |
| CMS | Sanity 5 with typed queries |
| Icons | Lucide React |
| Scheduling | HubSpot API + react-day-picker |
| Video | hls.js |
| Auth/Tokens | jose (JWT) |
| CI/CD | GitHub Actions on Node 24 |
Nothing exotic. But the *volume* of what needed to be wired together — CMS schemas, API routes, SEO configuration, dynamic routing, mobile responsiveness across distinct pages — is where complexity compounds fast.