Milestones, not lump sums
Builds bill 40 / 30 / 30 against deliverables you can inspect. Audits are a single fixed fee. Squads bill monthly in advance. Nothing is invoiced for work outside the scope document.
You should not need a sales call to learn roughly what something costs. These are real starting figures for real deliverables. Your scope document confirms the final number before work begins — and before you owe anything.
An independent read on a codebase, architecture, or vendor proposal.
5 business days · fixed fee · fully credited against a later build
A scoped system delivered end to end, with the reliability work included rather than deferred.
Typically 6 – 16 weeks · 40 / 30 / 30 milestone billing
Senior engineers inside your team, on your board, in your standups.
Minimum 3 months · 30 days' notice to cancel
USD, excluding third-party licences, cloud usage and applicable taxes. See Terms and Refunds.
| item | price | covers |
|---|---|---|
| Additional engineering | $135 / hour | Work outside an agreed scope, billed in half-day blocks. |
| Ongoing maintenance | From $1,200 / month | Patching, dependency upgrades, uptime monitoring, 8h of changes. |
| Incident retainer | $2,400 / month | Guaranteed response window with an agreed SLA and on-call rotation. |
| Compressed timeline | +35% | Parallel workstreams and a larger squad. Subject to availability. |
| Cloud & third-party costs | At cost | Passed through with no mark-up, estimated in your scope document. |
Builds bill 40 / 30 / 30 against deliverables you can inspect. Audits are a single fixed fee. Squads bill monthly in advance. Nothing is invoiced for work outside the scope document.
Invoices due 14 days from issue by bank transfer or card. If a line is genuinely in dispute, tell us — the clock stops on that portion while we resolve it.
Start with an audit and the full $3,500 comes off your build price if you proceed. You keep the report regardless. See the Refund Policy.
Because we never quote before the mapping phase. Reading the system first is what converts unknowns into line items. The scope document lists every service and migration we are building, and equally what we are not.
When something genuinely unforeseeable appears — an undocumented dependency, a vendor API that behaves differently than its docs — we price it as a change order and you decide. We do not absorb it silently and we do not surprise you with it later.
You do, in full, on final payment. That includes source, infrastructure definitions, and documentation, and it is written into our Terms of Service rather than promised verbally.
We retain only our own pre-existing internal tooling, and you get a perpetual royalty-free licence to keep using it inside your product.
Yes, and we prefer to. The best stack is usually the one your team can already maintain. We will flag a technology choice that we think is a genuine liability, with reasoning, but it stays your call.
The exception is where a choice makes the agreed reliability targets unreachable. In that case we say so in the scope document before you sign it, not after.
Then it says that. Roughly one audit in six concludes that an off-the-shelf product, a configuration change, or simply doing nothing beats a custom build.
You keep the report either way, and the audit fee is credited against a build only if you decide to proceed. We would rather lose the project than take budget for work that should not happen.
It is a calibrated range built from our actual delivery data, not a lead-capture toy. For a well-defined project the final scoped price usually lands inside it.
It is still an estimate produced without seeing your system. The mapping phase is what turns it into a fixed number, and that number can move in either direction.
With an incident retainer, yes — an agreed response window, a rotation, and escalation paths documented before anything goes wrong.
Without one we are not in your on-call path, but every build ships with runbooks so your team is not debugging blind.
NEXVRA works remotely with clients across Europe, North America, and the Middle East, on Monday – Friday, 09:00 – 18:00 UTC+1.
We hold at least four hours of overlap with your working day, run written asynchronous updates, and keep decisions in a shared channel so nothing depends on catching someone live.
Yes. We will sign yours before the mapping phase, or provide ours. For engagements touching personal or regulated data we agree a processing addendum covering storage, access, sub-processors, and deletion.
Access is least-privilege by default and revoked at handover.

Send the shape of the project and we come back with a written scope and a firm price, usually within two business days, at no cost and no obligation.