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 tasks for the most common starting points: brief distillation command, tone of voice skill, pitch template.
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 writes a draft using the client's tone of voice skill. The 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. It extracts the actual creative problem and writes the brief in 10 minutes rather than three briefing sessions.
• A designer produces on-brand work for an account they've never touched by loading the client knowledge file before they start creating concepts.
• A CD uses a presentation alignment skill before every client presentation. It reads the brief history, previous decisions, and the client's stated sensitivities to produce a 10-line context summary before the call.

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 brand 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 current campaign 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, so the next draft addresses what actually changed instead of guessing.
• Approved deliverables move to the records layer. In-progress work stays in the project layer.
• When a campaign hands off between team members, the incoming person reads the current brief and feedback log first, not the account's full history.

• A production designer picks up a campaign mid-flight and reads the current brief and feedback log to see exactly what's approved and what's still open, without pinging the account lead to catch up.
• After a round of client feedback, the account manager logs it directly against the campaign. The copywriter's next draft addresses round two instead of guessing what changed.
• A campaign pauses for two weeks over the holidays. The person who picks it back up reads the review notes and resumes exactly where the last round left off, instead of re-reading a month of email.

AI outputs are generic because AI has no context to make them specific. Voice calibration is manual every time because there's no brand 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. Process library (agency context, build this first): how your agency works, how you scope, how you present, how you give feedback, how you onboard a new client. The unwritten rules, written.
2. New hire context file (agency context, build this first): what someone needs to understand to work at this agency, meaning the standards, the culture, and the judgment calls that are never explained but always expected.
3. Client brand profile (client context, build one per account): the client's business, their audience, their competitive position, what makes them distinct, and how they sound. Owned by the account lead, not just the writers.
4. Account history (client context, build one per account): 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.
5. Pitch archive (agency context, grows with every account you win or lose): past pitches with notes on what won and what didn't. Patterns that appear across wins are your competitive intelligence.

Most "brand voice" documents stop at voice, which is useful to the writer and designer producing the work but incomplete for the account lead directing it. A useful client brand profile contains:

• Business context: what the client does, who their audience is, what they're trying to achieve, and where they sit against competitors. This is what an account lead references most.
• Decision-makers and sensitivities: who signs off, what they've reacted badly to before, and what's off-limits.
• Voice and tone: sentence rhythm, vocabulary this brand uses and would never use, and structural habits (does it open with a claim or a question, does it use subheadings), demonstrated with real examples rather than adjectives.
• Calibration examples: 3 to 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.