Pricing shaped around the programme you need to run.
RetailHawk pricing is quoted against the platform scope, programme volume and delivery support you need. We do not publish invented package prices or force unlike programmes into a single headline number.
Four things normally shape a RetailHawk quote.
Platform scope
The roles, workflows and product capabilities needed for your operating model — for example Mystery Shopping, audit/assurance workflows, reviewer operations and client reporting.
Programme and visit volume
The scale and cadence of the programmes being run, including the amount of fieldwork, review activity and reporting required.
Implementation and migration
Discovery, configuration, data preparation and migration support are scoped to the starting platform, programme complexity and cut-over approach.
Optional services and integrations
Additional integration, specialist implementation or programme services are scoped where they are needed rather than assumed into every quote.
Separate the recurring platform from one-off or optional work.
Recurring platform scope
Your quote identifies the RetailHawk platform scope and the programme assumptions it is based on.
Implementation
Any agreed configuration, onboarding or migration work is identified separately so procurement can see what is recurring and what is project work.
Integration work
Where an external system needs configuration or development, the requirement is discussed and scoped against the actual interface rather than advertised as universal out-of-the-box support.
Changes in scale
If programme scope or volume materially changes, the commercial impact can be reviewed against the agreed pricing basis rather than hidden behind an unexplained package label.
What buyers usually want to know before a quote.
Do you publish fixed per-user prices?
Not currently. RetailHawk supports several operating models and programme shapes, so the quote is based on the scope being evaluated rather than an unapproved public list price.
Is migration included?
Migration is scoped against what needs to move, how it will be validated and the cut-over approach. See the migration methodology.
Are integrations included?
The quote states what integration work, if any, is in scope. See Integrations for the current integration model.
What security information is available?
Start with Security and the Trust Pack. We keep security claims tied to current evidence rather than certification language we cannot substantiate.
Can we start with one programme?
The migration approach is designed around controlled programme-by-programme adoption where that fits the operating model. Scope and commercials are agreed for the actual rollout plan.
Show us the programme. We will scope the commercial model around it.
A short product discussion is normally enough to establish the workflows, likely programme scale, migration needs and integration questions that affect pricing.