November 2026
Newsletter

The technology ecosystem, updated

When I first mapped out how Adaptive Edge runs, it was seven tools. It's now eleven. I added Descript for the avatar videos, Zapier to connect things, Gmail for the personal replies, and Zoom for the live sessions.

Here's how it grew. I started off just building an HTML web page and deployed it manually to Netlify. Then I wanted to automate it, so I added GitHub so I could push from my laptop. I also added Stripe for payments, but I wanted to trigger welcome emails from MailerLite, and that required a zap from Zapier. Things just grew organically as I automated more of these flows.

Here's what I keep coming back to. Most businesses don't have a tool problem. They have a hand-off problem. Every tool does its one job well enough, and then nothing carries the work to the next one. So I think of it as three phases: build the thing, sign up and get paid, then deliver it. Claude builds. A form, Stripe, MailerLite and Zapier handle the middle. GitHub, Netlify and Zoom put it in front of you.

You don't need all eleven. Start with an AI assistant and a folder on your computer. That takes you a surprisingly long way. Add the next piece when a real need shows up, not before.

This is also the new Technology Ecosystem module, the sixth in the subscription. It's my actual setup, not a theoretical one, and your version will look different. If you want a head start, try this in Claude:

See the full ecosystem map

Claude desktop: chat and Cowork are now one

On September 16, Anthropic announced that chat and Cowork are merging into one Claude. You don't pick where a task goes anymore. Claude works out what it needs, and the Cowork abilities show up in any conversation, using your existing skills and connectors. It's rolling out to Pro and Max first, in the web, desktop and mobile apps. Team and Free plans are listed as "soon," with no date.

Just as we all got comfortable with Cowork, it folds back into plain Claude. That's the point of what I do. The tools keep changing, and the modules have to keep up.

If you do one thing from this newsletter, set up your projects properly. It makes a bigger difference than any prompt. Start with one project per area of work, with its standing instructions written once so you're not retyping them in every chat. Then give it your files in two different ways, because they do two different jobs. Here's the order I follow.

Step 1: Create the project. Click New project, then add a name and a description.

Step 2: Use Context for things that don't change much. While you're setting up, the Context section lets you add files: your solid business plan, your brand guidelines, your writing voice. You pick the files from a folder on your computer, and Claude keeps a snapshot copy. That's perfect for reference material. If the original changes, you swap the copy. Note that you can't add a folder here. Only files.

Step 3: Create the project, then go back in. This is the catch. You can't connect a local folder while you're setting the project up. You have to finish creating it first.

Step 4: Add the local folder in Context. Open the project again and go to Context. This is where you connect a local folder, and it's the one for work that keeps changing: drafts, finished pieces, summaries of what you just did.

Step 5: Choose a parent folder. Connect the folder that sits above everything for that project, not one subfolder. Everything underneath it is then available to Claude, including folders you add later. That matters, because new folders will appear. Claude will often create a subfolder on its own to group files from a chat, and you can ask it to create one too.

That split is the whole idea. Context holds what stays put. The local folder holds what moves.

Now the three things that trip people up.

Check the folder is really connected. It's easy to disconnect a folder without noticing, and some people have reported a folder showing as linked but not actually available to Claude. A few have also said that once you remove a folder from a project, putting it back isn't always possible. So don't unlink a folder unless you mean to. I check anyway. When I finish an asset and create an MD file, a PDF, a Word doc or some other file, it's saved automatically. But I still look on my MacBook Pro to be sure. Until I feel confident things are flowing where I want them to, I keep checking. Before you ask Claude to build anything, ask which folders it can see. It takes ten seconds.

Check where it saved things. Claude usually files things sensibly. But look anyway. Open the folder after the first save, or just ask, "Where did you save that?" Getting this right early makes everything after it easier.

Deleting isn't as easy as you'd think. You can always delete a folder yourself on your computer. But if you ask Claude to do it, it will either ask your permission first or tell you it can't, and you'll need to do it by hand. That's a good thing. Just don't be surprised by it.

Here's why I care so much about all this. When a chat produces something, a file, a visual workflow, or a summary of what we just did, I have Claude save it into the project folder. Then I run my /complete-artifact skill, which checks that nothing from the chat is missing from my tracker. And then I delete the chat. The work lives in the folder, not in a conversation I'd have to dig back through.

