We'd like to hear from you

Yes — you can start a free 14-day trial right now, no credit card required. See the Pricing page for plans.

Wholesale and open-access fibre network operators, first — a PMO Manager, several PMs, an Access Planning specialist, and one or two Sales/KAM seats, running multi-site fibre rollout. The governance model is designed to eventually serve other delivery-constraint industries too, but this is the first, sharpest use case it's being proven against.

Zolvd for Teams isn't a horizontal task tracker. It's built around a specific operational sequence — order intake, PM assignment, scoping, baseline sign-off, delivery execution, closure — with RAID, RACI, SLA/OLA, escalation, and budget governance enforced at every stage, not bolted on as optional widgets.

Neither. The system drafts, flags, and surfaces exceptions — a human always approves, declines, edits, or escalates. It never acts unilaterally on a client-facing commitment. The goal is letting one PM safely hold more load, not removing the PM from the loop.

Five tiers — Owner/Admin, Contributor, Specialist, Limited, and External/Portal — control both what you can do and what you can see. A Sales/KAM (Limited) user sees their own clients' project status and RAG, for example, but never RAID specifics or internal escalation notes.

Flat monthly or annual tiers by seat count — Teams Starter, Growth, and Scale — rather than per-seat billing. Every plan includes the full feature set; only the seat limit changes. See the Pricing page for exact figures.

Yes. Every table is scoped by organisation with row-level security enforced at the database layer, and role-based visibility layered on top at the application layer — a Sales/KAM user, for instance, is blocked from RAID Log and Escalation Matrix data at the database level, not just hidden in the UI.

Yes — that's exactly what this contact form is for. Tell us about your team and what you'd want to see, and we'll follow up directly.