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
Developers build what the ticket says, so a feature described as "add notifications" can turn into a week of guessing. We take the features you plan for your product and write them as user stories with acceptance criteria in Given, When, Then form, add edge cases such as empty states, errors and permissions, and split big items into stories a team can finish in one sprint. You can paste them straight into Jira, Linear, Trello or YouTrack.
What is included
- What you getA backlog of user stories grouped by feature, each with acceptance criteria, edge cases and open questions, plus a suggested priority order, as formatted text ready to paste into your tracker.
- User storiesAs a role, I want, so that
- Acceptance criteriaGiven, When, Then for every story
- Edge casesEmpty states, errors, permissions, limits
- Sprint-sized itemsBig features split into small stories
- Priority orderWhat to build first and why
How it works
- 1BriefYou describe the product and features
- 2WritingWe write stories, criteria and edge cases
- 3BacklogYou get stories ready for your tracker
What we need from you
A short description of your product and its users, the features you want to add, screenshots or links to the current version if it exists, and any rules the features must follow.
We will ask you:
- What is the product and who uses it?
- Which features should the stories cover?
- Which user roles exist in the product?
- Which tracker do you use?
Compare packages
| Packages | BasicUp to 3 features$19 | StandardUp to 8 features$39 | PremiumUp to 15 features$79 |
|---|---|---|---|
| Deadline | 1 day | 3 days | 5 days |
| Revisions | 1 | 2 | 3 |
| Features covered | up to 3 | up to 8 | up to 15 |
| User stories | up to 10 | up to 30 | up to 60 |
| Priority order | No | Yes | Yes, with release plan |
| 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 estimate story points?
No. Estimates belong to your team, who know the code. We mark stories that look large or risky so they discuss them first.
Can you write stories for an existing product?
Yes. Describe or show the current behavior with screenshots or links, and we write the new stories around it.
Can you import them into Jira for us?
No, we do not need access to your tracker. Each story is formatted so you can paste it as a new ticket.