How much does custom software cost?

Price follows modules, data migration, APIs, permission complexity and whether a mobile client is in v1 — not a round number with no work breakdown.

Where the money actually goes

Coding is one slice. Discovery, master-data cleanup, interface tests, exception documents, permissions and training all enter the estimate. Buying source and buying only a seat are different commercial shapes. We do not publish a fake "market average starting at…".

Five things that move the number

  • History must migrate: dirty fields and colliding codes often take longer than new screens.
  • Each extra ERP, finance or messaging API adds a test and retry loop.
  • Row-level or multi-org isolation.
  • Admin and a phone client both required in v1.
  • Private network, specified database or a compliance window.

A small tool and an operations platform are not one price

Internal expense claims and a multi-org ledger with three external APIs can differ by an order of magnitude and still both be called "a management system". Warehouse execution should be estimated as WMS, not folded into a generic admin quote.

Control cost by cutting v1, not tests

Ship the main flow and permissions first. Reports and mobile can be a second release. An opaque low number before scope is frozen is not control — it is deferred argument.

Frequently asked questions

Why do some firms quote one integer immediately?

Usually a packaged bundle, or a scope written narrowly on purpose. Work built from your documents has to be split into packages first.

How do we keep the budget honest?

Freeze v1. List interfaces. Say what is out. We estimate work packages, not a single sticker.

Is source included?

In our custom work, source and runbooks are part of handover unless the contract says otherwise. Ask that out loud.

We will not drop an integer while scope is fog. Send modules and must-have interfaces to /en/contact/.

See the service Contact