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.
One job, done properly — receiving, approvals, or a field checklist.
from $10,000
Fixed price, agreed before we start
About 4 weeks
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
Several sites, a device fleet, and an ERP that is not vanilla.
from $20,000
Fixed price, scoped with you
Timeline agreed with you
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.
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.
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.
Every workflow priced on its own line, plus the integration foundation and handover. You can strike a line out and the total changes.
The number does not move. If you add scope later it is quoted separately and you decide, before any work starts.
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.
Agreed in writing before work starts. No hourly meter, and no discovery invoice before you have a number.
Half on acceptance, half on go-live and source handover — tied only to what we deliver.
Development and UAT run against your sandbox. Production go-live happens only after your sign-off.
Full source, build pipeline and store accounts handed over. Continue with us on support, or take it in-house.
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.
Stated up front, because the fastest way to waste your time is a proposal that hides its edges.
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.
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.
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.
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.
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.
Describe what your team does today and which ERP they do it in. An engineer replies — not a sales script.