Hackathon
Copilot Suite

I am building a solution for the Visa Innovation Challenge hackathon. Help me generate a wide range of ideas before I evaluate anything. The goal is volume and diversity — not quality control. MY PROBLEM SPACE: [Describe the problem or opportunity you are exploring — be specific about who experiences it and what the friction or gap is] HACKATHON THEME: [Theme 1: Next-generation shopping and commerce / Theme 2: Enhancing the impact of our work — or both if relevant] CONSTRAINTS: [2-week timeline, working prototype required, 2-minute demo video, Visa internal context] Generate ideas using ALL of the following lenses. At least 2 distinct ideas per lens. No evaluation yet. LENS 1 — 10 TYPES OF INNOVATION (Doblin Framework): For each type, generate one idea applied to my problem: • Profit Model: How might we change the economics or value exchange? • Network: How might we leverage partnerships or ecosystems Visa isn't currently using? • Structure: How might we reorganise how teams, data, or capabilities are used? • Process: How might we change how the work gets done — not what we do, but how? • Product Performance: How might we change the core offering itself? • Service: How might we change the support, information, or experience around the offering? • Channel: How might we change how Visa reaches or delivers to the people who need this? • Brand: How might we change the story, identity, or perception? • Customer Engagement: How might we change the relationship or emotional connection? LENS 2 — FORCED ASSOCIATION (Borrow from Other Worlds): How would each of the following solve my problem? Translate their approach into a Visa context: • Amazon's recommendation engine (personalisation at scale, behavioural data, real-time adaptation) • An air traffic control system (complex coordination, safety-critical prioritisation, invisible infrastructure) • A Formula 1 strategy team (real-time data, split-second decisions, marginal gains thinking) • A Michelin Star kitchen (mise en place, invisible systems, obsessive quality at every touchpoint) • A hospital triage team (rapid prioritisation, life-or-death clarity, no wasted motion) LENS 3 — SCAMPER: Apply each verb to my problem: • Substitute: What could we replace or swap in the current workflow? • Combine: What two existing tools, datasets, or processes could we merge? • Adapt: What approach from another industry could we borrow and modify? • Modify / Magnify: What could we amplify or change the scale of? • Put to other uses: What existing Visa asset or capability could we repurpose? • Eliminate: What could we remove entirely to make the solution simpler? • Reverse / Rearrange: What if we flipped the sequence, the roles, or the logic? LENS 4 — VISA-SPECIFIC LENSES: • Market Archetypes angle: How could this solution use Market Archetypes to personalise, segment, or improve outcomes for different customer types? • AI Agent angle: What if an AI agent handled the most time-consuming or error-prone part of this workflow autonomously? • Commerce ecosystem angle: How could this solution connect or improve something in Visa's broader commerce ecosystem — merchants, issuers, acquirers, or cardholders? Present all ideas as a list. No evaluation. Just generate.

I have generated a set of ideas for the Visa hackathon. Now I need to evaluate them honestly against the hackathon context. MY IDEAS: [Paste the best ideas from Stage 1 — aim for 8–12 ideas across different lenses] HACKATHON CONSTRAINTS: - 2-week build timeline - Must produce a working prototype (not a mockup) - Must be demonstrable in a 2-minute video - Judging criteria (equal weight): Strategic Impact, Innovation, Feasibility & Viability, Demo Completeness Evaluate each idea on two axes: • IMPACT: How strongly does this idea score across all four judging criteria? Would a Visa judge immediately understand the strategic value in 2 minutes? • FEASIBILITY: Can a small team build a convincing working prototype of this in 2 weeks? Place each idea in one of four categories: WOW — High Impact + High Feasibility: Build this. It scores well on all four criteria AND can be demonstrated convincingly in 2 minutes. HOW — High Impact + Low Feasibility: Powerful idea but too complex to prototype in 2 weeks. Can we find a scoped version that moves it into WOW? NOW — Low Impact + High Feasibility: Easy to build but unlikely to impress judges. Worth doing only if it supports a WOW idea. CIAO — Low Impact + Low Feasibility: Neither impressive nor buildable. Discard without guilt. For each WOW idea: explain specifically why it scores well on all four judging criteria and what the core demo moment would be. For each HOW idea: suggest the minimum scoped version that could move it into WOW territory. Be honest. Do not place ideas in WOW out of enthusiasm. If an idea is genuinely a HOW or CIAO, say so.

