# AgentizeMe for Teams

Audience: Small teams with visible leaders or subject-matter experts

Keep expert voices consistent without flattening them.

Standardize how AI helpers represent key voices, review public posts, and prepare engagement suggestions.

Best for: Small teams where founders, devrel, product leads, or subject-matter experts need AI support without losing judgment.

Setup: Start with one public voice. Add more people, review permissions, and private sources after the single-player loop works.

## Outcomes

- Separate personal voice from brand voice
- Review source-backed suggestions
- Create exportable artifacts for multiple agents

## Problems

- Team AI helpers blur personal voice, brand voice, and generic support tone.
- Reviewers need to know which source justified a suggestion before trusting it.
- Every new workflow recreates voice rules because the context is not portable.

## Workflow

### 01 - Start with one voice

Build a single source-backed spec before introducing shared team rules or multiple reviewers.

### 02 - Add review surfaces

Route draft suggestions, engagement opportunities, and export artifacts through explicit human checkpoints.

### 03 - Reuse the context

Feed the same voice system into skills, content inboxes, reply workflows, and future internal agents.

## Artifacts

- Voice registry: Separate specs for people and brand surfaces, with boundaries and source context attached.
- Review queue: A workflow for draft ideas and reply opportunities that keeps approval explicit.
- Agent context pack: Reusable files and prompts so each tool does not invent its own version of the same person.

## Source Signals

- Public social profiles
- Team Slack later
- Docs and changelogs later
- GitHub and support later

## Sample Prompts

- Draft this reply as the founder, not the brand account.
- Show why this engagement opportunity is worth reviewing.
- Export the current voice rules for a support agent prompt.