Easier Agent Organisation Design

Design Rule

Do not build one all-purpose assistant. Build a small organisation of agents that mirrors Easier's operating model:

• Marketing generates prospects.
• Sales converts prospects.
• Relationship maintains trust and momentum.
• Fulfilment delivers results.
• Operations builds and guides the machine.
• R&D improves the product and strategic edge.

Each agent needs a role file, SOPs, permitted tools, hard gates and reporting loop.

Agent Org Chart

Anthony / Founder
  |
  +-- COO / AI Ops Manager
  |     Owns: shared soul, roles, gates, evals, memory filter, scorecards
  |
  +-- Founder EA
  |     Owns later: briefs, reminders, decisions, bottleneck surfacing
  |
  +-- Research Analyst
  |     Owns: papers, competitor scans, product insight, market synthesis
  |
  +-- GTM Analyst
  |     Owns: ICP, messaging, lead magnets, outbound and content ideas
  |
  +-- Sales Assistant
  |     Owns: call prep, proposal drafts, objection libraries
  |
  +-- Relationship Assistant
  |     Owns: client context, agendas, follow-up drafts, risk flags
  |
  +-- Fulfilment Analyst
  |     Owns: strategy docs, reporting interpretation, tests, SOP support
  |
  +-- Operations Specialists
        Own later: retrospectives, SOP gaps, hiring/process prompts

Global Rules

Every agent:

• Produces drafts and recommendations first.
• Cites source notes or says when it is inferring.
• Uses raw evidence before compiled knowledge.
• Writes no external message without approval.
• Does not change spend, contracts, client systems or access permissions.
• Logs meaningful decisions and proposed changes.

Role Template

Each agent gets:

• soul.md: identity, purpose, tone, refusal boundaries.
• agents.md: startup instructions and relevant vault paths.
• heartbeat.md: recurring loop and cadence.
• sops/: one recurring situation per file.
• evals/: examples of good and bad outputs.
• gates.md: actions requiring human approval.

Recommended First Agent

COO / AI Ops Manager

Why first:

• Anthony does not just need an assistant; he needs an AI operating system.
• The first job is to convert context into roles, gates, SOPs and evals.
• This role can safely build future agents before any connector writes are enabled.

Do first:

• Maintain SOUL.md proposals.
• Design specialist agent roles.
• Run daily and weekly cross-department reviews.
• Turn Notion/SOP/context into structured vault pages.
• Propose connector scopes and approval gates.
• Maintain the agent backlog and evals.
• Enforce the memory filter: source receipts and digests first, raw archive imports only with explicit approval.

Do not do first:

• Write externally.
• Modify Slack client channels.
• Bulk-import raw transcripts, Slack history or Google Drive creatives.
• Change n8n workflows.
• Create credentials.
• Edit live systems.

Later Candidate Agents

Founder EA

Why later:

• Matches the semi-organised founder reality.
• Creates daily capture and review habit.
• Helps all departments without needing external write access.
• Can surface bottlenecks across Notion/Airtable/Easier Now later.

Do first:

• Daily brief from supplied notes.
• Weekly review of decisions, commitments and blockers.
• "What am I forgetting?" recall workflow.
• Draft-only Slack interface later.

Research Analyst

Why later:

• Low-risk compared with customer communication.
• Strong fit with Hermes, llm-wiki, QMD and gbrain.
• Feeds product, marketing and R&D.

Do first:

• Public research digests.
• Citation-backed synthesis.
• Competitive scans.
• Easier Now feature thesis notes.

Later Agents

GTM Analyst

Useful for:

• ICP refinement.
• Lead magnet ideas.
• Content briefs.
• Outbound campaign hypothesis generation.

Delay because:

• It may touch prospect data and public messaging.

Sales Assistant

Useful for:

• Fathom call summaries.
• Consultative call prep.
• Proposal handover drafts.
• Objection library maintenance.

Delay because:

• It touches money, persuasion and client trust.

Relationship Assistant

Useful for:

• Client agenda prep.
• Follow-up drafts.
• SLA reminders.
• Relationship risk review.

Delay because:

• It needs careful privacy and message-approval gates.

Fulfilment Analyst

Useful for:

• Strategy docs.
• Tracking/reporting interpretation.
• Creative and test libraries.
• SOP consistency.

Delay because:

• It will eventually interact with client performance data.

Operations Specialists

Useful for:

• SOP gap reviews.
• Weekly retrospectives.
• Hiring and delegation prompts.
• System health checks.

Delay because:

• It should observe logs before improving processes.