Benchmark #1 · SlotKeeper · Tested Oct 14–15, 2026
Base44 builds a working booking app in under 10 minutes
| Works end to end | 30/30 |
| Time to first working version | 15/15 (8–9 min) |
| Bugs | 11/15 (4 minor, 0 critical/major) |
| Deploy ease | 15/15 (4 clicks, ~45 s) |
| Cost | 10/10 (free tier) |
| Design / UX | 11.25/15 (avg of 2 reviewers: 12.5, 10) |
Verdict
Base44 got to a first working version of SlotKeeper, a booking and waitlist app for a demo yoga studio (Maple Yoga Studio), in 8–9 minutes, with no fix prompts and no clarifying questions. It then passed all 10 checklist items on the live URL. It deployed free in 4 clicks and finished on the free tier. We found 4 minor bugs and no critical or major ones. Final score: 92.25/100: 81 of 85 non-design points plus 11.25/15 for design, the average of two independent reviewer scores.
Disclosure: affiliate link. If you sign up through it, BenchCoded may earn a commission at no cost to you. It doesn't affect our scores. Learn more.

What we tested
Benchmark #1 is SlotKeeper. Customers book slots and join a waitlist, and an owner manages slots and bookings. We tested it Oct 14–15, 2026 on Base44's free plan. Base44 didn't show which AI model it used. Our method: one fixed prompt, at most 5 fix prompts, no hand-editing of code, a 90-minute cap, a 10-item checklist and a fixed rubric (methodology).
Live app: maple-slot-flow.base44.app
How it went
We submitted the prompt at about 17:16 EDT, and the first working version was done by about 17:25. It needed zero fix prompts and asked no clarifying questions.
Base44 tested its own work while it built. It hit a platform rate limit, so it rewrote the booking functions to make fewer database calls. It also patched Radix dialog buttons that couldn't be clicked. It flagged that it couldn't verify the /admin redirect or the owner sign-up flow. Both passed later in our testing.
The stack is a React frontend with shadcn/Radix components, Base44's built-in database (Slot and Booking tables), backend functions, and built-in auth. Owner sign-up sends a 6-digit email code that expires in 10 minutes, so a fake address won't work.
Publishing used the in-tool Publish button: 4 clicks, about 45 seconds, free, and it gave us a public base44.app URL.
Checklist (all pass)
- 3 seeded slots
- Booking reduces spots left
- Form validation
- Bookings persist after refresh
- Waitlist with position #1
- Duplicate email blocked
- Owner sign-up with email code, and logged-out /admin redirects to login
- Create, edit and delete a slot
- Cancelling auto-promotes waitlist #1
- Stats line correct at every step

What broke
All 4 bugs are minor:
- The name error banner stays up after it's fixed. To reproduce, submit an empty form, fill in the name, enter a bad email, and submit again.
- Invalid emails (e.g. "abc") are caught only by the browser's native popup. There's no in-app message.
- The free-plan "Edit with Base44" badge covers content on mobile on the public page.
- A promoted booking still shows "#1". After auto-promotion, the admin list shows "#1 · Test Three", a leftover waitlist prefix.
Also noted (not scored as bugs): the admin's cancel "X" button has no accessible name; the seeded 9:30 slot is 90 minutes long; customers can't cancel their own booking (not requested).

Caveats
- No visible credit usage. We can confirm the build stayed on the free tier but can't say how many credits it used.
- Data persistence across a redeploy wasn't tested.
- Security was probed only at the UI level. We didn't test unauthenticated reads against the backend API.
- The design score is subjective. Both reviewers credited a cohesive, calm visual system, strong type pairing, a real hero image, and clear status chips. Points came off for the badge overlap on mobile and the generic owner login.
How Base44 compares
| Tool | Score | First working version | Deploy | Critical | Minor |
|---|---|---|---|---|---|
| Base44 | 92.25/100 | 8–9 min | 4 clicks, free | 0 | 4 |
| Lovable | Testing in progress | ||||
| Bolt | Testing in progress | ||||
| Cursor | Testing in progress | ||||
Pros and cons
- First working version in 8–9 minutes with zero fix prompts
- All 10 checks pass, including owner auth and waitlist auto-promotion
- Free, one-step publish (4 clicks, ~45 s)
- Finished on the free tier
- No critical or major bugs
- 4 minor bugs, including weak in-app email validation
- The free-plan badge covers content on mobile
- No visible credit usage
- No customer self-cancel (not requested)
Who it's for
Non-developers and small business owners who want a working booking site with an owner admin, deployed quickly and free. Before you rely on it, check how it handles backend security and redeploys, since we didn't test either.
Build your booking app with Base44 →
Disclosure: affiliate link. If you sign up through it, BenchCoded may earn a commission at no cost to you. It doesn't affect our scores. Learn more.
FAQ
Can Base44 build a booking app?
Yes. In BenchCoded's Benchmark #1, Base44 built SlotKeeper, a booking app with an owner admin, that passed all 10 checklist items. The checks covered booking, waitlist, duplicate blocking, owner sign-up, and auto-promotion.
How long does it take Base44 to build a booking app?
In our test, Base44 reached a first working version in 8–9 minutes with no fix prompts and no clarifying questions.
What bugs did Base44's booking app have?
Four minor bugs: a name error banner that stays up after it's fixed, invalid emails caught only by the browser's popup, a free-plan badge that covers content on mobile, and a leftover "#1" label on promoted bookings.
What score did Base44 get?
Base44 scored 92.25/100 on BenchCoded's SlotKeeper benchmark: 81 of 85 non-design points plus 11.25/15 for design, the average of two independent reviewers' scores (12.5 and 10).
Is Base44 free for building a booking app?
Our build finished on Base44's free plan and deployed free. Base44 doesn't show credit usage, so we can't say how much of the free allowance it used.
Do I need to code to use Base44?
Not for our SlotKeeper build. Our method bans hand-editing code, and Base44 produced a working app from one prompt with zero fix prompts.
Get each new benchmark when it lands
One email per new test: the scores, the bugs, and the verdict. Nothing else.