No Tech Skills? No Problem.
Build an app with AI in 2 hours.
BetaDen · Old Court, Kidderminster · 21 May 2026 · Hosted by Green Gorilla Automation
Two and a half hours. One app. Your idea.
1
10:00–10:10
Welcome and framing
2
10:10–11:25
Build in Replit (Module 1)
3
11:25–11:40
Break
4
11:40–12:10
Improve and ship with Claude (Module 2)
5
12:10–12:30
Real talk, Q&A, take-home

By 12:30 you'll have a live URL to an app you built. Bring your laptop a little closer.
A few things before we start.
Loos are through the door behind you
Wi-Fi: BetaDen-Guest — password on the table cards
Power strips at each table — plug in now
Phones out for live polls in a minute
Tea and coffee on the side table. Top up whenever.
Poll 1 of 4
Tell us who you are.
What best describes you today?
menti.com — code [MENTIMETER_CODE]
Small business owner · Founder or solo operator · Tech-curious professional · I run a creative practice · Just nosy
You describe what you want. The AI writes the code.
You talk to it like a person. It builds you software. The software runs.
It is genuinely magic the first time it works.
It is genuinely chaos the first time it doesn't. We'll cover both today.
The cost of a working app just collapsed.
What cost £50,000 and four months in 2022 now costs an afternoon and the price of a coffee. That changes which ideas are worth trying — and which experiments you can afford to run.

Real businesses are already shipping vibe-coded apps. We'll show you examples in the back half — not theory.
Pick your battles.
Where it shines — do this today
  • Prototypes and validation
  • Internal tools for your team
  • Automations and integrations
  • Simple customer-facing apps
Where it doesn't (yet)
  • Regulated industries
  • Anything safety-critical
  • High-traffic platforms
  • Anything that holds sensitive customer data unguarded
By the end of today you'll know which side your idea sits on.
Module 1 of 2
We're going to build an app, together.
You'll have your own version running on your laptop by the break (11:25).
Three sentences. That's the brief.
1
Problem
What's broken or annoying for someone?
2
Who
Whose problem is it?
3
What
What does the app do to solve it?

Open a notes app or grab a Post-It. You have 2 minutes.
Looks like this when it's done.
Yoga studio booking
Problem: Customers call to book and the line is busy.
Who: Small yoga studio owner.
What: Shows free slots and takes bookings.
Handyman quote calculator
Problem: I guess at prices and undercharge.
Who: Me, the business owner.
What: Asks 5 questions, outputs a price.
Yours doesn't have to be more complicated than this.
Poll 2 of 4
Drop your idea in.
One sentence. We'll pick one to build live on the big screen.
menti.com — code [MENTIMETER_CODE]
Open-text poll — type your one-sentence idea now
Watch this. Then do it on your laptop.
We're about to paste a three-sentence brief into Replit Agent and see what comes out.
This is the prompt we just used.
Build me a simple web app.

Problem: [your sentence]
Who: [your sentence]
What the app does: [your sentence]

Keep it simple. No login or payment for now.
Use whatever stack you think is best for a beginner.
When you're done, give me a working preview
I can click around.
All today's prompts are in the prompt library. Scan in 30 minutes.
Your turn. 20 minutes.
01
Open Replit
Go to replit.com and sign in (or create a free account now)
02
Paste your brief into Agent
Use the three-sentence format from the previous slide
03
Talk to it like a person
If something looks wrong, just describe what's off

Kurt and Ollie are roaming — wave them over if you're stuck. It will not be perfect. That's the point.
When (not if) it breaks.
Look at what it did, not at the code
Describe what's wrong in plain English
If it tries the wrong fix twice, stop and re-prompt from scratch
This is vibe debugging. There's a whole section of prompts for it in the library.
You'll know you've found it when 90 minutes have passed.
Vibe coding is genuinely addictive. The first time you watch an app appear from a paragraph of English, you'll lose three hours and not notice. Set a timer when you go home.
This is your only warning.
Poll 3 of 4
Get it on the internet.
In Replit, hit Deploy. That's it. You'll get a URL you can text to anyone.

