Payment protectionDetails
- Revisions within the package are free.
- If you do not respond within 3 days of delivery, the work is accepted automatically.
The money is reserved when you pay and released only once you accept the work.
Example result
Technical specification: booking website for a yoga studio
1. Project goals
- Let clients see the timetable and book a class in under one minute, from a phone.
- Sell class passes and memberships online.
- Cut the time staff spend on bookings from about 10 hours a week to under 2.
Success measures (3 months after launch): 70% of bookings made online; no-shows below 10%.
2. Users
| Role | What they need |
|---|---|
| Visitor | See classes, prices and teachers; buy a first-class trial |
| Client | Book and cancel classes, see remaining passes, join a waitlist |
| Teacher | See their own classes and the list of booked clients |
| Admin | Manage timetable, prices, passes, teachers and refunds |
3. Pages and screens
- Home: next classes today, trial offer, studio address.
- Timetable: week view, filters by class type, level, teacher and room.
- Class page: description, teacher, length, places left, Book button.
- Prices: single class, 5- and 10-class passes, monthly membership.
- Teachers: list and individual profiles.
- Account: upcoming bookings, history, passes, payment methods.
- Admin panel: timetable editor, client list, sales report.
4. Key features
4.1 Booking
- A client can book if they have a valid pass or pay for a single class.
- Class capacity is set per room (Room A: 18, Room B: 10).
- When a class is full, the client can join a waitlist; if a place opens, the first person in line gets it and receives an email and text message.
4.2 Cancellation
- Free cancellation up to 12 hours before class; the pass credit returns.
- Later cancellation or a no-show uses up the credit.
4.3 Payments
- Card payments through a payment provider chosen by the studio.
- Passes expire: 5-class after 2 months, 10-class after 3 months.
4.4 Notifications
- Booking confirmation, reminder 3 hours before class, waitlist updates.
5. Non-functional requirements
- Mobile-first; pages load in under 2 seconds on 4G.
- Works in the two latest versions of major browsers.
- Personal data stored in line with local data protection law.
6. Open questions
| # | Question | Who decides |
|---|---|---|
| 1 | Do teachers mark attendance in the app, or does the front desk? | Studio owner |
| 2 | Is a 2-week trial pass needed in addition to a single trial class? | Studio owner |
| 3 | Should the timetable be embedded on the current website or replace it? | Owner + developer |
| 4 | Which payment provider and text-message service are preferred? | Owner |
Client: Lotus Lane Yoga, a studio with 2 rooms, 9 teachers and about 60 classes a week. Today bookings go through direct messages and a paper sign-up sheet. Standard package: specification up to 10 pages. Excerpt below.
The client and all details are made up.
About this service
We write a product requirements document for an iOS or Android app: the problem, target users, core user flows, a screen list and features ranked by priority. Mobile-specific needs such as push notifications, offline mode, permissions and app store requirements are covered. Developers and studios get one document to estimate and plan from.
What is included
- What you getA PRD with problem, users, key flows, a screen list, prioritised features, mobile requirements and success metrics; Premium adds user stories and acceptance criteria. It comes as formatted text you can paste into a document or send to developers; any time or cost figures are rough guidance, not a quote.
- Key user flowsOnboarding, the main task and payment
- Screen listEach screen with its content and actions
- Mobile specificsPush, offline, permissions, store rules
- Success metricsWhat to measure after launch
How it works
- 1BriefYou describe the idea and users
- 2FlowsWe map flows and screens
- 3PRDWe write the requirements document
What we need from you
Your app idea, who uses it and when, the main features, iOS, Android or both, apps you like and your budget and launch date.
We will ask you:
- What problem does the app solve and for whom?
- iOS, Android or both?
- Which features are a must for launch?
- How will the app make money?
Compare packages
| Packages | BasicOne-page app brief$19 | StandardPRD up to 10 pages$39 | PremiumFull PRD with user stories$79 |
|---|---|---|---|
| Deadline | 1 day | 3 days | 5 days |
| Revisions | 1 | 2 | 3 |
| Length | 1 page | up to 10 pages | up to 20 pages |
| Screens listed | up to 10 | up to 25 | up to 40 |
| User stories and acceptance criteria | No | No | Yes |
| Order Basic | Order Standard | Order Premium |
Payment protection
You pay when you order, but the money is released only for accepted work.
- Fixed priceThe package price does not change after you pay.
- The money is reservedWhen you pay, the amount is only reserved. It is released to the service once you accept the work.
- Checked before deliveryEvery result goes through a quality check before it reaches you, and you see it on the order page before accepting it.
- Free revisionsAsk for changes within your brief as many times as the package allows.
- Acceptance after 3 daysIf within 3 days of delivery you neither accept the work nor ask for changes, it is accepted automatically. If you write in the order chat after delivery, the order waits; once we answer, we may start the 3 days again and will say so in the chat.
- Redo or a full refundIf the result does not match your brief and the revisions did not fix it, or the work takes more than twice its deadline, write in the order chat: we will redo the work or refund the payment in full.
Questions and answers
Do you design the screens?
No. We describe what each screen contains; a designer turns that into mockups.
Native or cross-platform?
We can note the options, such as Flutter or React Native, but the choice is best made with your developers.
Will it pass App Store review?
We list the store requirements we know of, but review decisions are made by Apple and Google.