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
A SaaS product is more than its main feature: sign-up, trials, plans and limits, team invites, roles, billing, cancellations and the admin panel all need decisions before code is written. We write product requirements that cover the core workflow and this whole account layer, from the first sign-up email to a failed card payment. Your development team or agency gets a document they can plan the first release from.
What is included
- What you getProduct requirements with goals, user roles, the core workflow, account and billing scenarios, a roles and permissions matrix, admin needs, release scope and open questions, as formatted text; any time or cost figures are rough guidance, not a quote.
- Core workflowThe job users come to do, step by step
- Account layerSign-up, trial, invites, password reset
- Plans and billingLimits, upgrades, failed payments, cancellation
- Roles and permissionsFrom Standard: who can see and do what
- Release scopeFirst version separated from later ideas
How it works
- 1BriefYou describe the product and plans
- 2RequirementsWe map workflows, accounts and billing
- 3DocumentYou get requirements for the first release
What we need from you
What the product does and for whom, your planned plans and prices, the features of the first version, competitors or tools you admire and the payment provider you prefer if any.
We will ask you:
- What does the product do, and for whom?
- How will you charge?
- Which features must be in the first release?
- Will users work alone or in teams?
Compare packages
| Packages | BasicOne-page product brief$19 | StandardRequirements up to 10 pages$39 | PremiumFull requirements up to 20 pages$79 |
|---|---|---|---|
| Deadline | 1 day | 3 days | 5 days |
| Revisions | 1 | 2 | 3 |
| Length | 1 page | up to 10 pages | up to 20 pages |
| Roles and permissions matrix | No | Yes | Yes |
| 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 help with pricing?
We describe the plan structure you choose and how limits work in the product. Picking prices is a business decision; our financial forecast service can test options.
Do you cover GDPR and data deletion?
We include data export and account deletion as requirements and flag privacy questions. This is not legal advice; check compliance with a lawyer for your markets.
Will you choose the tech stack?
We can note common options, but the stack is best chosen with the team that will build and support it.