The KhaBot mission, in five notes, part 3 of 5
You built the app. Now what?
Step two: guidance you can run.
I keep meeting the same young developer.
Sometimes it is a student. Sometimes it is someone who graduated last year. They read every day that AI is replacing developers, and they are afraid. So they do the right thing. They push themselves. They learn to work with AI, they find a first client, and they build a real app or a real website.
Then they stop. And the code is fine.
They stop on questions like these.
Where do I rent a server? Which one?
How do I buy a domain and connect it?
The client wants a key for the service. How does that work?
I opened five accounts for this project, and I can't tell how much the client is using.
I have managed developers for years, and I used to call these things obvious. That was unfair. They are obvious to me because I have done them a hundred times. Nobody teaches them. You learn them by losing a weekend, and then another one.
So a person who just built a working product is stopped by a server, a domain and a billing page.
The agent already knows
Here is what changed.
The same AI that helped them build the app can also do these steps. It needs only two things. A place where it is allowed to act, and something to read.
That is what step one of KhaBot gives. One key is the place. The documentation is the thing to read, and I wrote it for agents as much as for people. If you cannot follow it, your agent can.
So the distance between a finished app and a live app becomes one prompt.
One key, one prompt
Something like this:
Here is my KhaBot key. Read the KhaBot docs. Start a small machine and put this project on it. Give me its address. Then create a second key for my client, limited to $20 a month. Tell me what each step cost.
Now look at the four questions again.
The server. It is a Linux machine inside the account you already have. You pay by the minute while it runs.
The domain. The machine comes with its own HTTPS address. The project is online today. The domain can wait until the client asks for one.
The client's key. It is a separate key with its own limit. The client can never spend more than you agreed.
The tracking. Every request made with that key is recorded with its cost. At the end of the month you know what the client used, to the cent.
Four problems, one account, one prompt.
Guidance you can run
This is what I mean by the second step of the mission.
Advice is not enough. People have plenty of advice. A guide should be something you can run. It says what you will get. It says what it will cost before you start. It needs one key. And when it is finished, the scripts are on your machine. Read them. Ask an AI about them. Show them to a friend who knows more than you. Change them. They are yours.
And it is not only for juniors. I am an expert in a few things and a beginner in many others. So are you. An engineer who can design a circuit may not know which speech service is cheap. A person who runs servers all day may have missed the model that was released last week. Everyone is one step away from something.
I am writing these guides one by one. Moving your files out of a cloud drive and into storage you control. A private meeting server that exists for one meeting. A scan of your own disk that tells you what is filling it. A check of your browsing history that shows where your data went.
The step
I cannot tell a young developer what the job market will do. Nobody can.
But I can remove the step where they stop.
You built the app. Now it is one prompt.
The first guide is the one from this note: put your project online with one key.