Services

How to Build an Online Contract Signing / E-Signature System: Legal Validity, Payments, Self-Build vs SaaS (with real costs and a 90-day roadmap)

2026.07.07 · 52 views
How to Build an Online Contract Signing / E-Signature System: Legal Validity, Payments, Self-Build vs SaaS (with real costs and a 90-day roadmap)

A build framework that pins down Taiwan's Electronic Signatures Act, DocuSign pricing and real self-build costs — turning "print, mail back, scan and file" into a 10-minute online flow.

Share:

When "a contract takes three days" becomes an operations bottleneck

A B2B services company with 20 sales reps sends out roughly 120 quotes and service contracts a month. The flow looks like this: a rep edits a Word file, prints it, gets the client to sign, photographs or scans it back, then admin renames it and files it to a cloud drive. On average each contract takes 2.8 days from send to return, and 11 a month get bounced back because "the client forgot to sign the last page." Admin burns nearly 6 hours a week just chasing contract status. This isn't a technical problem — it's an undigitized process. An online signing system is the piece that compresses those 2.8 days into 10 minutes.

Where it fits × where it doesn't

E-signature isn't a cure-all. Before you start, confirm which side of the line your contract types and volume fall on.

Good fitPoor fit / handle with care
Quotes, service contracts, NDAs, purchase orders and other general business documentsReal-estate transactions and documents that require notarization or are excluded from electronic form (per Taiwan's Electronic Signatures Act and agency notices)
A steady 30+ contracts a month with high repetitionFewer than 5 a month, all with the same familiar clients — a free PDF sign-off may be cheaper
Cross-city or cross-border signing where mailing costs are highInternal rules requiring physical seals or paper originals on file
You need an audit trail (who, when, from which IP)Signatories who can't use a smartphone, where the training cost outweighs the benefit
You want to wire it to a CRM/back office so "deal closed" triggers signingVery high-value contracts where counterparty legal insists on a physical original

Alternatives matrix: self-build vs SaaS vs hybrid

Each path suits a different company size. Taiwan's Electronic Signatures Act, amended in 2024 and in force from 2025, establishes that electronic signatures generally carry the same legal effect as handwritten ones (see the Electronic Signatures Act on Taiwan's Laws & Regulations Database), which gives self-build a firmer compliance footing.

OptionProsConsCost band (TWD)Best for
Global SaaS (DocuSign / Dropbox Sign)Works out of the box, complete audit trail, high international recognitionPriced by envelopes sent — expensive at volume; largely English UISolo ~US$10–45/mo up, business tiers higher (see DocuSign official pricing)Moderate volume, frequent overseas clients
Local SaaS (e.g. Kdan / Taiwan e-sign providers)Chinese UI, local invoicing and support, familiar with local lawLimited customization; deep back-office integration is extra~NT$300–1,500/mo per userModerate volume, mostly domestic clients
Self-build (Laravel + PDF signing + audit log)100% data ownership, deep CRM/payment integration, no envelope capHigh upfront build cost; you own compliance and audit designOne-off NT$180,000–450,000 plus maintenanceHigh volume, deep integration with existing systems

Full process breakdown (with tools and deliverables)

ScriptWalker's "online signing system build" runs in five stages, for both self-build and hybrid:

  • Stage 1 · Requirements & compliance audit (weeks 1–2): inventory contract types, signing roles, notarization needs. Deliverables: contract flow diagram (Figma / Miro), compliance checklist, Electronic Signatures Act applicability assessment.
  • Stage 2 · Template & field design (weeks 3–4): convert Word contracts into PDF templates with dynamic fields, define signing order. Tools: Adobe Acrobat / PDF.js. Deliverable: a reusable template library.
  • Stage 3 · Signing engine & audit trail (weeks 5–8): build sending, signing pages, timestamps and an audit log in Laravel (recording IP, UA, sign time, document hash). Deliverable: a production-ready signing flow and API.
  • Stage 4 · CRM / payment / notification integration (weeks 9–10): wire the CRM so a closed deal triggers a contract, add LINE Notify / Email reminders, optionally collect a deposit via ECPay. Deliverable: end-to-end automation.
  • Stage 5 · Testing & go-live (weeks 11–12): multi-device testing, legal sign-off, launch and training. Deliverables: go-live report and operations manual.

Full cost breakdown

The build fee on the quote is only part of the ledger. Here's the three-year view for a self-build:

  • Build fee (one-off): NT$180,000–450,000, depending on template count and integration depth.
  • Timestamp / certificate service: if you need a trusted timestamp (TSA), priced by provider, typically a few to tens of NT dollars per document.
  • Payment fees (optional deposit): ECPay credit card is generally ~2.75%–3% (per the ECPay official rate page).
  • SMS OTP verification: if you verify identity by SMS, ~NT$0.8–2.5 per message.
  • Hosting & SSL: cloud hosting NT$1,000–5,000/mo; SSL can use free Let's Encrypt.
  • Maintenance: budget ~12%–18% of the build fee per year for security updates, legal changes and backups.

