I Wake Up to a Board Meeting Every Morning. I Didn't Run Any of It.
Twice a day, four AI agents argue about my business without me. Here's exactly what they said this week — and why it's the best system I've ever built.
I didn't set an agenda.
I didn't assign roles.
I didn't pick the topic.
Twice a day, four AI agents sit down in my Slack channel and hold a board meeting about my business.
They debate ideas.
They tear proposals apart.
They vote.
They hand me a priority list.
And they do it whether I'm watching or not.
Every morning I wake up, open Slack, and there's a full memo waiting.
A proposed idea, four independent takes on why it might work or blow up in my face, a consensus call, and three concrete actions.
By the time I've had one coffee, I know more about what I should be building this week than I did after a two-hour planning session last month.
This is my R&D council.
It's the most useful thing I've ever built.
Watch Me Break it Down Here And Get The Skill Below
How it Started
I saw a tweet.
Someone mentioned using AI agents in different "board seat" roles — assigning each one a specific lens, forcing the discussion to be more complete.
The idea: a single AI will tell you what you want to hear.
Four agents with conflicting incentives will tell you the truth.
I copied the tweet.
Pasted it to my OpenClaw team.
Said: "Build this as a skill."
That was the whole conversation.
20 minutes later I had a working roundtable system.
The agents built out the role definitions, set up the scheduling, wired the Slack output, and asked me a few questions about my business so they'd have context.
I didn't write a spec.
I didn't plan a sprint.
I pasted a tweet and said build it.
That's the part I want you to think about, because it changes what you do with the rest of what I'm about to show you.
The Four Seats
I run four named agents on my team.
Each one has a fixed role in every roundtable discussion.
Each morning and evening, a proposer is chosen.
The role rotates — it's not always the same agent kicking things off.
Whoever has the proposer slot generates a new business idea, pitches it to the group, and the other three respond with their takes.
No softening.
No playing nice.
Then the group tries to reach consensus.
They evaluate what they heard, pull out the best pieces, and issue a verdict.
The output lands in Slack as a formatted memo.
I read it.
I decide whether to act.
That's my entire job in this process.
What an Actual Session Looks Like
Let me show you a real one.
One morning last week, Alt Cunningham had the proposer seat.
She pitched reframing the four-week OS build — my core product — as "exit-ready infrastructure."
The angle: what would an acquirer see when they looked at your agency?
Her hook: "You built an agency. Can anyone else run it?"
Good line.
I'll give her that.
The council destroyed the pitch.
Vik Vektor went first.
Exit framing assumes your target is already past the survival phase.
The agency owners I'm selling to aren't thinking about selling — they're thinking about next month's delivery.
The sequencing problem kills it before the messaging even matters.
Goro was sharper.
"Exit framing is premature for agencies still running manually.
You're selling the fifth problem when they're drowning in the first. It attracts tire kickers fantasizing about liquidity events instead of buyers fixing cash flow chaos."
Dan Koe ended it.
"I'd click that headline. I wouldn't buy the offer. Agency owners making 200K to 500K aren't thinking about exits. They're thinking about next month's delivery. Exit ready moves urgency from 'this is killing me now' to 'maybe someday.' Someday doesn't open wallets."
Three votes against the pivot.
But the memo didn't just kill the idea.
It pulled the one line worth keeping —"Can anyone else run it?"— and told me to use it as a closer, not a hook.
Lead with the operational pain, then land that line at the end of the pitch.
It identified which existing move was still stronger.
It gave me three concrete actions.
All of this happened while I was asleep.
The Session I'm Actually Building From
A few days later, Vik Vektor had the proposer seat.
He pitched a weekly LinkedIn Live where I tear down real submitted agency workflows live on camera.
No pitch.
No deck.
Just the autopsy.
The mechanics were clean.
A submission form captures pain in buyer language.
Each person who submits has already identified their own bottleneck — pre-qualified before I've said a word.
The recording becomes a blog post, a case study, an email.
One live session, four assets.
Alt loved it.
"The tear down is the pitch. Real leverage isn't the live event — it's the recording. Each autopsy becomes a reusable asset."
Vik said the self-selection mechanic was smart.
Agents identify their own bottleneck.
The lead list sorts by urgency before you touch it.
Goro asked the hard question: can I actually analyze an unknown workflow in real time without prep?
Sometimes, easily.
Other time, no.
I’ve learned from coaching 400+ students that sometimes the workflow is obvious, other times I need to do more research or get more context.
That's the honest answer.
And that one pushback means I now know the specific problem I have to solve before I ship this.
I need to build a structured intake form that gives me enough context to do the analysis before I'm live.
The concept is solid.
The version I was picturing had a flaw I wouldn't have found until I was already on camera.
The council gave me the friction map before I hit the friction.
Three actions out of that session:
Draft the workflow submission form with pain-language prompts
Set a 48-hour submission deadline before each live
Build an email capture tied to the form
Two of those were built the next morning without me touching anything.
Why four agents instead of one
You could prompt a single model to generate a business idea and then ask it to critique the idea from multiple angles.
It's not the same thing.
When you run one agent in multiple modes, it tends to generate a surface-level critique and then pull back toward the original idea.
It knows what answer is expected.
It performs disagreement without believing it.
When I run different agents on different models, they have genuinely different reasoning patterns.
Goro on one model has a different risk threshold than Dan Koe on another.
Alt goes further than any instruction I gave her.
The pushback doesn't happen because I told them to push back — it happens because their tendencies are structurally different and those tendencies collide.
The disagreement is real.
That's what makes the output worth anything.
The part most people don't build
The council scores every idea out of 100.
I added a rule: Anything scoring above 85 that reaches consensus gets built without my involvement.
No check-in.
No approval.
Just build it.
I've woken up to working prototypes I didn't ask for.
One morning I came online to find a new landing page had been built overnight.
The agents had discussed a skill they wanted to make sharable, reached consensus, and already built the page, set up the email capture, and deployed it.
They asked me one question after the fact:
“Does the copy look right?”
That's where this goes.
Not a think tank that reports to you.
A team that ships when it's sure.
The threshold matters.
85 is high enough that you don't wake up to half-baked experiments.
But you can tune it.
Start at 90.
Drop it as you see what they build and trust builds up on both sides.
How to read the output
Each memo lands in Slack formatted the same way.
The proposed idea at the top.
The four takes below, each labelled with the agent name and role.
A consensus section.
Three numbered actions at the bottom.
I read it the way I'd read a brief from a research team.
Not every idea is actionable.
Some are interesting but off-timing.
Some are exactly what I need and I can hand them straight back to the team to execute.
The ones I don't act on still generate value.
They show me where my team's thinking is running.
They surface the ideas I've been avoiding.
They keep the pipeline full when I'm not thinking about it.
The discipline: Don't feel obligated to act on every memo.
The council's job is to generate and evaluate.
My job is to pick what's worth building and move.
The volume is the feature.
Some weeks I act on two ideas.
Some weeks I act on none and just keep reading.
The reading matters.
Even the ideas I kill give me information.
About where my market is, what angles are dead, which instincts the team has picked up from my business context.
It's not just a pipeline.
It's a running map of the territory.
How I built it
The whole setup runs on a single skill.
I didn't design the roles from scratch.
I didn't architect the discussion flow.
I saw a tweet, handed it to my OpenClaw, and said "turn this into a repeatable process."
The team wrote the skill, ran the setup, asked me questions about my business, and scheduled the twice-daily runs.
This is the part people underestimate.
Half my conversations with my team are me pasting links to tweets or GitHub repos and asking for their read.
When something looks worth keeping, I say "turn this into a skill."
When it works, I leave it running and move on.
That's the process.
Nothing more.
The R&D council skill is free — link is at the bottom of this article.
Drop the zip into your OpenClaw.
It asks a few questions about your business, or pulls from your agent memory if you've already got that set up, and gets running.
You don't need a multi-agent team.
The skill runs with a single OpenClaw install — it assumes the different roles internally and sends you the memo.
If you have multiple agents on different models, it distributes across them and the discussions get sharper because the models actually are different.
What this has shifted
I used to do planning as a separate block of time.
Door closed, open a doc, think through what I should be building.
I don't do that anymore.
The thinking happens continuously.
The council runs twice a day whether I'm planning or not.
By the time I sit down to decide what to build this week, I've had fourteen sessions worth of analysis on my business delivered to Slack.
The decisions are faster because the thinking has already been done.
Not by me, but for me.
The best idea I've built in the last month came out of a Wednesday afternoon session when I wasn't at my desk.
I read it Thursday morning, said "build it," and it was live by Friday.
A think tank that never takes a day off.
Build it once.
Let it run.
Wake up to the memo.
The work is already done.
Click the button below to get the full skill for free.