Bank
Internal approval system
Internal forms and sign-off moved into a system.
- Approvals
- Forms
- Banking
Internal systems Custom internal business systems Internal systems
built around your workflow.
Staff records, leave and approvals, work orders, inventory, customer records: packaged software never quite fits, and spreadsheets and chat groups stop scaling. We start by talking to the people who do the work every day, then build the system around their roles, permissions and approval steps, connected to your existing ERP, accounting and accounts. Built by our in-house team with no subcontracting, and the full source code is yours.
Free requirements review · Reply within 1 business day · NDA available
JoinX experience
- projects delivered
- 520+
- clients served
- 220+
- years of development
- 10+
- legacy systems taken over
- 100+
Should we buy packaged software or build a custom internal system?
If your team is small and your process looks like everyone else's, such as simple leave and attendance, a cloud package is the cheapest start. If your process has its own steps and exceptions, several departments need to share the same data, or you need to connect to an ERP, accounting or other existing systems, custom development usually pays off: the system follows your workflow instead of your staff working around the software. Most companies use both, packages for the standard parts and custom software for the workflows unique to them, connected through APIs.
Real projects Internal systems we have built
Approvals, HR, dispatch and reporting: we have built them all.
These are internal systems we actually developed, from a single workflow in one department to several sub-systems behind one sign-in.
2022–2024Insurance brokerage
HR management system
An HR system built around the brokerage's organisation and HR rules, plus a separate tool for importing staff data.
- HR
- Staff records
- Insurance
GUDO Talent
Back-office dispatch plus an organizer app
Jobs used to be assigned by phone and paper, and payments were reconciled by hand. Now scheduling, job acceptance, payment collection and pay calculation all run in one system.
- Dispatch
- Reconciliation
- Pay calculation
Food group
Custom dispatch system
A dispatch system designed around the group's internal workflow.
- Work orders
- Dispatch
- Food
Since 2020Yoga and fitness chain
Multi-branch operations system
Classes, instructor scheduling and multi-branch performance dashboards, continuously improved since 2020.
- Scheduling
- Dashboards
- Multi-branch
Large office tower
Fit-out management system
Tenant fit-out applications and management moved into a system.
- Applications
- Back office
- Real estate
Long-established food brand
Reporting system
We took over maintenance of the existing reports, then added new requirements.
- Reports
- Takeover
- Ongoing
Taipei City Education Bureau
Cooc, Taipei's school cloud and parent–teacher–student platform
One entry point for 9 sub-systems, with different access for the bureau, schools, teachers, students and parents, and vulnerability scans and access control to the bureau's ISMS standard.
- Single sign-in
- Role permissions
- Public sector
* Projects without a client name are described by industry under confidentiality agreements.
What we build Common internal systems
Start with one workflow, then connect the rest.
Most internal systems are a mix of these. The first release covers the step that takes the most time or causes the most mistakes.
Staff and HR records
Staff data, organisation, roles, onboarding and offboarding in one place, with access updated as people change roles.
Leave, approvals and forms
Leave, overtime, purchase requests and other forms signed off online, with different steps by amount or department, on mobile too.
Work orders and dispatch
Repair, maintenance and support tickets from creation to closure, showing who is handling each one and for how long.
Inventory and orders
Purchasing, stock and shipping share one set of data, with an ERP or accounting connection when you need it.
Customer records
Customer data, history, quotes and sales progress in one place, so records stay put when staff change.
Back office and reports
A shared admin back office and management dashboards, with numbers calculated from system data instead of compiled by hand.
Buy or build Packaged or custom
Cloud package, package plus extensions, or fully custom?
Not every part needs custom work. It depends on how standard your process is and whether the data must be shared with other systems.
| Approach | Fits when | Watch out for |
|---|---|---|
| Cloud package (HR, forms or CRM software) | A small team with a common process that wants to start now | Usually priced per user per month; the process cannot change, and data is spread across several services |
| Package plus custom extensions | The package covers the main process; only a few steps, reports or connections are missing | Check first which APIs and data exports the package offers |
| Fully custom internal system | Your process has its own steps and exceptions, and several departments share the same data | Requirements take the longest; launch in phases, starting with the most painful step |
Process How we work
We look at how you work before deciding what the system looks like.
Every phase ends with something you can review and accept, so you are not waiting until the end to see results.
- STEP 01
Interviews and workflow review
2–4 weeks
We talk to the people who do the work: how forms are filled in, who approves, how exceptions are handled, and where the most time and mistakes go.
- STEP 02
Spec and prototype
Depends on scope
A functional spec and role-permission table, plus a clickable prototype your staff try before we agree on the first release.
- STEP 03
Phased build and launch
3–8 months
Delivered module by module, each with a working version; existing data is imported and checked against the source.
- STEP 04
Support and growth
Ongoing after launch
Fixes during the warranty period, then an optional support contract that adapts the system as your process or organisation changes.
Pricing Price ranges
How much does a custom internal system cost?
Estimates for custom projects in Taiwan in 2026. The final price depends on the number of workflows, the complexity of roles and permissions, and the systems to connect.
| Scope | Price range | Typical content | Timeline |
|---|---|---|---|
| Requirements review | NT$100k–300k | Workflow interviews, functional spec and role permissions, producing a spec you can compare | 2–4 weeks |
| Single-workflow system | NT$500k–1M | One workflow for one department, such as leave approvals, work orders or repair requests | 3–5 months |
| Mid-sized internal system | NT$1M–2.5M | Several departments, roles and workflows, with ERP or account integration | 5–8 months |
| Integrated platform | Quoted by scope | Several sub-systems behind one sign-in, with data migration and phased launch | 8–18 months |
Third-party services such as cloud hosting, SMS and e-signatures are billed separately; support after launch is under a separate contract.
FAQ Common questions
Internal system development FAQ
How long does it take to build an internal system?
A single workflow, such as leave approvals or work orders, takes about 3–5 months; a mid-sized system shared by several departments takes about 5–8 months. We recommend launching in phases, starting with the most painful step, so you do not wait for the whole system before using it.
How much does an internal system cost?
Based on custom projects in Taiwan in 2026: a requirements review is about NT$100k–300k, a single-workflow system about NT$500k–1M, a mid-sized multi-department system about NT$1M–2.5M, and an integrated platform of several sub-systems is quoted by scope. Once the spec is clear, the quote lists each item by person-days.
Can it connect to our existing ERP, accounting or attendance system?
Yes. Most systems offer an API, database views or file import and export, but what is available depends on the version and licence. We first check which interfaces your systems offer, then decide how to connect; some interfaces require an extra module from the vendor.
How are staff accounts and permissions managed?
Permissions follow roles, approvals follow your workflow, and important actions are logged. The system can also use your existing company accounts for single sign-on, so when someone changes roles or leaves, you disable them in one place.
Who owns the source code? Can we maintain it ourselves later?
The full source code is handed over to you. We build with our own team and never subcontract, so afterwards you can maintain it yourselves, sign a support contract with us, or hand it to another team.
Can you take over an internal system another vendor built?
Yes. We first review the source code, database and hosting to confirm a complete handover is possible, then decide whether to fix, refresh or rewrite in phases. Parts that still work well can stay.
Get started Start with one workflow
Tell us which workflow gets stuck most often.
You do not need a full spec. Tell us which department will use it, what is currently handled in spreadsheets, on paper or in chat groups, and which systems it needs to connect to.
- 1A sales manager replies within 1 business day
- 2Sign an NDA first, then discuss your workflow and data
- 3We discuss workflow and scope first, and quote once the spec is clear