Buildspace

Buildspace was the school that didn't believe in school.

I joined on the founding team and stayed for the run that turned a small Web3 cohort into the biggest builder community in tech. Six seasons of Nights & Weekends, a dozen smaller programs, hundreds of thousands of people who shipped something for the first time because the place existed.

I led design across all of it. The identity, the unicorn, the program brands, the campus, the merch, the OS, the videos, the demo days. Most of what you saw came across my desk and most of it I either made or art-directed.

This page is the meta-case-study. Specific projects get their own pages — start with Nights & Weekends.

The brand problem

Tech education had a brand. It looked like a 2010 textbook. Earnest, blue, full of stock illustrations of people pointing at laptops. The buildspace brand had to be different — not for taste reasons, but because the program was already different. The product was a room full of people obsessed with what they were building. The brand had to feel like that room.

So the design language pulled from the opposite end. Anime. Sticker art. Manga panels. House lore. Wallpapers that looked like album covers. Acceptance packs that opened like games. A unicorn instead of a wordmark.

Build culture, not curriculum.

What surprised me most was how aggressively the brand was adopted by the community. Builders made their own posters. Their own season slide templates. Their own house merch. The wordmark ended up on hundreds of laptops, tattoos, projects, side projects. That's the metric I cared about — not the design system on a Figma page, but the design system in someone else's Github profile.

The voice

The brand was half visual and half written. I led the copy team and crafted the voice. All lowercase. No marketing voice. The emails read like a friend telling you something instead of a brand asking for attention. A builder who later wrote a public love letter to the program described the writing as "no-nonsense, candid, considerate" — close enough to the brief.

Most seasons had their own micro-site too — the main landing page, the acceptance pages, the demo day pages, and the four house sites (spectreseek.com, gaudmire.com, alterok.com, erevald.com). I treated each one less like a marketing page and more like a small zine. They were the first thing a new builder saw, and the easiest surface to make the brand feel like a place instead of a pitch.

What I led

Across the run, I owned or art-directed:

• The buildspace identity — wordmark, color, type system, motion
• The unicorn — origin, evolution, the mark itself
• Nights & Weekends — six seasons, four houses, all season assets. Full case study.
• The campus and event design language
• Acceptance packs and onboarding flows
• The "OS" — the in-program operating system where builders lived
• Posters, stickers, merch, wallpapers, slide templates
• The hiring of the rest of the design team

The parts that didn't have a deliverable

Most of the job didn't ship as a file. The rituals. The in-jokes. The chrome extension that turned a new-tab page into a builder dashboard. The wallpaper someone put on their desktop the morning of demo day. The discord usernames people made out of season references. None of it shows up in a portfolio review because there's nothing to hold up. It was the main work.

The invisible work is what makes a community feel like a place.

What's worth more space

A few things I want to write up properly:

1. The unicorn redesign. How we got from the first sketch to the final mark, and why it works. Coming.
2. The acceptance-pack pattern. Every season had one. They were the thing builders shared most often on day one. I want to break down the design moves that made that happen.
3. The "OS" — operating system as design surface. Most program design lives in marketing. The harder, more interesting work was inside the product — what builders saw when they logged in on Monday. That's where the program actually happened.