Spatial computing rates in 2026: Vision Pro and beyond

Spatial computing is a small market with high specialist rates. Vision Pro shipments are low, yet published figures put senior spatial developers well above ordinary mobile developers. The premium comes from scarce skills and enterprise pilots, not from volume, so price for expertise and protect yourself against projects that stall.

The headset market is small

Apple Vision Pro has not become a mass-market product. According to a Slashdot summary of an IDC estimate, Apple was expected to ship about 45,000 units in the fourth quarter of 2025, after around 390,000 in the 2024 launch year. The headset costs $3,499, and Apple sold it directly in 13 countries without expanding availability in 2025. Apple released an upgraded M5 version in October.

Those numbers describe consumers. Enterprise is a different story. A TechRadar headline reports Tim Cook saying half of Fortune 100 companies have bought an Apple Vision Pro. A purchase is not a rollout, and I could not confirm the details from the article text, so read it as evidence of interest, not of scale.

The practical picture is a small number of buyers with large budgets and pilots to run, and few people who can build for the platform.

What the published rates say

There is no official rate card for spatial work, so the best you can do is compare sources and note who wrote them.

A May 2026 hiring guide from the staffing firm KORE1 lists US contractor rates for AR and VR developers of $110 to $185 an hour at mid-level and $185 to $280 at senior level. KORE1 earns placement fees on these hires, so its numbers lean toward what employers will pay. The same guide gives spatial UX and visionOS employee pay of $225K to $300K for seniors, and reports an ex-Apple premium of 15 to 30 percent.

A studio, Frame Sixty, gives a lower figure in its visionOS cost guide: senior visionOS developers at US and European agencies at $100 to $200 an hour, as of 2025, and offshore teams at $40 to $80.

For comparison, Arc.dev reports that freelance mobile app developers charge $61 to $80 an hour on average. So the published spatial figures are roughly two to four times the mobile average, depending on the source and the seniority level. Treat that as a range, not a rate card, and expect big differences by country.

Why the premium exists

The premium has three causes, and none of them is volume.

Skills are scarce. Native work means Swift, SwiftUI, RealityKit and a feel for depth, gaze and hand input. Few people have shipped on those tools, and companies with an urgent pilot cannot wait to train someone.

Budgets are large relative to the audience. Frame Sixty's table puts a focused visionOS app or port from $15,000, a full-featured spatial app at $25,000 to $80,000, and an immersive or enterprise build at $80,000 and up. Custom 3D assets add $10,000 to $30,000. These are one studio's estimates and a sales document, so use them as a guide to the order of magnitude.

The buyers are not price shoppers. A manufacturer building a training simulation compares you with the cost of an in-house hire and a delayed project, not with a marketplace listing.

Where the premium does not apply: cross-platform AR work that avoids platform-specific tools tends to sit closer to general mobile rates, because the pool of people who can do it is larger.

Where the risk sits

A small installed base is a risk for you, not only a fact about the market.

Pilots can stall. A company that bought headsets may decide not to roll out, and your project can stop with a milestone unpaid. Procurement cycles at large companies also slip, so a project promised for next month can start in the quarter after.

Skills tied to one platform age with the platform. If the hardware does not take off, demand for the skill can fall faster than for general mobile work.

Plan for it:

• Do not rely on one pilot. Run two or three discovery conversations at once.
• Pair spatial skills with something broader, such as SwiftUI and visionOS, or 3D asset pipelines and Unity, so one slow platform does not stop your pipeline.
• Keep a public demo you own. Client work is often under NDA, and a demo is the only portfolio you can show.
• Get a deposit and scheduled payments in writing before you build.

Our pricing guide covers how to set the base rate behind a quote like this.

Which skills command the most

The published guides agree on one point: the premium follows the hardest-to-find skill, not the job title.

Native engineering sits at the top. The KORE1 guide lists spatial UX and visionOS pay above gameplay work in Unity or Unreal at every level, and above lightweight web-based AR by a wide margin. That matches how the projects work. A native build has to respect the platform's input model, its performance limits and its review rules.

Next comes 3D asset and motion work that fits the engineer's pipeline. If you can hand over assets that load correctly the first time, you save the client a week of rework, and that is worth paying for.

Then come designers who understand depth, scale, occlusion and comfort. A layout that looks fine on a flat screen can cause eye strain in a headset. Designers who have tested on a device and can explain why a panel sits where it does are rare.

Last is the generalist who can run the whole pilot: scope it, build a prototype, present it to stakeholders and write the follow-up proposal. These people are often paid for judgment more than code, and their rate depends on how they package the work.

If you are moving into this field, build one small, real prototype on a device you own before pitching. A working demo says more than any list of tools.

How to price a spatial project

Quote the outcome, not the hours. A fixed fee in stages protects both sides, because you can be paid for what you deliver even if the pilot stops.

A common structure is a paid discovery phase, a prototype, then a build. The discovery phase has its own price and its own deliverable, a scoped plan the client keeps. That filters out companies who only want free advice.

Spell out what is in each stage in a statement of work. Our guide to the statement of work shows the sections, and the post on milestone payments shows how to split the fee so cash arrives as work is delivered.

Add the things that bite later: who owns the source and the 3D assets, how many revision rounds are included, which devices and OS versions you test on, and what happens if the client's hardware changes. Contract wording should be checked by a lawyer.

How Delivvo runs a staged spatial project

Delivvo does not build or host spatial apps. It handles the engagement around them: the quote, the contract, the staged payments and the delivery of big files.

Here is the flow:

1. An enterprise contact fills in your inquiry form, which asks about the platform, the goal and the timeline. The lead lands on your lead board.
2. You send a quote built from packages and add-ons. Discovery, prototype and build can each be a package, with extra 3D assets or testing as add-ons.
3. The contract is created with the quote. It uses a typed or drawn signature, and the signing record stores a SHA-256 hash, the IP address, the device and an archived PDF.
4. A payment schedule splits the fee into up to 12 payments, so each stage has its own invoice and due date. Invoice numbers run in order in your format.
5. You deliver builds and assets through the client portal. Files upload up to 50 GB each on Pro and above and are resumable, which suits large 3D scenes and recorded demos.
6. The client approves a version, and the approval is recorded with a name and a time, so a stalled project has a record of what was accepted.

Two details matter for enterprise buyers. And every invoice and contract carries a verification code that a finance team can check.

The client pays through your own gateway and Delivvo takes 0%. See the payment schedules page for how staged billing works.

This sits inside Delivvo's CRM for service businesses. More on contracts and e-signatures.

FAQ