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
When a shop has to talk to a CRM, or a booking system to accounting, projects stall on questions nobody wrote down: which field maps to which, what happens on a duplicate, which side wins when both change. We describe the integration between your two systems: the events that trigger an exchange, the direction of each data flow, a field mapping table, rules for duplicates, deletions and errors, and what each side must log. Your developer or integration partner can estimate and build from it without a week of calls.
What is included
- What you getAn integration requirements document with systems and goal, triggers and data flows, a field mapping table with formats, sync and conflict rules, error handling and open questions, as formatted text; any effort figures are rough guidance, not a quote.
- Data flowsWhat goes where, on which event
- Field mappingSource field, target field, format and rule
- Conflict rulesDuplicates, deletions and which side wins
- Errors and logsRetries, alerts and what gets recorded
- Open questionsWhat to confirm with each vendor
How it works
- 1BriefYou name the systems and the data
- 2MappingWe map flows, fields and rules
- 3RequirementsYou hand the document to your developer
What we need from you
The two systems and what you use each for, which data has to move and when, the fields you know about, links to their public API documentation if you have them, and problems you have today.
We will ask you:
- Which two systems need to be connected?
- Which data should move, and in which direction?
- How fresh must the data be?
- Is there a ready connector or plugin you have looked at?
Compare packages
| Packages | BasicOne data flow$19 | StandardUp to 4 data flows$39 | PremiumUp to 10 data flows$79 |
|---|---|---|---|
| Deadline | 1 day | 3 days | 5 days |
| Revisions | 1 | 2 | 3 |
| Data flows | 1 | up to 4 | up to 10 |
| Field mapping table | Yes | Yes | Yes |
| Test scenarios | 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 check that the APIs really allow this?
We read the public documentation you link and note limits we find, but we do not test the APIs. Your developer confirms the details before building.
Will you connect the systems for me?
No, we write the requirements only and never log in to your accounts.
Can it cover a no-code tool like Zapier or Make?
Yes. The same flows and mapping work as a plan for a no-code scenario; say so in the brief and we describe it step by step.