Lesson 4 · 16 min
Here the deliverable becomes infrastructure: website, second brain, company system, prototypes and micro-SaaS. Three of them are pure building and have lost value. Two become Mentor work, because the hard part is not assembling: it's getting someone at the company to own what was assembled and getting the handoff to IT done cleanly.
Start the lesson
Goal: turn a building (website, prototype) into part of a Mentor or Consultant service and write the empowerment framing.
Two rise as mentoring, three are building. Click each box.
When someone in the market advertises "do X and charge a fortune", it's a sign that X has already become a commodity.
Click each tab.
Gather scattered knowledge (people's heads, loose folders, old spreadsheets) into a repository you can query in natural language. For companies with a lot of long-time staff and little documentation.
The proof that matters is your own: nobody buys organization from someone disorganized. Build yours in public first.
Build the layer that makes a department run with AI: procedures, connected tools, owners. To prove value fast, pick the department with the most written procedures; for maximum value, the messiest one.
It's not about creating a replacement in case this person leaves. It's about them no longer putting out the same fire, becoming the owner of the system and gaining status.
The employee who knows everything and never documented anything isn't lazy: that is their protection. Show up saying "let's create a replacement" and you've made an enemy inside the client.
Not for people starting from zero: it takes reading office dynamics.
On the website, the client will ask about search and ads. Having a good AI tool doesn't make you an expert in that.
Say you can point out improvements, and hire one or two hours of a real specialist to review. You deliver well and learn along the way.
The first is the inventory that opens the prototype conversation. The second is the line from the lesson.
You are a pragmatic, skeptical solutions architect. My client is <type of company, number of employees>. These are the software subscriptions he pays for each year: <list: generic category, what it is for, how much it costs per year, how many people use it> Do the following, in this order: 1. Classify each one as: REPLACEABLE (can be rebuilt custom within 2 weeks), RISKY (rebuilding is possible but expensive to maintain) or DO NOT TOUCH (integration, compliance or volume that doesn't pay off). Justify each classification in one line. 2. For the REPLACEABLE ones, write the minimum scope that covers 80% of real use and say which 20% is left out. 3. Say who on the client's team can become the owner of each tool and what I need to teach that person. 4. List the 3 objections he will raise and the honest answer to each. Don't flatter me. If most are DO NOT TOUCH, say so.
<Name>, you are the person who knows best how <process> works here. The idea is not to replace you: it's for you to stop dealing with <repeated fire> every week and become the owner of the system that does it on its own. I'll work with you until it runs.
Two exercises.
Run the prompt with the subscriptions of a company you know (or your own). Read the classification with suspicion.
Done when: the list has at least one subscription marked DO NOT TOUCH and each REPLACEABLE one has a named owner on the team; if everything came out replaceable, redo it.
Adapt the line to a real process in your niche and log opportunities 6 to 10 in the filter table.
Done when: the line does not contain "replace" as a goal, names the repeated fire, and the 5 rows are in the table.
3 questions.
Question 1 of 3
In a company system project, the employee who knows everything resists documenting. What should you do?
Question 2 of 3
The client asks whether you handle ads and you don't know the subject well. What's the honest answer?
Question 3 of 3
Why does the second brain fall in the Mentor box and not in the building box?
Choose an option. The explanation appears after you answer.