I Run My Business From a Black Screen

Most people picture running a company from a browser. Twenty tabs. Three dashboards. A CRM that loads in six seconds if you are lucky.

I run mine from a black screen with a blinking cursor.

I am going to explain why, and then I am going to tell you who should absolutely not do this, because half the value of a real explanation is the part where it does not apply to you.

What a terminal actually is

The terminal is the oldest interface on your computer. No buttons. You type a command, the machine does it, it tells you what happened.

Tools like Claude Code now let you talk to an AI model from that same black screen, and the model can read your files, write your files, run your programs, and check its own work. It is not a chat window. It is a worker sitting inside your computer.

Here is what that changed for me.

Speed

A browser tool has to load a page, render it, wait for you to click, send the click to a server, and wait for the server to answer. The terminal skips all of that. You type, it runs.

When I am building a client site, I do not open a page builder. I describe the section, the model writes it, I look at it, I say what is wrong, it fixes it. The loop is seconds, not minutes. Over a day that is the difference between three pages and twelve.

Memory that I own

Every project I run keeps its notes in plain text files. Markdown. The kind of file you could open in 1995 and can still open in 2040.

The model reads those files at the start of every session, so it knows what we decided last week. No database. No subscription that can get cancelled. No platform that changes its terms. A folder of text on my machine, which I own outright.

Every night a script zips every one of those folders and pushes the archive to cloud storage. If my laptop fell in the lake tomorrow, my entire working brain is a download away.

Less browser, less drift

I have not measured this scientifically, so take it as a statement and not a study: when I work from the terminal I stay on task longer. There is nothing to click on. No feed. No notification badge. The screen has one job and so do I.

Who should not do this

Now the honest half.

If you are not technical, do not start here. The terminal has no undo button and no safety rail. A mistyped command can delete a folder with no confirmation. If the phrase "file path" makes your eyes glaze over, a browser tool with a big blue button is the right tool for you, and there is no shame in that.

If your team is not technical, the browser wins. You can hand a page builder to a front desk employee. You cannot hand them a terminal.

The learning curve is real. It took me weeks of frustration before it took me minutes. I had the time and the stubbornness. You may have neither, and your business may be better served by you spending those weeks on customers instead.

AI in the terminal makes mistakes faster too. The same speed that lets me build twelve pages a day lets me build twelve wrong pages a day. Somebody still has to know what right looks like. That is the part the tool cannot do for you.

If you want to try it

Start with one low stakes thing. A folder of notes. A script that renames files. Something you could redo by hand if it broke.

Do not start with your customer database.

I am teaching this to a small group of business owners this fall, in person, plain English, no coding background required. If that interests you, text me at (903) 500-8898 and tell me what you would want to automate first.