Prototyping & Automation

AI app builders have changed who can make software. In this hands-on session you build two small working apps for your own hotel or a ready-made example, without writing code: a page where guests ask for things, and a tracker your team uses to handle those requests. You plan each one, build it with AI, test it and put it online. You leave knowing how simple this way of building has become, what a prototype can and cannot show, and when it should go to IT or a developer.

Who it is for

Anyone curious about building with AI, from business users and department heads to IT and systems owners. No technical background is needed.

Learning objective

Plan, build, test and publish a working app without writing code, and judge what a prototype can show, what it still lacks, and when it should go to IT or a developer.

• Write a one-page specification: problem, users, core features, constraints, success criteria
• Direct AI to build a working prototype from that specification, without writing code
• Test and debug your app, then improve it based on what your testing shows
• Decide whether a prototype gets kept, thrown away, or handed to IT
• Build an internal tracker that keeps its records, changes their status and limits access to staff
• Tell a working app from a mock-up that only looks finished, and know what must never run unattended

1. Section 006-1 · 120 min

   From Problem to Working Prototype

   Plan a small app on one page, build it with AI, test it, fix what you find and publish it. Each stage is taught and demonstrated live, then done by each participant for their own hotel or a ready-made example.

   You leave with: A working prototype built from your own specification, the spec template that produced it, and a keep, bin or escalate decision.

2. Section 006-2 · 110 min

   From Manual Steps to a Workflow That Runs Without You

   The same loop, applied to the staff side: an internal tracker for the requests guests make, with records that are kept, statuses that change and access for staff only. You build it, test it on a second device and publish it. A live demonstration shows an app acting on a new request by itself, and the session closes on what an automation must never do unattended.

   You leave with: A working request tracker, a test and release checklist, and a written list of what stays under human control.

• A working prototype

  Built in the session from your own one-page specification, tested, improved and published.

• A specification template

  The format that separates a prototype which works from one that misses, reusable on the next problem you bring it.

• A working request tracker

  An internal app for the requests guests make, with records that are kept, statuses that change and access for staff only.

• An escalation ladder

  What a prototype, a published app and a production system each need, and the point where the work belongs to IT.

• Each participant fills in a short property card at the start of the session, and builds for their own hotel or a ready-made example.
• Apps are built on practice accounts with made-up records, so no real guest or staff data is used.
• No technical expertise is required. Anyone from business users to IT can join.