When should you use it?
- Clients book you through scattered DMs and no-shows are common
- You want to test an idea before paying a developer
- You can review an app's flows carefully
Not for: Taking real payments before security and refunds are reviewed; Launching without terms, privacy notice and testing
What do you need, and what do you get?
You need
- A one-paragraph product description
- Accounts for payments, email and sign-in
- Sample services and availability
You get
- A page where clients pick a slot
- An artist dashboard for bookings and availability
- Confirmation emails
How does it work, step by step?
- Describe the product in one paragraphName the calendar style, sign-in, payments and email services you want.
- Let it scaffold everythingAccept the backend, integrations and front end it generates first.
- Push on the hard partsTest time zones and double bookings yourself; that is where it struggled.
- Watch for regressionsIt sometimes rewrote working code; retest flows after each change.
- Hold payments until reviewedKeep deposits switched off until someone checks security and refunds.
The prompt
Our own prompt, inspired by Ilias Hatzis and written to work in Custom agent. Values in lime are placeholders.
Create appointment software for a one-person [service] business. Clients see the provider's availability, choose a service and time, and receive a confirmation email. Providers sign in, set availability and services, and see a dashboard of bookings. Use [sign-in, email and payment services], but keep payments in test mode. Handle time zones explicitly and block double bookings. After each change, list which flows I should retest.
Inspired by Ilias Hatzis: From Zero to Working Prototype in 48 Hours with Replit. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- The agent occasionally said a bug was fixed when it was not; verify by testing.
- Time-zone logic needed repeated correction.
Our take
Ilias Hatzis shows how quickly a niche product idea can now become something clickable, and also where that speed runs out. One paragraph got a working skeleton; the hard parts, time zones and polish, took real effort, and the post honestly records the agent rewriting working code and claiming fixes it had not made. Treat this as a way to validate an idea with real users, not as a launch. Before taking bookings, test the scenarios that hurt small businesses: overlapping appointments, a client in another time zone, daylight saving changes, cancellations and no-shows. Decide deposit and refund rules in writing, because software only enforces what you define. Keep payments in test mode until someone with security experience has reviewed authentication, password resets and how client data is stored, since a booking app holds names, phone numbers and sometimes health notes. Commit often so regressions can be undone, and keep a short log of what you asked for and what changed. Show it to two or three artists before building more.
Where the time goes back: A product idea becomes a clickable, testable prototype in a weekend instead of a hiring decision.
FAQ
Is it launched?
Were payments live?
Source and credit
Inspired by Ilias Hatzis. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- From Zero to Working Prototype in 48 Hours with Replit
- Creator
- Ilias Hatzis
- Published on
- iliashatzis.substack.com (Substack)
- Original date
- Jul 7, 2025
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.