Questions.
How fast is deployment?
Live within a single sprint (less than two weeks) via one lightweight snippet; optimisation compounds over the first cycle (~a month).
Our data is a mess.
That's fine. That's normal. All the engine needs to begin: your product feed and images.
What does it cost?
The ten-day test is £10K, paid only if it works. Beyond it, pricing is set to the size of the transformation, not to seats or searches: one predictable fee at full scale, and once the engine runs across the whole business, performance terms can enter the conversation.
Will it slow our site?
No. One minimal, unobtrusive snippet, built to leave your page speed alone.
What about privacy?
No names, no emails, no identifiers, in-session signals alone. Sessions stay anonymous to us, and personalisation never needs to touch your CRM.
We're considering building in-house.
Wescover did, then measured VISII ahead of their own build: +32% more conversions.
Do we have to rip out our existing providers?
Not necessarily, though you may want to. Complement the stack or replace it.
Brand-new products with no history?
No cold start: the engine understands a product from its image and meaning before the first click.
The practical questions.
Do we really need an AI engine?
If your catalogue outgrew what your team can hand-tag and your shoppers can describe, yes. Most of the growth problems we are hired for, flat conversion, rising acquisition costs, merchandising that cannot keep up, are understanding problems wearing other names.
Is our catalogue too small, or too large?
The engine earns its keep from the high hundreds of items upwards and compounds as the catalogue grows. Smaller, taste-led catalogues still benefit, especially on mobile, where patience is shortest.
Which lever should we start with?
One engine, five commercial levers: average order value, conversion, engagement, traffic and costs. Start where your number hurts most; because each understanding teaches the others, the second lever is cheaper than the first. Most clients start with recommendations or search, and expand when it pays.
How do we integrate, and how long does it take?
Two routes: one lightweight snippet that sits on top of your existing site, or a RESTful API if you would rather build it in. Either way you are live within a single sprint, less than two weeks, on any platform; a product feed (Google Shopping included) and images are all we need to start.
What does a typical deployment look like?
Week one: we read your feed and images, and you see what the engine understood of your own catalogue before anything goes live. Week two: the first surface goes up behind a randomised split test, with success criteria you set in writing. From day ten you read the result in your own analytics and decide with evidence in hand.
Can it work with the platforms we already run?
Yes: Shopify, Magento, BigCommerce, Salesforce, WooCommerce or your custom build, headless or traditional. VISII works alongside your stack or replaces it surface by surface; nothing asks you to bet the stack on day one.
Can we test it against what we already have?
We insist on it. Deployments run as randomised split tests against matched controls; your analytics referee, not the incumbent and not us. If the test does not clear the bar you set, you pay nothing.
We sell in several languages.
The engine reads meaning from images and whatever text exists, in any language, with no dictionaries to maintain. Multi-language catalogues are normal deployments, not special projects.
How fast does it respond for shoppers?
Under 100 milliseconds in session. Understanding is only useful at the speed of browsing.
Any further questions?
Don’t hesitate to get in touch, a member of our team will be very happy to help.
Book Your Growth Call