Working method
We shop the live path, then write like a buyer.
The method is the same whether the question is conversion, basket mix, category ladder, or a season calendar. Evidence comes from the pages a shopper can already see, plus files you choose to share with names removed.
1. Name the rail
You pick one storefront and one privilege: a category, a hero family, or a season. We refuse “the whole shop” on the first engagement because a dossier that names every SKU names nothing. Contractual must-keep items are listed before we start clustering duplicates.
2. Walk as a stranger
Two readers shop listing, product, cart, and checkout on a laptop and a mid-size phone. We do not log into your admin. We do not paste a script into your theme. If a guest login is required for a wholesale path, you create it and we delete it from our notes when the dossier ships.
3. Pair the page with the ticket
Where you send a stripped order-line export, we sit pairs and singletons next to the live attachment modules. A cloth that never shares a basket with the throw it is meant to protect is a merchandising placement problem, not a mystery of “behaviour.”
4. Rank what to touch
The dossier lists changes in the order a small team can actually brief: copy under the price, photograph slot two, module that appears too late, SKU that should stop being recommended. We also name what we would leave alone so the readout does not become an endless punch list.
5. Readout, then one round of questions
You receive the PDF two days before we meet. The meeting is for argument, not a first reading. After delivery you may send written questions once. Further seasons or categories are new engagements.
Desk utility, optional
Some clients keep their own conversion and basket notes in a local desktop utility for record-keeping. If you want that listing, it is available through Veve as a normal web link. Buildstreamgrid readings do not require it.