How to Build an Internal Approval / Workflow (BPM) System: Dynamic Forms, Multi-Stage Sign-off and Audit Trails — Cost and 90-Day Roadmap

Seventeen unsigned reimbursement forms sit on the finance lead's desk; a salesperson keeps chasing "did my purchase from last week get approved?"; the boss is travelling and the whole chain is stuck in his unread LINE messages. This is daily life at many 30–200-person companies — not a missing system, but "approval" scattered across email, LINE and paper, with no one able to say where a form is stuck or for how long. Here's how to turn it into an internal approval / workflow (BPM) system: real costs, tools, and a 90-day rollout.

When It Fits vs When It Doesn't

• Fits: ≥50 approvals/month (reimbursement, purchasing, leave, stamp use, contracts); two or more sign-off stages; you need an audit trail (who approved what, when); multi-department or multi-site; the boss wants to "see where it's stuck at a glance."
• Doesn't fit: <10 people where approval is a single word; a process that changes every month and isn't settled; you just want an e-form, not sign-off stages (Google Forms is enough); a budget below the system's minimum scope with no willingness to use off-the-shelf SaaS.

Alternatives Matrix

Full Process Breakdown (Stage × Time × Deliverable × Tools)

• Stage 1 · Process audit (1–2 wks): interview departments, map current flows and stage rules. Deliverables: process list + approval matrix. Tools: Miro/Figma, Notion.
• Stage 2 · Form and stage design (1–2 wks): define dynamic form fields, conditional stages (extra approver above an amount), delegate rules. Deliverables: form prototype + stage spec. Tools: Figma.
• Stage 3 · Development (3–5 wks): build the approval engine, permissions and audit trail on Laravel; wire LINE/Email notifications. Deliverables: working system + test environment.
• Stage 4 · Pilot and training (2 wks): run one department first, fix, then roll out. Deliverables: user manual + go-live.

Real Cost Breakdown

For a custom system covering 4 form types, 3 approval stages, LINE notifications and audit reports: build is roughly NT$180,000–350,000 depending on stage complexity. Don't forget hidden costs: hosting/VPS ~NT$800–2,500/mo, SSL (usually included), the LINE Messaging API (free tier, extra at volume), and post-launch maintenance ~NT$5,000–15,000/mo (updates, backups, small tweaks). By contrast, SaaS at NT$300/user/month × 100 people = NT$30,000/mo = NT$1.08M over three years — the custom upfront cost is often overtaken by per-seat fees within 1–2 years.

Implementation Truth vs Client Imagination

• Imagined: just move paper into a system. Truth: the slowest part is "spelling out the process first" — many companies have never fully written down their approval rules.
• Imagined: every process must go into the system. Truth: digitising the 2–3 highest-volume, most-stuck forms first beats an all-at-once launch.
• Imagined: launch and done. Truth: the real challenge is getting managers to actually use it — change management and training decide whether it lives.

Common Traps and How to Avoid Them

• Building before the process is settled → run off-the-shelf forms for a month first, confirm rules are stable, then customise.
• Over-complex stage design → use a few conditionals like amount thresholds; don't hard-code every exception.
• No delegate mechanism → one business trip and everything jams; design for delegation and overdue reminders.
• No audit trail → you can't reconstruct who approved; keep a timestamp and record at every step.
• Ignoring mobile → managers mostly sign on phones; nail the mobile view and LINE push.

Success Metrics + 90-Day Roadmap

• Day 30: core forms live; watch whether average approval time drops and adoption rate.
• Day 60: add the 2nd–3rd form types; watch overdue-unsigned rate and rejection rate.
• Day 90: integrate accounting/ERP to cut re-keying; use audit reports for bottleneck analysis.

Decision Checklist

• ☐ Are there ≥50 approvals per month?
• ☐ Two or more sign-off stages?
• ☐ Do you often "lose track of where a form is stuck"?
• ☐ Do you need an audit trail (compliance/internal control)?
• ☐ Do managers mostly handle approvals on their phones?
• ☐ Are the process rules stable (no big change in 3 months)?
• ☐ Do you need to integrate an existing ERP/accounting system?
• ☐ Do three years of SaaS per-seat fees approach one custom build?
• ☐ Is there an owner to drive adoption and change management?
• ☐ Are you willing to start with 2–3 form types?

FAQ

Does an approval system have to be custom? Won't off-the-shelf SaaS do?

With low volume, simple flows and acceptance of per-seat fees, SaaS is the fastest answer. Custom pays off when you need special stages, deep ERP/LINE integration, or headcount high enough that monthly fees exceed the amortised custom cost. Compute the three-year total first.

How long to launch?

A custom system covering 3–4 form types usually reaches pilot in 8–10 weeks. The key isn't coding but spelling out the process and stage rules upfront — do that well and the rest is fast and stable.

Can we do just reimbursement and purchasing, then add more later?

Yes, and we recommend it. Digitise the 2–3 highest-volume, most-stuck forms first, prove it works, then expand — far higher success rate than all-at-once.

What if managers won't use it?

Usually the UI is clunky or mobile wasn't done well. Design around "one-tap approval on mobile + LINE push reminders," and gather manager feedback during the pilot to iterate fast — change management matters more than features.

Call to Action

Want to know whether your approval flow should be SaaS or custom, and the three-year total cost of each? ScriptWalker offers a free 30-minute process check to map your current flow and give an initial quote. Get in touch:

• Email: [email protected]
• Phone: 0916-224-047
• LINE: @ufv9089p