Skip to content

How we work

Everything on this page is how engagements actually run: prices, process, ownership, and what happens if things go wrong. Nothing here changes on the call.

Start small, own everything, grow on evidence

  1. Fixed-price pilot

    One equipment package from your CAD, one working procedure or demo flow, running standalone on Quest 3. Delivered in 2-5 weeks at a fixed price from $6,000. You end the pilot holding a build your team can try and a written proposal for the full program. Start the program within 6 months and 50% of the pilot is credited, because its groundwork transfers directly.

  2. Full program

    The complete simulator: scenarios, assessment, reporting, deployment. Typically $20,000-$45,000 over 6-14 weeks, built in weekly increments you watch grow.

  3. Care plan

    After handover, optional care covers compatibility watch, priority fixes, and content updates as your equipment evolves. Connected systems require ongoing integration maintenance; standalone apps typically need lighter compatibility support. If your system needs neither, we'll say so.

What happens after you get in touch

  1. Scoping call

    30 min

    You bring the training problem. You get straight answers about feasibility, live on the call.

    Feasibility answered, on the spot

  2. Written feasibility + ballpark

    2 business days

    You get a short written document you can forward internally: what's buildable, what it roughly costs, what we'd pilot first.

    Written feasibility and a ballpark

  3. Fixed-price pilot

    2-5 weeks

    You bring CAD for one equipment package, reference documents, and one subject-matter contact. You get a working standalone build on your own headset, performance-validated, plus written findings and a scoped program proposal.

    A working build on your own headset + findings

  4. Design & greybox

    1-2 weeks

    You bring SOPs and procedure documents. You get a playable greybox of every scenario, with layout, flow, and interactions proven before visual polish.

    A playable greybox of every scenario

  5. Production build

    4-10 weeks

    You bring one SME review round per module. You get a new build every week, and project source handed over at every milestone.

    Weekly builds + source at every milestone

  6. Deployment & acceptance

    ~1 week

    You get the build installed on your fleet, exports flowing to your LMS if scoped, and optional train-the-trainer sessions so the program runs without us in the room.

    Fleet installation + LMS exports if scoped

  7. Handover & care

    You get final builds, project source, and documentation, owned outright. Then a care plan if, and only if, your system warrants one.

    Builds, source, and documentation, owned outright

Open numbers, and what moves them

Pilot

from $6,000

2-5 weeks
  • one equipment package converted from your CAD
  • one working procedure or demo flow
  • standalone Quest 3 build, performance-validated
  • written findings + full program proposal