Check before you build. Save it as a file. Then let the chat go.

What's happening in AI, and how to keep up without drowning

If you feel behind, you're in good company. A recent AP-NORC poll found 64% of U.S. adults say AI is developing too quickly. And honestly, it's hard to argue. In the past month alone, Anthropic has released three Claude 5.5 models, with Haiku 5.5 the latest, and Claude Docs and Slides are reportedly out of beta and on every plan. Meta and Sierra put out an open standard for AI assistants to deal with businesses directly. Billions are moving into AI infrastructure, a lot of it now as debt.

Most of that won't change your Tuesday. Some of it will. The hard part is telling which.

That's why I built Adaptive Edge the way I did. Not a pile of videos. Not a checklist. A way to meet each new thing from several directions, so it actually sticks and you can use it in your business:

• Read it. The module's tabs give you the overview, the tools and the Field Report.
• Watch it. A short presentation from my avatar, my "digital cousin," and then a walkthrough on the real tool.
• Try it. Prompts you can run on your own business the same day, like the one above.
• Ask about it. A monthly live small-group session on Zoom, built from your questions.
• Stay current. A new module every month and this newsletter, with the filtering already done.

I curate and filter so you don't have to. That's the job.

Claude Teams: when it's worth it, and what you actually get

A few of you have asked about Claude Teams, mostly how it's priced and how people really collaborate in it. So I read through how it works. Here's the short version.

It isn't a discount for buying multiple accounts. A Standard seat is $20 per person per month billed annually, or $25 monthly. A single Pro account is $17 annually or $20 monthly. So you're paying a few dollars more per person. What that buys isn't more of the same. It buys things Pro doesn't have at all:

• Shared projects. Project sharing is a Team feature, not a Pro one. You create a project and choose who can get in. Private means only the people you invite. Public means anyone in your organization can find it and use it. Each person gets "Can view" (they can chat in it and see the instructions and knowledge) or "Can edit" (they can change them).
• One account in charge. One bill, and an owner who adds and removes seats as people come and go. Admins can also set spend caps, control which connectors people use, and roll out skills to everyone.
• More room per person. A Standard seat gets about 1.25 times the Pro session allowance. Premium seats, at $100 annually or $125 monthly, get about 6.25 times.
• Cowork and Claude Code come with it. Every seat includes them.

Teams run from 2 seats to 150. Past that you're looking at Enterprise.

How it works for a small team: three examples.

A three-person marketing shop. One shared project holds the brand guidelines, the writing voice and the templates. The owner has "Can edit." Everyone else has "Can view." Everyone works from the same source, and nobody pastes the guidelines into a chat again. Then each client gets their own Private project with only the people on that account invited. Client A's material never sits next to Client B's.

A consultant and an assistant. A shared "Business Operations" project holds the business summary and the pricing sheet. The assistant can edit it. The owner keeps a separate Private project for anything the assistant doesn't need to see.

Handing off a result. Say you finish something in a chat and want a teammate to see it. Share that one chat with a link. It captures the conversation up to that moment, and you can update it or switch it back to Private whenever you want.

What stays separate. Chats inside a shared project are not shared. Your chats stay yours unless you choose to share one. Each project also keeps its own memory, so one client's context doesn't bleed into another's. And every seat belongs to one named person.

One honest caution. Separate doesn't mean invisible to the account owner. The primary owner can request a data export that can include conversations. So if something should never reach the owner, don't put it in a work account.

So when do you want it? My rule of thumb: when two or more people need the same instructions and reference material and you're tired of copying them around, or when you want one person in charge of access and billing. If it's just you, or you only occasionally hand someone a finished file, Pro is plenty.

One more thing to know. Projects tied to a folder on your computer stay on that computer and aren't shared with teammates. Shared projects live in your Claude account. If your team's work lives in local folders, that matters, and a shared drive is the usual bridge. This may change as the combined chat and Cowork experience reaches Team plans.

If you're weighing it for your own team, hit reply and tell me what you'd need it to do. I'll use the real questions in a follow-up.

Until next month,

Michael