Your application, built before you engage us.

Nothing. The demonstration is included, and we build it before any payment because it represents our work considerably better than a presentation does. If you review it and decide against proceeding, nothing is owed. Websites and online stores are handled differently: a demonstration would constitute most of the finished product, so these are quoted directly from your submission.

You do. The application is published under your own Apple and Google developer accounts, in your name, and you control the listing. We build it, submit it, and host the backend that supports it. Should you choose to leave, you retain the store listing and receive a complete export of your data.

Service businesses whose customers book time or purchase from a defined list: clinics and med spas, gyms and studios, salons and barbers, dental and veterinary practices, trades and home services, restaurants, tutoring, and professional services. If your customers currently book by telephone, direct message, or an outdated web form, an application is likely worthwhile. We do not build marketplaces or social networks.

The demonstration is ready six business days after we receive your form, followed by three to five days for the revisions you request. Upon agreement, the production build takes four to eight weeks depending on scope: live data, payments, staff and room scheduling, and testing on physical devices all require considerably more time than the demonstration. Allow a further week for the store listing and Apple's review, which typically takes one to three days but occasionally returns items requiring correction.

Realistically this is eight to twelve weeks from first contact to launch. Any firm quoting three weeks for a custom application is either excluding review time or has not completed the process before.

Because the demonstration need only function correctly along a single path. The production application must handle every case: a booking that fails partway through, a customer without a connection, two staff members double-booked, a declined card. It also requires your live data migrated in, testing on physical devices rather than a simulator, and it must satisfy Apple's reviewers.

The demonstration remains genuinely useful; it is the fastest way to establish whether the project is worth undertaking. It is simply not the finished product, and we prefer to state that at the outset rather than at week four.

In many cases, yes. If your current system provides an API, we can synchronise availability in both directions. If it is a closed system, the application becomes your booking system and we migrate your catalogue across. We will confirm which applies during the first call, not after an agreement is signed.

Text changes, pricing updates, new services and defect fixes are covered by the retainer and are typically delivered the same day. Larger new features are quoted separately before any work begins; you will not receive an unexpected invoice.

No. You register the developer accounts in your name and add us as a manager, which takes approximately fifteen minutes. We handle the builds, screenshots, listing copy, submission, and all correspondence with Apple's reviewers.