There is no price list, and inventing one would be worse
We have not delivered enough engagements to publish tiers that would still be true in six months. So instead of a table of numbers designed to make you call, here is what drives the cost, what the three engagement shapes look like, and what you own when it ends. Public platform tiers come when the numbers behind them are real.
Three shapes, in order of commitment
Nobody starts at the bottom of this list. Most people should not.
A scan
Free
You point the Web Compliance Agent at a domain and it returns findings mapped to the clause each one comes from. No account, no call, no obligation. Most people stop here, and that is a legitimate outcome.
One finishable piece
Fixed quote
A site, a workflow, a shoot, a scan of a facility. Scoped tightly enough that it either works or does not inside a few weeks, and priced as a single number agreed before it starts.
An ongoing build
Monthly
Modules switched on as they are needed, with the studio work around them. Only sensible once the first piece has landed and both sides know how the other works.
What actually moves the number
If you can answer these four for yourself, you already know roughly what an engagement will cost, and whether it is worth the call.
The state of your data
Clean exports make a migration a week. Fifteen years of spreadsheets with three spellings of the same supplier make it a month. This is the single largest driver, and it is the one nobody quotes for honestly.
How many people have to change what they do
Software that one person uses is a project. Software that forty people on a shop floor use is a change programme, and the training and handover are most of the cost.
Whether the residency rules bind
If your workloads must stay in a specific region, routing and provider selection are constrained from day one. It is not more expensive to build — it is more expensive to retrofit, which is why we ask early.
What has to be captured in the real world
Crew days, flight days and scan days are the only part of what we do that cannot be compressed by working smarter. They are priced per day, and the day count is agreed before anybody travels.
What you own at the end
The repository. The domain. The hosting account. The database. The raw capture files from every shoot and every scan, not just the exports we chose to give you.
Leaving should cost you a handover meeting, not a rebuild. A vendor who holds your infrastructure is not charging you for value, they are charging you for the difficulty of leaving — and that arrangement makes the software worse, because it no longer has to earn the renewal.
Questions we get before the first call
How is CUZN priced?
Engagements are scoped and quoted individually today, because the work varies more than a tier table would suggest. Public platform tiers are planned once we have enough delivered engagements to price them honestly.
Can I keep my existing ERP or CRM data?
Yes. We migrate from spreadsheets or an existing system and reconcile the result so you can check it, rather than asking you to trust the import.
Do I own what you build?
Yes. You keep the repository, the domain and every hosting account. We do not hold infrastructure as leverage.
How small a project will you take?
One workflow is a perfectly good place to start, and it is usually the right one. It gives both sides a real result to judge before anything larger is committed.
Start with the free one.
The scan costs nothing and tells you something true about your site in a couple of minutes. Everything else can wait until after you have seen how we work.