
Aki Wijesundara
Manu Jayawardana

"You are my Chief of Staff."
Your job, priorities, what matters this quarter.
Tell it exactly what to do, not vague asks.
Bullet brief? Table? Draft email? Say it.
What to skip, what to prioritize, length limits.




Every task your AI Chief of Staff runs follows this pattern. It is the whole configuration. Once your prompts encode it and your connectors give it the reach, every ask lands the same shape: retrieved context, structured analysis, an actionable artifact, and a nudge toward the next high-leverage move.

Feed it your notes or transcript, and the follow-up work compresses to a review pass.


Search your docs. Pull past decks. Attach relevant files to briefings.
Triage messages the same way you triage email. Draft replies inline.
Automate the handoff. When one task ships, the next one fires.
Write updates and one-pagers directly into your workspace, not a chat.
Pre-built GPTs: research assistants, writing coaches, data analysts · all configurable to your workflow. The store is a shortcut to configurations someone else already tested.
Hands-on, portfolio-ready. Build multi-agent systems, RAG pipelines, and production AI workflows for PMs, founders, and operators. Where the master prompt becomes a shipped product.


The people whose calendars stop owning them are the people whose day starts from a briefing, not from a scroll. Your AI Chief of Staff is only as good as the frequency you use it. Barely anything. Highest-leverage move on your calendar.
For PMs, founders, and operators. Build multi-agent systems, RAG pipelines, and production AI workflows. Cohorts start monthly.
Where this leadsPost one line: what task would your Chief of Staff run first. Aki or Manu will draft the prompt for it live.
Open floorSave the version you land on after a week. Email it to us. We reply with a short audio review before the bootcamp starts.
The receipt