You are not out of AI. The backpack is too full.

If you have used a chat app like Grok, ChatGPT, or Claude, you already know the basic trick. You type. It answers.

Many of those apps also give you a weekly budget. When people run out, they blame the model. That is usually the wrong diagnosis.

The budget moves when the bot has to reread a pile of leftover notes on every turn. One fat bot that does five jobs, checks five tools, and keeps last month's chat in the room will spend uses even when you ask a small question.

Think of the chat as a backpack. If you pack every textbook you own, you pay the weight even when you only need the math book.

The fix is not a cheaper model. The fix is a smaller job and a quieter loop.

Split the job

One bot that tracks every workout, every inbox, and every school project will drag the wrong memory into the next question.

Give each job its own chat. A running log does not need last week's lift. An inbox helper does not need the homework board. A code helper does not need the social calendar.

You will end up with more bots. That is the point. Each chat carries only the notes that job needs.

Write the job in the profile

Do not spend twenty turns answering interview questions. Write the job once, the way you would write a short spec.

Name what it does. Name what it does not do. Name what it should hand off. Then keep the live chat short so the seat stays free.

A vague profile makes the bot ask. Asking spends the budget. A written job is cheap.

Hand off the heavy work

The chat you still want to use is not the place for a ten-minute job.

Send a short brief to a helper chat or a background worker. Send code work to a cloud helper that already has the files. Those can run while you keep talking.

Write that rule into the bot. If this will take more than a couple of minutes, hand it off and come back.

If a helper already has the project files, do not download them and search them again from the main chat. That is the same work twice.

Connect tools. Do not screenshot every page.

If the bot needs data from a site or an app, use a normal connection when you can. A screenshot is for showing the bot a picture. It is not how the bot should read a site page by page.

Put that in the profile. Screenshot scraping spends a lot and returns a worse answer.

Teach it once

The second time you explain a procedure, stop typing it into chat. Save the steps. Point the profile at that saved note. Re-teaching is weight you will pay for forever.

Automatic checks are where the budget dies

A routine runs without you asking. If the bot picks how often, you can empty a day of uses on silence.

Check every unattended loop.

• Fire when something happens, not on a timer. A mention, a new file, a ticket change. Do not ask every hour if anything happened.
• Keep the watch small. One channel. One folder. One queue. Watching everything is polling with extra steps.
• Run as rarely as the job allows. Daily is the default. Hourly only if you can name the reason.
• Keep the routine short. Point at the saved steps. Stay quiet when there is nothing to do. A bot that says “no updates” still spends uses.

A routine should act, or it should be silent. Those are the only two good states.

One specialist plus one manager

A chat cannot remember everything. As it grows, earlier detail falls out. The bot is not getting dumber. The window is full.

The pattern that scales is a manager that routes, plus specialists that each hold one job. The main bot does not carry every helper's memory.

Next notes in this series: /blog/chief-of-staff-only-routes and /blog/hire-specialists-until-the-buildout

Copy-paste profile rules

Paste this into the bot profile after you have named the job in one sentence. Edit the job line. Do not paste secrets.

Job: <ONE SENTENCE>. Do only this job. Do not carry notes from other jobs.

Keep this chat short and high level. If a task will take more than a couple of minutes or needs a project folder, hand a short brief to a helper and report back. Do not do heavy work in this thread.

If a helper already has the files, do not download or search them again from this chat.

Use a normal connection for data. Never gather site data by taking screenshots page by page. Screenshots are only for showing me something.

If I teach a procedure twice, save those steps and point at them next time. Do not re-interview me for a spec I already wrote.

Routines: prefer an event over a timer. Watch one channel, one folder, or one ticket. Default cadence is daily. Stay silent when there is nothing to act on. Do not send “no updates.”

Do not invent extra jobs, extra routines, or extra monitors.

A first week that will not empty the meter

• List the fat bot's jobs on paper. Split each job onto its own bot. Write the job in the profile. Delete the blob.
• Turn any second-time instruction into a saved note. Point the profile at it.
• Kill hourly routines you cannot defend. Switch the rest to an event or to once a day.
• Scope every listener to one channel, one folder, or one queue.
• Replace one screenshot scrape with a normal connection. If there is no connection, fetch less, not more pages.
• Send one fat task as a brief to a helper. Keep the main chat free.

Why this belongs here

A setup is not a longer prompt. It is a smaller job, a written profile, a handoff rule, and a quiet routine.

Write the job. Split the seat. Hand off the heavy work. Listen instead of poll. Stay quiet when nothing changed.