Online Forms & Data-Collection Systems: Self-Build, Google Forms, or Typeform? (Data Ownership, Payments, Costs)

Opening: a Google Form that broke at record 3,000

A training company collected sign-ups with Google Forms — smooth for six months. Then a popular course opened: 900 entries in two hours, payment was "wire to this account," and reconciliation was one assistant matching by hand. The result: overselling, refunds, and complaints all at once. What they needed wasn't a fancier form — it was a collection system that takes money, prevents duplicates, feeds a CRM, and keeps the data theirs.

Fit vs no-fit

Good fit for a real form/survey/collection system:

The form needs payment + receipts (registration, donations, orders).
Data must flow automatically into CRM/Google Sheet/LINE notifications.
Conditional logic (pick A shows B), multi-step, file uploads.
Data involves PII/medical/financial records needing self-hosting and audit.

Don't over-invest when:

Occasional non-paid RSVP, under 100 entries → Google Forms is enough.
Pure satisfaction survey, nice UI but no system integration → Typeform, no build.
One-off event, use-and-toss → not worth customizing.

Alternatives matrix

Option	Pros	Cons	Cost tier
Google Forms	Free, 5-min setup, data to Sheets	No payments, plain UI, weak logic, low brand	Free
Typeform	Great UX, strong logic, integrations	Responses/features gated to monthly plan, data on their platform, pricing rises with volume	~US$25–83+/mo
Self-build (Laravel)	Data ownership, deep payment/CRM integration, no response caps	Upfront dev cost, needs maintenance	From ~NT$60,000

Full process (tools + deliverables)

Phase 1 · Requirements & field design (3–5 days): map fields, logic, flow in Figma/Notion. Deliverable: field spec + wireframe.
Phase 2 · Form engine & admin (1.5–2 weeks): Laravel form, validation, dedupe, admin view/export. Deliverable: working admin.
Phase 3 · Payments & notifications (1 week): integrate ECPay or Stripe, e-receipts, LINE/Email on success. Deliverable: full payment flow.
Phase 4 · Data flow & integration (3–5 days): auto-write to Google Sheet/CRM, or webhook to n8n. Deliverable: automated data flow.
Phase 5 · Test & launch (3–5 days): load test concurrency, payment tests, accessibility. Deliverable: launch + handover docs.

Real cost breakdown

Development: basic system from NT$60,000; with payments + CRM ~NT$120,000–200,000.
Payment fees (hidden): ECPay card ~2.75%–3%, Stripe ~3.4% + fee, per official pricing.
SSL: free via Let's Encrypt, or commercial cert from ~NT$3,000/yr.
Hosting: entry VPS ~NT$500–1,500/mo.
Maintenance: recommended retainer ~NT$3,000–8,000/mo.

Reality vs client imagination

Client thinks: "A form is simple, a day or two." Reality: field logic + payments + dedupe + reconciliation — the complexity is all invisible.
Client thinks: "Google Forms is free, why pay?" Reality: no payments, no auto-reconciliation; manual labor eats the savings.
Client thinks: "The data is mine, obviously." Reality: on a third-party platform, data lives on their servers; export and deletion follow their rules.

Common traps and fixes

Trap: no dedupe on submit → Fix: idempotency key + frontend disable.
Trap: payment succeeds but data isn't saved (missed webhook) → Fix: queue retries + reconciliation job.
Trap: PII unencrypted/unaudited → Fix: encrypt sensitive fields, keep access logs.
Trap: peak-time concurrency spikes → Fix: load-test pre-launch, add queueing if needed.
Trap: forms too long, low completion → Fix: multi-step, ask only essential fields.

Success metrics + 90-day roadmap

Day 30: completion rate (submitted/started), payment success rate, any missed orders.
Day 60: optimize the most-abandoned field, A/B test form length, add auto reminders.
Day 90: pipe data into reporting/CRM for segmentation; evaluate expanding to other forms.

Decision checklist

☐ Does this form need to take payment?
☐ Will single-peak entries exceed 500?
☐ Does data need to auto-flow into CRM/Sheet/LINE?
☐ Does data involve PII/finance/medical?
☐ Do you need conditional logic or multi-step?
☐ Do you need your own brand look and URL?
☐ Will you use it more than once a year?
☐ Do you need full export/control of data?
☐ Any compliance (de-identification, audit) needs?
☐ Want to avoid response-count monthly fees scaling with volume?

5+ checked: self-build is worth evaluating; 2 or fewer: start with Google Forms/Typeform.

FAQ

Can Google Forms really not take payment?

Not natively. You can only place a bank account or an external payment link, still requiring manual reconciliation. For "pay on submit, auto-receipt," use paid Typeform integrations or self-build with ECPay/Stripe.

How much and how long for a self-built form system?

Basic from NT$60,000, ~3–4 weeks; with payments + CRM ~NT$120,000–200,000, ~6–8 weeks. Payment fees (ECPay ~2.75%–3%, Stripe ~3.4%) are ongoing — budget for them.

What's the risk of keeping data in Typeform?

Data lives on their servers, bound by their terms, retention, and export rules; deactivating an account can lock you out. For PII or data you must control long-term, self-host or at least export backups regularly.

How do I avoid overselling during a hot registration?

Enforce quota locking on the backend (with idempotency and transaction locks), not just a frontend number. Pair with queue processing and real-time inventory checks to avoid overselling when hundreds arrive in two hours.

Call to action

Unsure whether your form should be Google Forms, Typeform, or self-built? ScriptWalker offers form/data-collection planning and build (self-build from NT$60,000). Book a free 30-minute consult and we'll compute your three-year total cost first.