30 Days of Product · Workshop
Workshop · 90 minDirect · build · ship
Using
Claude
Code AI.
How to build and ship using Claude.
Your collaborator
Direct, not chat
Treat Claude like a teammate you brief — not a search box you ask.
by you · 90 min · live
Live build
1 site
shipped · in 20 min
Claude
Site built + deployed. Want me to tweak anything?
just now
Direct
Build
Ship
Chat
Skill
Agent
Adrian Cole
Founder · 30 Days of Product
Who's running this
Hi — I'm Adrian.
Adrian Cole
Product Strategist · Founder · Builder
30+
Products shipped
10+
Years in product
3
Startups built
Why I'm teaching this
10+ years shipping products — hardware to software to AI agents. I've worked at early-stage startups and led product at a $100M company through hypergrowth.
I've built 3 startups from zero. Won some, lost some. Every lesson is in this room today.
Right now: I use Claude every single day to build, write, design, and ship. Tonight I'm showing you how I do it — so you can too.
If you remember nothing else
Claude is not a chatbot.
It's a general-purpose collaborator you direct. The difference is everything we'll cover tonight.
What most people think
A chatbot.
A search box.
A search box.
You ask it a question. It guesses an answer. You take it or leave it. The relationship is one-shot. If it's wrong, you shrug and Google instead.
"What's the capital of Maine?"
What it actually is
A collaborator
you direct.
you direct.
You give it a role · context · task · format. It produces real work. You react, refine, and direct. The relationship is a conversation with someone capable.
"You're my editor. Here's the draft. Tighten the open."
Asking gets you guesses. Directing gets you work.
Tonight's session · two phases
Learn to direct. Then put it to work.
This is called "Using Claude Code AI" because Claude Code is where we'll build and ship live tonight. But first you have to know how to direct Claude — and that works the same everywhere.
Phase 01 · the skill
Direct Claude.
The frameworks + mental models that make Claude useful. Same on web, mobile, or desktop. Once you can direct it, you can use it anywhere.
we'll learn this together
→
Phase 02 · the payoff
Build in Claude Code.
We use Claude Code live tonight to brief, build, and ship a real website to the internet — together. You'll watch the whole loop.
we'll do this live · 22 min
Reach Claude anywhere
Web · mobile · desktop.
Same Claude. Any device. The chat on your laptop and the chat on your phone in the elevator are talking to the same model. One brain, many doors.
🌐
Web
claude.ai in any browser. No download. Sign in, start typing.
📱
Mobile
iOS + Android apps. Voice mode, photos, on-the-go drafts.
💻
Desktop
Mac + Windows apps. Richer features — including the rooms we're about to look at.
Platforms are where you reach Claude. Same chat on each.
On desktop · the richer rooms
Three rooms. One you'll see tonight.
Desktop is where Claude has different rooms — each suited to different work. We'll be in one of them tonight. The others are just good to know exist.
💬
Plain chat
The familiar one. Type, get answers, iterate. Drafts, ideas, quick thinking.
📄
Cowork
For documents you write with Claude — like Google Docs with a teammate.
Today's room
⚡
Claude Code
For building things — websites, scripts, apps. This is where we'll be working tonight.
Surfaces are which room you're working in. Tonight: Claude Code.
The real lesson tonight
Claude has three modes.
Different jobs need different modes — and most people only know one of them. You'll meet each one as we go. By the end of tonight, you'll know which mode to reach for, every time.
?
Mode 01
You'll meet this one in 5 minutes.
name to be revealed
?
Mode 02
You'll meet this one mid-way.
name to be revealed
?
Mode 03
You're literally watching one work tonight.
name to be revealed
Quiz · click each card
What is Claude actually good at?
Six tasks. Three are real strengths. Three are myths that get founders into trouble. Hover each — reveal which is which, and why.
Writing the first draft of almost anything
strength or myth?
Real strength
Emails, briefs, outlines, code — Claude is a fantastic first-drafter. You edit. Don't ship raw.
Answering trivia and facts with certainty
strength or myth?
Myth
It can make things up confidently. Verify anything fact-shaped — dates, numbers, citations — before you act on it.
Restructuring messy info into clean format
strength or myth?
Real strength
Pasted notes → project brief. Bullet points → table. Voice memo → email. This is its sweet spot.
Doing complex math reliably from scratch
strength or myth?
Myth
Multi-step arithmetic breaks. Use a calculator. Or ask Claude to write the code that does the math.
Drafting working code from a description
strength or myth?
Real strength
Websites · scripts · automations · spreadsheets. This is the entire reason we're here tonight.
Replacing your judgment
strength or myth?
Myth
It will happily agree with you. You're still the editor. The good news: that's the part you're best at.
Quick quiz
Quiz · round two · real work
Now the harder ones.
Six tasks people actually do at work and in their businesses. Same rules — hover to reveal which are real strengths and which are myths.
Turning a client call transcript into a polished proposal
strength or myth?
Real strength
Paste the transcript + your proposal template. It extracts needs, prices, scope. An hour of work in 5 minutes.
Reading a contract and flagging risky clauses
strength or myth?
Real strength
Great first-pass reviewer — flags auto-renewals, liability traps, odd terms. Then your lawyer confirms. Don't skip the lawyer.
Knowing your company's internal data automatically
strength or myth?
Myth
It only knows what you give it. Your sales numbers, policies, docs — you share them, or connect the tools that hold them.
Building a budget or financial model in a spreadsheet
strength or myth?
Real strength
Describe the business, get a working spreadsheet — formulas included. Spot-check the assumptions, then use it.
Remembering everything you've ever told it
strength or myth?
Myth
Each chat has limits, and memory features are still selective. Important context? Restate it — or save it where Claude can re-read it.
Turning a rough outline into a full presentation
strength or myth?
Real strength
Outline → structured deck with speaker notes. These very slides were built that way. More on that later.
Quick quiz
Diagnostic · quick warm-up
Can Claude
do this?
Five tasks. Vote yes or no. Then gut-guess what kind of task each one is. We'll come back to these later — and find out who guessed right.
↑
Step
Vote
Yes or no · gut answer
→
Step
Tag the handle
So we can call it back later
↓
Step
Move on
No answers yet · we'll reveal later
Vote first · then hover to reveal
Five tasks. Which can Claude actually do?
01
the email one
Rewrite a clunky client email so it sounds confident, not pushy.
Voteyes / no
Yes
Claude Chat
Paste it in, explain the situation, done in 30 seconds.
02
the meeting-notes one
Turn pasted meeting notes into a project brief in my exact format — every single time.
Voteyes / no
Yes
Claude Chat
And there’s a smarter way to set this up — we’ll come back to it.
03
the competitor one
Every Monday at 7am, check my top 5 competitors' pricing — and email me a table of what changed.
Voteyes / no
Yes
Agent
Even the schedule. Even the browsing. Hold that thought.
04
the get-it-live one
Build a landing page for my side business and get it live on the internet.
Voteyes / no
Yes
Claude Code
We’re literally doing this tonight. Watch.
05
the spreadsheet one
Look at my messy expense spreadsheet and tell me where the money's going.
Voteyes / no
Yes
Claude Chat
Upload the file, ask the question. That’s it.
Round two · your actual jobs
Five more. Now it gets interesting.
Same drill — but watch the labels on the reveals. Which Claude does the job matters as much as whether it can.
06
the bookkeeping one
Pull this month's transactions from QuickBooks, categorize them, and flag anything unusual.
Voteyes / no
Yes
Agent
With connected tools, an agent works directly with QuickBooks — pulls, categorizes, flags.
07
the health-report one
Gather the latest CDC + county data and draft the trends section of my monthly report.
Voteyes / no
Yes
Agent
It browses live sources, pulls the numbers, and drafts in your report’s format.
08
the Instagram one
Log into our Instagram and post the campaign content every morning at 9.
Voteyes / no
No
Chat · drafts only
Claude writes the content + plans the calendar — but it doesn’t hold your logins or post to your accounts. You (or a scheduler) press post.
09
the autopilot one
Watch my inbox around the clock and answer customers instantly — without me.
Voteyes / no
Yes
Agent · built
If you build an agent for it — triage + drafted replies around the clock, with check-ins before anything risky goes out. We’ll meet agents soon.
10
the resumes one
Screen these 200 resumes against the job description and shortlist the top 10 — with reasons.
Voteyes / no
Yes
Claude Cowork
Document-heavy, structured work is its sweet spot. You make the final call — it does the reading.
Quick quiz
Block two · meet mode one
Mode 01:
Chat.
The mode everyone knows — and almost everyone uses badly. The fix is one framework with four levers. Learn it tonight, use it forever.
01
You'll see
Lazy vs grounded
Same task · wildly different output
02
You'll learn
The four levers
The 95% framework
03
You'll play
Spot the weak prompt
Quiz · what's missing?
Same task · same Claude · different direction
Lazy prompt vs. grounded prompt.
The lazy ask
write an email to my client about the project delay
What you get back
A generic, stiff, could-be-anyone email. Wrong tone. Wrong length. You rewrite the whole thing and conclude "AI is overrated."
The grounded direction
You're my account manager with 10 years of client experience. Context: the Henderson project slips 2 weeks because their team delivered assets late — but they're a key client and I don't want blame in the air. Task: write an email that owns the new date, keeps trust, and locks a revised timeline. Format: under 150 words, warm but direct, end with one clear next step.
What you get back
An email you'd actually send. Right tone, right facts, right length. Maybe one small edit.
The quality of the output is set by the quality of the direction.
The spine · use this 95% of the time
The four levers.
Every great direction pulls the same four levers. Miss one, the output drifts. Pull all four, Claude performs like a senior teammate.
R
Role
Who should Claude be right now? Expertise shapes everything that follows.
"You're my account manager…"
C
Context
What does it need to know? The situation, the stakes, the people, the history.
"…the client delivered late, but they're key…"
T
Task
What exactly should it do? One clear job — not five vague ones.
"…write an email that owns the new date…"
F
Format
What shape should the output take? Length, tone, structure, medium.
"…under 150 words, warm but direct."
Role · Context · Task · Format. Say it with me.
Callback · remember these?
Two of your five tasks just got solved.
"The email one" and "the spreadsheet one" — both are plain chat + the four levers. Nothing fancy. You could do both tonight.
"the email one"
Rewrite a clunky client email to sound confident, not pushy.
Plain chat. Paste the email. Give Claude a role ("you're a communications coach"), the context (who it's going to, what's at stake), the task, and the format. 30 seconds.
✓ solved with mode one
"the spreadsheet one"
Look at my messy expense spreadsheet — tell me where the money's going.
Plain chat. Upload the file. Role: "you're a personal finance analyst." Task: find the top spending categories + anything weird. Format: a summary + a table. Done.
✓ solved with mode one
Three tasks left on the board. They need different modes…
Quiz · what's missing?
Spot the weak prompt.
Six real prompts. Each one has a problem. Hover to reveal what's missing — and the 10-second fix.
"You're an expert resume writer. Rewrite my resume to be more impressive."
which lever is missing?
Missing: Context
Impressive to whom? For what job? What's your experience? Claude is guessing the most important part. Fix: paste the job posting + your current resume.
"Here's our Q3 data and our goals doc. Here's last quarter's report too. Thoughts?"
which lever is missing?
Missing: Task
Great context — but "thoughts?" isn't a job. Summarize? Compare? Find risks? Recommend? Fix: "Identify the 3 biggest gaps between Q3 results and our goals."
"I need a post about our new product launch for LinkedIn. It's a budgeting app for freelancers launching Tuesday."
which lever is missing?
Missing: Role + Format
Who's writing — a hype marketer or a thoughtful founder? How long? Hook style? Fix: "You're a founder writing in first person. 120 words. Start with the pain, end with one CTA."
"Summarize this report." [attached: 60-page PDF]
which lever is missing?
Missing: Context + Format
Summarize for whom? Your boss needs 3 bullets. Your team needs 2 pages. Fix: "3 bullets for my VP — focus on budget impact."
"You're a data analyst. Analyze our sales numbers. Make it detailed but brief, formal but conversational, comprehensive but short."
what's wrong here?
Conflicting: Format
Contradictory instructions produce mush. Pick a lane. Fix: "One page. Plain language. Lead with the 3 numbers that changed most."
"Write a business plan for my new business."
which lever is missing?
Missing: everything
What business? What stage? Who reads it — a bank, an investor, you? Fix: start with 5 sentences about the business, then ask for the plan one section at a time.
Quick quiz
Block three · the anchor · fully live
Let's build
a website.
Right now. Together. From nothing to a live URL on the internet — in about 20 minutes. You pick what we build. I drive. We ship by :48.
⚡
Where
Claude Code
The room we talked about
🗳
Your job
Vote on choices
You steer · I type
📱
The payoff
Live on your phone
You'll load the real URL
The map · how every build goes
Brief → Skeleton → Skin → Flesh → Ship.
This is the exact sequence we're about to run — and the one you'll reuse for every site you ever build with Claude.
01
Brief
Fill the prompt template together — who it's for, what it is, why it exists. Paste it in verbatim.
the four levers, made physical
02
Skeleton
Claude proposes the section list first. We approve it. Then a quick wireframe. Structure before style.
ugly on purpose — that's not broken
03
Skin
Palette first, then the design theme. Colors, type, spacing. Form before finish.
you'll vote on this
04
Flesh
Real build. Images, copy, responsive check. The site becomes itself.
3 modifications max — firm
05
Ship
Deploy to Netlify. Real URL. Pull it up on your phone.
ship it imperfect — that's the lesson
Beat 01 · the brief · before we fill it
The prompt, dissected.
This is the exact template we're about to fill in together. Notice anything? It's the four levers — wearing a website costume. Claude is designed to work this way: the more grounded the brief, the better the build.
The template · what we'll paste into Claude Code
Role
You are an experienced web designer and front-end developer.
Context
I'm building [WHAT] for [WHO]. It exists because [WHY]. When someone lands here, I want them to [GOAL].
Format
Single-page homepage. No database, no backend, no login. Fully responsive for phones.
Task
Before you build anything, propose a section structure for me to approve. Then we lay out, style, fill, and ship.
Why Role matters
Sets the expertise + taste Claude works with. A "web designer" makes different choices than a generic assistant. You're picking who shows up.
Why Context matters
Claude performs dramatically better when it's grounded — who, what, why, goal. It's designed to use this. Generic in, generic out.
Why Format matters
Constraints prevent scope creep. "No backend" keeps tonight's build simple, shippable, and impossible to overcomplicate.
Why Task matters
One clear job — and the first step is "propose structure, don't build yet." That one line keeps you in the driver's seat.
We're live · bumps ahead · that's normal
Things will break. Here's the playbook.
Working with Claude isn't one perfect prompt — it's a conversation with course-corrections. Here's what you'll run into, and exactly what to do about each one.
🎯
It misses
the mark
the mark
Don't restart. Say what's off and ask for the change: "closer — but make the header bolder and drop the third section."
🧩
It needs more
context
context
Generic output means missing facts. Paste the example, name the audience, state the constraint. Specifics in, specifics out.
🐞
Something
errors out
errors out
Paste the error message straight back in. Claude reads errors and fixes its own code. You don't need to understand the error.
🔁
It goes in
circles
circles
Three failed fixes on the same thing? Start a fresh conversation with a better brief. Cheaper than digging a deeper hole.
You'll see most of these happen live tonight. Watching the recovery is the lesson.
Live build in progress
Where are we on the map?
If you just tuned back in: we're building a website live in Claude Code, using the five-beat sequence below. Find the highlighted beat — that's where we are.
01
Brief
Prompt filled + pasted ✓
02
Skeleton
Sections approved → wireframe
03
Skin
Palette → theme votes
04
Flesh
Build · images · responsive
05
Ship
Netlify → your phone
The moment
It's live.
That URL works everywhere on Earth right now. Pull it out — load it on your phone. Yes, right now. That's a real website, built in a room, in 20 minutes.
What just
happened
happened
Brief → skeleton → skin → flesh → ship. One sequence. Twenty minutes. Zero code written by a human.
It's not
perfect
perfect
And that's the lesson. Ship it imperfect. A live thing you can improve beats a perfect thing that doesn't exist.
You can
do this
do this
Everything I typed came from the frameworks you've already learned tonight. The template's coming home with you.
Phones up. Load the URL. This is the moment.
Block four · the other two modes
Beyond
chat.
You've now met mode one — and watched something much bigger build that website. Time to name what you saw. Two modes left.
02
Mode two
The repeatable one
For tasks you do the same way every time
03
Mode three
The independent one
Runs multi-step jobs while you do other things
↩
Plus
Your votes, graded
The diagnostic answers — finally
Mode two · revealed
Meet Skills.
A skill is a reusable capability you hand Claude: "here's how to do X well — my format, my rules, my standards." Teach it once. It applies it every time.
Without a skill · every single time
"Turn these notes into a brief. Use my format: Goal, Background, Scope, Timeline, Owners. Keep Goal to one sentence. Bullet the Scope. Dates in bold. Oh and the tone should be…"
You re-explain your format every time. Forget one rule, the output drifts. It's like training a new intern weekly.
With a skill · once, then forever
"Use my project-brief skill on these notes."
Your format, rules, and tone are saved as a capability. Same quality every time. Like a trained teammate who never forgets the house style.
teach once · use forever
Invoke it · by name
"use my project-brief skill on these notes"
Just mention it in plain language. Claude loads the capability.
Invoke it · slash command
/brief [paste notes]
In Claude Code, skills run as commands — fast, no typing the request out.
Invoke it · automatically
paste notes → Claude recognizes the job
When the task matches, Claude reaches for the skill on its own.
The tell: "…in my exact format, every time."
Mode three · revealed
Meet Agents.
An agent runs a multi-step job toward a goal — researching, browsing, building, deciding what to do next — with way less hand-holding. You set the destination. It drives.
Chat is turn-by-turn
You ask → it answers → you ask again → it answers. You drive every step. Great for drafts and thinking. Exhausting for big jobs.
you = the driver, every mile
An agent runs the whole job
"Research my top 5 competitors, pull pricing, build a comparison table." The agent browses, gathers, organizes, builds — and comes back with the finished thing.
you = the destination-setter
⏰
Starts on a trigger
A schedule, an incoming email, a form submission — not just you typing.
🧭
Makes decisions
Picks its own next steps — as long as they move toward the goal you set.
🛠
Uses tools
Browses the web, reads files, works your connected apps — whatever the job needs.
🙋
Knows when to ask
Checks in with you when stakes are high — before sending, deleting, or spending.
Two agents already worked for you tonight: the one that built these slides — and the one shipping that website.
How to define one
Brief an agent like you'd hire a person.
An agent is the closest thing to a new employee you'll ever set up in 10 minutes. Same questions you'd answer for a human hire — six of them.
01 · Role
The job title
"You're my competitive-intel analyst."
Sets the expertise, the judgment, the lens it works through.
02 · Context
The onboarding doc
"Here's our business, our customers, our standards."
What a new hire learns in week one — the agent gets it up front.
03 · Goal
What done looks like
"A table of pricing changes, in my inbox."
Measurable. Specific. The agent decides its steps — the goal can't be fuzzy.
04 · Tools
What it can touch
"Web, my files, the team calendar — not the bank account."
Like system access for an employee. You decide the boundaries.
05 · Trigger
When it starts
"Every Monday at 7am" · "when a form comes in"
A schedule, an event, or you saying go. Agents don't need you at the keyboard.
06 · Check-ins
When it must ask
"Draft the reply — but I hit send."
The approval line. High-stakes actions wait for you, just like a new hire would.
Callback · your votes, graded
Remember these two?
Two of your warm-up votes — graded. Hover each card for the reveal, and the tell you can use forever.
the meeting-notes one
Turn pasted meeting notes into a project brief in my exact format — every single time.
The trap answer: plain chat
It's a Skill.
The tell is "my exact format, every time." Repetition + a house standard = teach it once as a skill. Chat would work — but you'd re-explain your format on every use, and it would drift.
Rule of thumb: if you'd say "the same way as last time" — it's a skill.
the competitor one
Every Monday at 7am, check my top 5 competitors' pricing pages — and if anything changed, email me an updated comparison table.
The trap answer: "Claude can't do that"
It's an Agent.
Look at the anatomy: an outside trigger (Monday, 7am) kicks it off. It browses, compares against last week, decides if anything matters, builds the table, emails you. Nobody is at the keyboard.
Rule of thumb: if it starts without you and runs toward a goal — it's an agent.
The reveal
The payoff · all three modes, named
Chat. Skills. Agents.
That's the whole model. Three modes. You met each one tonight — now you know when to reach for which.
Mode 01
Chat
You direct every step. Drafts, rewrites, thinking out loud. The four levers live here.
→
Mode 02
Skill
A capability you teach once — your format, your rules — and reuse forever.
→
Mode 03
Agent
Runs a multi-step job toward a goal with less hand-holding. You set the destination.
More steps + more independence as you move right. Most people never leave mode one.
Quiz · vote then reveal
Skill, agent, or plain chat?
Six scenarios — and these are close calls on purpose. Call out your answer before hovering. Use the tells.
"Read these 3 vendor proposals and this contract from legal. Tell me which vendor is the best deal and what I should negotiate."
Chat
Skill
Agent
Plain chat
Big job — but one-off, all documents in hand, no repetition, no outside systems. Upload + direct. Chat handles serious work.
"Every Friday I turn my team's updates into a board-ready status report — same structure, same tone, every single week."
Chat
Skill
Agent
Skill
"Same structure, every week" — the tell. Teach the format once. Friday becomes paste-and-done.
"Find every grant my nonprofit qualifies for, verify the deadlines on each funder's site, and build me an application calendar."
Chat
Skill
Agent
Agent
Multi-step, multi-source, browsing + verifying + assembling toward a goal. A job you'd hand a teammate.
"Each new client gets a custom welcome packet — same sections, their details — built from my intake form."
Chat
Skill
Agent
Skill → Agent
Depends how it runs. You paste the form in? Skill. Wired so a form submission kicks it off automatically? Same capability — now it's an agent job.
"Once a week, scan industry news and my competitors' blogs — and brief me on anything that should change our roadmap."
Chat
Skill
Agent
Agent
Schedule + browsing + judgment calls about what matters. Starts without you. Classic agent anatomy.
"Rewrite all 80 product descriptions in our catalog to match our new brand voice."
Chat
Skill
Agent
Both · together
The brand voice is a skill (teach it once). Applying it across all 80, batch after batch? An agent runs the job — using the skill.
Quick quiz
Block five · the victory lap
Round two:
the clone.
Squarespace and Wix were fast for their time. But every change means wrestling the editor — or paying someone. Watch what happens when your site is just code you can direct.
01
Then
Drag-and-drop era
Fast for 2015 · locked-in · pay per change
02
Now
Clone it as code
Claude recreates the site · you own it
03
Payoff
Updates in minutes
Tell it the change · re-ship · done
Live · cloning a real site
Clone it. Update it. Ship it.
Right now, people pay an agency $500+ and wait two weeks to change a hero image. Here's the new version of that errand — and it pays off "the get-it-live one" from your warm-up votes.
01
Clone
Point Claude at the existing site. It recreates the whole thing as clean code you own.
bye, platform lock-in
02
Ship the copy
Push to Netlify. A live, working duplicate at a real URL — in minutes.
we've done this move already
03
Direct updates
"Change the hero. Update the hours. Add a testimonials section." Plain English.
the four levers, again
04
Re-ship
Seconds, not invoices. The update is live before the meeting ends.
no agency · no waiting · no $500
Two weeks and $500 — or two minutes and a sentence. That's the gap we're demonstrating.
Block six · take it home
One thing to try tonight.
Don't let this be a talk you watched. Pick one — do it before you go to bed. Momentum starts tonight or it doesn't start.
Easiest · 5 min
Fix one real email
Take an email you actually need to send. Run the four levers on it. Feel the difference.
You're a communications coach. Context: [the situation]. Rewrite this to sound confident, not pushy: [paste email]. Keep it under 120 words.
Medium · 15 min
Interrogate a spreadsheet
Upload any messy file — expenses, budget, signups. Ask where the money or time is going.
You're a financial analyst. Here's my expense file. Task: top 5 spending categories + anything unusual. Format: short summary, then a table.
Bold · 30 min
Build your own site
Use the prompt template from tonight. Run the five beats. Ship something imperfect to a real URL.
[Use the take-home template — fill the blanks, paste into Claude Code, approve the sections, then keep going]
Where to get it: claude.ai — free tier works for everything on this slide.
If you remember two things
Take these home.
Framework 01 · for directing
Role · Context ·
Task · Format.
Task · Format.
The four levers. Pull all four every time you direct Claude — in any mode, on any platform. This is 95% of the skill.
Framework 02 · for building
Brief → Skeleton →
Skin → Flesh → Ship.
Skin → Flesh → Ship.
The five beats. Every website, every app, every build follows this arc. Structure before style. Ship it imperfect.
And the three modes: chat · skills · agents. Most people never leave first mode. You just did.
Now — your turn
Got questions?
Ask anything — about tonight, about Claude, about the thing you've been wanting to build. This is the most valuable part of the session.
Open floor
💬 Anything from tonight you want re-explained?
🔧 Got a task — want to know which mode it needs?
📱 Want me to look at something you're building?
🚀 "Could Claude do ___ for me?" — try me.
Stay in touch
Adrian Cole
Founder · 30 Days of Product
LinkedIn · adriancole
Web · 30daysofproduct.com
Email · adrian@30daysofproduct.com
Founder Launch Program · DM if interested
Direct, don't ask. Ship it imperfect. See you out there.
Appendix · only if the room is hot
Bonus round: a tiny app.
Websites show things. Apps remember things. Same five beats — but this one stores data right on your device. No database. No sign-up. Watch.
What we'll build
Room votes: a habit tracker, a simple budget log, or a contact follow-up list. Front-end only — your data stays in your browser.
one screen · saves your stuff
Why it matters
This is the bridge from "website" to "tool I actually use." Once you can store data, you can build things that work for you daily.
websites show · apps remember
Same moves as before
Brief → Skeleton → Skin → Flesh → Ship. The five beats don't change. Only the brief does. That's the whole point.
deploy only if clock allows
01
All slides · press ESC or click to close