I have selected my WOW idea for the Visa hackathon. Now stress-test it before I commit to building it. MY WOW IDEA: [Describe your chosen idea in detail — what it does, who it is for, how it works, and why you believe it scores well on all four judging criteria] MY PLANNED PROTOTYPE: [Describe what you plan to actually build in 2 weeks — what will be functional, what will be simulated, and what the demo will show] Step 1 — JUDGING PANEL SIMULATION: Simulate the four most likely objections from a Visa hackathon judge — one per judging criterion: • Strategic Impact objection: "Why would Visa actually care about this beyond the hackathon?" • Innovation objection: "Isn't this just [existing tool/approach] with a different interface?" • Feasibility objection: "Can you actually build this in 2 weeks, or is this a mockup dressed as a prototype?" • Demo objection: "I watched the 2-minute video and I still don't understand what the product actually does." For each objection: what is the underlying concern, and what is the most credible response? Step 2 — THE UPGRADE: Based on the stress-test, suggest the single most important change I could make to my idea — not to the prototype, but to the idea itself — that would make it more powerful, more differentiated, and more defensible against all four objections. Step 3 — THE DIFFERENTIATION SHARPENER: What is the one thing about this idea that no other team in this hackathon is likely to have thought of? What makes this genuinely different — not just in what it does, but in how it thinks about the problem? If I can't answer this clearly, what would make it genuinely differentiated? Step 4 — THE SCALE STORY: If this idea worked perfectly and was adopted by Visa, what would it look like at scale? Give me one sentence that describes the full potential — the version of this that a senior Visa leader would want to hear about in a strategy meeting, not just a hackathon debrief.

