ILLUSTRATIVE EXAMPLE · LOCAL WORKSHOPS

Let customers book and pay. Focus on the experience.

For cooking classes, creative workshops and local learning experiences: customers choose a session, reserve seats and pay on mobile while your team manages bookings and attendance in one place. One organiser, with a complete journey from discovery to attendance.

At a glance

Package: Production Web MVP
Illustrated build price: ⃁18,500
Launch Partners: ⃁14,500
Target delivery: 4–6 weeks after approved scope and required inputs
Outcome: Paid bookings, controlled seat availability and clear attendance

Who uses the product?

Adult customers discover experiences, book, pay and follow their own bookings. The organising team maintains sessions, bookings and attendance. The business owner manages staff access and the payment account and oversees operations.

The customer journey

Discover an experience and choose a session and seat quantity.
Sign in and review the details and price.
Pay and receive confirmation after payment is verified.
Return to the account to check the date or request cancellation.
Staff records the attended-seat count on the day.

What can you launch?

Experience listings with images, dates, prices and available seats.
Customer accounts, login and account recovery, with booking details.
Booking and one payment gateway, with seat protection and clear payment, cancellation and refund states.
An operations dashboard for sessions, bookings, payments and attendance, with filters, basic totals and export.
Email confirmations and important updates, with bookings still visible in the account if email is delayed.
A responsive Arabic and English interface, checked for text direction and mobile/desktop use.
Design, an interactive prototype, review and testing, review and live environments, appropriate monitoring/backups, recovery instructions and code handover.

How does the team operate it?

Add experiences, images and dates, then set each session's capacity and seat price. See paid, pending and cancelled bookings, review cancellation requests and export attendance. If a date changes or a session is cancelled, staff manages communication and affected bookings, initiates refunds in the gateway dashboard and sees the correct status in the product.

Deliberate launch choices

One organiser, one seat price per session and one session per purchase. Purchaser accounts are for adults, without individual attendee profiles; staff records attendance quantities in the dashboard. Child registration or specific consent arrangements need assessment before the proposal. Cancellation covers the whole booking under the organiser's published policy and applicable statutory rights.

What could come later?

Independent organisers and split payouts.
More complex ticket categories and pricing.
Native mobile apps or offline ticket scanning.

Detailed scope and launch acceptance

Detailed scope and operating rules

Accounts: visitors see published experiences, customers see only their own bookings, and authorised staff manages sessions and attendance. Customer/payment information is restricted to permitted users.
Sessions: each experience has a description, images and venue; each session has a date, capacity and price. Cancelled or unpublished sessions cannot be purchased, and a later price change does not rewrite an existing booking.
Reservations: seats are held temporarily during checkout under an agreed deadline. Repeated clicks do not reserve extra seats, and the last seat cannot be sold to two customers.
Payments: provider verification confirms the outcome; a success page alone does not confirm a booking. Failure/cancellation allows a controlled retry if seats remain, and duplicate notifications do not confirm another booking.
Late payments: if payment succeeds after the hold expires, availability is checked again. When no seats remain, the booking enters a visible resolution/refund process and the customer is notified instead of receiving an impossible reservation.
Cancellation/refunds: the customer requests whole-booking cancellation from its details; staff approves or declines with a reason. The decision appears in the account and queues an email. Staff initiates a full refund through the provider dashboard under the approved policy. Pending or failed refunds remain visible and are never shown as complete before confirmation. Individual-seat cancellation is outside this example; an unexpected partial refund is reconciled rather than misreported as a full refund.
Attendance: staff records an attended count from zero to the confirmed, non-refunded seat quantity, with authorised correction. A three-seat booking with two attendees records two; saving again does not increment it. Exports and totals distinguish paid, pending and refunded amounts without exposing unnecessary information.
Email: delivery failure does not undo a valid booking. Confirmation remains in the account, with retry and an appropriate operational alert.

How do we check that it is complete?

A customer buys seats and sees a confirmed booking, then staff records the correct attendance.
Concurrent attempts for the last seat cannot create two valid reservations; repeated clicks or payment events do not duplicate the operation.
Pending, failed and late payments have clear states and a recovery path without overselling.
A whole-booking cancellation request reaches staff, the customer sees approval or refusal, and a confirmed refund updates attendance eligibility and totals.
A three-seat booking with two attendees saves two and rejects a count greater than the purchased seats.
A customer cannot open another customer's booking or data; only authorised staff can export.
The Arabic and English journeys work on agreed mobile and desktop browsers.
Staging, production, monitoring and recovery setup are reviewed; test evidence and code are handed over with no unresolved critical or major defect against approved acceptance criteria.

What do we agree and review together?

We agree the cancellation policy, reservation deadline, late-payment handling and methods supported after provider approval, plus content, launch volume and operating responsibilities. Review starts with a written scope, one design direction and refinement, two consolidated coded-prototype rounds, progress demonstrations and final acceptance. Small journey refinements are assessed within the plan; material changes are discussed before work. Agreed-scope defects, necessary details we omitted and our estimating errors are not paid expansions or feedback rounds. The package includes fixes for agreed-scope defects reported within 14 calendar days of documented production handover, with covered reports followed through to resolution; ongoing maintenance and development are separate, without limiting statutory rights.

An illustrative scope that can be built within the package, not a delivered client project. The price covers the version described, not a fixed template for your idea. Your scope and price, including any Launch Partners offer, are confirmed in writing before you commit. Payment-provider, hosting and external service charges are disclosed separately before contracting. Target timing starts after approved scope, required inputs and necessary provider approvals.