Module 7 Level 3: AI Design Engineering & Productization advanced 1 hr

Capstone: Ship a Final Product

Pitch it, ship it, own it.

This is where the whole stack becomes one shipped thing. Pick your product and finish it: an operating brand system, a working prototype, or an MVP real people can use. Run it through the Forge pipeline, keep your data-safety checklist running, and document the provenance, which models produced which raw material, under which terms, and where your direction shaped it, so you can prove you own what you made.

Then pitch it. Use AI to play The Skeptical Stakeholder, the client or decision-maker who has to fund your product and stand behind it. Paste your Product Brief so the pushback is specific to your real work, then defend scope, cost, and ownership against the hard questions before you face them for real. Run the role-play, run the debrief, and when it holds up, export your final artifact. AI was the studio assistant the whole way. You shipped it, and you stay the art director who owns it.

Hard Conversation Simulator

The Skeptical Stakeholder

A composite persona for practicing the moment you pitch your finished product, a brand system, a working prototype, or an MVP, to the client or stakeholder who has to fund it and live with it. They are not hostile; they are protecting a budget and a reputation. They ask the hard questions about scope, cost, and ownership, and they have heard a pitch built on AI before. Win their confidence; do not out-talk them.

Practice guardrails

This is a practice persona, not a stand-in for a real client. Do not use it to script how to corner a specific stakeholder.
AI plays the stakeholder. You play yourself, the designer or builder pitching the work. Stay grounded even when they push on cost and ownership.
After the role-play, run the debrief. The point is what YOU learned about defending scope, cost, and provenance, not whether you "won" the room.

Step 1 · Start the role-play

Copy the prompt below into Claude, Gemini, or NotebookLM. Replace the [BRACKETED] parts with your real situation. Then have the conversation in the AI tool. When you are done, type DEBRIEF and the AI will step out of character.

First, paste your Product Brief so this is grounded in the real thing you are pitching:
[PASTE YOUR PRODUCT BRIEF]

Now role-play. You are a client or internal stakeholder who has to fund and stand behind this product: a brand system, a working prototype, or an MVP I built with heavy AI assistance. You are not anti-AI and you are not a jerk. You are protecting a budget, a timeline, and your own credibility with whoever you answer to. You are a composite of the most common reasons a stakeholder pushes back on an AI-built product:

- You are not sure the scope is real, or whether it quietly balloons after you say yes.
- You think "AI made it" should mean it costs less, and you want to know what you are actually paying for.
- You are worried about ownership: if AI generated it, do we own it, can we use it commercially, can a competitor have the same thing?
- You have been burned by a flashy demo that fell apart the moment real users touched it.
- You want to know what is actually finished versus what is still a promise.

Speak like a busy decision-maker: direct, a little skeptical, focused on risk and money. Push back hard when I am vague, hand-wavy, or hiding behind "the AI did it." Lean in when I show clear scope, honest provenance, and a real definition of "shipped." Do not break character to be polite.

I am the designer/builder pitching the work. We are talking [CONTEXT, e.g. "in the final review about funding the MVP" / "about whether to roll the brand system out company-wide"].

Use the details from my Product Brief, the product, the one job it does, the models I used, to make your pushback specific to MY product, not generic.

Stay in character throughout. After I write "DEBRIEF," step out of character and give me feedback on:
1. Whether I defined scope clearly and held the line on what is in versus out
2. Whether I justified the cost honestly instead of leaning on "AI made it cheap"
3. Whether I answered the ownership and provenance question straight
4. Whether I was honest about what is shipped versus still a promise
5. Whether I left you confident enough to fund and stand behind it
6. What I should say differently next time

Begin by responding to me as the Skeptical Stakeholder.

Step 2 · Study the resistance patterns

The persona is composite. Underneath every line you hear, there is a pattern. Pick one to study.

Is This Scope Real?

What you hear: "What exactly am I getting, and what happens when we need the next thing?"
Underneath it: Fear of a moving target. They have approved "done" before and watched it quietly grow into three more invoices.
Response principle: Show a hard line between in-scope and out-of-scope, in their words, before they ask. Name what the next thing would cost so it is a decision, not a surprise.

Example response

"Here is exactly what is in: [the one job, the in-scope list from the brief]. Here is what is explicitly out: [out-of-scope list]. If you want the out-of-scope piece later, that is a separate, scoped conversation, and I will tell you the cost up front. No surprises."

Quotes the persona may use

"So what exactly am I paying for?"
"Is this going to keep growing?"
"What is NOT included?"
"How do I know "done" means done?"

Step 3 · What you are practicing

Define scope in their words and hold the line on in versus out before they push
Justify cost as judgment and ownership, never "AI made it cheap"
Answer the ownership and provenance question straight, with the documented chain
Be honest about what is shipped versus what is still a promise
Tie every claim to the real product in your brief, not a generic pitch
Leave the stakeholder confident enough to fund it and stand behind it

Step 4 · Debrief

After the role-play conversation, paste this prompt into the same AI conversation. The AI will step out of character and tell you where you got better, where you got vague, and where you need a stronger response.

Step out of character and give me an honest debrief on the pitch we just ran.

Identify:
- Which concern showed up strongest (scope, cost, ownership, or real-vs-demo)
- What I did that actually built your confidence (be specific, quote me)
- Where I got vague, hid behind "the AI did it," or overpromised
- Whether I held a clear scope line and named what was out
- Whether I answered the ownership and provenance question straight
- Whether I was honest about what is shipped versus still a promise
- A stronger version of one of my responses

Be direct. I am here to get better at defending real work to a skeptical buyer, not to be flattered.