"Have you built something like this before?" That question is nearly worthless. Everyone says yes, and everyone has a folder of pretty screenshots. What actually filters the pretenders are the seven questions below, asked in this order. One: who owns the model source files when the project ends? The model is the project's foundation. If the source files — the GLB or FBX, the separated parts, the material textures — stay locked with the vendor, you have no negotiating leverage later. Ask directly: does the contract state that source files are delivered? If you switch vendors in two years, can you take the assets with you? Vague answers are a red flag, not a technicality. Two: where does the rule logic live? Rules like "this frame cannot be paired with that door" — are they hardcoded, or built as a configurable rules layer? Hardcoded logic means changing one pairing rule requires a code change, a redeploy and another invoice. A proper rules layer lets your own team adjust combinations without touching code. Three: how is pricing connected — hardcoded numbers or an API? If your prices move with size, material, exchange rate or volume discounts, the configurator must pull from an API or a back-end calculation, never a constant baked into the front end. Hardcoded prices mean a redeploy every time you change a number, which for a cross-border seller watching exchange rates is a small disaster. Four: what does it cost to add a colorway or update a model later? This is the long-term cost everyone forgets. Vendor pricing for model revisions ranges from roughly €200 to €500 per update, or a flat annual maintenance agreement. Ask what a new colorway costs, and what a new component costs. Their answer tells you more about their long-term intentions than any sales deck. Five: who guarantees mobile performance, and against what numbers? Configurators that fly on a desktop and crawl on a phone are extremely common. Ask for specifics: how large is the initial model payload, how fast does it become interactive on a mid-range phone, is lazy loading implemented? A vendor who can't quote numbers usually doesn't test performance. Six: who owns the configuration data and analytics? What customers configured, how long they lingered, where they abandoned — that data is worth more than the conversion rate itself. Ask where it's stored, whether it exports, and whether it connects to your CRM or GA. Seven: can you open a live example right now, on my phone? The harshest and fairest question. A vendor who has actually shipped this opens a link in seconds — we do exactly that with our own furniture 3D configurator when clients visit. A vendor who only makes slides will explain that the case "is with a client and can't be shared."
Three red flags on the quote sheet
A suspiciously low upfront price paired with a per-change maintenance table that recovers the difference and then some. A subscription model that takes a percentage of sales — the better your configurator performs, the more you pay, and after three years you still can't walk away with your data. And acceptance criteria written as "mutual confirmation of satisfaction," which is worth nothing in a dispute. Any one of these three, and it's worth pausing before signing.
How I score vendors
Technical capability — modeling pipeline, rules engine, cross-platform delivery — carries 30 points. Verifiable case studies, ideally demoed live, carry 25. Quote transparency, meaning itemized pricing with long-term costs stated, carries 20. Communication and change-request handling carries 15. Source file and data ownership terms carry 10. Below 70, walk away. Above 85, talk about a long-term partnership. We run this same checklist on ourselves at XuanJi Animation, and clients are welcome to score us against it — it makes both sides faster. At the end of the day, vendor selection rewards whoever asks more specific questions. The more precise your questions, the less room there is for hand-waving, and the better the contract holds up a year later. For the money side, our 3D configurator cost breakdown covers pricing tiers and payback math, and the full delivery process lives on our 3D configurator development service page.
FAQ
How do I judge whether a quote is reasonable?
Compare line items, not totals. Modeling, interaction logic, system integration and post-launch maintenance should be listed separately. A quote with only a total price leaves room for later additions.
What must the contract state?
Source file and asset ownership, acceptance criteria specific enough to test, unit pricing for future changes, and the right to export your data. Those four matter more than the headline number, because the price is negotiated once while these shape the next several years.
Is this level of detail necessary for a small project?
Especially for a small project. The smaller the budget, the less it can absorb rework. Writing down what gets delivered and how acceptance is measured is the cheapest protection available.