Free guide · AI Bear

Build your own AI system.

Right now you have a chat window that forgets you every morning. In two weekends you can have something that knows your work, remembers your decisions, and does real jobs while you get on with something else.

2 weekendsTime
Nothing extraBeyond your AI plan
No terminalCoding needed
5 partsIn build order

The same question, asked two different ways.

This is the whole difference, and it has nothing to do with which model you pay for. Pick a question and watch what changes.

A chat window
A system that knows you

Notice what actually changed. Both answers came from the same model. The one on the right is not smarter. It just had somewhere to look things up, and a note explaining who was asking.

That is the entire gap, and it is made of four things nobody tells you are separate: where it lives, what it remembers, what it is allowed to do, and what it knows how to do.

The words everyone assumes you already know.

Almost everything written about this is written for people who already speak it, which is why it reads as harder than it is. This is the whole vocabulary you need. Open any word you are not sure about, and skip the ones you already know.

What "memory" actually means.

The word gets used loosely. There are three different kinds, they do different jobs, and most people build none of them. This is the layer that decides whether you get a colleague or a stranger.

What you are actually installing.

Guides like this normally say "whichever tool you prefer" and leave you to it. Here is the exact stack, named. If you already use something else, the third column is the swap, and after this the guide stops hedging.

What
The one I name
If you use something else
Folder
Google Drive
Dropbox or OneDrive
Editor
Obsidian
Any markdown editor, or none at all
The engine
Claude Code, desktop app
The command line version
Rules and memory
One CLAUDE.md file
Same file, any agent that reads it
Skills
Markdown files you write
Nothing at all, until part 4
Undo
GitHub Desktop
Git, if you already know it

The build, in the right order.

Not the order a diagram would give you. This is the order that stops you rebuilding things. Weekend one is the foundation, weekend two is the workforce.

0 of 5 done
The rule underneath all of it

Never build ahead of a bottleneck you have actually hit. Twice.

This is the only difference between the parts of my system I use every day and the parts I built and abandoned. The next section has the receipts.

What it actually costs.

Nobody publishes this, so here is mine, itemised. Untick anything you would skip and watch the number move. Most of it is free.

Three things I built and abandoned.

Every write-up like this shows you the parts that worked. These are the parts that did not, and each one cost me a weekend to learn.

Doing this for a company instead?

Same architecture, bigger stakes, and two extra layers you cannot skip: governance and the people. There is a scored assessment for that.

Open the company assessment