From the outside, L.A. Design & Dev looked like some guy's occasional meetup. It wasn't. It was 5,000 designers and engineers, a jobs channel, a podcast, a newsletter, and events most weeks of the year.

The problem was that all of it lived somewhere different. The founder wanted to charge for membership, which is a hard sell when the only proof you exist is an invite link somebody has to send you.

He designed the site. I built it solo over ten weeks, and shaped the CMS so he could run it without me.

Six scattered efforts, one page

The podcast was on Spotify. The newsletter was on Beehiiv. Jobs and events were Slack channels. Membership was a bare payment link. Every piece was working, and none of them added up to anything a stranger could see.

The homepage puts them in one view. Episodes come straight from Spotify automatically, so a new one appears without anybody touching the site. Events and partners come from the CMS. The newsletter and the paid join flow sit right there on the page. None of this was new material. It already existed, just nowhere you could take it in at once.

That is what made membership sellable. A sponsor or a recruiter lands on one page and sees an organization with a back catalog, not a Slack invite.

Built around how Frank actually runs his business

The founder, Frank, is a designer, not an engineer. If posting an event meant emailing me, the site would have gone stale by March.

So I spent the early part of the project on how he runs the community week to week, before I modeled any content at all. What he posts constantly, what he touches twice a year, what he wants to fix on a Sunday night. The content model came out of those answers rather than out of the page designs.

Events, FAQs, member quotes, partners, the about page, the nav, the footer: all of it is his. He can add a whole new page, and it goes live without a developer touching it.

Built to expand nationally

Design & Dev also runs in San Francisco and New York. We knew that at the start, so the build assumed it instead of treating Los Angeles as the only version.

Nothing specific to LA is written into the code. The copy, the events, the FAQs, the partners, and the navigation all come out of the CMS, so standing up another city is new content and a domain rather than another codebase. That was as much a business decision as a technical one. It makes city two cheap, and it means all three can look like one organization instead of three side projects.

What changed

Membership revenue went from about $2,900 a year at launch to roughly $4,900 six months later, up about 70 percent since the site went live in February 2026. The site is not the only reason; the community was already growing before it, but it is where people join now.

Frank put it better than I would have: It took them from looking like some guy's occasional meetup to looking like something you can charge money for.

How it's built (Tech Stack)

• Next.js 16 and React 19 on Vercel, TypeScript throughout, Tailwind v4 for styling.
• Contentful for every piece of content, with TypeScript types generated from the live content model.
• Podcast episodes come from the Spotify Web API, cached in Redis so the homepage never waits on it and clients can never spam the Spotify endpoint and rack up a huge bill
• Beehiiv handles the newsletter
• Stripe handles membership management and payments.