Implementation reality vs client imagination

Clients assumeWhat actually happens
"An e-signature can't be as valid as a stamped one"The Electronic Signatures Act generally gives e-signatures the same effect as wet signatures; the key is a complete audit trail and solid identity verification.
"Just build a signature canvas — two weeks, done"The canvas is the easy part; the real time goes into audit trail, signing order, compliance and template design.
"Clients will just use it"Older or less tech-savvy signatories need guidance; support volume rises briefly at launch, so prepare visual guides.
"SaaS is cheaper"SaaS is cheaper upfront, but at volume with deep integration, the three-year TCO often exceeds self-build.

Common pitfalls × how to avoid them

  • Storing only the signature image, not the audit trail: hard to prove in a later dispute. Fix: record IP, timestamp, UA and document hash in full.
  • Hard-coding the signing order: any change to a multi-party flow means code changes. Fix: make the signing flow configurable data, not hard code.
  • No tamper protection: a signed PDF can be altered invisibly. Fix: hash and seal the document after signing, then verify integrity by comparing hashes.
  • Ignoring non-eligible documents: dropping documents that can't be electronic into the system. Fix: run the compliance audit in Stage 1 and flag ineligible documents in the UI.
  • No reminders or expiry: a sent contract vanishes into silence. Fix: build in automatic Email/LINE reminders and auto-expiry when overdue.
  • Weak identity verification: a single link is enough to sign, inviting impersonation. Fix: add SMS OTP or a second Email verification.

Success metrics + post-launch 90-day roadmap

  • Day 30: check whether "average contract turnaround" drops from 2–3 days to under 1 day and completion rate exceeds 85%. Optimize the signing page's mobile usability (target LCP < 2.5s, see web.dev Core Web Vitals).
  • Day 60: check whether re-signs caused by process errors fall below 3% and support tickets recede. Auto-fill client data into templates to cut manual entry.
  • Day 90: measure total hours saved (target: 4–6 admin hours a week) and the share of "close-to-sign" automation after CRM integration. Start analyzing the signing funnel to find the stuck steps.

Decision checklist (should you self-build an online signing system?)

  • ☐ My monthly contract volume exceeds 30 and is expected to grow
  • ☐ My contracts are mainly general business documents, not real estate or notarization types
  • ☐ I need a complete audit trail for dispute evidence
  • ☐ I want the CRM/back office to auto-trigger signing after a deal closes
  • ☐ I care about keeping 100% of contract data in my own hands
  • ☐ SaaS is priced per envelope, and I've calculated a three-year TCO above self-build
  • ☐ I have budget for a one-off build fee above NT$180,000
  • ☐ I'm willing to budget annually for maintenance (12%–18% of the build fee)
  • ☐ Most of my signatories can operate a phone or computer
  • ☐ I have an internal contact for legal sign-off and testing

Seven or more checked: self-build or hybrid is worth serious evaluation. Three or fewer: start pragmatically with local or global SaaS.

FAQ

Are e-signatures really legally valid in Taiwan?

Yes. Taiwan's Electronic Signatures Act generally grants e-signatures the same effect as handwritten ones, though certain documents (such as specific real-estate transactions or those requiring notarization) are excluded by law or agency notice. In practice the key is whether identity verification and the audit trail are complete — the exact thing self-build should guard.

How much cheaper is self-build than DocuSign?

DocuSign is priced by plan and envelopes sent, with solo plans from about US$10/month and business tiers higher. Self-build is a one-off NT$180,000–450,000 plus maintenance, with no envelope cap. At high volume with deep integration, self-build's three-year total cost of ownership typically comes in below SaaS within two to three years.

Can a signed contract be tampered with? How do you prove it wasn't?

The correct approach is to generate a hash of the PDF after signing and seal it; any later change makes the hash mismatch. Combined with a timestamp and audit log (IP, time, device), you can prove in a dispute that the document hasn't changed since signing.

What if clients don't know how to use it?

The key is a signing page you can use by tapping a link — no sign-up, smooth on mobile. Prepare a visual guide at launch and keep a support contact; inquiries usually drop noticeably within two weeks.

Can we sign first and collect the deposit later?

Yes, and it can be automated. A common ScriptWalker pattern is to auto-trigger an ECPay payment link once signing completes, so "signing" and "collecting" happen in one flow and cut admin chasing.

Next step: digitize your contract flow

ScriptWalker is a development studio focused on Laravel + Flutter. We offer "online signing system builds" starting at NT$180,000 for self-build, covering the compliance audit, template design, audit trail and CRM/payment integration. Want to confirm whether your contracts are a fit for going electronic first? We offer a free 30-minute consultation and a self-assessment sheet.

Share: