I run my company as one person with an AI bridge crew. Five AI crew members handle operations, communications, scheduling, engineering and records. I make the decisions, and nothing posts, publishes or sends without my approval. This setup is how I keep step 12 of my book, Fail To Brand, Plan To Fail, running every week: install a weekly loop and repeat it.
Why run a one-person company at all?
I spent 25 years inside the Fortune 500, starting in IT in 1978, then 20 more building my own businesses. I have seen what large teams do well, and what they cost. When I started over at 62, I did not want to rebuild a payroll. I wanted leverage.
A one-person company with good systems lets me stay close to clients, move fast and keep overhead low. The constraint is attention. There is only one of me. The crew exists to protect that attention for the work only I can do.
Who is on the bridge crew?
I named the crew after a starship bridge because each role has a clear station:
- Spock runs operations. Planning, research, drafting and the approval queue. Spock turns my priorities into a weekly plan and keeps score.
- Uhura handles communications. Inbox triage, replies drafted for my review, and keeping conversations from going cold.
- Sulu manages the schedule. Calendar, recording blocks, deadlines and the rhythm of the week.
- Scotty handles engineering. Websites, automations, integrations and anything technical that breaks.
- Data keeps the records. Notes, files, decisions and the history of what worked, so nothing is rebuilt from scratch.
What stops the AI from posting something I would not say?
Approval gates. This is the most important rule in the whole system. The crew drafts and I decide. Nothing is posted, published or sent under my name without my explicit OK.
In practice, that means every draft lands in a queue. I review it, edit it or reject it. Only then does it go out. The crew can work fast because the gate is at the end, not in the middle. I never wake up to a post I did not approve.
If you take one idea from this article, take that one. Automation without a gate is how leaders damage reputations they spent decades building.
How does the crew support my personal brand?
A personal brand is not a launch. It is a loop. Step 12 of the book describes it: every week, one wound named, one receipt shown, one application to the current madness. Then you book ninety days of the same verdict with better evidence.
The crew makes that loop sustainable for one person:
- Spock watches the market for current events my sentence explains, and drafts the application.
- Data pulls the right receipt from my records.
- Sulu protects the recording time on my calendar.
- Uhura keeps up with the replies and conversations each post starts.
- Scotty keeps the site and tools working so the proof stays where skeptics can find it.
I still record, review and approve. The crew removes the friction that makes most leaders quit by week three.
Do I need AI to install a weekly loop?
No. The loop works on paper. AI makes it cheaper to keep running. If you are starting out, run the loop manually for a month. Notice which parts eat your time. Those are the first jobs worth handing to a system, with a gate before anything goes public.
What does a weekly loop look like?
- Monday: pick the wound and the current event for the week.
- Tuesday: pull one receipt that proves your sentence.
- Wednesday: record or write the piece.
- Thursday: review, approve and publish.
- Friday: note what landed and file it for next time.
Exercise: map your crew
- List every recurring task in your week that touches your reputation.
- Assign each task to one of five stations: operations, communications, schedule, engineering, records.
- Mark the tasks that must never go public without your review. Those are your approval gates.
- Run the weekly loop above for four weeks before you automate anything.
Next step
The weekly loop is step 12 of the system in Fail To Brand, Plan To Fail. Get the free 12-Step Plan to see all twelve steps. If you want to build your own loop with me, apply for coaching.

