Pricing
Scoped per deployment, quoted after a call.
There are no figures on this page, and that is deliberate rather than evasive. Here is exactly how the commercial side works, what drives the number, and what you get in writing before committing to anything.
The shape of it
Wardly is a paid engagement. There is no free tier, no trial, and no self-serve plan. What you are buying is the deployment and the configuration — the work that makes the measurement correct and the reporting specific to your business — plus the system that delivers it.
Commercially that has two parts. There is the initial deployment and configuration, and there is the ongoing running of the system with the review that keeps the configuration current as the business changes. Both are set out separately in the scope so you can see what you are paying for.
What drives the number
Almost entirely the configuration work, which is why it cannot be read off a traffic band.
- How many conversion paths need instrumenting, and whether any of them complete inside third-party checkout, payment or scheduling flows.
- How settled your conversion definition already is. Where marketing and finance already agree what counts, this is quick. Where defining it surfaces a disagreement, that conversation becomes the project.
- How many entry points and campaign structures need grouping and verifying.
- How much reporting shape is needed, and whether different teams need genuinely different views over the same data.
Traffic volume matters much less than people expect. A high-traffic site with one clean, well-understood conversion path is a straightforward deployment. A modest site whose conversion completes across three third-party flows is not.
How you find out the number
You book a scoping call. Thirty minutes, no deck, with the person who would do the work. We look at your site and your traffic and get your conversion event pinned down to something countable.
After that you get a written scope: what we would deploy, what we would need from your team, a timeline expressed as a range, the terms around data, and the cost. Nothing is committed until you have that document in front of you.
If the call establishes that this is not a fit, you get that answer instead, along with the reasoning and — where we can — a pointer to what would fit better. That costs you nothing.
For comparison
Where this sits.
This is more expensive than an analytics subscription and less expensive than hiring someone to own measurement internally. That is the band it is designed to sit in, and it is the honest comparison to make.
If what you need is accurate traffic reporting, a self-hosted tool costs a fraction of this and does that job well. If what you need is a properly configured measurement layer and nobody in your business currently owns that work, the comparison is not tool versus tool — it is this against the internal time that would otherwise go into it, which is usually the larger number and the one that never gets counted.
Questions
Common questions.
Why don't you publish a price?
Because the work varies enough that any number we published would be wrong in both directions. A deployment on a single site with a clearly defined purchase event is not the same job as one spanning several entry points with a conversion nobody has agreed on yet. Publishing a figure would mean either over-quoting the simple case or under-quoting the complex one, and then renegotiating on the call — which is worse than not publishing.
Is it a subscription or a one-off?
Both parts exist. There is the deployment and configuration work at the start, and there is the ongoing running of the system and the review that keeps the configuration current. The split between them is set out in the written scope.
What determines the number?
Mostly the configuration work: how many entry points and conversion paths need instrumenting, how settled your conversion definition already is, and how much reporting shape the deployment needs. Traffic volume matters far less than people expect — a high-traffic site with one clean conversion path is a straightforward deployment.
Is there a free trial?
No. There is no free tier, no trial and no pilot pricing. The value of the engagement is the configuration work, and a version of that done cheaply to win the deal would be the same badly configured measurement everyone already has.
How do we pay?
By invoice, on the terms in the scope. We do not process card payments through this website and there is nothing to check out.
What if it turns out we don't need this?
We tell you on the scoping call and you pay nothing. It happens reasonably often — sometimes the honest answer is to configure your existing analytics properly, or to use a cheap self-hosted tool. Both are better outcomes than an engagement that was never going to earn its cost.
The number comes after the call.
Thirty minutes to scope it, then a written scope with the cost in it. Nothing committed before that.