Who Owns Your 3D Configurator? Domain, Customer Data and Prices

In short: Before commissioning a 3D configurator, put in writing whose name the domain and hosting are under, who owns the customer data and the price table, and what happens to all of it if the relationship with the developer ends.

Who owns your 3D configurator is a question almost nobody asks at the start, and it's worth asking before any work begins. It's not about distrust. It's about keeping things clean. A 3D configurator brings together three things that matter a lot to your company —your domain, your customer data and your pricing— and you should know from day one whose name each one is under and what happens if you ever switch providers.

Why it matters more for a configurator than for a regular website

A company website shows who you are. A configurator does something more sensitive: it takes in inquiries with a customer's name, phone number and location, stores what each person built, and often holds the logic you use to price your jobs. That last part is close to a trade secret for a steel building company: what a frame costs, what a foot of sheeting costs, what a roll-up door adds.

So "the developer puts it online and that's it" isn't enough. You want to know where each piece lives.

Five things to settle up front

1. The domain. The healthiest setup is for the configurator to live on your domain, for example a subdomain like `design.yourcompany.com`. That way every link shared by text, on a business card or in an ad belongs to you. The EQUIBOX quoting tool, for example, runs on a subdomain of the manufacturer's own domain.
2. Hosting. Where the system runs and whose name the account is under. There are several ways to handle it and no single right answer, but it should be written down.
3. Customer data. Inquiries, contacts and quotes belong to the manufacturer. Agree up front that you can export them in a common format, like a spreadsheet, whenever you ask.
4. The price table. Your team loads and changes the numbers. Nobody outside should need to touch them, and nobody outside should use them for anything else.
5. What happens if the relationship ends. What gets handed over, in what format, and how the transition works. It's the most awkward conversation and the most useful one.

If any of this touches legal or data privacy questions, check with a professional where you operate. I'm talking about business housekeeping here, not legal advice.

Your customer data is yours

A public configurator brings in inquiries that used to never arrive, or that arrived as "price?". Now they come with dimensions, options and an image. Over time, that list tells you a lot: which areas inquire most, which products people want, which rep closes what.

That information belongs to you. If there's a CRM for your reps, like the one I built for EQUIBOX with lead stages, follow-up dates and collections, what goes in there is part of your business. I cover how that follow-up is organized in CRM for manufacturers.

Prices: protected, and in your hands

Two separate decisions often get mixed up: whether prices are shown to the public, and who manages them.

• Showing them or not is a sales decision. Many manufacturers prefer the public to see the 3D model without a price, with prices only visible to logged-in reps. I explain that in keeping prices private in a configurator.
• Managing them should always be your job, from a price table you control. If every price change goes through the developer, you lose control of the thing that changes most.

What's yours and what's the developer's

It's worth being straight about this, because that's where misunderstandings start. In a custom configurator, some things are clearly yours: your brand, your domain, your data, your prices, your photos, your building rules. And there are base tools a developer uses across every project that don't get "sold" with each one.

In my case, configurators are built on an engine of my own that generates structures from rules. That engine is what lets me avoid starting from scratch with every manufacturer. What belongs to your product —your rules, your parts, your prices, your information— and what gets handed over, and how, is agreed in writing on each project. What matters is that we talk about it before, not after.

In questions to ask a 3D configurator developer there's a list you can use with any provider, me or anyone else.

A short list for the first call

• Which domain will it live on?
• Whose name is the hosting under?
• Can I export my inquiries and quotes whenever I want?
• Who changes prices, and how?
• What do I get if I decide to end the relationship?
• How are changes and new products handled after launch? (I cover that in maintaining a 3D configurator.)

If a provider answers all of these clearly, you're in good shape. If they dodge one, ask again.

I'm Facundo Campo, and I build 3D configurators and quoting tools for manufacturers, working remotely from Buenos Aires, Argentina. I answer these questions on the first call, before you have to decide anything. If you want to ask them, message me on WhatsApp at +54 9 11 6193-3176 or email facundocampo100@gmail.com. I answer in English and Spanish. You can also see how custom 3D quoting software projects work.

Frequently asked questions

Can the configurator run on my company's domain?

Yes, and that's what I recommend. It can live on your own subdomain or be built into the website you already have, so every link that gets shared carries your brand.

Who owns the customer data that comes in through the configurator?

You do. Inquiries, contacts and quotes are part of your business, and it's worth agreeing from the start that you can export them whenever you need to.

Will the developer see my prices?

While building and testing the pricing logic, the developer works with your numbers or with sample numbers. Once it's live, your team loads and changes prices from its own table. If that's a concern, you can agree to work with test values.

Does this replace a contract?

No. It's a list of topics to keep the conversation organized. Whatever you agree on should go in writing, and if you have legal or personal data questions, check with a professional where you operate.