“Customer portal” can describe a secure page with a few documents or a full application with accounts, orders, approvals, messages, payments, and workflow status. Define the customer task before comparing prices.
The portal's data, permissions, integrations, and support model usually drive more cost than the login screen.
Define the customer job
List what customers need to see or do: download documents, approve work, view status, request support, pay an invoice, update details, schedule service, or communicate with a team.
Separate portal scope from website scope
A marketing site can explain the portal, but the authenticated experience needs user accounts, sessions, permissions, data retrieval, audit history, password recovery, and error handling.
Decide whether customers, staff, managers, vendors, or other roles see different data or actions.
List integrations and data ownership
Identify the CRM, accounting system, project system, inventory, support desk, payment provider, document storage, and notifications. Decide which system owns each fact and how changes sync.
The customer portal feature guide and login cost guide cover adjacent scope decisions.
Plan security and operations
Budget for role-based access, secure sessions, file permissions, secret management, logging, backups, account recovery, monitoring, and support. A portal that exposes the wrong document is a serious failure even when the interface looks polished.
Ask for a staged estimate
Request separate scope for discovery, authentication, core workflow, integrations, notifications, QA, launch, and support. A focused first release is often easier to test than an all-in-one portal.
At Vertinus's published rate of $49.99 per hour, quotes should show the assumptions behind each stage and the work excluded from the initial release.
Have a portal idea but no agreed first workflow? Ask Vertinus to turn the customer tasks into a scoped release plan.