Excludes (that's program scope):

  • multiple scenarios
  • LMS integration
  • custom platforms

50% credited toward a program started within 6 months.

Get a fixed-price pilot quote

Program

$20,000-$45,000

6-14 weeks
  • complete training scenarios with hands-on interaction
  • assessment with scored steps, pass/fail, and per-session results
  • exportable reporting, SCORM/xAPI where scoped
  • deployment support and documentation
  • project source at milestones

What moves the number: scenario count · equipment complexity · assessment depth · multiplayer or AI characters · LMS and data integration · new environments

What lowers it: CAD you already have, available subject-matter experts, existing SOPs, and reusing environments across modules. Follow-on modules are typically lower-cost because the foundation, pipeline, and reusable systems are already built.

Owned, not rented

Yours

  • Every scene and environment
  • All training content and scenarios
  • Every build, for every device
  • Project source code, handed over at milestones rather than at the end

Simvra's, licensed to you forever

  • The reusable framework: interaction system, assessment engine, device abstraction, tooling
  • Licensed to you perpetually and non-exclusively, embedded in your project
  • You can maintain and extend your simulator with anyone, anytime

Platform products rent you your own training content. A Simvra build is yours the way your equipment is yours. And because the framework matures with every project, your next module costs less than your first.

Asked plainly, answered plainly

  • You always hold current source and documentation.

    Handover happens at every milestone, not at the end. At any moment, you possess everything needed to continue.

  • Documentation is a deliverable.

    Every project ships with build instructions and architecture notes a competent Unreal team could pick up cold.

  • Concurrent work is capped.

    Simvra runs at most 2 builds at a time. Your timeline is a commitment we can actually keep.

  • If Simvra were unavailable tomorrow,

    you'd hold your source, your builds, your documentation, and a perpetual framework license. Any competent Unreal Engine team could continue the work. That is the design.

What we need, how we communicate

What you provide:

  • CAD models (CATIA, SolidWorks, STEP, via Datasmith)
  • Subject-matter expert access: roughly 4-8 hours per module
  • SOPs, procedure documents, safety standards
  • Headsets for deployment, or we'll spec the purchase with you
  • Device management (ArborXR, ManageXR) licensed by you, if your fleet warrants it; see the FAQ

How we work with you:

  • Weekly progress builds, video or installable APK, every week, no exceptions
  • Written updates; decisions documented, not remembered
  • 4+ hours of daily overlap with European business hours; full overlap with the Gulf
  • NDA available before any material exchange
  • Working language: English

Stack & standards

EngineUnreal Engine 5
CAD pipelineDatasmith: CATIA / SolidWorks / STEP
DevicesQuest 3 standalone · PC VR · desktop
Training standardsSCORM · xAPI
Fleet deploymentArborXR / ManageXR ready (client-licensed)
Browser demosUnreal Pixel Streaming
Connectivityfully offline standalone builds · networked where scoped

money

A fixed-price pilot from $6,000 (2-5 weeks). A typical full program $20,000-$45,000 (6-14 weeks). Larger multi-scenario, multiplayer, or AI-driven systems are scoped individually. The factor lists above are the honest levers; nothing else secretly moves the price.

Cost structure, not corner-cutting. Simvra's engineering is based in Indonesia, and there is no account-management layer to fund. You work directly with the engineer who builds your simulator. For calibration: a leading North American studio's published pricing guide lists $100,000-$200,000 per interactive training module, and $20,000-$45,000 for the discovery phase alone. A complete Simvra pilot, a working build in your hands, costs less than that discovery phase. Same engine, same headsets, same standards.

Milestone-based, tied to deliverables you've already seen. You never pay for work that doesn't exist yet. An initiation and a delivery payment per module is typical, and cadence can align with your internal approval process.

ArborXR, ManageXR and similar run roughly $5-15 per device per month, licensed by you directly with the vendor, the same way you license your LMS. Simvra delivers management-ready builds and assists setup during deployment. Below about 5 headsets you may not need device management at all; manual installation works fine.

risk

You already hold everything. Source and documentation are handed over at every milestone, and the framework license is perpetual. Any competent Unreal Engine team could continue. The continuity section above is the full answer; it's designed in rather than promised.

You own the project: scenes, content, builds, and project source, delivered at milestones. Simvra retains its reusable framework, licensed to you perpetually and non-exclusively. Owned, not rented. You are never locked in.

NDA before any material exchange, offered before you ask. CAD stays within the project, is used solely to build your simulator, and every deliverable built from it is yours. Deletion on request.

Two mechanisms. First, assessment: scored sessions produce data, and unused training is visible in the numbers, to you. Second, deployment includes optional train-the-trainer sessions, so your own staff run the program confidently without a vendor in the room. A simulator that isn't used is a failure we both can see, and the process is built to prevent it.

tech

Standalone builds run fully offline. Connected features, such as live dashboards, multiplayer, data feeds, and LMS sync, need a network, and we scope for whatever your site allows, including offline-first designs that sync later.

Content updates are normal life. Environments and equipment are modular packages, so a revised component is updated without rebuilding the simulator. Actively evolving systems can put content updates on a care plan; stable ones update per change.

Get a number you can take to your boss

A 30-minute call, then written feasibility and a ballpark within two business days. Forwardable, specific, and free.

Get a fixed-price pilot quoteBook a 30-minute scoping call
Download the capabilities one-pager

replies within 1 business day · written feasibility and ballpark within 2 business days of a call · NDA before any material exchange