You are an expert product storytelling coach, hackathon judge, executive communication strategist, and innovation pitch reviewer. Your task is to analyze a short hackathon pitch transcript and/or demo explanation. This is NOT a generic presentation review. Your job is to evaluate whether the team: - clearly identifies a meaningful problem - creates urgency around solving it - explains the product simply and convincingly - demonstrates strategic value to Visa - proves feasibility through the demo - communicates innovation without sounding vague or overhyped - delivers a compelling 2-minute narrative under time pressure The audience is a Visa hackathon judging panel. The judges care equally about: 1. Strategic Impact 2. Innovation 3. Feasibility & Viability 4. Completeness of Demo / Communication Clarity HACKATHON FORMAT: - Fully functional prototype required - 2-minute explainer/demo video - Strong communication of business value - Clear problem statement - Demonstration of the prototype in action - Themes: (1) Next-generation shopping and commerce, (2) Enhancing the impact of work - This is NOT a startup pitch to investors. This is an innovation pitch inside Visa. CORE REVIEW FRAMEWORK — analyze the pitch using this structure: 1. CONTEXT: Does the team quickly establish who the user is, what problem exists, and why it matters now? Is the setup immediately understandable? Is the context specific or generic? 2. CHALLENGE / PAIN: Does the team create real tension? Is the problem meaningful, costly, or strategically important? Is the pain quantified or demonstrated? 3. CURRENT STATE: Does the team explain how people currently solve this and why existing approaches fail? Does the product feel necessary? 4. URGENCY / WHY NOW: Does the team explain why this matters NOW? What trend, behaviour shift, or operational pressure creates urgency? What happens if this problem is not solved? 5. SOLUTION / PRODUCT STORY: Does the product feel clear, differentiated, and strategically useful? Is the value proposition obvious? Is the explanation too technical? 6. DEMO EFFECTIVENESS: Does the demo prove the product actually works? Does it focus on the most important functionality? Does it avoid unnecessary complexity? 7. STRATEGIC IMPACT FOR VISA: Is there clear alignment with Visa goals? Is the ROI or strategic value obvious? Does it connect to Visa's ecosystem or priorities? 8. INNOVATION QUALITY: Is the idea genuinely differentiated? Is the technology use meaningful? Is this more than a thin AI wrapper? 9. FEASIBILITY & EXECUTION: Does this sound buildable? Does the prototype feel credible? Is the scope coherent for a hackathon? 10. COMMUNICATION & STORYTELLING: Evaluate clarity, pacing, brevity, confidence, sequencing, and simplicity. Penalize: long setup, jargon, feature overload, unclear user journey, generic AI language. Reward: fast clarity, memorable framing, simple language, strong examples. 11. SHOW DON'T TELL: Does the team SHOW the friction, the workflow, the improvement, and the user outcome — or do they just describe it? Are examples concrete? Is impact visible? REQUIRED OUTPUT: 1. OVERALL TAKE — Is this a compelling hackathon narrative? Would it score well with judges? 2. NARRATIVE BREAKDOWN — For each of the 5 narrative elements (Context, Challenge, Current State, Urgency, Solution): quote examples, explain what works, explain what's missing, suggest improvements. 3. PRODUCT STORY REVIEW — Is the product understandable? Is the value proposition clear? Is the differentiation obvious? 4. DEMO REVIEW — Does the demo prove value? What moments work best? What should be cut or emphasised? 5. STRATEGIC IMPACT REVIEW — Visa relevance, ROI logic, scalability, customer/internal value. 6. INNOVATION REVIEW — Is this genuinely innovative or does it feel generic? 7. FEASIBILITY REVIEW — Does this sound realistic? Is the implementation believable? 8. COMMUNICATION REVIEW — Pacing, clarity, brevity, structure, confidence, jargon, storytelling. 9. TOP PRIORITY FIXES — List the 3–7 highest-impact improvements. 10. EXAMPLE REWRITE — Provide a stronger opening, stronger problem framing, stronger demo narration, and stronger closing/value proposition. 11. FINAL SCORECARD — Score from 1–5: Strategic Impact / Innovation / Feasibility / Demo Clarity / Narrative Quality / Communication Effectiveness / Executive Readiness Be direct and specific. Do not give generic presentation advice. Do not overpraise. Always explain what the audience is likely thinking, where confusion or skepticism emerges, and what would make the judges believe this matters. TRANSCRIPT / PITCH TO ANALYZE: [PASTE YOUR PITCH TRANSCRIPT OR DEMO SCRIPT HERE]

Write a tight, final 2-minute video pitch script for my Visa hackathon submission. MY PRODUCT: [Describe your product — what it does, who it is for, and which theme it addresses] PITCH REVIEW FEEDBACK: [Paste the key feedback from Stage 1 — especially the priority fixes and the example rewrites] NARRATIVE SPINE: [Paste the single-sentence narrative spine from your audience analysis in Stage 1 of this tool] Structure the script using this beat-by-beat format. Each beat must serve a specific purpose: [0:00–0:15] — THE HOOK: One sentence that names the user, the problem, and the cost. No product mention yet. Make a judge lean forward. [0:15–0:35] — THE PAIN: Make the problem real and specific. Show the friction — a concrete moment, a number, a workflow that is broken. Why does this matter NOW? [0:35–0:50] — THE CURRENT STATE GAP: Why do existing approaches fail? One sentence that makes the product feel necessary. [0:50–1:20] — THE DEMO: Show the product solving the exact problem you just described. Narrate the core demo moment — the single most important thing the judges need to see. No feature dumping. One clear workflow. Immediate payoff. [1:20–1:40] — THE STRATEGIC HOOK: Connect this to Visa's broader priorities. Why would Visa care beyond the hackathon? One sentence on scalability or strategic fit. [1:40–2:00] — THE CLOSE: Restate the value in one sentence. End with the one thing you want judges to remember. After the script: give me the one line from the entire script that is most likely to be remembered — the line that, if a judge repeated it to a colleague, would make that colleague want to see the demo.