// Pricing

3D Web Design Pricing — How the Quote Is Built

Every project gets a written fixed quote after a short brief — scope, complexity, and timeline set the price, not a rate card.

3D web design pricing varies more than most services because scope varies so much — a hero-section upgrade and a full configurator with custom-modeled assets are different projects, not different tiers of one package. That's why I don't publish a rate card: it would be wrong for most of the inquiries I get. Every project starts with a short written brief, and the answers set the scope: how complex the scene is, whether assets are custom-modeled or sourced from libraries, how many interactions and integrations the build needs, how much content it has to hold, and the deadline. That brief turns into a written offer — a scope list, the deliverables, and a timeline — agreed before any work starts. Per-project quoting beats a fixed rate card for 3D work because two "hero scene" requests can differ by weeks of build time depending on asset complexity alone; a rate card either overcharges the simple one or underquotes the complex one. The written offer is what avoids both.

The brief comes first

Every quote starts with a short written brief, exchanged over e-mail: what the site needs to do, who it's for, what exists already, and when it needs to ship. No call required — the brief goes back and forth in writing until the scope is clear on both sides.

What drives the number

Five factors set the price on every project: how complex the 3D scene is (a single rotating object versus a multi-chapter scrollytelling sequence), whether the assets are custom-modeled or sourced from libraries, how many interactions and integrations the build needs (configurators, forms, CMS, analytics), how much content the site has to hold, and the deadline. Two projects that both sound like "a 3D hero" can differ by weeks of work once these factors are accounted for.

What the written offer contains

Once the brief is clear, I send a written offer: a scope list describing exactly what's built, the deliverables (source files, assets, documentation), and a timeline with milestones. Nothing starts until that offer is agreed in writing — no verbal estimates, no moving target.

Why not a rate card

A published rate card either overcharges simple projects to cover the complex ones, or underquotes complex projects because the simple ones set expectations. Per-project quoting means the price reflects what your project actually needs. It takes one extra step up front — the brief — in exchange for a number that's accurate rather than approximate.

Frequently asked questions

How do I get a quote?
Send a short brief by e-mail — what you're building, what exists already, and your timeline. I reply in writing with clarifying questions if needed, then send a written offer with scope, deliverables, and timeline.
Do you work from a price list?
No. Scope varies too much between projects for a price list to be accurate. Every quote is written after the brief, based on what your specific project needs.
What makes one project cost more than another?
Scene complexity, whether 3D assets are custom-built or sourced, the number of interactions and integrations, how much content the site holds, and the deadline. A simple hero upgrade and a full configurator are different projects, not tiers of the same one.
Are payment terms negotiable?
Terms are set out in the written offer before any work starts, so there's no ambiguity on either side once the project is underway.
Can I get a rough range before sending a full brief?
A short description is usually enough for a ballpark — send what you have and I'll tell you honestly whether it needs a full brief or if I can size it quickly.

Ready to ship a 3D experience?

Tell me what you need — clear written scope, no surprises.

Pozovi