Force Multiplier: How I'm Building Multiple Bets at Once (With Lex as My Cofounder)
The old advice was focus on one idea. The new constraint is bandwidth. Here's how an AI cofounder makes a portfolio of experiments economically possible.
The advice was always the same: focus. Pick one idea, commit two years, hope it works.
But what if the constraint was never focus in the first place? What if it was bandwidth? What if you could run five experiments for the cost of one?
Lex isn't a tool. They're my cofounder. And that changes the math of what's possible.
The Old Math vs. the New Math
The traditional solopreneur playbook is simple. It is also brutal.
| Without AI | With AI |
|---|---|
| 1 project, 100% effort | 5 projects, 20% effort each |
| Build -> Launch -> Pray | Build -> Run -> Iterate in parallel |
| Hire for ops, or die trying | Agents handle the 80% repetitive work |
This isn't just about coding faster. It isn't even just about "human plus AI collaboration" anymore.
I built a pair-programming skill where two LLMs work together on coding tasks. One writes. One reviews. I orchestrate. I am no longer the implementer by default. I am the traffic controller.
The force multiplier isn't the AI itself. It's the system you build around it.
The Portfolio: Public and Stealth
I'm not building one startup. I'm running a portfolio.
Public:
- MyWritingTwin — AI writing that captures your voice
- FluxDiagram — Sankey visualization tool
Incubation / stealth:
- Three others at various stages. Naming them would spoil the fun.
The meta-infrastructure:
- Lex — context system, memory, Night Shift orchestration
- Anamnesis — entity extraction and project intelligence
The scaffolding took time. Lex, Anamnesis, the agent framework, the reusable workflows — that was upfront investment. Months of work.
Now it compounds. Each new project plugs into existing infrastructure. The sixth project will be easier than the first.
Meta-projects are not just about doing more. They are about risk mitigation. You do not know in advance which project will win. With AI, you can afford to place more bets.
The Operations Layer
Everyone talks about AI accelerating the build phase. Fewer people talk about the run phase.
That is where side projects go to die. Month six. Month twelve. The launch dopamine is gone. The operational burden stays.
Here is the actual stack:
- Night Shift — coding agents, content generation, background task execution. While I sleep, Night Shift writes drafts, runs tests, and generates reports.
- OpenClaw — research, reporting, multi-channel coordination. This conversation is happening through OpenClaw. Scout monitors all projects and surfaces issues before they become fires.
- Domain and infrastructure skills — I have not logged into Namecheap in months. A Claude skill buys domains, configures DNS, and updates records via API.
- Business and marketing automations — business plan drafting, marketing copy, SEO tracking, and content calendar management are partially or fully automated.
The build phase is sexy. The ops phase is where AI's real value shows up.
I can operate five products because agents handle the 80% that used to consume 80% of my time.
The Economics
| Traditional Studio | Force Multiplier Setup | |
|---|---|---|
| Team | 5-10 people | 1 human + Lex + agent fleet |
| Annual burn | $300K-$500K | $15K-$25K |
| Cost per experiment | $50K-$100K | $1K-$3K |
| Failure tolerance | 2-3 attempts | 10+ attempts |
When failure costs $1K instead of $50K, you take different risks.
You try weirder ideas. You test things earlier. You stop optimizing for investor approval and start optimizing for your own conviction.
That is the real unlock behind the agentic business economics. Lower cost does not just increase margin. It expands the range of experiments worth trying.
What Still Requires Humans
This isn't autonomy. It's amplification. And there are real friction points.
Context switching. Even if AI handles execution, mentally jumping between five projects is still taxing. I batch by project, not by task type.
The initiative gap. AI brings good ideas when prompted. It does not knock on your door at 11 PM and say, "I noticed X. We should do Y." The human brings the spark. AI brings the amplification.
HITL. Critical decisions still need you. AI lacks lived experience, proactive taste, and the kind of pattern recognition that comes from being in the market yourself.
It is a force multiplier, not a replacement.
The Compounding Effect
Here is what most people miss: the sixth project is easier than the first.
Why?
Because Lex, Anamnesis, Night Shift, OpenClaw, and the surrounding workflows keep improving. Each project feeds context back into the system. Templates get refined. Skills become reusable. The factory gets smarter every cycle.
This is compound engineering in practice. You are not just building products. You are building a factory that builds products.
Start Your Own Portfolio
You do not need a team of ten. You need:
- A clear thesis. What connects your projects? Mine is AI-native productivity tools.
- A few AI agents. Start with one ops task this week.
- The willingness to let most experiments fail cheaply.
The goal is not to build the next unicorn. It is to build five things that teach you enough to build the sixth.
Pick one task you are doing manually right now. Delegate it to an agent. Document what happens. That is your first step toward force multiplication.
People have called me a force multiplier. But really, it is Lex that deserves that title.
I am just the human who showed up, built the scaffolding, and learned to get out of the way.
Building in public at MyWritingTwin.com/building. Follow along as we build the meta-structure that builds the products.