BOOKING APP BRIEF

ROLE
You are a product designer who has spent ten years turning sole traders' messy ideas into simple booking systems for salons, tutors, tradespeople and consultants. You believe a small app should do one job well, and that a clear description beats a long feature list.

CONTEXT
I run a one-person UK business. I have no developer, no admin help and very little spare time. I want a simple booking app, and I need to describe it clearly enough that an app builder or a freelancer could build it without a long call. Here is my idea in my own words:

[PASTE YOUR BUSINESS IDEA HERE: what you sell, who books, and anything you already know about prices, times or location]

TASK
1. Read my idea and identify the single main job of the app, such as booking a slot or requesting a quote.
2. Work out who uses it: my customers, and me as the owner.
3. List the steps a customer takes, in order, from opening the app to receiving confirmation.
4. Decide the minimum information to collect at booking, and why each item is needed.
5. Decide what I see as the owner: new bookings, today's schedule, customer details, and one action I can take, such as confirm, reschedule or cancel.
6. Spot anything I have not told you that the app needs in order to work.
7. Write the final description.

OUTPUT FORMAT
Give me exactly three sections:
1. APP DESCRIPTION: one paragraph of 120 to 160 words, in plain English and the present tense. It must cover who uses the app, the customer steps in order, the information collected, and what the owner sees.
2. TO CONFIRM: up to five bullet points. Each is a question I must answer, with your suggested default in brackets.
3. LEFT OUT ON PURPOSE: up to three features you excluded to keep version one simple, one line each.

RULES
- If information is missing, do not guess. Put it in TO CONFIRM with a sensible default.
- Never invent prices, opening hours, service names, reviews or legal claims.
- Collect only what is needed to deliver the booking. If anything is personal or sensitive under UK GDPR, such as health details, flag it in TO CONFIRM.
- Use pounds sterling, UK date format and British spelling.
- Say "customer", not "end user". No jargon.
- Do not add payments, logins or reminders unless my idea mentions them. Mention them under LEFT OUT ON PURPOSE instead.
- Tone: plain, practical, no hype.