What drives the price
Pricing complexity is the biggest factor. A configurator with a handful of options and fixed surcharges is dramatically simpler than made-to-measure pricing where every centimeter changes the price via lookup tables. If your pricing lives in spreadsheets with hundreds of rows, budget for a real price engine with an import flow.
The second factor is the preview. Text summaries are cheap; a live visual preview that redraws as the customer configures takes real frontend work; 3D previews are a project of their own.
Third: who maintains it? If your team needs to change prices, fabrics and options without a developer, the configurator needs an admin panel. That's worth it in almost every case, but it's a chunk of the budget.
Typical ranges (and why I don't publish fixed prices)
A focused single-product configurator with straightforward pricing is typically a few weeks of development. Made-to-measure configurators with price tables, live previews and an admin panel are bigger projects, and multi-store platforms bigger still. I don't publish fixed prices because two configurators that look identical on the surface can differ 3× in effort based on the pricing rules underneath.
What I do promise: a fixed, scoped quote before any work starts, based on your actual pricing rules and products, not an hourly meter running on an open-ended project.
What to prepare before requesting a quote
Three things make quoting fast and accurate: (1) your pricing rules, in whatever form they exist today (spreadsheet, PDF, or the brain of a colleague); (2) two or three examples of configurators you like, with notes on what you like about them; (3) clarity on who should manage prices and options after launch.
With those in hand, I can usually tell you within one call whether your idea is a two-week build or a two-month platform, and give you a written scope shortly after. Use the project configurator on this site or book an intro call to get started.