The most common way setup breaks isn't a bug

When someone new sets the system up, the first ten minutes decide almost everything. Get through them and people are fine. Trip in them and a good number never come back. So I spend more time thinking about those ten minutes than about almost any feature.

Here’s what I learned watching real setups: the thing that goes wrong most often isn’t a bug in the system at all. It’s that Google Drive on the person’s computer and the Claude connector are signed into two different Google accounts. When that happens, the system can’t see its own files. Everything looks empty. It reads exactly like the product is broken, and the natural next move is to assume it is and give up.

It isn’t broken. It’s two accounts that need to match. But you’d have no way of knowing that from what’s on your screen, and telling someone to check their accounts after they’ve already decided the thing doesn’t work is too late.

So I built for it in two places. First, a short pre-flight checklist: four things you confirm with your own eyes before you start, about ten minutes, and it clears the snags that otherwise eat the first twenty. Second, and more important, the system itself now knows about this failure. If it opens and finds nothing where its files should be, it doesn’t shrug and report a problem. It says, in plain words, that the most likely cause is the two accounts, and walks you through checking both before you touch anything else.

The idea I’m pushing against is that setup problems are the user’s job to figure out. When something fails silently and looks like a defect, telling people to read the instructions more carefully is not a fix. The fix is a system that recognises its own most common failure and tells you what it actually is.

A product that works beautifully once it’s running, but loses people in the first ten minutes, is not a product that works. The setup is the product too.