Great post. Love seeing how teams are building. Just here to add Obsidian into the conversation around knowledge base / context layer. It’s been mentioned on this Substack before and is my favorite digital tool—period. User-friendly, no lock-in (it’s just .md files), and the community plugins make it super extensible for every use case.
I tried one bot for all of marketing and killed it. Too much for one agent to hold. What works is one bot per outcome. Competitor intel came first, then research, then content. The orchestrator that sits above them can wait until handing work between them actually hurts. Danny’s slice-of-the-funnel model is the same instinct, just at a bigger scale. The chief of staff agent is the one everyone wants to build first, me included but it’s the last one you need.
Great post. Love seeing how teams are building. Just here to add Obsidian into the conversation around knowledge base / context layer. It’s been mentioned on this Substack before and is my favorite digital tool—period. User-friendly, no lock-in (it’s just .md files), and the community plugins make it super extensible for every use case.
I switched over to obsidian for the MKT1 team and love it. Part 3 of this series is about our set up so will talk it up there!
I tried one bot for all of marketing and killed it. Too much for one agent to hold. What works is one bot per outcome. Competitor intel came first, then research, then content. The orchestrator that sits above them can wait until handing work between them actually hurts. Danny’s slice-of-the-funnel model is the same instinct, just at a bigger scale. The chief of staff agent is the one everyone wants to build first, me included but it’s the last one you need.