What Jason Fried Learned from 26 Years of Building Great Products

Running a company doesn’t thrill me the way making products does, and yes, I’m a watch nerd—today it’s a vintage Heuer from the seventies with a bright orange pop that just feels right on the wrist.

Gorgeous; I’m wearing a Sub I picked up to mark five years, which leads to this—your taste in things like watches and cars shows up in your products, so what’s the overlap?

I draw from non‑software worlds: watches are the same basic form but endlessly interpreted, cars reveal care through ergonomics and tactility, and architecture can feel spiritual; I try to give software that sense of proportion and calm even though it’s just pixels.

What’s the last space that gave you that feeling and why?

A circular meditation building at Esalen in Big Sur—its scale, materials, curves, and setting clicked; I favor honest materials that feel better in person than in photos, which I use as my north star.

It reminds me of Christopher Alexander’s idea that the best spaces emerge from living in them, not drafting them—does that resonate?

Totally; I keep books on handmade houses because non‑architect spaces can have rare soul, even as I love masters like Lautner—some call these places messy, but to me they’re alive.

Let’s bring in AI: we incubate products, each led by one person building for themselves first, which feels like the right moment to create things you actually live in.

That’s great for personal tools, but making for others is different—AI can whip up your own thing fast, yet multi‑user edge cases are where product craft lives; I learned that years ago with FileMaker, which was a similar build‑it‑yourself leap.

Non‑technical folks can prototype, but production takes more; pros using AI can now shape full systems by writing in English, almost like executable pseudocode, and it’s changing how we ship.

Then where are the breakout second‑order products—the non‑AI tools made possible by this wave—given all the talk of spinning up endless agents?

In our case, fifteen people run four apps, each owned by one builder, serving thousands to tens of thousands of users, with revenue in the millions thanks to AI; I think we’re early, and it takes time for orgs to fully switch how they code.

Our team loves hand‑crafting code and uses AI more for learning and boilerplate; I worry about skill atrophy, and I still don’t see the tidal wave of new market‑ready products the hype implies.

Come see what we’re doing—and shifting gears, you’ve been at this twenty‑six years; how have you changed?

I care less about ‘running a business’ and more about building; Basecamp funds our freedom, and if I weren’t here I wouldn’t start another company—also, I used to dismiss luck and now see how much timing and randomness matter.

What was the biggest lucky break?

Graduating as the web took off, learning HTML early, and getting chance connections—meeting David, designing the first Meetup, joining Groupon’s board; even a neighbor’s Mac when I was a kid pulled me into computers.

If you graduated into today’s AI boom, what then?

I’d use whatever tools existed and probably consult, but with natural language lowering barriers, my edge might feel different than when knowing HTML was rare.

I think demand might still be high; personally, this era is a joy—I’m writing and coding across four products with AI and shipping more than ever.

It’s like growing extra limbs, and I lean on AI to learn and smooth clunky writing.

Here’s the selfish part: Every has fifteen people, around one point three million in ARR plus a fast‑growing consulting arm, four AI products, and a media arm that feeds them; we’ve raised very little and want to build an institution—what should I watch for at this inflection point?

It’s normal not to know—keep making it up day by day because you hold the history; at your size, product and operations are one fabric, so don’t split them with a COO unless you truly want someone else to change the shape.

My worst calls came from doing what I thought I ‘should’ do, and growth makes me feel like I need to get serious in that way.

That’s how you end up imitating and destabilizing the core; we’re in an age of sameness, so your edge is being fully yourself—even if that fails, it’s a better failure than copying the playbook.

I learned that when I stopped writing to play CEO and growth flatlined; going back to writing half my time brought the spark back.

The writing is part of the business because the whole is one material; delegate what you no longer love, but protect the work that defines you since unused skills fade.

Where did your ‘it’s all one thing’ view come from?

From complete works—think Frank Lloyd Wright—where swapping a sink or repainting the floor breaks the idea; the best products feel like that, coherent and considered, even if software must adapt to shifting screens and contexts.

I feel that most in writing—like a short story where every line belongs—and sometimes in spaces that feel sacred.

We see fewer fully conceived works now, but that’s still the aim: a whole you can feel, trade‑offs and all.

That’s a perfect place to end—thank you, Jason.

Thanks, Dan—this was a pleasure.

Smash like and subscribe to AI and I for a wild, high‑energy ride into where AI meets real work, with Dan steering the ship.