What we look at first
How this platform fits the wider commerce estate.
Questions we get asked.
Will you guarantee a Lighthouse score?
No. Lighthouse is a synthetic test. We commit to measurable real-user targets on the journeys that matter, written down, and we measure against those.
Is Hyvä the answer to a slow store?
Sometimes. It helps when the rest of the stack co-operates. Where the bottleneck lives in backend, integrations or extensions, Hyvä alone will not fix it. We say so honestly.
How does an iWeb rescue actually start?
With a short, written read on the brief. We look at what is broken, what is still working, where trading risk sits and what we would protect first. No drama, no pitch.
Do you blame the previous team?
No. Blame slows recovery down. We describe what we see, sequence what matters, and write down trade-offs so the owner can make informed calls.
Will you push us to replatform?
Only when the current platform genuinely cannot carry the next twelve months. Most rescue work is stabilisation first; rebuild is the second conversation, not the first.
How does iWeb choose between platforms?
Against operational shape: catalogue depth, trade complexity, ERP integration, multi-territory rules and five-year cost. The decision is written down with trade-offs, not assumed from a vendor demo.
Where does ERP integration sit in the platform decision?
It is a primary input. Some platforms make ERP integration straightforward, some make it expensive. iWeb names the trade-off rather than hiding it.
Does iWeb deliver headless or composable storefronts?
Where they earn their place. The trade-off between optionality and integration surface is named upfront; composable is not a default.
How is search handled on this platform?
Native search where the query mix supports it; specialist engines (Algolia, Constructor.io) where the catalogue, volume or merchandising appetite justify them. Relevance is a continuous activity.
Where does PIM sit relative to the commerce platform?
PIM owns catalogue truth (attributes, variants, assets, channel readiness). The commerce platform reads from PIM rather than re-modelling deep product data in the storefront.
Can iWeb take over an existing build on this platform?
Yes, where the brief fits. iWeb will give a senior, written read on what is working, what needs remediation and what is honestly fixable, and the first month on support stays deliberately conservative on change.
How does iWeb size a five-year total cost picture?
Licence, hosting, engineering and support across the lifecycle, including the integration surface and operational ownership. The headline year-one number is rarely the honest comparison.