A busy hair salon owner takes forty calls a day — half are "any slots left?" and "I need to reschedule." Miss one call and she may lose a NT$2,000 color job; mis-write one row and two clients show up at once. What an online booking system solves is not "looking trendier" — it is this money that leaks daily and no one ever tallies: missed calls, double-bookings, no-shows, and a phone chained to the front desk.
When It Fits vs. When to Wait
| Great fit for a booking system | Don't rush it |
|---|---|
| Services need time-slots and staff (clinics, salons, studios) | Selling in-stock goods with no appointment (that's a cart) |
| Phone/message bookings are too many to handle | Under 5 bookings a week — Excel + chat is enough |
| No-shows or double-bookings already cost money | Customers insist on talking to a real person |
| Want payments to take deposits and cut no-shows | Every service needs heavy custom quoting first |
| Need one calendar across branches/coaches | The team hasn't defined services and slot rules yet |
Alternatives Matrix
| Option | Pros | Cons | Cost band |
|---|---|---|---|
| SaaS (Calendly/SimplyBook) | Live same day, no maintenance | Per-seat fees, limited layout, your data on their servers | NT$300–1,500/seat/mo |
| Open-source self-host (Cal.com) | No license fee, deep custom, own your data | Needs hosting and upkeep | Host from NT$300/mo + build hours |
| Packaged plugin (Wix/WordPress Bookings) | Cheap, integrates with existing site | Stalls on complex rules (staff×slot×resource) | NT$0–800/mo + plugin |
| Full custom (ScriptWalker) | Rules, payments, notifications, reports exactly to your flow | High upfront, needs clear requirements | One-time build, from ~NT$80,000 |
Full Process Breakdown
- Week 1 | Requirements and rules (deliverable: rules table): In Notion, list every service, duration, staff, resource, buffer and cancellation policy. Nine in ten booking systems fail because this step wasn't cleaned up.
- Week 2 | Flow and screen design (deliverable: Figma wireframe): In Figma, draw the five steps — pick service, pick time, enter details, pay deposit, get confirmation — and let the owner click through.
- Weeks 3–5 | Build (deliverable: testable site): Backend in Laravel handles slot conflicts and staff scheduling; payments via ECPay or Stripe; notifications via LINE and email.
- Week 6 | Test and launch (deliverable: live site + admin training): Stress-test "two people grabbing the same slot," no-show auto-reminders and refund flow, then train front-desk staff on the admin panel.
Real Cost Breakdown
The "development fee" on the quote is the tip of the iceberg. Budget the hidden monthly costs first: payment fees (ECPay credit card ~2.75% + a few NT per transaction, Stripe ~2.9% + NT$10), SMS/LINE push (~NT$0.8–2 each), SSL and domain (~NT$1,500/yr, or free SSL via Cloudflare), hosting, and the most-forgotten "ongoing maintenance" — rules change, holidays need blocking, staff turn over, so reserve 15–20% of the build cost yearly. SaaS looks cheap, but with 8 staff at NT$800/seat that's nearly NT$80k a year — it crosses over with a one-time custom build.
Reality vs. What Clients Imagine
| Clients assume | What actually happens |
|---|---|
| "A booking page is quick, one week" | Rules mapping + payment testing is the real work, usually 5–6 weeks |
| "Customers will just use it after launch" | It needs nudging: QR, LINE menu, staff saying "please book online" |
| "Wiring payments is simple" | Refunds, partial refunds, invoices and reconciliation each need handling |
| "A system kills no-shows" | It only reduces them — deposits + auto-reminders make it work |
Common Pitfalls and How to Avoid Them
| Pitfall | Fix |
|---|---|
| Building before slot rules are clean | Complete the "staff×slot×resource" table before coding |
| Not handling "same-slot race" | Use DB locks/transactions for concurrency, not just front-end checks |
| Online only while staff still write by hand | Share one calendar between admin and online; ban two sets of books |
| No deposit, no-shows still explode | Always take a deposit or card hold for high-value services |
| Notifications only by email | In Taiwan customers watch LINE; email reminders get ignored |
| Forgetting the cancel/reschedule flow | Design cancellation policy and self-service rescheduling from day one |
Success Metrics + 90-Day Roadmap
- Day 30: Check whether "online booking share" reaches 40% and whether staff phone time drops.
- Day 60: Check whether the no-show rate falls (aim to halve it) and the deposit mechanism runs smoothly.
- Day 90: Check that double-bookings and complaints hit zero, and use admin reports to optimize scheduling around the busiest slots and staff.
Decision Checklist (self-check before you build)
- ☐ My daily phone/message bookings are too many to handle
- ☐ I can estimate how much no-shows cost me per month
- ☐ My services have clear durations and staff rules
- ☐ I'm willing to take deposits on high-value services
- ☐ At least half my customers will self-book on a phone
- ☐ I have a phone I want freed from "answering calls"
- ☐ I can state a clear cancel/reschedule policy
- ☐ I need one calendar across branches or staff
- ☐ I'll spend 5–6 weeks getting the rules clean
- ☐ I've budgeted maintenance (15–20% of build cost)
Frequently Asked Questions
Why not just use a SaaS like Calendly? Why customize?
For small teams with simple rules, SaaS is fine — start with the free/low tier. Customization pays off in three cases: complex rules (staff×slot×resource), needing local payments and invoicing, or so many staff that per-seat fees exceed a one-time build. Multiply staff × monthly fee × 12 and compare to a one-time build.
Does a booking system have to take deposits via payments?
Not always, but strongly recommended for high-value, high-no-show services. Deposits are the most effective way to cut no-shows — far more than reminders alone. If your price point is low and no-show cost is small, start with auto-reminders and add deposits later.
How long does it take and roughly how much?
A custom build from requirements to launch is usually 5–6 weeks, one-time from ~NT$80,000, depending on rule complexity, payments and notifications. On a tight budget, start with self-hosted Cal.com — much lower build cost — and expand later.
What if customers won't use it and keep calling?
This is the most common launch issue; the fix is 'nudge + rephrase': put the booking QR in your LINE menu, business card and in-store sign, and have staff say 'I'll send you the booking link — it's faster.' Online share usually climbs noticeably within one to two months.
Call to Action
If you checked more than half the list above, a booking system isn't a "whether" for you — it's "the sooner, the less you bleed." ScriptWalker offers one-stop booking system development from rules mapping, Figma design and Laravel customization to payments and LINE notifications (one-time build from ~NT$80,000), plus a low-cost Cal.com self-hosted option. Start with a 30-minute chat — we'll help you estimate how much you're losing monthly to missed calls and no-shows, then decide whether to build.
- Email: [email protected]
- Phone: 0916-224-047
- LINE: @ufv9089p