Chapter 5: Build Your Brief Builder Gem


Priya's First Win

Priya had tried ChatGPT. She'd tried Claude. She'd even paid for Jasper for three months. Every time, the same pattern:

Copy a client email. Paste it into the AI. Get a generic brief that didn't match her format. Spend 30 minutes fixing it. Conclude that starting from scratch was faster.

"AI is overhyped," she told her team. "It doesn't understand our work."

Then a friend showed her Gems.

"The difference is you teach it YOUR way," the friend said. "Give it your template. Your sections. Your tone. It stops being generic when you stop giving it generic instructions."

Skeptical, Priya tried it. She copied her actual brief template into a Gem. She added context about her typical clients—Fortune 500 marketing teams, nonprofit development directors. She specified her format.

Then she pasted a messy client email into the Gem.

What came out wasn't perfect. But it was 80% there. Her sections. Her language. Her format. Ten minutes of editing instead of forty-five minutes of writing.

"Okay," she said. "Maybe I was doing it wrong before."

The First Good Draft - the moment AI produces something usable


What You're Building

The Brief Builder Gem takes messy client input and turns it into a structured creative brief.

Input: Client call transcript, scattered notes, email thread, or voice memo transcription

Output: Professional creative brief with:

Time savings: 60 minutes → 10-15 minutes per brief


Exercise 5.1: Create the Brief Builder Gem

Goal

Build a working Brief Builder Gem using the instruction formula.

Time: 15 minutes

Steps

  1. Go to gemini.google.com → Gem manager → Create new Gem

  2. Name: "Brief Builder"

  3. In the instructions field, paste the following (then we'll customize it):

## Role
You are a creative brief writer for a video production studio. You transform messy client communications into clear, actionable creative briefs.

## Task
When I give you client notes (from calls, emails, or messages), create a structured creative brief that my team can use to start work.

## Output Format
Structure the brief with these exact sections:

**PROJECT OVERVIEW**
[2-3 sentences: Who is the client, what do they want, why are they doing this project]

**DELIVERABLES**
[Bullet list of specific items we're creating]
- Primary deliverable:
- Secondary deliverables (if any):

**TIMELINE**
- Project start: [date or "TBD"]
- Key milestones: [if mentioned]
- Final delivery: [date or "TBD"]

**BUDGET CONTEXT**
[What's the budget range? If not mentioned, write "Not discussed - needs clarification"]

**SUCCESS CRITERIA**
[How will we know this project succeeded? What does the client really want?]

**OPEN QUESTIONS**
[List anything unclear that needs client clarification before we proceed]

## Style Guidelines
- Be direct and specific, not vague
- If information is missing, flag it in "Open Questions" rather than inventing it
- Use the client's language when describing what they want
- Keep total brief under 400 words

## Context About My Business
I run a video production studio. Our typical projects include:
- Corporate promotional videos ($5K-$20K)
- Social media content packages ($2K-$8K)
- Event coverage ($3K-$10K)

Our clients are usually marketing teams or business owners who know what they want but not how to describe it technically.
  1. Customize the context: Edit the "Context About My Business" section to match YOUR studio:

    • Your typical project types
    • Your price ranges
    • Your typical clients
  2. Save the Gem

Check Your Work

Before testing, verify:


Exercise 5.2: Test With Real Client Input

Goal

Test the Gem with actual client communication.

Time: 10 minutes

Steps

  1. Find ONE of these from a recent project:

    • Client call notes
    • Email thread with project discussion
    • Voice memo transcription
    • DM conversation about a project
  2. Open your Brief Builder Gem

  3. Paste the client input and send

  4. Review the output:

    • Does it capture the key information?
    • Is anything wrong or missing?
    • Would you send this to your team?
  5. Rate the output:

Dimension Rating (1-5)
Accuracy _____
Completeness _____
Formatting _____
Usefulness _____

Interpretation


Exercise 5.3: Iterate and Improve

Goal

Make the Gem better based on actual output.

Time: 10 minutes

Steps

Based on your test, identify what needs to change:

Problem Instruction Fix
Output too long Add stricter word limit
Missing section Make that section more prominent in instructions
Wrong tone Add specific tone guidance
Inventing details Emphasize "flag as Open Question if unknown"
Wrong priorities Reorder sections or add weighting instructions

My specific issue: ________________________________________________

My fix: ________________________________________________

Now:

  1. Go back to Gem manager
  2. Edit the Brief Builder Gem
  3. Implement your fix
  4. Save
  5. Test again with the same input
  6. Did it improve? Y / N

Repeat Until Satisfied

This iteration process IS the skill. Most Gems need 2-3 rounds of refinement before they're production-ready.


The Final Brief Builder Prompt (Reference)

After iteration, your Brief Builder should look something like this:

## Role
You are a creative brief writer for [YOUR STUDIO NAME], a [your specialty] studio based in [location].

## Task
Transform client communications into actionable creative briefs my team can immediately use.

## Output Format
**PROJECT OVERVIEW**
[2-3 sentences: client, project, purpose]

**DELIVERABLES**
- Primary:
- Secondary:

**TIMELINE**
- Start:
- Milestones:
- Delivery:

**BUDGET CONTEXT**
[Range or "Not discussed"]

**SUCCESS CRITERIA**
[What "done well" looks like]

**OPEN QUESTIONS**
[Everything unclear - must have at least one item or write "None - all clear"]

## Style Guidelines
- Maximum 350 words
- Flag unknowns, never invent
- Use client's own words for their goals
- Be specific: "short video" → "60-90 second video"

## Context
[YOUR BUSINESS CONTEXT - 2-3 sentences about typical work]

Exercise 5.4: Validate With a Second Test

Goal

Confirm the Gem works on different types of input.

Time: 5 minutes

Steps

  1. Find a DIFFERENT piece of client input (different project, different client)

  2. Run it through the Brief Builder

  3. Confirm:

    • [ ] Output follows the same structure
    • [ ] Quality is consistent with first test
    • [ ] No new problems appeared

If the second test fails, you may have over-fitted the instructions to your first example. Generalize the instructions and test again.


What You Built

You now have a working Brief Builder Gem that:

Estimated time savings: 45-50 minutes per project

Weekly impact (if you do 3 projects): 2-2.5 hours back


Knowledge Check

Before Chapter 6:

  1. How many test-and-iterate cycles did your Gem need? Your answer: _____

  2. What was the main improvement you made? Your answer: ________________________

  3. Does the Gem produce output you'd actually send to your team? Your answer: Y / N

If "N" — keep iterating. The Gem should be good enough to use, not just good enough to exist.


Chapter Time: ~40 minutes

Next: Chapter 6 — Build Your Scope Creep Detector Gem