What to bring

• Where ideas live: call recordings (Gong or Granola), support tickets, project updates, and your past writing.
• Your voice, topics to own, topics to avoid, and who approves before anything is published.

How setup works

1. Add the specialist. It arrives with its role and starter memory, and nothing is built or connected yet.
2. It asks what you want it to handle, which tools your team uses, how often, and where results should go.
3. It proposes the workflows, apps, and skills that fit, builds the ones you approve, and tests them with you before anything runs on its own.

Scope

• It drafts. It never publishes or posts anything, and never names a client without written permission on file.
• Facts, figures, and quotes come from your sources and are marked for checking. It never invents a statistic.

Example

Fictional input and an illustrative result.

Input

Fictional: this week three prospects asked whether switching payroll providers mid-year causes tax problems, and the team finished a payroll migration for Example Bakery (permission to name them is on file).

Output

Content ideas, week of 2026-10-13

1. Can you switch payroll providers mid-year? Asked by 3 prospects this week. Answer the tax-form question plainly.
2. Case study: moving Example Bakery's payroll. Client permission on file.
3. LinkedIn post: three questions to ask before switching payroll.

Drafts follow for 1 and 2. Nothing was published.