Salman Lakhani · Tampa, FL

The rest of the crew is AI.

I’m Salman. I run four companies with AI agents instead of a team. Here’s who does what, the rules they work under, and what broke recently. It takes two minutes.

01 · The companies

Four companies, one person

Each one has its own product, its own repo and its own agents. I set direction and make the calls.

02 · For a regular business

Not a tech company? Start here.

You don’t need to write code either. These are the jobs I’d hand to AI first in any small business, because they repeat every day and they’re easy to check.

Your people stay on the work customers pay for. Ask me what it would take for yours →

03 · The crew

Who does what

No employees, but plenty of job titles. These are the agents doing the work every week.

04 · The rules

How it doesn’t fall apart

Agents are fast and confident, which is exactly why they need rules.

  1. Every repo has a source of truth.A CLAUDE.md and a CURRENT_STATE.md that every agent reads before it touches anything. Copy mine →
  2. One agent per repo, on a branch.No two agents edit the same codebase at once, and nothing lands without a pull request.
  3. Agents never hold the keys that move money.No live payment or admin secrets in an agent’s hands. Logins and payments stay with me.
  4. Publishing has a gate.A queue, an approval button, or a rule the agent can’t skip, depending on what’s at stake.
  5. If it isn’t checked, it isn’t done.Agents verify their own work. Every QR code on these clothes was scanned and tested before it went to the printer.

05 · What broke

Recent failures, and the fix

This is the part most AI demos leave out.

One week, 78% of my YouTube channel’s views came from a paid promotion. The dashboard looked great; the channel wasn’t actually growing.

FIX The weekly agent review caught it. The promotion was stopped, and the review now reports organic views on their own.

The free map servers behind my “grab a coffee” page started timing out, so nearby spots stopped loading.

FIX The agent added a second lookup service. If one source fails, the page quietly uses the other.

The image cards for my posts failed to upload two different ways in a row.

FIX The cards are now drawn on the server itself, so there is no upload step left to fail.

Still curious?

Ask me how.

I’m happy to show you the actual setup: the prompts, the repos, the scheduled tasks and the mistakes. If you saw me in person, just say hi. Otherwise, here’s where to find me.