Leads who went quiet for months are suddenly back. Here's why.

I had a lead go quiet last October. A serious company, with a real budget. We had two great calls and then nothing. I followed up twice, got nothing back, and moved on.

Last week they emailed me. "Tim, sorry for the delay. Can we still work with you?"

Then it happened again. And again. Three old leads, all back inside the same week. People I'd written off months ago.

Part of me wants to ask why they waited. The other part already knows.

These companies didn't suddenly discover AI. They've been watching it the whole time. What changed is who's asking them about it.

Boards are asking. Investors are asking. The CEO down the hall who did something with AI is making everyone else look slow.

The cost of sitting still finally got bigger than the discomfort of starting.

The conversations happening now look different from a year ago too. The question has shifted from "should we try this" to "how do we move everyone." Companies are coming in with mandates and a real sense of scale behind them.

Some of the most interesting asks have been for someone in the room every week — not a vendor, but someone steering the whole thing. That shift in what organizations are asking for says a lot about where urgency has actually landed.

The burden of proof is changing too. Three weeks into a recent program, a client stopped asking about ROI and started asking what else they could do. That's a meaningfully different conversation from six months ago, and I think it's becoming more common.

I sat in on a client debrief this week with one of their operations leaders. He said something I haven't stopped thinking about.

His worry wasn't whether the tools work. It was whether his people would make the leap on their own. Knowing that AI can do something is not the same as figuring out how to apply it to your actual job.

His instinct: don't assume people get there by themselves. You have to meet them where they are. Show the customer support person the three things they can do this week. Show the analyst the bigger build. Be specific. Take the creative leap off their plate, because most people don't have the time or the headspace for it.

Getting a human to change how they work on Monday morning is the hard part, so companies must help their people cross that gap.

It's worth asking honestly inside your own organization: who is doing that translation work right now, and for whom?

A few of you asked what's changed in my own setup, so here’s what I’ve been building.

For two years my whole operation lived in Markdown files. Notes, deal context, client history, all of it in folders I could read myself. It worked, but it doesn't scale to agents.

So I built a brain. One database that holds everything: every deal, every call, every client. One agent does nothing but ingest. It reads what comes in, parses it, and drops it into that brain. Other agents only query it. They ask the brain a question and get back exactly what they need, with the source attached.

The shift is subtle but it's a big one. Markdown is for humans to read. The brain is for agents to search. I'm not reading files anymore. I'm asking my own business questions and getting answers pulled from years of context in a second.

I built most of it in an afternoon with Claude Code, reading every line but writing almost none of it myself. That's a newsletter of its own. I'll write the full guide soon.

Opus 4.8 just landed, and Opus 5 isn't far behind. The pace is not slowing down. If your plan assumes today's models are as good as it gets, your plan is already old.

Microsoft shipped Copilot Work and Copilot Tasks. This matters because Copilot is the default at a lot of big companies, whether people love it or not. We're starting to build Copilot training for a few cohorts now, meeting clients on the tools they already pay for instead of forcing a switch.

Claude Code now has workflows. This one is quietly important. A workflow is scripted in actual code. It spins off agents to do the work, and the data passed between them stays in code, not in the context window. That's a real step toward something we couldn't say before: parts of AI work can be made repeatable and predictable.

Your media buyer opens Slack at 8am. There's already a cross-platform brief in #growth: Google Ads spend vs. ROAS, Meta CPA by campaign, Stripe revenue by channel. Viktor posted it at 6am. Nobody asked for it.

Same colleague caught a spend spike overnight on your brand campaign. Flagged it before anyone logged in. The problem was handled before the first standup.

Your strategist reviews trends. Your account manager checks attribution. Same Slack channel. Same colleague. Before anyone's first coffee.

Google Ads, Meta, Stripe. One message. No Looker. No Data Studio. No dashboard tab left open since Tuesday.

11,000+ teams use Viktor daily. SOC 2 certified. Your data never trains models.

Get Started for Free

After Google I/O this year, Google rebranded most of their apps and started wiring real AI into them. The one that caught my eye: Google Keep now has a conversational mode. You just talk. It listens to your rambling, works away in the background, and turns the mess into clean notes and lists.

That's a bigger deal than it sounds. Google's models were always strong. The problem was everything around them. Docs didn't talk to Sheets. Every tool sat on its own island. Great engine, bad plumbing. Now the plumbing is catching up, and that mix is worth watching.

It hits a personal nerve too. I've wanted this exact tool for years. Every morning I'd love a 30-minute conversation with an AI that listens to whatever is in my head and maps it into notes, tasks, and a plan for the day. I get close today. I run my morning routine in Claude Code and dictate into it with Aqua Voice. But nothing is truly built for this yet. The first tool that nails the "just talk to me and sort my brain out" job is going to win a lot of mornings. Mine included.

This summer, I’d planned for a slower pace, clear head, maybe some unscheduled afternoons. Then three old leads came back in the same week, and that was the end of that.

I'm not complaining. When the work is something you genuinely love, a wrecked summer plan just feels like more of a good thing.

It's not working “hard” - it’s working consistently on something that pulls you forward. I'm not grinding through this. I'm obsessed with it. And we're still at the very beginning, which if anything makes it harder to slow down.

Hit reply and tell me: has your board or your investors started asking you about AI yet? And where does your business context live right now? I read every reply.

See you next week.

Tim