It depends primarily on the verification method required, the volume of content and documents the portal will hold, and whether it integrates with other systems — we scope against those specifics rather than quoting a flat number that would not reflect your actual requirement.
A portal with manual approval and a small document library is a fundamentally different project from one with registry-based verification across several markets and integration with a medical information system. Quoting one number for both would misrepresent one of them.
Verification method complexity, document and content volume, number of markets and languages, and integration requirements with other systems are the factors that actually move the estimate. See HCP portal for what the build actually includes.
We assess your verification requirement, content volume and integration needs before quoting — see project scoping for how that discovery phase works.
Manual verification is often cheaper to build initially, since it avoids integrating with an external registry system. It costs more over time in ongoing administrative time, though, as someone has to review each request by hand. A registry-based check costs more upfront but reduces that recurring operational burden considerably.
Multi-market support typically adds meaningful complexity to both the access model and the content model, since different markets often need different verification rules and different approved content. That complexity, more than the raw number of markets, is what affects the cost estimate, so scoping should focus on how much the rules diverge.
Project scoping is where a full discovery process produces a real number, covering verification method, content volume and market count. See project scoping for what that process involves, since any estimate given before scoping is necessarily a rough placeholder rather than a figure you can plan a budget around.
Content volume affects the estimate meaningfully, but usually less than functionality choices like verification method and access rules, since content can often be added incrementally after launch. Functionality decisions tend to be structural and expensive to change later, which is why they should be settled early in scoping.
Tell us your verification and content needs and we will give you an actual estimate.