Agency vs. productized build
A generalist development agency will typically quote $25,000–150,000 and six to eighteen months for a configurator, and spend a meaningful share of that budget learning your domain. A productized build — a vendor who has built this specific class of tool repeatedly — is fixed-price and measured in weeks, because the hard problems were solved on someone else's project. Both are legitimate. This page is about telling them apart, and the contract terms that matter more than either.
Most of the price is uncertainty, not code
When a good agency quotes $90,000 for a configurator, they aren't overcharging. They're pricing what they don't yet know: how many rules your catalogue really has, how your part numbering works, what happens when a dealer picks an invalid combination, how your pricing tiers interact. That uncertainty is real, and it is expensive to carry.
A vendor who has built twenty configurators has already paid for that learning. Rule validation, part number generation, dealer permissions, quote output — those stop being open questions and become setup. The saving isn't a cheaper hourly rate. It's that fewer hours are spent discovering things that are already known.
The corollary is the honest limitation: a productized vendor is opinionated. If your requirements genuinely sit outside the shape they build, the efficiency disappears and a flexible agency is the better partner. A good specialist tells you that on the first call.
Side by side
Highlighted cells mark where each model has the genuine advantage — and it isn't one-sided:
| Dimension | Generalist agency | Productized build |
|---|---|---|
| Pricing model | Usually time & materials, or a fixed price with a large risk premium | Fixed price agreed before work starts |
| Typical cost | $25,000–150,000 for a configurator; enterprise scopes go far higher | $12,000–45,000 depending on rules, pricing, and integrations |
| Timeline | 6–18 months is common once discovery and revisions are counted | 4–5 weeks to live |
| Domain knowledge | Learns configurator problems on your project, at your expense | Has solved rule engines, part numbering, and dealer logic before |
| Breadth | Will also build your ERP portal, mobile app, and rebrand your website | Configurators and buying tools only — narrow by design |
| Truly bespoke scope | Genuinely open-ended — anything you can specify, they can attempt | Opinionated. Unusual requirements outside the shape may not fit |
| Team continuity | Varies — the people who pitched may not be the people who build | Small team, no account-management layer |
| You own the code | Depends entirely on the contract — read it carefully | Yes, contractually, including content and infrastructure |
Agency cost and timeline ranges are drawn from published 2026 industry pricing surveys and vary enormously by scope, region, and seniority. Treat them as the shape of the market rather than a quote.
The ownership trap
This is the part worth reading twice, because it costs more than the difference between any two quotes on your desk.
Two clauses, not one
Code assignment. Without an explicit clause transferring ownership, the agency may retain the copyright in what they wrote and license it to you. Many standard agency contracts are drafted this way by default. It rarely matters until the relationship ends — and then it matters enormously.
Infrastructure control. Owning the code means little if the application runs in the vendor's cloud account. Companies have paid well above market hosting rates for years because leaving meant rebuilding from scratch. Require deployment into accounts registered to your company, with your team holding admin access — on day one, not at handover.
Ask for both in writing before you sign anything. We're a vendor, not your lawyers, and this isn't legal advice — have someone qualified read the actual clause in the actual contract, including ours.
Eight questions to ask any configurator vendor
Including us. If a vendor is evasive on any of these, that's the useful signal — the answers matter less than the willingness to give them straight:
- 1Have you built a product configurator with a real rules engine before?Not a colour picker or a product finder — a tool that blocks physically invalid combinations. Ask to use one they built, live, in the browser. Screenshots and case-study copy hide an enormous amount.
- 2Is this fixed price, and what specifically changes it?Time and materials transfers all scoping risk to you, which is fine if you have deep in-house product expertise and bad if you don't. If it's fixed, get the change-order triggers in writing before signing.
- 3Who owns the source code when we're done — in the contract, not the pitch?Without an explicit clause, the developer may retain ownership of the code they wrote. This is the single most common expensive surprise in custom software, and it only surfaces when you try to leave.
- 4Whose cloud account is it hosted in?Code ownership means little if the infrastructure lives in the vendor's account. Manufacturers have paid inflated hosting fees for years because the vendor held the keys. Insist on deployment into infrastructure you control.
- 5Who does the product modelling and the visual assets?This is the bulk of the real work in any configurator. Some vendors quote the software and quietly assume you'll supply structured product data and every variant image. Establish exactly where that boundary sits.
- 6How do we add a product line in year two without calling you?A configurator you can't update is a depreciating asset. Ask specifically whether non-technical staff can add options, prices, and variants through an interface — and ask to see that interface.
- 7What happens when a buyer finds a combination the rules didn't anticipate?Every catalogue has edge cases nobody documented until a customer hits one. The answer reveals whether they've done this before. 'That won't happen' is the wrong answer.
- 8Can I speak to a manufacturer you built one for?Not a logo wall — a phone call. Ask that reference what went over, what took longer than planned, and what they'd scope differently. Every real project has those answers.
When to hire the agency instead
There are situations where a broad agency is straightforwardly the right choice, and pretending otherwise would make this page worthless:
- The configurator is one workstream inside a larger digital programme, and you want a single accountable partner across all of it
- Your requirements involve genuine novelty — simulation, physics, hardware integration, or a workflow nobody has productized
- You need a long-term embedded team rather than a delivered project
- Procurement requires a vendor of a certain size, with certifications and insurance thresholds a small specialist won't clear
If none of those describe you, and what you need is a buyer-facing configurator for a product line you can name today, the productized route is usually faster and cheaper for the same outcome. The way to find out is cheap: ask for a working concept before anyone quotes you a number, and compare what actually appears.
Questions, answered
How much does it cost to hire an agency to build a product configurator?
Published ranges for custom configurator development run from about $25,000 at the small end to $150,000 for complex projects, and full enterprise builds with deep ERP and CAD integration have been quoted in the $300,000–750,000 range over 12–18 months. The spread is enormous because 'configurator' covers everything from a guided product finder to a constraint-solving engine driving CAD output. A productized build — a vendor who has done this specific thing repeatedly and quotes a fixed price — typically lands at $12,000–45,000.
Why is a specialist cheaper than a generalist agency for this?
Because most of the cost in a custom project is uncertainty, not code. A generalist agency prices in discovery time, learning your domain, and the risk of unknowns — reasonably, since they don't know yet what your rules engine needs to do. A vendor who has built the same class of tool repeatedly has already solved rule validation, part number generation, dealer permissions, and quote output, so those stop being research and become configuration. The narrower the vendor, the less of your budget pays for their learning curve.
When is a full custom agency genuinely the better choice?
When the configurator is one part of a much larger programme — a new ecommerce platform, a dealer portal, an ERP replacement — and you want one accountable partner across all of it. Also when your requirements are genuinely unusual: unique physics or simulation, hardware integration, or a workflow no productized approach anticipates. In those cases the flexibility is worth the premium, and a narrow vendor will hit its limits.
Who owns the code when an agency builds custom software?
It depends entirely on your contract. Without an explicit assignment clause, the developer or agency may retain ownership of the code they wrote, licensing it to you rather than transferring it. Even with clean legal language, companies get locked in through infrastructure — if the application lives in the vendor's cloud account, practical control sits with them regardless of who owns the IP. Get both written down: assignment of the code, and deployment into infrastructure in your name. This isn't legal advice, and it's worth having a lawyer read the actual clause.
What is a productized build?
A service delivered with a repeatable scope, process, and price, rather than quoted fresh from scratch each time. For configurators it means a defined deliverable, a fixed price agreed upfront, and a known timeline — because the vendor has built the same class of tool many times and knows what it takes. The trade-off is honest: you get speed, price certainty, and accumulated domain expertise, and you give up open-ended flexibility. If your requirements sit outside the shape, a productized vendor should tell you rather than stretch to fit.
How long should a configurator take to build?
A focused buyer-facing configurator for a defined product line should be live in four to eight weeks. Agency projects commonly run six to eighteen months, but that's usually a scope difference rather than a speed difference — broader remit, more stakeholders, deeper integrations, more review cycles. If a vendor quotes a year for a single product line's configurator, ask precisely what's consuming those months. There may be a good answer; you should hear it.
ChatGPT
Perplexity
ClaudeKeep reading
Compare us against a quote you already have.
Send us your most quote-heavy product and we'll build a free working concept in about a week. Put it next to whatever an agency has quoted you, and judge on the working thing rather than the proposal.
Get a free concept