Whatever your stores need next.
Launching the first sites, keeping the ones already live in good health, or absorbing the banner you acquired last quarter. Twelve engagements, each scoped in writing, delivered by a named team, and priced before it starts.
Four regional delivery teams, each led from inside the region it serves.
Your team already does some of this. We do the rest.
Solution design, integration, deployment, and enablement. Everything the team delivers draws on these four, and each one is scoped and priced on its own.
Solution design
A consultant walks your sites and works through the use cases with the people who will run them. What comes out is a design that fits your formats, not a template with your logo on it.
Integration
Connecting Clarity to the ERP, WMS, and order systems you already run, so the item-level record and your systems of record agree. This is the work most often underestimated by everyone involved.
Deployment and rollout
Site surveys, hardware installation, reader tuning, and store-by-store go-live. Sequenced so every store learns from the wave before rather than repeating the first one's mistakes.
Enablement
Training your trainers, building the material they will reuse, and staying close through the first cycles. A rollout that depends on us being in the room has not finished.
Everything from the first survey to the fifth year.
Each one is scoped, priced, and delivered on its own. Retailers tend to start with a single piece of work and come back when the stores change, which they always do.
Survey and solution design
A consultant on your sites, and a design your team can build a business case from.
Scope this 02Design and launchStore floorplan and RF design
Antenna placement, read zones, and shielding mapped to your actual layouts, including new formats and shop-in-shops.
Scope this 03Design and launchIntegration build
The ERP, WMS, or OMS connection, scoped and delivered as its own piece of work.
Scope this 04Design and launchRollout wave
A defined block of stores taken live together, with the pattern documented for the next wave.
Scope this 05Keep it healthyEvery 12 monthsAnnual site health check
Read rates, accuracy, and hardware condition measured across live sites, with the fixes ranked by impact.
Scope this 06Keep it healthySeasonalPeak season readiness
A pre-peak check that the stores, the hardware, and the integrations will hold through your busiest eight weeks.
Scope this 07Keep it healthyAdoption review
Which stores use which features, and which ones quietly stopped, drawn from usage data rather than anecdote.
Scope this 08Keep it healthyTraining refresh
Re-training for a store population that has turned over since go-live, and material your trainers keep.
Scope this 09Grow your storesNew store openings
A repeatable package applied to each site you open, so a new store is live on day one rather than in month three.
Scope this 10Grow your storesNew banner or new DC
Bringing an acquisition, a new format, or a new distribution center onto the stores you already run.
Scope this 11Grow your storesSource tagging program
Defining the tag spec, onboarding your suppliers, and cutting the invalid tags arriving on inbound stock.
Scope this 12Grow your storesUpgrade and optimization
Moving to the current release and tuning workflows around how your teams actually work.
Scope thisFor stores that went live a while ago, the annual health check is the usual starting point. It is short, it produces a ranked list, and it answers whether the accuracy you had at go-live is the accuracy you have now.
You sign a design, not a pitch.
A consultant walks your sites first. What you approve at stage two is built from what is actually there.
Survey
On-site workshops with operations, IT, and the store or DC teams. Formats, systems, use cases, and the constraints nobody writes down.
Scope
A solution design and a statement of work with deliverables, dates, and price. This is the document you sign, and nothing starts before you do.
Deliver
Configuration, integration, installation, training, and go-live, tracked against the SOW so you can see what is done and what is next.
Hand over
A documented handover to Customer Experience, who own support from that point on. The people answering your tickets know how your stores were set up.
Flexibility is built into the way we work.
Retail programs move. A banner is added, a DC opens, a format you were not planning for arrives. Two things make that easy to absorb: a quick change order inside a project, and a retainer across several.
A change order, turned around quickly.
- Anything outside the signed scope is written up and priced before it starts
- The effect on dates and cost is spelled out, so you decide with the whole picture
- Keeping the original plan is always one of the options, and it is chosen more often than you would think
One retainer, many projects.
- A single signed retainer instead of a fresh procurement cycle for every statement of work
- Several projects at once drawn down against the same agreement
- Streamlined signatures so the next piece of work starts in days rather than after the next approval round
A named team, working from your region.
You get the people whose names are on the SOW. Delivery leads are based in the UK, the Nordics, the Middle East, and the Americas, because a rollout in Kuwait should not be run by someone who has never seen the site.
- A delivery lead who owns your program end to end
- Solutions consultants who have run RFID rollouts before
- Regional presence so a site visit is a normal part of the plan rather than an escalation
- A handover into a support team that was part of the build
Delivery slots are booked by quarter, so the earlier a rollout is scoped the more say you have over when it starts.
Tell us what needs delivering.
This goes to the delivery team rather than to sales, so the first conversation is about scope, sequence, and what it would take, not about a contract.
A scoping call
With a delivery lead who can scope the work there and then.
A written outline
What the work involves, roughly how long, and what it depends on from your side.
A statement of work
Deliverables, dates, and price. You approve it before anything starts.
There is always a next piece of work.
A first wave, an annual check, a new banner, a team that has turned over since go-live. Whichever it is, it gets scoped before it starts and priced before you commit — and when there is more than one, a single retainer can carry them all.