You Really Need Teammates to Talk About This

My wife said that last Wednesday.

I had walked into the kitchen in the evening and immediately started brain-dumping.

I'd just been talking to a potential customer and something had clicked. A feature. A pain point. A wedge. The kind of thing that makes your brain start running faster than your mouth.

And my wife (because she's the best) listened. For a while.

But I lost her pretty quickly.

She's not in the weeds. She hasn't been staring at the same problem for months and she didn't have all the weird little pieces of context floating around in her head like me.

Which meant it was less of a debriefing and more of me explaining.

And (of course) she was completely right: I needed teammates to talk about this.

Earlier that week, I had a great conversation with a potential customer.

Great because they clearly articulated a real pain.

They were missing follow-ups with clients. Things were slipping in email. Work was getting lost in the quiet gaps between people, and it was costing them business.

That is exactly the kind of thing I've been building toward. I got off the call and went outside with my mind racing.

I had six things I wanted to say immediately. I wanted the five-minute debrief with someone who had been there with me.

"Did you catch that?"

"That's the whole product right there!"

"That's the line we should be leading with."

But there was nobody to say it to.

Ameya, our summer intern, would have been game. He's been crushing it and would have listened…but he wasn't on the call. I could have brought him up to speed quickly, but that's not it.

I didn't need to brief someone. I wanted to turn to the person next to me and say, "Okay, you heard that too, right?"

And that's a very different thing.

Later that week, I met up with a former colleague from Apple.

We talked about work, families, old stories, the usual stuff. And pretty quickly the conversation settled back into a cadence we'd had hundreds of times before.

Part problem-solving. Part therapy. Part "what are you seeing that I'm not seeing?"

Within minutes, I felt my brain start doing the thing it used to do all the time.

I would say something out loud, hear myself say it, realize I only half-believed it, then sharpen it in real time. She'd push on some part of it. I'd push back. Then one of us would say something neither of us fully had in our head five minutes earlier.

That is such a specific kind of energy; and you don't notice how much you rely on it until it's gone.

When the check came, I felt two things at once: I was grateful that those people are still in my life and I was very aware that conversations like that are no longer my default.

When you have an amazing team, you barely notice it.

When you don't, you miss it badly.

Steve Jobs used to describe building great products as a rock tumbler.

You put in rough stones. Partial ideas. Sharp edges. Strong opinions. The conviction that something great is in there somewhere.

Then the rocks collide. Over and over. Eventually, if the process works, something polished comes out.

About a decade ago, I was in a war room at Apple. AirPods were ramping toward launch and there was a blocker. One critical feature. One uncomfortable decision. Twenty people in a room.

Everyone had data, context, and an opinion.

Nobody was phoning it in. The conversation went over several hours. Intense, not dramatic. Real problem solving energy. No one trying to sound smart for the room. Just a bunch of very good people trying to get to the best answer before the clock ran out.

When we finally landed, nobody was entirely happy. Which was probably a good sign.

The product shipped on time. The customer was better off for it. The decision was better because the room was better.

That's what I miss most.

The room.

World-class people facing the same direction, attacking the same problem from different angles, sanding down the rough edges until something cleaner appears. Not because everyone agrees. Because everyone cares enough to disagree well.

The friction works.

What I have now didn't exist a year ago.

I'll have four Claude sessions open, one to three Codex sessions running, ChatGPT next to me, and a messy stack of customer notes, product ideas, and half-finished thoughts spread across the day.

These tools are doing work that would have taken a small team not long ago.

It's also not the same.

Models do not properly disagree with you. They'll challenge an assumption if you ask them to. They'll critique a draft, generate five alternatives, tell you something is "solid" when it very much is not.

But they don't look at you across the table and say, "I think you're solving the wrong problem."

Interns tend not to tell you your taste is off. Advisors are incredibly helpful, but usually in focused slices. Friends and family support you, but they are not living inside the maze with you. And my wife knows me well enough to notice when I've gone too long without someone else in the maze.

The rock tumbler is running.

But maybe everything went in a little too smoothly.

That's the part I'm still trying to figure out. AI can replace a shocking amount of output: it can help with code, copy, strategy, research, design, analysis, planning, and all the weird middle work in between.

But it does not replace shared context.

It does not replace the person who was in the meeting, saw the customer react, heard the hesitation, noticed the throwaway line, and then sits with you afterward trying to figure out what it means.

It does not replace the teammate who cares enough to fight for a better answer.

And still - I would do it again.

I left an amazing team to build something I believed in.

I would make that trade again.

It has not been easy, but my frustrations with inefficient organizations cannot be tamed.

I hate watching good work get buried under unnecessary overhead. I hate dropped balls. I hate missed commitments. I hate the quiet failure mode where everyone is busy, everyone means well, and still the important thing slips.

There is a better way to work. I believe that deeply enough to spend years of my life pushing toward it.

That conviction feels different from anything I've had before.

I can be wrong, learn, rebuild, change the wedge, stake another six months on a sharper version, and keep moving without asking anyone's permission.

The agency is the point. The loneliness is part of the price. And the team comes later.

At least, that's the bet.

I don't write about the tradeoffs enough.

Maybe because founders are supposed to perform a certain level of certainty.

Maybe because admitting something is hard feels dangerously close to admitting it is not working.

But those are not the same thing.

Runway math is hard. Late nights are hard. Uncertainty is hard. Everyone knows that. There are tomes of startup writing about those things.

The part I did not fully expect was missing the people I would be building alongside.

The people.

The shared language. The inside jokes. The hard conversations. The glance across the room when everyone knows the meeting just changed. The debrief after the customer call. The person who knows why the thing matters before you explain it.

That's what I miss.

And I'm willing to bet a lot of solo founders feel the same thing, even if they don't say it out loud.

Anyone who says it's completely fine may have forgotten what a great room feels like.

So here I am: slower than I expected, still building, still convinced.

My wife is right that I need teammates to talk about this.

My former colleague reminded me what great teams feel like.

Ameya is right that there is good work to do this summer, and we'll do it together.

And I am still right that the trade was worth it.

Even now. Especially now.

I'm building toward a team I can't fully see yet.

For now, the room is smaller than I want it to be.

Some days, it's just me, a few agents, a few advisors, a summer intern, and a wife kind enough to listen until the context runs out.

It's not the rock tumbler I remember. But it is something.

And if you're building alone and you read this far, maybe you're in the room too.

What do you miss most?

The detailed ones. The ones with examples and edge cases. Wispr Flow lets you speak them instead — clean, structured, ready to paste into any AI tool. Free on Mac, Windows, and iPhone.

Try Wispr Flow free