An intranet website can be a private collection of policies and announcements or a connected internal workspace for staff, documents, directories, requests, approvals, search, and reporting. Cost depends on how much internal information is curated and how many daily workflows the intranet must support.

Separate information from internal workflow

Basic scope may include staff sign-in, pages, announcements, search, navigation, directory, and document links. More involved scope can add departments, role permissions, document versioning, forms, approvals, requests, calendars, training, polls, notifications, dashboards, integrations, and audit history.

Clarify who owns content, what is confidential, which groups see which pages, how stale pages are reviewed, how staff search, what happens when a person changes roles, and which system owns people, files, requests, and permissions.

Budget for governance and adoption

Include authentication, hosting, search, file storage, backups, monitoring, accessibility, security, privacy, content migration, training, support, analytics, and governance reviews. Decide who owns the domain, code, content, user directory, files, and integrations.

The portal features guide offers related workflow context. The custom web application guide shows how internal rules and integrations can change scope.

Compare quotes by staff usefulness

Compare search success, page freshness, document errors, permission incidents, request completion, announcement reach, support volume, onboarding time, and content ownership. A lower quote that omits governance may produce a polished but stale intranet.

Planning an intranet website budget? Ask Vertinus to map staff access, content, workflows, search, and ownership.