A restaurant-brand owner brought us two quotes: vendor A at NT$180,000, vendor B at NT$95,000, with "roughly the same" features. He asked "why the gap," but the right question is another one — over three years, what will this website cost me in total? The quote is often just the tip of the iceberg. Here is a framework for total cost of ownership (TCO), so you compare three-year totals, not quotes.
Myths to Break
- Myth 1: "lower quote = cheaper." Truth: the quote covers the build only; payment fees, hosting, maintenance, redesigns, and third-party services accrue monthly and yearly — the three-year total is often 2–3x the build fee.
- Myth 2: "launch is the finish line." Truth: launch starts maintenance. A site with no maintenance budget gets slow, breaks, or gets breached within a year.
- Myth 3: "more features = better value." Truth: every feature is a maintenance liability. Unused features are not assets; they are regression-testing cost at every upgrade.
Core Framework: 3-Year TCO Formula
Split the total into five buckets, estimated over three years:
- TCO = build + fixed ops (host/domain/SSL/CDN) x36 months + transactional (payment fees x projected revenue) + maintenance (retainer or hours) x36 + change (annual redesign/new-feature reserve)
Payments are the most underestimated bucket: at ECPay published rates (~2.x% card) or Stripe ~3.4% + fixed, NT$10M annual revenue means NT$200k–340k in fees per year — nearly NT$1M over three years, often bigger than the build fee yet on no quote.
Three Typical Scenarios
- Startup/solo shop (revenue < NT$3M): low volume, TCO sits in build and maintenance; payment fees minor; use SaaS or light custom and keep cash for marketing.
- Growth SMB (~NT$10M): payment fees become significant, integration needs rise; TCO shifts from "build once" to "ongoing ops" — a retainer pays off.
- Mature enterprise (> NT$50M): fees, integration, audit, performance are all large; TCO is dominated by ongoing ops + change, where an in-house team or a deep outsourcing partner earns its value.
Hidden Cost Checklist
- Payment fees: 2–3.4% of revenue, compounding yearly (the most-missed big item).
- Hosting and traffic: VPS/cloud monthly, plus peak-season elasticity.
- Third-party services: SMS, email (Mailgun usage-based), maps API, support tools.
- Maintenance hours: dependency upgrades, security patches, bug fixes — if not outsourced, it is your staff's hidden hours.
- Change and redesign: a mid-redesign every 18–24 months, often 30–50% of the build budget.
- Opportunity cost: launch delays, dropped complaints, lost revenue from neglected SEO.
- Exit cost: data migration and rebuild when switching vendors.
Partner KPI Scorecard
- ☐ Quote split into build vs ops vs maintenance
- ☐ Proactively flags ongoing payment/hosting costs
- ☐ Maintenance SLA in writing
- ☐ IP and source-code ownership stated
- ☐ Data portability/exit plan offered
- ☐ Tech choices avoid needless lock-in
- ☐ Real cases and reachable past clients
- ☐ Clear contact and response times
- ☐ Change pricing defined (hours/fixed)
- ☐ Honest about "what you do not need"
ScriptWalker's Fit + When We Are Not
ScriptWalker builds on Laravel + Flutter with long-term retainer maintenance, and lays out three-year ops cost at quote time so clients decide on TCO, not a one-off price. We are not a fit when:
- You only want the lowest price and do not care about long-term maintenance or quality.
- Requirements change weekly with no willingness to do discovery first.
- You are large enough to need an in-house team and outsourcing would slow decisions.
Transition / Onboarding Playbook
- Month 1: assess current state, build the TCO sheet, define maintenance scope and SLA.
- Months 2–3: build or take over, add monitoring (UptimeRobot), backups, and a security baseline.
- Day 90: review three numbers — uptime, response time, and whether actual ops cost matches the TCO estimate — and adjust next quarter.
Decision Checklist
- ☐ I compare three-year totals, not one-off quotes
- ☐ I estimated three years of payment fees
- ☐ I budgeted for maintenance
- ☐ I know each feature's maintenance liability
- ☐ The quote splits build/ops/maintenance
- ☐ I confirmed code and data ownership
- ☐ I have an exit/data-portability plan
- ☐ I know the next redesign reserve
- ☐ I assessed opportunity cost
- ☐ My partner tells me the truth proactively
FAQ
Why do two quotes differ by nearly 2x?
Usually it is the unwritten parts: whether maintenance is included, self-host vs SaaS, IP ownership, performance and security baselines. Put both into one TCO sheet and the gap shows up in the ops and maintenance columns.
How much maintenance is reasonable?
It varies with update frequency and SLA. The point is not the number but whether security patches, dependency upgrades, monitoring, and backups are included — skip those and the savings come back doubled at the next outage.
Can payment fees be negotiated?
Rates are mostly published by the processor, with room at volume. More practically, price the fee into your products and TCO and pick the right processor by order value and refund rate, rather than discovering the margin hit later.
Call to Action
Want your site/system recalculated on three-year TCO? ScriptWalker offers a free 30-minute consult to lay out the real total behind the quote:
- Email: [email protected]
- Phone: 0916-224-047
- LINE: @ufv9089p