If you run a one-person company, you do not have an automation problem. You have a picking problem.

Automate these first:

1. Follow-ups. If a lead, client, or invoice goes quiet, a workflow should nudge, not you.

2. Inbox triage. Labels, drafts, and "needs a human" vs "already handled." You should only see the first pile.

3. Content recycling. One idea into a post, email, and thread. Stop rewriting the same thought four times.

4. Status updates. Weekly recap to yourself or a client, pulled from what actually shipped.

Leave these alone for now:

1. Sales calls. A bad script loses more money than a slow calendar.

2. Pricing decisions. If an agent sets your rates, you will undercharge forever.

3. Anything you have not done 10 times by hand. You cannot automate a process you do not understand.

Rule I use: if it happened the same way last week and last month, it is a candidate. If it still surprises you, it is not.

I am collecting the boring repeats from founders this month and turning them into drop-in templates. If you have one that eats an hour a week, drop it in the comments.

I used to give an AI a VPS login and hope it didn't brick the box.

That's a bad trade. You want it to write files, restart a process, and read a crash log. You do not want it holding root on a machine you still have to patch.

So I built Redon3 around that. You connect ChatGPT or Claude once over MCP (28 tools, on your account only). It can:

• write the project files

• put the site live

• read the log when it dies

• it cannot delete your panel

Panels last 30 days. Same editor, terminal, and logs on every plan. RAM is the only thing that changes: 450MB / 1GB / 2GB.

If you've been copy-pasting deploy errors back into chat, skip that. Connect the assistant and tell it to ship.