Built by one person. Run by AI.
You're one person doing the work of a whole team, for clients or for an employer. No one to delegate to, so you build the team out of AI. Every Tuesday I send one workflow I actually run, proven inside a real corporate job: the prompts, the steps, the part that broke and how I fixed it. Copy it, adapt it, ship it by Friday.
Written by Wayne ForemanHead of Sales Enablementworkflows that cleared real IT & legal review
Two desks, one problem
Solo operator means one person carrying a function that used to take a team. The context changes. The math doesn't.
On your own
You're the consultant, the fractional exec, the one-person service business. Also the marketer, the support team, and the bookkeeper. There's no one to delegate to, so you delegate to AI and learn to manage it like staff.
Inside a company
You run a function alone. Enablement, ops, marketing, whatever the org calls it. The headcount never came; the targets did. AI is the only way the work fits in the week.
Same workflows. Same kits. The framing shifts, the work doesn't.
What lands in your inbox
Six recurring sections. No filler, no recycled prompts, just the working parts of one real workflow.
- 01
The Workflow
One workflow I shipped this week, the trigger, the prompt, the tool stack, and how long it took. Put it to work before Friday.
- 02
What Broke
The thing that didn't work. Why it didn't. What I tried before giving up. Failure logs are the fastest education available.
- 03
Time Ledger
Hours saved this week, audited honestly. If something was a wash, it gets logged as a wash. No inflated ROI math.
- 04
The Prompt File
A working prompt, not a template, pulled from this week's actual system. Pasted in, used in production, lightly redacted.
- 05
Manager's View
One question to ask your CEO, your CRO, or your security team this week. Useful for getting unstuck without sounding naive.
- 06
Field Notes
Two or three short observations from the week. Calendar, comp, politics, the back-channel parts of corporate AI nobody writes about.
Recent dispatches
My membership had an August launch date. I deleted it and wrote a number in its place: 50 subscribers before launch. Then I checked the current count. Four, and one of them is me.
My first product sat finished in a folder for two months while I waited to feel ready for the launch infrastructure. I treated the launch as a checklist instead of a department and shipped it in three evenings, for the price of a one-dollar test purchase.
I read one line about how AI memory works, then audited the three files my assistant loads before every session. They were three to four times heavier than they should be, and trimming them surfaced three processes I thought were running but weren't.
One person, one desk
I'm Wayne Foreman, Head of Sales Enablement at a B2B security company. SoloBuilt documents the AI workflows I actually run at work, the ones that cleared internal security review, that survived legal, that a boss signed off on.
No startup context. No "act as a CEO" theater. Just the specific, sometimes-boring reality of using AI inside a real corporate function, written for people who have a job and four meetings before lunch.
There's also a catalog of $49 kits and an all-access bundle on the way: every kit, one payment, no subscription. But the free weekly is where to start, and where the work shows up first.
One workflow, every Tuesday morning.
Be among the first subscribers. Real workflows from one person doing the work of a whole department. Free, forever.
You're in. First issue lands Tuesday.
No tracking pixels. No drip campaigns. Unsubscribe anytime.