How Much Does a Custom Back-office System Cost in Thailand?

The honest answer to “How much does a custom back-office system cost in Thailand?” is that the price depends less on the number of screens than on the operating decisions behind them. A simple employee directory and a multi-step purchasing workflow may look similar in a proposal, but they carry very different requirements for permissions, exceptions, evidence, and testing.

For planning purposes, a focused startup back-office build commonly begins around ฿45,000. Growing-team projects with several modules, approvals, reports, and migration often begin around ฿70,000. Broader multi-department systems may begin around ฿130,000 and increase with integrations or complex controls.

These are useful planning ranges, not substitute quotations. Here is how to understand what moves the number.

The five components of system cost

The first component is the operating foundation. This includes the data model, user access, navigation, basic configuration, testing, and deployment. It is the part every working system needs even when the first phase contains only one module.

The second component is module scope. HR records, vendor contracts, approval workflows, dashboards, and access control each introduce different records and responsibilities. Two modules that share data may be cheaper than two unrelated modules because the foundation can be reused.

The third component is feature complexity. A searchable employee database is more predictable than a configurable approval builder. Complexity rises when a feature needs conditional rules, several approvers, parallel steps, escalation, or an immutable audit trail.

The fourth component is migration and integration. Cleaning 200 current employee records is different from importing five years of mixed spreadsheets. Connecting Slack, LINE, Google Workspace, accounting, payroll, or identity services adds discovery, authentication, failure handling, and testing.

The fifth component is ongoing service. Hosting, backups, small changes, monitoring, and support are often priced monthly. Clarify which costs belong to the service provider and which third-party licences are billed separately.

Example budgets for startup teams

A 15-person startup replacing an employee spreadsheet and basic leave tracking might choose a Starter foundation with HR records, onboarding, leave, and simple access roles. Its initial budget may sit near the lower end of the range if the data is clean and the workflow is standard.

A 35-person company managing employees and vendors may need a Growth foundation, contract reminders, invoice status, manager approvals, and a pending-work dashboard. The price increases because several teams share records and decisions.

A 75-person business with departments, advanced access, multi-step approvals, scheduled reporting, and integrations may need a Scale foundation. The implementation needs more test cases, role definitions, and launch support.

Use the interactive system builder to turn your exact module and feature choices into a planning range rather than relying on a generic average.

Why two similar proposals can differ

One provider may assume that your team will clean and prepare data; another may include migration work. One may quote a fixed workflow, while another includes configurable rules. Support, documentation, training, warranty periods, and hosting may also be treated differently.

Compare proposals using explicit questions:

• Which records and workflows are included?
• How many roles and approval variations are assumed?
• Who cleans and validates migration data?
• Which integrations and third-party fees are excluded?
• What happens when a requirement changes?
• What support is included after launch?
• Can the business export its data?

A lower price can be correct for a narrower first phase. It becomes risky only when important assumptions are invisible.

How to reduce cost without reducing value

Start with one operational bottleneck and the records it depends on. If vendor renewals are causing late fees, begin with the vendor database, contract owner, renewal date, reminders, and status view. You do not need a complete procurement suite to solve that problem.

Use standard rules where possible. A single approval threshold is easier to launch than a different chain for every department. Exceptions can be documented and added after the team sees real usage.

Prepare clean data. Remove duplicate vendors, confirm active employees, standardise department names, and decide which documents should migrate. Good preparation reduces both implementation effort and post-launch confusion.

Choose a clear decision owner. Slow feedback and unresolved internal debates create more cost than many technical features. One empowered owner should confirm scope, data, and acceptance criteria.

Onboarding versus the monthly subscription

The onboarding phase covers discovery, configuration, migration, testing, and launch. Backoffice Builder waives the onboarding charge on annual plans; monthly plans show it separately before checkout. The subscription then covers the continuing service: hosting, maintenance, support, monitoring, and the plan's included improvements.

Ask whether the monthly agreement is flexible and how cancellation works. Also ask what happens to data and documentation at handover. A low onboarding quote paired with unclear long-term terms can become expensive.

Conversely, a monthly service can be valuable when the startup expects its processes to change. Instead of treating the launch as a finished software project, the team can refine workflows as it learns.

Build a credible budget before the sales call

Before requesting a formal proposal, list the current tools, number of employees and vendors, the work areas involved, three workflows that create the most friction, and any essential integrations. Decide what success should look like 60 days after launch.

That information is enough to create a realistic first-phase range. It also helps providers separate required work from optional ideas.

You can compare the current Starter, Growth, Scale, and Custom plans, then configure an exact planning range. The final quotation should follow a discovery conversation that confirms migration, exceptions, integrations, and ownership.