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
Browser extensions are small, but store reviewers are strict: every permission must be justified, data use must be disclosed, and Chrome now accepts only Manifest V3 extensions. We write a specification that covers what the extension does on which sites, the popup, options page and in-page elements, the permissions it needs and why, where data is stored and the store listing requirements. A developer gets a clear task, and you avoid a rejection for asking for too much access.
What is included
- What you getAn extension specification with goals, user flows, interface parts, a permissions list with reasons, data storage and privacy notes, store listing needs and open questions, as formatted text; any time or cost figures are rough guidance, not a quote.
- User flowsWhat users click and what happens
- Interface partsPopup, options page, side panel, in-page elements
- Permissions with reasonsThe minimum access, explained for reviewers
- Data and privacyWhat is stored, where and what is sent
- Store listingChrome Web Store, Edge and Firefox needs
How it works
- 1BriefYou describe the extension and sites
- 2PlanningWe map flows, interface and permissions
- 3SpecYou get a specification for a developer
What we need from you
What the extension should do, on which sites, which browsers you need, similar extensions you know, whether users sign in or pay and any service it must connect to.
We will ask you:
- What should the extension do?
- On which sites will it work?
- Which browsers do you need?
- Will users sign in, pay or sync data?
Compare packages
| Packages | BasicOne-page brief$15 | StandardSpec up to 5 pages$29 | PremiumSpec up to 10 pages$55 |
|---|---|---|---|
| Deadline | 1 day | 3 days | 5 days |
| Revisions | 1 | 2 | 3 |
| Length | 1 page | up to 5 pages | up to 10 pages |
| Browsers | 1 | up to 2 | up to 3 |
| 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
Why do permissions matter so much?
Broad access like reading all sites triggers longer reviews and scares users off at install. The spec asks only for what each feature needs.
Can one extension work in Chrome, Edge and Firefox?
Mostly yes, as they share the WebExtensions approach. The spec notes the differences your developer should plan for.
Will you publish the extension?
No. We write the specification and listing requirements; publishing is done from your developer account.