成果範例
標準版方案範例
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.
客戶與所有細節皆為虛構。
關於此服務
SaaS 產品不只有核心功能：註冊、試用、方案與限制、團隊邀請、角色、計費、取消與管理後台，都需要在寫程式前做出決定。我們撰寫的產品需求涵蓋核心工作流程與整個帳號層，從第一封註冊郵件到信用卡付款失敗。您的開發團隊或代理商會拿到一份可據以規劃第一個版本的文件。
包含內容
- 您會收到什麼產品需求，包含目標、使用者角色、核心工作流程、帳號與計費情境、角色與權限矩陣、管理需求、發布範圍與待釐清問題，格式化文字；任何時間或費用數字僅為粗略參考，並非報價。
- 核心工作流程使用者來完成的事，逐步說明
- 帳號層註冊、試用、邀請、密碼重設
- 方案與計費限制、升級、付款失敗、取消
- 角色與權限標準版起：誰能看到與做什麼
- 發布範圍第一版與後續構想區分開來
服務流程
- 1需求說明您描述產品與方案
- 2需求我們整理工作流程、帳號與計費
- 3文件您會收到第一版的需求文件
需要您提供的資料
產品的功能與對象、您規劃的方案與價格、第一版的功能、您欣賞的競爭對手或工具，以及您偏好的付款服務商（若有）。
我們會詢問您：
- 產品的功能是什麼，給誰使用？
- 您打算如何收費？
- 第一版必須包含哪些功能？
- 使用者是單獨使用還是以團隊使用？
比較方案
付款保障
下單時付款，但只有在驗收成果後，款項才會撥付。
- 固定價格付款後，方案價格不會變動。
- 款項先行保留付款時，金額只會先保留，在您驗收後才會撥付給服務。
- 交付前檢查每份成果在交到您手上之前都會經過品質檢查，您也可以在驗收前於訂單頁面查看成果。
- 免費修改在需求說明範圍內，可依方案允許的次數提出修改。
- 3 天後自動驗收若您在交付後 3 天內未驗收也未提出修改，成果將自動驗收。若您在交付後於訂單聊天室留言，訂單會暫停自動驗收；我們回覆後，可能會重新起算 3 天，並會在聊天室中告知。
- 重新製作或全額退款若成果不符合您的需求說明且修改後仍未改善，或製作時間超過交付期限的兩倍，請在訂單聊天室留言：我們將重新製作，或全額退還款項。
常見問題
你們會協助訂價嗎？
我們會描述您選擇的方案結構，以及限制在產品中如何運作。訂價是商業決策；我們的財務預測服務可以測試各種選項。
你們有涵蓋 GDPR 與資料刪除嗎？
我們將資料匯出與帳號刪除納入需求，並標出隱私問題。這不構成法律意見；請針對您的目標市場請律師確認合規性。
你們會選擇技術架構嗎？
我們可以註明常見的選項，但技術架構最好與負責建置與維護的團隊一起決定。
沒有找到您要的答案？