1
Context stays coherent
If Manny separately chats with the copywriter, designer, and funnel builder, each one ends up with a partial version of the truth. The manager keeps one current brief and passes the right slice to each worker.
Agent architecture recommendation
Use a manager agent. Do not chat with every specialist.
Direct specialist access feels like more control. At scale, it usually creates more context drift, more coordination work, and weaker accountability.
The core idea
The human should manage the outcome, not the org chart. A Marketing Manager agent keeps the business goal, campaign strategy, brand standards, constraints, and current state in one coherent place. Then it calls specialist sub-agents as tools to get the work done.
You talk to the Marketing ManagerOwns the campaign goal, brief, priorities, memory, and final quality.
CopywriterDrafts hooks, emails, VSL, ads.
DesignerBuilds layout and visual direction.
Funnel BuilderAssembles pages and flows.
QA / ResearchChecks claims, polish, and fit.
Why this is the better default
2
The human stops being the project manager
Direct access makes Manny responsible for remembering who knows what, which version is current, and whether the copy still matches the funnel. That is exactly the work the agent system should absorb.
3
Parallel work becomes easy
A manager can run research, copy, design, funnel structure, and QA at the same time. If the human controls every specialist thread manually, the human becomes the bottleneck.
4
Accountability is cleaner
When the funnel underperforms, the answer should not be "which sub-agent did it?" The Marketing Manager owns the output and uses specialists to improve it.
5
Specialists optimize too narrowly
A copywriter may write stronger copy that hurts the funnel. A designer may make the page prettier but less direct. The manager balances tradeoffs against the business objective.
6
Telegram stays usable
If every specialist becomes a Telegram contact, the interface turns into noise: more threads, repeated explanations, and harder retrieval. A few high-level agents keep the system manageable.
7
Memory belongs at the campaign level
The manager can remember what was tried, what was rejected, what the brand voice is, and what the current launch goal is. Sub-agents can remain task-specific and disposable.
8
You still keep control
Control should live in the brief, standards, constraints, approval gates, and final review. Manny can still ask for the copywriter's reasoning or three variants without making that copywriter a permanent chat relationship.
Direct specialist chats
- Many threads with partial context.
- Human coordinates handoffs.
- Workers optimize their own lane.
- Harder to know who owns the final result.
- More interruptions and more repeated briefing.
versusdefault pattern
Manager orchestration
- One front door for the business goal.
- One owner for campaign state.
- Specialists run in parallel behind the scenes.
- Clear accountability for the assembled output.
- Cleaner memory and less Telegram noise.
What Manny should control
- The objective: revenue, leads, booked calls, launch assets, speed.
- The brief: audience, offer, objections, proof, voice, constraints.
- The standards: examples, non-negotiables, approval gates.
- The output: accept, reject, revise, compare variants.
What the system should control
- Which specialist gets which sub-task.
- When specialists run in parallel.
- How drafts get handed from copy to design to funnel build.
- When QA loops work back to a specialist before the human sees it.
The reasonable compromise
Direct sub-agent access can exist, but it should be an exception, not the default. A good compromise is "workshop mode": Manny can talk directly to the copywriter for a short, intentional session, then the Marketing Manager ingests that transcript and resumes ownership of the campaign.
This preserves the feeling of control without turning every specialist into a permanent coordination burden.
Simple operating rule
- If the conversation is about the business outcome, campaign strategy, priorities, or final approval, talk to the manager agent.
- If the conversation is a short deep dive into one specialist's reasoning, use temporary specialist access.
- When the deep dive is done, route the conclusion back through the manager so the system memory stays clean.
Use direct specialist access for moments of insight. Use manager orchestration for production work.That gives Manny control without making him the bottleneck.