Threekit, Salesforce CPQ and visual configuration

What's changed

• Salesforce CPQ is end of sale. Salesforce stated in July 2026 that it no longer sells new CPQ licenses to new customers. Existing customers keep full use, renewals and support, but new features go into Revenue Cloud Advanced (RCA), which has an attribute-based catalog and a constraint-based configurator. A new buyer today is evaluating visual configuration against RCA, not CPQ. An existing CPQ customer is choosing whether to stay or migrate.
• Threekit has broadened. Threekit is known for 3D product visualization and AR. It announced an integration with RCA in 2024 and, in October 2026, launched an AI-native CPQ for manufacturers. That makes it both a potential visual layer on Salesforce and a potential CPQ in its own right.

RenderDraw isn't affiliated with Threekit. Vendors' capabilities change; confirm current features in your evaluation rather than relying on any comparison page, including this one.

What to compare

Three architecture patterns

1. Visual layer inside the Salesforce configurator. Salesforce holds rules and pricing; the visual tool renders the current state. One rule engine, but the visuals depend on Salesforce's configuration model.
2. External rules engine passing results to Salesforce. The visual tool validates the configuration and creates quote lines. Simpler for complex visuals, but now two systems have product logic.
3. Separate CPQ. The external tool configures, prices and quotes, and Salesforce gets the opportunity and the outcome. Cleanest for dealer and web channels; most change for a Salesforce-centric sales team.

Each pattern affects where rules live, how pricing is calculated, and how many places need updating when a product changes. Two rule engines that must agree are a maintenance risk.

Questions to ask

• Where do configuration rules live: Salesforce, the visual tool, or both?
• Which system calculates price, and how are discounts and approvals handled?
• How are product changes synchronized between systems?
• Does it support Salesforce CPQ, RCA, or both, and what changes if we migrate?
• What happens when the visual tool is unavailable?
• Who builds and maintains 3D models, and in what formats?
• How does the configuration reach orders, ERP and production?

Evaluation steps

1. Write requirements first. Products in scope, rules, pricing approach, outputs, users, integrations, and non-functional needs (mobile performance, load times, accessibility, data residency, security review). Rank must-haves.
2. Pick a hard product with real rules and pricing, including the edge cases that cause errors today.
3. Map rules to where each tool would hold them.
4. Test quoting from configuration to a Salesforce quote, including approvals.
5. Test admin. Have each vendor change a rule and a model end to end and show it in a quote.
6. Cost it over several years: licenses, implementation, visual content, integration maintenance, admin time and usage fees.
7. Call references with products as complex as yours. Ask how long changes take and who makes them.

Total cost beyond license fees

A tool with a lower license price can cost more if every product change needs specialist work. Visual content is often the largest hidden cost. Ask whether models can be generated from your CAD, and who updates them when products change.

Where RenderDraw fits

RenderDraw adds guided, visual product configuration to Salesforce-centered quote workflows. Buyers and reps make choices, rules explain conflicts, and a validated selection moves into pricing and the configured quote or proposal workflow. It works alongside Salesforce CPQ or Revenue Cloud as a visual layer. Bring one configurable product and its rules to a demo.