Skip to main content

What a mobile app actually costs

A fixed price, itemised workflow by workflow, agreed before anyone writes code. No discovery invoice, no hourly meter, and no number that moves after you have signed it.

How much does a mobile app cost?

ECOSIRE's mobile app builds come in three bands: Single workflow (from $10,000), Operations app (from $15,000) and Multi-site programme (from $20,000). Every build is a fixed price agreed before work starts.

What a mobile app actually costs

Single workflow

One job, done properly — receiving, approvals, or a field checklist.

from $10,000

Fixed price, agreed before we start

About 4 weeks

  • One platform — iOS or Android, whichever your team carries
  • ERP integration foundation: authentication, sandbox wiring, and a formal API validation of every workflow in week one
  • Up to six workflow functions, itemised individually
  • Private or MDM distribution to your own devices
  • Weekly working builds — you use it from week one, not at the end
  • 30 days of support after go-live, included
Scope your build
Most common

Operations app

The whole operation on a device, including where there is no signal.

from $15,000

Fixed price, agreed before we start

About 6–8 weeks

  • Both platforms — iOS and Android from one codebase
  • Everything in Single workflow
  • Up to twelve workflow functions, itemised individually
  • Offline-first: local storage, visible sync queue, and conflict rules agreed per record type
  • Hardware scanner support for rugged devices, or camera scanning on phones
  • App Store and Google Play submission handled, or Managed Google Play / Apple Business Manager
  • 30 days of support after go-live, included
Scope your build

Multi-site programme

Several sites, a device fleet, and an ERP that is not vanilla.

from $20,000

Fixed price, scoped with you

Timeline agreed with you

  • Everything in Operations app
  • Multiple sites, warehouses or entities in one app
  • Single sign-on against your existing identity provider
  • Fleet deployment through Intune, Jamf or your own MDM
  • Custom or heavily configured ERP objects, not just standard records
  • Rollout sequenced site by site, with a pilot crew first
  • Extended support window agreed up front
Scope your build

Every figure is a starting point for a fixed quote, not an estimate that drifts. We put the number in writing after a technical session — never on the first call, because we would be guessing.

How the number is built

We itemise the price by workflow, so you can see exactly what each function costs, add one, or drop one, and watch the total move. Individual workflow modules typically fall between $400 and $1,500 depending on complexity; the integration foundation is quoted separately because it is shared by all of them.

  1. 1

    Technical session

    A working call with the people who will use the app and, where it helps, your ERP consultant. No price is quoted before this — we would be guessing.

  2. 2

    Itemised proposal

    Every workflow priced on its own line, plus the integration foundation and handover. You can strike a line out and the total changes.

  3. 3

    Fixed on signature

    The number does not move. If you add scope later it is quoted separately and you decide, before any work starts.

  4. 4

    50/50 on delivery

    Half on acceptance, half on production go-live and source-code handover. Payments are tied only to our deliverables, never to a third party's timeline.

The same on every engagement

Fixed price

Agreed in writing before work starts. No hourly meter, and no discovery invoice before you have a number.

50/50 milestones

Half on acceptance, half on go-live and source handover — tied only to what we deliver.

Sandbox first

Development and UAT run against your sandbox. Production go-live happens only after your sign-off.

The code is yours

Full source, build pipeline and store accounts handed over. Continue with us on support, or take it in-house.

After go-live

Thirty days of support are included with every build. After that, support is optional and flat — OS-release compatibility passes, certificate renewals, crash monitoring, dependency and store-policy updates, and regression testing when your ERP is upgraded. Entirely optional: the app is yours either way.

$200 / month

Optional, after the included 30 days. Cancel whenever you like.

What the price does not include

Stated up front, because the fastest way to waste your time is a proposal that hides its edges.

  • ERP licensing, configuration or consulting inside the ERP itself — that is your ERP consultant's domain, and we coordinate with them.
  • Hardware. Scanners, printers, tablets and labels are yours to buy; we tell you exactly what works.
  • Historical data cleanup or migration inside your ERP.
  • Third-party subscriptions the app may use — cloud storage, SMS gateways, mapping — billed to your own accounts, not resold through us.
  • Anything discovered after signature is quoted separately and starts only when you approve it.

Questions about the price

Why won't you give me a price on the first call?

Because it would be a guess, and a guess either loses you money or loses us the project halfway through. We run a technical session first — usually an hour with the people who will actually use the app — and the written number follows within a day or two. That number is then fixed.

What makes one app $10,000 and another $20,000?

Three things, in order of impact: how many workflow functions you need, whether it must work offline, and whether it runs on one platform or both. A single-platform receiving app with six functions sits near the bottom; a multi-site offline app on iOS and Android with SSO and fleet deployment sits at the top.

Can I start smaller and add later?

Yes, and most clients should. Because the price is itemised per workflow, phase one can be the two functions that hurt most, with the rest quoted and added once the first is proven in daily use. Nothing about the architecture forces a big-bang launch.

Do we own the app at the end?

Yes. Full source code, the build pipeline and the store accounts are handed over on completion, and the developer accounts should be in your organisation's name from the start. An app published under a vendor's account is a risk to you, and we will not recommend it.

What happens if our ERP is upgraded?

Tell us the window and the integration is regression-tested against the new version. On a support agreement that is included; without one it is quoted as a small piece of work. This is the case where an ERP-side partner is worth more than a general app agency.

Tell us the workflow, and we will price it

Describe what your team does today and which ERP they do it in. An engineer replies — not a sales script.