Jump 450 · Your First Week

Your AI Immersion

One day. One real problem. You'll ship a working app with Claude Code — and pick up how we build with AI here.

10:00
You're set up
12:30
Check-in
3:15
You demo

What You're Doing Today

Today you'll go from a fresh laptop to a working app that solves a real Jump 450 problem — built with Claude Code, our AI coding tool.

You don't need to be a developer. Claude writes the code. Your job is to describe the problem clearly, steer Claude toward what you actually want, and know when something's good enough to ship. By 4:00 you'll demo what you built to a small panel. That's the whole day.

What You'll Walk Away With

A working app

Something real that runs and solves an actual problem from your world.

Hands-on Claude Code

You'll have built with it yourself — not watched a demo.

Your AI toolkit

Installed on your machine and ready for real work after today.

How we work

A real feel for how Jump 450 uses AI day to day.

Your Day, Hour by Hour

10:00 – 10:45
Get set up With your AI Buddy

Sign in to glass.jump450.com and install your tools. Your buddy — a teammate from your team — is right there to help.

10:45 – 11:00
Get your challenge

Your buddy hands you a real problem matched to your role and walks you through what a good result looks like.

11:00 – 12:30
Build — block 1

You and Claude Code. Stuck? Post in #internal_ai-support — asking well is part of the skill.

12:30 – 1:00
Check-in with your buddy

Show what you've got — broken is fine. Get unblocked and trim scope if you need to.

1:00 – 1:30
Lunch / breather

Step away and eat. You'll come back for the final build with a clear head.

1:30 – 3:00
Build — block 2

Keep going, and deploy it if you can — your tools are already set up for that.

3:00 – 3:15
Prep your demo

Plan a five-minute walkthrough: the problem, what you built, how you worked with Claude.

3:15 – 3:45
Demo it To the panel

Five minutes to show it, ten for questions.

3:45 – 4:00
Debrief

Feedback and what's next — skills to pick up, a follow-up session if it'd help.

Your Challenge

You'll get one real pain point from your world — scoped to fit a day and simple enough to show working by 3:00. It's picked for your role, so it'll feel familiar even if the tools are new.

A working slice beats a broken vision. It's smarter to ship something small that actually works than to aim huge and demo nothing. Cutting scope to hit the demo is a good call — not a failure.

How to Get the Most Out of It

The Demo

At 3:15 you'll get about five minutes to show what you built and ten for questions. Cover three things:

Be honest about what's rough or unfinished — that's expected on day one, and talking about it clearly actually counts in your favor.

How You'll Be Scored

The panel looks at four things:

Does it work?
Your app runs and does the job on the demo path.
Working with Claude
Clear, specific prompts — and you steer when it goes sideways.
Scope & judgment
You picked a demoable slice and asked for help when stuck.
Communication
You explain the problem, the build, and your process clearly.

This is a real test — and that's the point. Everyone goes through the same day under the same clock. The score sets the follow-up support you get next, not your standing — so push hard and show us how you work.

Before Day One

Come in with these ready so the morning is spent building, not troubleshooting:

Your AI Buddy handles the rest — your Claude seat, your challenge, and the calendar holds are already set. You just need to show up ready to build.

Where to Get Help