Kelly SETT Pursuit

DaySmart Meeting

Presenter Dashboard — Roxy + Treasure

Meeting Presenter Dashboard

DaySmart Pursuit — Meeting Flow

Share this screen. Walk the team through each step in order. Everything you need is here.

  1. 01
    Set the Stage
    Welcome. Share your screen on this page. Tell the team: "We've put together something different for this pursuit. Richard built an intelligence portal and I'm going to walk you through how we approach Jason Kirk on Friday."
    2 minutes
  2. 02
    Walk Through the Intelligence Portal
    Open the Project Nova portal. Scroll through each section — the DaySmart story, Jason's profile, tech stack analysis, our approach. Let the team absorb it.
    10 minutes
    Open Portal (code: ship-fast-win-big)
  3. 03
    Team Roundtable — "How Do We Approach Jason?"
    Say: "Now I need everybody's input. Say your name and tell us — how should we approach Jason on Friday? What do we lead with? What do we avoid?" Let each person contribute. This is being recorded.
    15 minutes
  4. 04
    Live Vibe Code — "Watch This"
    Say: "Everything you just said — Amber heard it. She's going to build the Jason-facing pitch right now, live." Richard drives the terminal. Team watches it come together in real time. Refresh the link when it's ready.
    10-15 minutes
    See Vibe Code Notes
  5. 05
    Play the Podcast — "Meet AI-Jason"
    Say: "We built an AI version of Jason Kirk based on everything he told us. Listen to how he'd react to our pitch — then we can all jump in and ask him questions."
    10 minutes (play first 10 min, full episode is 21:35)
    Go to Podcast Player
  6. 06
    Interactive Q&A with AI-Jason
    Open NotebookLM Interactive Mode. Team asks questions out loud — AI-Jason responds. Practice the hard questions: "What is Kelly doing with AI?" / "Why should we trust you after last time?"
    10 minutes
    Open NotebookLM
  7. 07
    Reveal the Jason-Facing Playbook
    Say: "This is what we're bringing to Jason on Friday. Operation Nova — a full AI transformation playbook, built with the same tools we're proposing for his teams." Open the link. Let the team see it.
    5 minutes
    Open Operation Nova (code: nova-actual)
  8. 08
    Close — The Punchline
    "Everything we just did — the intelligence, the roundtable, the live build, the AI rehearsal — this IS the proof. We just showed ourselves that AI-powered teamwork works. Now let's go show Jason."
    2 minutes
Act 4 Notes

Vibe Code Session

When it's time for the live build, here's what to say:

Your Script
"Alright team — you just gave your input on how to approach Jason. Now watch this. Amber is going to take everything you said and build the actual pitch we're presenting to Jason — right now, live, while we watch. And here's the important part — we're going to show Jason how we built it. Full transparency. He's going to see that our whole team came together, used AI to synthesize our thinking, and produced this in real time. That IS the proof that we know what we're doing."
For Richard: Have the pi terminal ready. When Roxy gives the signal, paste the team's key points and say go. Build or update the Operation Nova portal with whatever the team discussed. Deploy to Cloudflare. Team refreshes and sees it live.
Act 5

The Podcast

AI-generated conversation between a Kelly executive and "Jason Kirk" — built from everything he told us. Play it for the team, then go interactive.

AI Agent Orchestration for DaySmart Project Nova
21 minutes 35 seconds — Deep Dive featuring AI-Jason Kirk
Before You Hit Play, Say:
"We created an AI version of Jason Kirk. He's going to react to our pitch — ask tough questions, push back on our approach, and test whether we really understand his business. Listen to how he thinks. After about 10 minutes, we'll pause it and go interactive — you can ask him questions live."

Visual Companion — Key Moments

0:00
Jason (AI)
"Before you try to sell me anything, you really need to understand the beast I'm trying to tame here at DaySmart."
He opens with a test — do you understand my complexity?
2:30
Jason (AI)
"We now have a portfolio of 10 distinct products, and the tech stack is utter chaos. PHP, .NET, Python, Node, Ruby on Rails... it's like acquiring a massive fleet of vehicles where some are fully electric, some take diesel, and some run on coal."
The tech stack problem in his own metaphor
5:00
Kelly Exec
"We don't standardize it. We don't touch the code base right now. The key isn't swapping out the engines — it's standardizing the dispatch system."
Our core insight: integrate at the operational layer (Jira, GitHub), not the code
7:30
Jason (AI)
"If my star developer uses Claude and writes code 5x faster, but the product manager and QA team are still moving at human speed — I haven't actually solved anything."
The bottleneck shift — individual AI gains are a mirage
9:00
Kelly Exec
"We're proposing AI agents acting as functional employees within a pipeline. Product agent, architecture agent, dev agent, QA agent — an entirely automated pipeline where the conversation is perfectly formatted API calls."
The agent workforce vision — exactly what Jason asked for
11:30
Jason (AI)
"Kelly lost to an offshore competitor. You were basically just selling staff augmentation. Why should DaySmart hire you now?"
The hard question — he brings up the India loss directly
12:30
Kelly Exec
"We learned a hard lesson. Selling staffing bodies — the old model of throwing 50 offshore developers at a problem — is completely obsolete in an AI-driven market. We're bringing a three-phase approach built around proving orchestration value."
Honest answer — we lost, we learned, here's how we're different now
14:00
Jason (AI)
"I do not need a $15,000 PDF document telling me my multi-cloud tech stack is complicated. I just told you it was complicated."
He pushes back on the discovery — we need to show it's a playbook, not a study
15:30
Kelly Exec
"Because it isn't a study, Jason. It's a technical implementation playbook. We map exactly how to wire AI tooling into your distinct Jira and GitHub pipelines via Claude's Model Context Protocol."
MCP is the key technical differentiator
18:00
Jason (AI)
"Since you guys are the experts — what is Kelly actually doing with AI internally?"
THE question. Listen carefully to how we answer it.
18:30
Kelly Exec
"We are building our AI practice in real time. We are drinking our own champagne. The very intelligence briefing my team used to prepare for this pitch was built using our internal AI orchestration agents."
Radical honesty. This is exactly how we should answer on Friday.
21:00
Both
"Deep technical empathy for the client's internal chaos is your absolute strongest weapon. You have to prove you understand their constraints before you can sell them the acceleration."
The thesis of the entire pitch. This is our edge.
After the Podcast
Open NotebookLM Interactive Mode. Let the team ask AI-Jason questions live. Practice the Friday pitch in real time.
Open NotebookLM Interactive
The Punchline

Everything We Just Did Is the Proof

AI gathered the intelligence. AI synthesized the analysis. AI built the portals. AI generated the podcast. Humans directed, reviewed, and refined. This process IS what we're proposing for DaySmart.

Your Closing Statement
"This is exactly what we're going to do for Jason and his teams. We just proved the model works on ourselves. The intelligence portal, the live build, the AI rehearsal — this is the future of how Kelly pursues and wins deals. And it's the future of how DaySmart ships software. Now let's go do it for real on Friday."
View Operation Nova — The Jason Playbook (code: nova-actual)