
Last Thursday we hosted the Operator Dinner at the CLT Startup House, our 2nd one, with my co-host Kristi and a table of owners, operators and execs. Before anyone talks business, we go around the table and everyone names the friction they're feeling right now, in work or in life.
I went early. There's an old startup line that more companies die of indigestion than starvation, and that's the one I'm living with. We work in AI, everything is moving a million miles an hour, and there's no shortage of opportunity. So we're trying to be very intentional about how we grow.
The rest of the table ended up speaking right to it, so that's this week's issue.
1. I've done the other version
This is my second time running a company. The first time around I worked 80 to 100 hours a week for 7 years straight, and I burned out. I texted a few friends and told them I didn't know if I was employable anymore, I just knew I needed to figure out how to not die. I had a job 3 days later.
Growing with purpose means the right people at the right time, the right clients, and making sure the team has what it needs before we take on the next thing. We use the SEAL line a lot internally.. slow is smooth, smooth is fast.
The signals aren't always clear. Somebody shows up with a real problem, I want to help, and I can hear every mentor I've ever had telling me this isn't our customer.
2. Growing fast scales your workarounds
Kristi set the theme for the night as the cost of the workaround.
One team at the table has getting stuff done as a core value, and they realized they'd been getting it done the same hard way all year without getting any better at it. Somebody else pointed out that most of our processes were designed around the tools we had 5 years ago, and the new AI tools are getting bolted on top of all that bloat instead of anyone going back to redesign the work underneath.
That's the risk of growing too fast with AI. Every workaround you already have gets copied into more accounts, more people and more agents.

3. You have to say the bar out loud
AI makes it easier to hit the bar, and whether anyone raises it is a leadership call. A talented, tenured team with better tools can finish the week's work by Wednesday and call it good.
I'm still learning this one. I can't assume anything, which means I have to say the standard and say it and say it again, because I can't hold anyone to a bar I've never told them about. One guest's rule for this was "say it 7 times, 7 ways," and I'm stealing it.

4. I'm unlearning nice
My last decade was mostly learning how to corporate. A good chunk of that training sanded my edges down.. be agreeable, keep the peace, don't make it awkward. The last two years have been me sharpening those edges back up.
Part of it is that I want to be liked, and I'm guessing most people who run something feel the same. Someone at the table put it as be kind, not nice. Being kind means you give honest, direct feedback and you care about the person while you do it. Being nice means you say "it's fine, don't worry about it" when it isn't fine, and the team pays for that later. A few of us admitted we soften feedback to dodge a hard conversation.
The model I use is the one I learned in a leadership program at an old job, from the Radical Candor framework: care personally and challenge directly. Most people slip into one of two corners, challenging without caring, which is plain obnoxious, or caring without ever challenging, which the framework calls ruinous empathy.
Being relentless doesn't mean being ruthless. Holding people to a high bar does them a service as long as you care about them while you do it. And none of this requires going back to 100-hour weeks.

5. Why I keep hosting these
The people paying the most for not being in an office together have less than 5 years of experience. They miss the hallway conversations where they'd learn why the senior people make the calls they make, which is how anyone picks up judgment.
I told the table about the old Bell Labs story, where someone went looking for why certain engineers kept producing breakthroughs and found a lot of them ate lunch with the same guy, Harry Nyquist. Nobody scheduled those conversations. They happened because people were in the same room asking each other questions.
That's a big part of why the CLT Startup House exists, and why I keep hosting these dinners.

Wrapping up
Almost every workaround at that table came down to a decision someone hadn't made yet. Mine are which work we turn down, which standard I haven't said out loud yet, and which feedback I've been softening because I'd rather be liked this week.
Putting this into action
Pick the one process your team grinds through every week, and ask whether you'd design it the same way if you started today with the tools you have now.
Write down one standard you expect but have never said out loud, then say it this week. Plan on saying it 6 more times.
Look at the last opportunity you said yes to and ask whether it fit, or whether it was just there.
What I'm reading
New Founder Archetypes in the AI Age. Andrew Chen at a16z on the founders AI is opening the door for: solo founders, non-technical founders, domain experts, kids and creators, with the case for and against each. I shared this one with the Builders of Charlotte crew over the weekend. He also makes the point that coding might get easier while sales, recruiting, judgment and persistence don't.
Claude's team on one agent vs a team of subagents. Across several enterprise deployments, their Applied AI team found a single agent loading skills and tools as it needs them often beat a main agent handing work to specialists, frequently at lower cost. If your team is building agents, ask them to test it.
Claude Duet, now in research preview. Claude's entry in the personal assistant race I wrote about a few weeks ago. It comes to you with what needs your attention and waits for your approval before it sends something sensitive, makes a payment or deletes anything. It's an early preview for Pro and Max subscribers in the US.
Your Notion Agent can now use a computer. Go from a conversation to a finished Excel spreadsheet, Word doc, PowerPoint deck or PDF without leaving Notion. If your team already lives in Notion, try it on the report somebody rebuilds by hand every month.
Onward & upward 🤘
Drew
P.s. I'm curious what you've learned to tolerate that you should be fixing. Hit reply and tell me.





