Pricing
Priced to the program, on paper before you sign.
One agreement, two parts: a software line billed per project, and program services scoped to what your program actually needs. No per-seat licenses, no multi-year lock-in — and nothing in it you haven't seen priced.
For comparison: enterprise owner-side platforms are typically sold on multi-year contracts with five- to six-figure implementations and per-seat licensing. SiteOps360 bills the software to each project like the project cost it is, and scopes the rest to the program.
Pricing questions
How is the agreement priced?
Two parts, priced together on paper before you sign: a software line billed per active project — every module and every collaborator included — and a program line covering the scoped services your program actually needs. No per-seat licenses, no multi-year lock-in.
What counts as a project?
One capital project — one budget, its contracts, change orders, invoices, drawings, and schedule. The software line follows your active projects, so a one-project owner carries exactly one project line.
Do my collaborators pay anything?
No. Invite your architect, general contractor, engineers, and stakeholders at no cost — permissions control what each person can see and do. There are no per-seat charges, ever.
Can I expense this to the project?
That’s the point of per-project billing: the software line is a project soft cost, like reprographics or permit fees — not a departmental software purchase that needs an IT budget line.
What happens when a project closes out?
It comes off the software line. Your records, documents, and audit trail remain exportable — the history is yours.
Can we see it before we commit?
Book 20 minutes and we walk a real project with you — the actual record, not slides. During evaluation you work in a workspace with a fully populated sample project, so your team judges the fit on realistic data.