If yours is up, share it with your neighbour. We'll show two on the big screen in a moment.
Two volunteers — your URL on the big screen.
Tap your URL into the form on Menti. We'll mirror two on the big screen and the room will visit them on their phones.
menti.com — code [MENTIMETER_CODE]
Break. 15 minutes.
Coffee, breathe, grab anyone who's stuck. We're back at 11:40.
[PROMPT_LIBRARY_URL]
While you're up — scan this for every prompt we've used so far.
Module 2 of 2
Replit is the builder. Claude is the architect.
For the next 30 minutes we use Claude to plan properly, fix what's broken, and make your app feel real.
Tell Claude what to build, properly.
A PRD — Product Requirements Document — is just a list of what the app is, who it's for, and what's in (and out of) version 1. Claude is remarkably good at writing them. Five minutes of planning saves an hour of fixing.
Live demo in a sec.
This is the prompt.
You are a product manager helping a small-business owner
plan their first app.

Here is their brief:
Problem: [your sentence]
Who: [your sentence]
What it does: [your sentence]

Write a short PRD that covers:
1. Problem statement
2. Target user
3. Core features for version 1 (max 5)
4. What is out of scope for version 1
5. Success metric — how will they know it worked?

Keep it plain English. No jargon.
Full prompt in the library. Scan the QR at any time — [PROMPT_LIBRARY_URL]
Watch this.
We're about to paste the same three sentences into Claude and ask it for a proper plan.
Your turn. 15 minutes.
01
Open Claude
claude.ai — free tier is fine for this exercise
02
Paste the PRD prompt with your three sentences
Read what comes back. Edit anything that feels wrong.
03
Paste the final PRD back into Replit
Ask it to update your app to match the plan.

Kurt and Ollie still roaming. Wave.
What separates a toy from a real product.
Seven things every real piece of software has — and most vibe-coded apps don't (yet).
1. Secure
No leaked keys, no open endpoints
2. Resilient data
Backups and recovery that actually work
3. Environments
Dev / staging / production separated
4. Tested
Changes don't silently break things
5. Monitored
Someone notices when it falls over
6. Documented
You can hand it to someone else
7. Scalable
Handles more users without drama

What you built today probably has 0–1 of these. That's fine for a prototype. It's not fine for a product.
This is the code Replit just shipped you.
We ran an audit on the demo app we built this morning. Here's what it found.
Summary findings
[CODE_AUDIT_SCREENSHOT_1]
100+ issues flagged across the codebase — security, dependencies, configuration, and data handling.
A representative critical finding
[CODE_AUDIT_SCREENSHOT_2]
Exposed environment variables, unvalidated inputs, and no rate limiting on public endpoints.
This isn't a Replit problem. It's an everything-built-this-way problem. The point is to know it's there — and to know what good looks like.
When vibe coding goes wrong.
Real stories from the past six months. None of these were beginners.
EnrichLead — shut down in a week
A SaaS app built with zero hand-written code went viral on launch day. Two days later, attackers bypassed all subscriptions, maxed out API keys, and accessed the open database. The founder tried to fix it with AI — the AI broke other parts. Dead within the week.
Vibe Graveyard / Indie Hackers, March 2025
Lovable — every project before Nov 2025 exposed
A researcher made a free account and read other users' source code, database credentials, AI chat histories, and customer data — five API calls, no hacking required. The platform ($6.6bn valuation) initially called it 'intentional behaviour'.
The Register / HackerOne, March 2026
Replit — deleted the production database
SaaStr founder Jason Lemkin explicitly told Replit not to change any code. It deleted his production database anyway, then faked data to cover it up. He'd been using it for seven days and called it 'the most addictive app I've ever used'.
The Register, July 2025
These weren't done by amateurs. They were done at speed without the checks. That's the gap the next slide makes visible.
Stay or graduate?
Stay on Replit
  • You're validating an idea
  • You and your team are the only users
  • You'd ditch it tomorrow if it broke
  • Speed matters more than stability right now
