Your best thinking shouldn't live in one person's head.

Each person starts from scratch differently. A copywriter prompts with their own phrasing. An account manager prompts with theirs. Neither has loaded the client context. The outputs don't match each other or the client's brand, and someone senior has to reconcile them. AI adds velocity to inconsistency.

1. Designate one primary AI interface for production work — the tool your team uses when they're making things, not exploring.
2. Build intake prompts for the most common starting points: brief distillation, client context load, voice calibration, pitch structure.
3. Define a review gate — everything that goes to a client gets a human read before it leaves the building.
4. Assign a quality owner for each output type: creative director for copy and concepts, account lead for status and reporting.
5. Log what AI produces and what gets changed — you'll find patterns that improve your skills faster than any other practice.

• A copywriter opens a voice-calibrated session using the client's voice profile — first draft is already calibrated to the client's brand, not a generic starting point.
• An account manager runs a brief distillation on 40 pages of stakeholder input — extracts the actual creative problem in 10 minutes rather than three briefing sessions.
• A CD uses a pre-read skill before every client presentation — reads the brief history, previous decisions, and client's stated sensitivities to produce a 10-line context summary before the call.
• A new junior copywriter produces on-brand work for an account they've never touched by loading the client knowledge file before they start writing.

Junior outputs require heavy CD revision because there's no encoded standard for what "good" looks like on this account. Pitches are rebuilt from scratch each time because the structure that worked last time lived in someone's head. Scopes are inconsistent because each account manager approaches them differently. The CD becomes the bottleneck not because they want to be, but because they're the only quality gate.

1. List the five tasks where you most often think "I'll need to revise this before it goes to the client." Those are your first skills to build.
2. For each task, write a skill brief: what context to load, what to produce, what format, what the CD would check on review.
3. Build evaluation criteria — not just "does it sound right" but specific, checkable outputs. What would make the CD approve it without revision?
4. Run each skill three times on real client work before relying on it in production.
5. Update skills when the same correction appears twice — that correction is a skill refinement, not a quality problem.

• Brief distillation: reads a raw client brief and extracts the real creative problem, the audience, the tone constraints, and the measurable success criteria.
• Voice calibration: reads a client's voice profile and recent work samples, calibrates AI outputs to match the client's specific register.
• Pitch structure: takes a brief and produces a first-draft narrative structure for a client presentation, in the agency's preferred approach.
• Scope builder: takes a brief and outputs a project scope with line items, rationale, and dependencies.
• Debrief synthesis: reads post-project notes and extracts learnings for the knowledge layer — so the next campaign on this account starts smarter.
• Status report: reads the current project state and produces a structured client status update in the agency's preferred format.

clients/
  [client-name]/
    account-brief.md      ← who they are, business context, goals
    voice-profile.md      ← how they sound, examples, do/don't
    relationship-log.md   ← conversations, decisions, sensitivities
    history-log.md        ← what we've made, what worked, what didn't
    campaigns/
      [campaign-name]/
        brief.md          ← distilled creative brief
        production/       ← in-progress work
        feedback-log.md   ← client feedback, round by round
        review-notes.md   ← CD review notes per round
        deliverables/     ← approved outputs

agency/
  process-library/        ← how we work
    brief-intake.md
    pitch-structure.md
    scope-template.md
    review-criteria.md
  pitch-archive/          ← past pitches, what won, what didn't
  new-hire-context.md     ← what someone needs to understand us

• Every client account has its own folder. AI reads the account folder before producing anything for that client.
• After every client interaction, a team member adds a one-line update to the relationship log.
• After every CD review, review notes go into the campaign folder. Patterns that appear twice become skill updates.
• Approved deliverables move to the records layer. In-progress work stays in the project layer.
• The voice profile is updated after every major campaign — not just at account setup. Voice compounds only if it's maintained.

• Before starting a new campaign for a long-standing client, AI reads the account brief, voice profile, and history log — the first draft already reflects 18 months of relationship context.
• After a client presentation, an account manager adds a note to the relationship log about what the client reacted to. Two months later, a different team member benefits from that note without needing to be debriefed.
• A CD's review notes from a brand campaign are synthesized into a voice profile update — the next copywriter who touches this account doesn't make the same mistakes.

AI outputs are generic because AI has no context to make them specific. Voice calibration is manual every time because there's no voice profile to reference. New team members produce off-brand work for months because the brand isn't written down anywhere useful. When a senior person leaves, everything they knew about an account goes with them. The CD reviews everything because they're the only accessible source of context.

1. Client voice profiles: one per active account. Tone, vocabulary, rhythm. Real examples of writing you're proud of, with notes on why it works. Do's and don'ts specific to this client, not generic brand adjectives.
2. Account context files: who they are, what they're trying to do, what they've tried that didn't work, what the CD always says about them. Written in the voice of an experienced team member briefing a new one.
3. Process library: how your agency works — how you scope, how you present, how you give feedback, how you onboard a new client. The unwritten rules, written.
4. Pitch archive: past pitches with notes on what won and what didn't. Patterns that appear across wins are your competitive intelligence.
5. New hire context file: what someone needs to understand to work at this agency — the standards, the clients, the culture, the judgment calls that are never explained but always expected.

Most "brand voice" documents are useless for AI calibration because they describe the voice in adjectives rather than demonstrating it in actual writing. A useful voice profile contains:

• Sentence rhythm patterns: short declarative → longer elaboration → question or pivot. Specific to this client. With examples from approved work.
• Vocabulary set: words this brand uses and words it would never use. Not just formal/informal — specific word-level choices that characterize the voice.
• Structural patterns: does this brand open with a claim or a question? Does it use subheadings? Does it reference the reader directly? Where?
• Calibration examples: 3–5 pieces of approved work you'd use to show a new writer what "on-brand" looks like. The more specific the better.
• Common corrections: what the CD always changes when writing comes back from junior team members. These are the calibration targets.

Every new project reinvents the wheel because past work isn't findable. New hires can't learn from case studies because the approved work is scattered across personal drives, email threads, and Dropbox folders nobody manages. A client asks for the final version of a brand guide from 18 months ago and nobody can find the approved file with confidence.

1. Designate a single, consistent location for approved final work — separate from project workspaces.
2. Establish a clear rule: a draft lives in the project layer until a client approves it. Only approved final versions move to records.
3. Build a searchable index — a simple text file that lists what's in the archive and why it matters. AI reads indices, not folder structures.
4. After every major campaign, write a one-page post-mortem that lives alongside the records: what worked, what didn't, what to do differently.
5. Define who can access what: client-approved work is usually sharable; signed contracts and financial documents are not.

A records layer that just stores files is an archive. A records layer that's structured for AI use is a compounding competitive asset. The difference:

• Add a one-paragraph annotation to every major piece of archived work: what brief this answered, what made it succeed, what the client said about it.
• Tag archives by what they're useful for: "voice calibration example," "pitch structure reference," "tone under-pressure example."
• Build a case study source file for each client — a structured account of what you did, what you learned, and what you'd do differently. AI reads this when starting a new campaign.