One module, at its list price, taken apart.

The module

Appointment booking and scheduling, from the catalogue at its fixed price. Nothing here is a special case: this is the same module, at the same price, that a proposal would quote.

What it does — the acceptance criteria

This is the document the module is signed off against. It is written before anything is built, and a gap against it is a defect we fix at our cost.

• A customer can see available slots for a chosen service and staff member, and book one without creating an account.
• Slots respect each staff member's working hours, breaks, leave, and the public holiday calendar.
• Two people cannot book the same slot. The second one is told, at the moment it happens, not afterwards.
• A booking sends a confirmation to the customer and a notification to the front desk.
• A customer can cancel or reschedule from the link in their confirmation, within a window you set.
• The front desk can see the day and the week, book on someone's behalf, move a booking, and mark a no-show.
• An owner can set services, durations, staff, hours, holidays and the cancellation window without a developer.
• It works on a phone, a tablet and a desktop, and it is usable on a slow connection.
• Failures are visible: a booking that could not be saved says so and does not silently disappear.

Nine statements. If all nine are true on submission, the module is done; if one is not, it is a defect.

What the three weeks are spent on

Every module carries all eight layers. They are not line items you can decline — a booking system without testing is not cheaper, it is unfinished.

What it does not include

Stated as plainly as what it does, because an omission discovered at handover is worse than a higher price agreed up front.

• Hosting: Your product runs in a hosting account in your name, paid to that provider — typically ₹2,000–₹25,000 a month for a small business product. We set it up and look after it; we do not resell it.
• Payment collection: Taking money for a booking is a separate module (online payments, ₹24,000). Gateway fees are the gateway's, billed to your account.
• A mobile app: This price is the web app. The same module as a native Android and iOS app is the catalogue price plus 10%, plus store setup and submission.
• Anything not in the nine criteria: Group bookings, recurring appointments, a waiting list, deposits, multi-location — each is a real thing people want, each is quoted as its own module or change order, and none is assumed.

Why it is not more

A booking workflow from an agency is usually ₹1.5–4 lakh, and most of that difference is hours, not quality. Two things remove those hours here rather than shortening the work.

The requirements document is written with an AI assistant while you describe the project, so the discovery phase that agencies bill for as a project of its own is absorbed. The building is done by our engineers. The screens are generated from your design system by SketchXFlow itself and then finished by hand, so design time is spent on judgement instead of on drawing.

What is not removed: the architecture sign-off, the testing, the project management and the handover. Those are the parts that decide whether the thing still works in six months, and they are in every module's fixed price.

Questions