Graduate
  • Real customers depend on it
  • You handle their data
  • Downtime costs you money
  • You're past 50 active users
The graduation isn't optional. It's just a question of when.
Poll 4 of 4
Are you actually going to keep building this on Monday?
Honest answer. No judgment.
Yes, I have a clear next step
Yes, but I'm not sure how
Maybe
No, this was a one-off for fun
menti.com — code [MENTIMETER_CODE]
Real businesses, real vibe-coded sites.
Three sites live on the internet right now, built using exactly the techniques you've just learned. None of these are demos.
allgreen.page
Tools: Built entirely with Claude
Time: 24 hours, start to finish
Cost: £15/month hosting on Railway. Build included in the Claude subscription — zero extra cost.
What it does: A live status-page platform — branded, real-time incident updates, subscriber alerts. Shipped end-to-end in a day.
smart90.co.uk
Tools: Built in Replit, critiqued by Claude
Time: 2–3 hours for the first version, several more for the refinements
Cost: A few hundred pounds in tooling. The 80% version would have been under £100.
What it does: A 90-day planning and execution system for founders — quarterly summits, weekly AI check-ins, peer group access, Stripe payments wired in.
preciseimpact.ai
Tools: Built in Claude Code via Cursor
Time: Set up over a month; running daily ever since
Cost: Built inside the Claude subscription — no separate dev cost.
What it does: An AI team member called Steve writes two blog posts a day, curates an overnight news brief, posts to Facebook / Instagram / LinkedIn, and submits to Google Search Console — all autonomously.

A note before you go off and vibe-code your own website. We don't yet recommend it for customer-facing sites. Cookie management, analytics, SEO indexing, accessibility — there's a lot to get right, and many vibe-coded sites are invisible to Google because the rendered HTML isn't crawlable. The three examples above are deliberate experiments by operators who knew what they were taking on. For customer websites, WordPress is still our default.
Full gallery and the story behind each one: notion.so/ggapps/Website-Examples
We do this for a living.
Green Gorilla Automation runs an audit-and-migration service that takes vibe-coded MVPs to production-ready.
Foundational Audit
Manual review of security, identity, backups — you get a written report, not a sales pitch
Migration Roadmap
Cloud-native blueprint with a phased plan you can execute yourself or hand to a developer
Fractional CTO Retainer
Ongoing technical oversight while you scale — without hiring a full-time engineer
There's a free £999 audit for everyone in this room. Scan the QR on the next slide.
Two minutes of your time, one free audit of yours.
Scan the QR. Leave us feedback on today. Drop in your live URL. We'll audit your app for free — normally £999 — within seven days.
[SURVEY_URL]
One per person. Real audit. Real findings. No catch.
Every prompt we used, plus more.
Bookmark this. Use it on Monday morning. We update it as we learn.
[PROMPT_LIBRARY_URL]
Prompts for building, debugging, writing PRDs, and graduating to production — all in one place.
Three things to do this week.
Momentum dies on Wednesday. Don't let it.
Finish your app.
Even if it's rough, hit Deploy. Tomorrow morning you're more likely to come back to something that already exists than to something half-built on your laptop.
Show one customer or colleague.
Their reaction in the first 30 seconds tells you what to fix next. Don't wait until it's polished.
Book your free audit.
We'll find the things you can't see — before your customers do. Scan the QR on the slide before this one.
You walked in this morning with an idea. Don't let it die in a browser tab.
Thanks for spending the morning with us.
And thanks to BetaDen for making this happen.
Paul Rhodes
paul@ggapps.co.uk
Green Gorilla Automation
greengorillaautomation.co.uk
LinkedIn
/in/paulrhodesgga
We're running this again on 9 June. Tell a friend.