How to build a system on Aigap.
A real-world walkthrough: 22 minutes from "I have an idea" to a fully working booking system. Here's what happens at each step.
The scenario
Customer: Hair Atelier — a boutique salon chain with 3 locations in Istanbul. They take appointments by phone today, with a paper book. Customer complaints about "no online booking" rose 40% in the last six months.
Need: Customers should be able to pick a date and time on the website and book. Staff should see their calendar with no conflicts. Customers should receive SMS reminders.
Budget: They can't hire a developer. The owner, Ezgi, is comfortable with Excel and not much more.
Step 1: Tell Aigap what you want (3 min)
We open aigap.com. Top right, click "Create a new system."
The chat opens and the conversation begins:
"Build an online booking system for a salon with 3 locations. The customer should pick a location, a service (haircut, color, blowout, etc.), and a stylist. Then see available dates and times. When a booking is made, send an SMS reminder 24 hours before."
Aigap thinks for a few seconds, then replies: "Got it. I'll propose a data structure and a screen flow — confirm and I'll start building."
Step 2: Review Aigap's proposal (2 min)
Aigap presents a summary:
- 4 main tables: Locations, Services, Stylists, Bookings
- 3 main screens: Customer booking, Stylist calendar, Admin dashboard
- SMS integration: Twilio (international) or a regional provider
- Estimated build time: 14 minutes
We review the tables and flow and request one small change: "Each stylist should see their own bookings, but only the location manager should see the other stylists' bookings." Aigap notes it, updates the flow, and waits for approval.
Step 3: Watch Aigap build (14 min)
When you click "Start," Aigap begins construction. On your screen, in real time, you see:
- Creating database… ✓
- Designing customer booking screen… ✓
- Wiring up calendar logic (conflict detection)… ✓
- Building stylist panel… ✓
- Setting up SMS integration… ✓
- Seeding test data (3 stylists, 8 services, 1 week of bookings)… ✓
A live preview opens as each component completes. You can test the customer screen while the rest is still building.
Step 4: Test it yourself (3 min)
When the build is done, Aigap says "Ready. You can test it now." You click the test link in the right panel:
Test flow: Pick location → Haircut → Stylist: Mehmet → Tuesday 2:30 PM. The booking goes through, and a test SMS arrives on your phone.
Ezgi says: "Good, but time slots should be every 15 minutes, not every hour." We tell Aigap; it changes the slot interval in 30 seconds.
Step 5: Go live (private or Store)
The system is ready. Two options:
(a) Private to Hair Atelier: Click "Publish." Aigap assigns a subdomain (e.g. hairatelier.aigap.app). You share that link with customers.
(b) Sell in the Onremo Store: If this system would help other salons too, click "Publish to Store." Aigap reviews it technically and lists it in the Onremo Store.
Total time: 22 minutes
Building this system the classic way: 2-3 weeks plus $1,500-3,000 to a freelancer.
Renting a SaaS solution and customizing it: $100-200/month, but never quite what you wanted.
With Aigap: 22 minutes plus a one-time fee (an average Onremo Store system runs $20-50/month or $50-200 one-time).
And if you publish to the Store, you can earn revenue from the system.
Next step
Open an account at aigap.com and start imagining your own system. Your Onremo account is already linked — nothing else to set up.
If you want to publish your system to the Store, follow the publishing guide.