Choose a representative sales problem
Start with the machines that regularly generate placement or configuration questions. A first release does not have to contain the whole range. It should contain enough variety to test whether the catalog supports the way your team actually sells.
Select a few products that expose meaningful differences, such as a wall-mounted unit and a floor-standing machine or two genuinely different cabinet sizes. Write down the sales question each one is intended to answer. This gives the project a more useful scope than a target based only on the number of models produced.
Inventory source assets before estimating effort
Collect available CAD, 3D files, product photographs and approved dimensions. Identify the current sellable version of each machine. Engineering and marketing teams may hold different revisions, so settle those differences before modeling begins.
Vizbl's published workflow supports preparing existing 3D or CAD assets and creating models from photos and dimensions. Those routes involve different preparation work. A source file's existence is not proof that it has the correct scale, textures or complexity for use on a phone.
Define the configuration boundary
List which features are fixed and which options the buyer can select. A finish, branded wrap or module can change the visual model, but only if that option has been prepared and connected to the catalog. Avoid treating the configurator as a tool that can invent any requested variation.
Agree on the first release's supported combinations with the sales and product teams. If several choices cannot be sold together, the preview should not invite that combination. Stable option names and product codes help keep the model, proposal and eventual order aligned.
Review accuracy and usability separately
Have the product owner inspect scale, visible equipment and placement configuration. Then have a salesperson use the catalog in a realistic conversation. These reviews reveal different problems: an inaccurate cabinet detail is not the same issue as a model that is difficult to find or slow to open.
Check a phone, a desktop and the link or QR handoff that your team intends to use. When an external viewer is unavailable, the page should remain useful. Keep an approved image, product identity and a clear path to continue the inquiry instead of simulating a successful load.
Define what expansion depends on
At the end of the first release, review the actual questions the catalog helped resolve and the problems that remain. Useful findings may include a need for another machine size, clearer configuration labels or a better follow-up process. They do not need to be inflated into a claimed sales percentage.
Plan expansion around verified demand and preparation capacity. Pricing can depend on catalog size, model complexity, configuration work, usage and distribution, so retain those assumptions in the scope. A reviewed, maintainable collection gives the business a better foundation than a large catalog whose models no longer match the machines being sold.