Replit Agent builds a tattoo booking prototype
Ilias Hatzis reports using Replit Agent to build a tattoo-artist booking prototype over a weekend, with booking flows and email confirmations but payments still on the roadmap.
Original prompt
Shared by the source author. See source notes for context.
calendar like Calendly, Google OAuth, Stripe deposits, Postmark notifications
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Ilias Hatzis
- Original account
- Read the source ↗
- Published
- 7 Jul 2025
- Source link checked
- 15 Oct 2026
- Reported result
- Ilias Hatzis reports using Replit Agent to build a tattoo-artist booking prototype over a weekend, with booking flows and email confirmations but payments still on the roadmap.
- Human involvement
- Hatzis checks behavior, corrects time-zone issues and directs revisions. The prototype was unlaunched and payment collection remained on the roadmap.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Hatzis briefs Replit Agent on a tattoo booking service and its integrations.
- The agent scaffolds backend and frontend application components.
- Hatzis tests time zones, reports failures and requests UI revisions.
Ilias Hatzis used Replit Agent to prototype a booking service for tattoo artists. His opening brief requested a calendar, Google authentication, Stripe deposits and Postmark notifications. The agent scaffolded a backend and React frontend and connected the proposed integrations.
The build remained interactive. Hatzis describes challenging time-zone handling, reporting broken behavior and pushing for interface improvements over the weekend. The resulting prototype allowed clients to see availability and book appointments, while artists could manage availability, clients and bookings. The account says the system checked time conflicts and sent confirmation emails.
The payment claim needs qualification. Although Stripe was connected and configured, the article explicitly places accepting payments and managing deposits on the roadmap. It would therefore be inaccurate to describe a completed paid-booking transaction or assume deposit collection was working end to end.
Hatzis also says the product had not launched. Its reported outcome is a working prototype with booking logic and several integrations, rather than a proven service used by tattoo businesses. He notes that the agent sometimes rewrote working code or claimed fixes while breaking something else. Human testing, clarification and product decisions were part of achieving the result.
Prompt
Original prompt
Source: iliashatzis.substack.com · Ilias Hatzis
Frequently asked questions
Could it collect deposits at publication?
Stripe was connected, but accepting payments and managing deposits were explicitly roadmap items.
Was the product launched?
The author says the functional prototype had not yet launched.
What did human testing address?
Hatzis reports time-zone problems, broken behavior and interface revisions.
More details
Remaining steps
- The prototype supports bookings and email confirmations; payment collection remains future work.
About this account
Replit Agent generated booking application code and configured integrations through iterative natural-language corrections.
Original account opened and read. Original prompt excerpt from the published task or operating rules; additional context is omitted. Outcomes are author reports, not independently reproduced.
Credit: Ilias Hatzis
Source published 7 Jul 2025
Source checked 15 Oct 2026
Tools and topics
Replit Agent · React · Postmark · Stripe
Replit Agent · React · Postmark
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.