Pricing built around your project.
You pay for the modules you use — never per user, and never on the value of construction running through the platform. Storage is included; AI is metered by usage. Every engagement is scoped to your project, which is why we don’t publish list prices.
Four parts. Scoped to you.
A one-time implementation, an annual subscription with support, optional services when you need them, and AI billed by usage — the same for a single project or an enterprise.
Implementation
Onboarding through launch — scoped per engagement, paid once.
- Discovery, process mapping & configuration
- Data migration where needed
- Training for your team
- Testing, launch & early support
Per project
Scoped — fixed fee by complexity
Enterprise
Scoped — per program
Subscription + support
Platform access and working-hours support — bundled in your annual contract.
- Platform access for your whole team
- Working-hours support (9×5 local time)
- Platform updates & new releases
Per project
Annual
Enterprise
Annual — portfolio-wide
Additional services
Premium help beyond standard support, when you want it.
- Dedicated solution engineer for custom workflows
- On-site training & workshops
- Custom AI agent development
- Custom integrations beyond standard connectors
- Advanced analytics & benchmarking
- Extended support hours
Per engagement
À la carte — scoped
AI usage
AI is metered on token consumption — you pay for what the agents actually process.
- Billed on the tokens agents consume
- Transparent usage reporting
- Scales with adoption, not seats
- An allowance is included; overage is metered
Per project
Usage-based
Enterprise
Usage-based — pooled
No list prices — because no two engagements are the same work.
Your quote reflects the actual work of getting your team live and productive — not a tier you grow out of. Six things shape it.
Component
What it covers
What moves it
Modules switched on, workflows mapped to your approval matrices, templates and numbering to your standards.
Number of modules; the complexity of your delegation of authority.
Bringing existing registers, documents and histories in — with revision trails intact.
Volume and state of your existing data. None needed means nothing charged.
Connections to the tools you keep — ERP, scheduling, design.
How many systems, and how they exchange data.
Hands-on sessions with your real project data, per role.
Team size, roles, sites and shifts.
A structured cutover, project by project — no big-bang risk.
Number of projects, and how you phase them.
Intensive support in the first weeks after go-live, until steady state.
The duration and coverage you choose.
Scope these once, and the ongoing platform cost is simple: the modules you use, with storage included and AI metered by usage — never per user, and never on construction volume.
Pay for the work, not the seats.
Priced by the modules you use
You pay for the modules you turn on — not for a tier you grow out of.
Never per user
Never per user. Owners, contractors, consultants and vendors all come in at no per-seat cost, because collaboration is the point of one record.
Never on construction volume
Never on construction volume. Zepth does not charge on the value of construction running through the platform, so your cost does not rise because your pipeline did.
Storage is included
Storage is included. Your documents, drawings and project data are not metered.
AI metered by usage
AI is metered on usage — you pay for what the agents actually process, and you can see and control it.
Same model across the platform.Start withZepth CoreZepth VectorZepth Edge— each follows the same implementation, subscription, services, and AI-usage model.
Two ways to get started.
Whether you're starting fresh or moving an existing operation across, the path is the same shape — sized to your project.
Track 01 · New project
Greenfield rollout
Standard setup, no legacy data.- 01Kickoff
- 02Set up
- 03Connect your tools
- 04Train your team
- 05Launch
Track 02 · Enterprise
Enterprise rollout
Legacy data, integrations, bigger rollout.- 01Discovery
- 02Set up
- 03Configure & customise
- 04Move your data
- 05Train your team
- 06Review & launch
Start with one product. The record is ready for the other two.
Teams drowning in documents, RFIs, inspections and site records.
Typical starters
Owners and contractors fixing document chaos and review turnaround first.
Teams losing margin in tendering, purchasing and invoice reconciliation.
Typical starters
Commercial teams ending email tendering and unmatched invoices.
Owners and operators governing budgets, CapEx and assets after handover.
Typical starters
Hotel and real-estate owners replacing spreadsheet CapEx governance.
Most teams start with one product and one pain. Because all three run on the same record, adding the second is a configuration — not an integration project.
Questions, answered.
- How is Zepth priced?
- By the modules you use — never per user, and never on the value of construction running through the platform. Each engagement is quoted on scope: configuration, any migration and integrations, training, go-live and hypercare. Storage is included; AI is metered by usage you can see and control.
- Why don’t you publish list prices?
- Because the real cost of getting a team live is the work — configuration, migration, integration, training, go-live support — and that differs by scale and by the state of your data. A quote scoped to your actual engagement is more honest than a tier that fits nobody.
- Do subcontractors, consultants and vendors pay for access?
- No. Owners, contractors, consultants and vendors are all invited at no per-seat cost. Collaboration is the point of one record — charging for it would defeat the purpose.
- What happens to cost as our team or pipeline grows?
- Adding people costs nothing, and neither does building more. Cost changes when you switch on more modules, add projects or properties, or use more AI — all of it visible and predictable in advance.
- Do Core, Vector and Edge price differently?
- No — they share one model: a scoped implementation, an annual subscription, optional services, and AI metered by usage. Start with one product; adding the second is a configuration, not a new contract shape.
- How does AI billing work?
- AI is metered on the tokens agents consume — you pay for what they actually process, with transparent usage reporting and an allowance included. On an enterprise engagement, usage is pooled across your projects.
- What does implementation cover?
- A one-time, scoped setup — discovery and configuration, data migration where you need it, integration with the tools you keep, training on your real project data, go-live and hypercare. Paid once.
- What’s included in the subscription?
- Platform access for your whole team, working-hours support (9×5 local time), and ongoing platform updates — bundled in an annual contract.
- How does enterprise differ?
- It is a larger, portfolio-wide deployment scoped across all your projects, with configuration and data migration handled as a programme rather than per project. Same pricing model.
- Is support available 24/7?
- Standard support is working hours, 9×5 in your local time. Extended hours are available as an additional service.
Comparing us against something else?
Honest comparisons with Procore, Aconex, Unifier and Autodesk — including when to choose them instead. No competitor pricing, no review scores, no feature claims that go stale.
Let's scope your engagement.
Tell us about your project and we'll walk you through how pricing works for your scope.