Intranet Portal Development Costs — Consolidating Scattered Company Information

An intranet portal (company portal) is an internal website that consolidates announcements, policies, manuals, and request forms that would otherwise be scattered across the company, giving employees one place to find what they need. Before evaluating this, it's worth reviewing the basics of ordering a system build and then determining whether your organization actually needs custom development at all.

Much of what a company portal needs can already be handled by the portal features built into Microsoft 365 or Google Workspace, or by an off-the-shelf groupware product. If your requirements can be met with existing templates and configuration, that route offers better cost-effectiveness. Custom scratch development tends to make sense only when you need to integrate the portal tightly with a proprietary business system (attendance, inventory, CRM, and so on), or when an existing product's permission model can't represent your organizational structure.

- Announcements/bulletin board: company-wide or department-specific announcements with read tracking
- Policy and manual repository: a central place for work rules, operating manuals, and templates
- Workflow (requests and approvals): digitizing approval requests, expense reports, leave applications, and similar
- Internal search: cross-searching documents, announcements, and employee information
- Employee directory and org chart: department contacts and role visibility
- Permission management: controlling view/edit access by department and role

Cost varies significantly depending on whether you customize an existing product or build a scratch system tied to proprietary workflows. The ranges below are a rough guide — actual costs vary by requirements, so confirm with quotes from multiple vendors.

- Workflow complexity: more branching and conditional approval routes raise design costs
- Number of integrations with existing systems: whether data syncs with attendance, HR, or accounting systems
- Granularity of permission design: more finely segmented visibility by department, role, or employment type adds complexity
- Number of users and access concentration: larger organizations need more thought given to server and infrastructure design
- Volume of existing documents to migrate: how much of your legacy manuals and policies need to move over

A company portal isn't done once it's built — it only delivers value if announcements and policies keep getting updated. A commonly overlooked issue at build time is who will own day-to-day updates. If update duties are left entirely to IT, the latest information from each department rarely makes it in, and the portal turns into a place people check only to find stale content — one of the most common failure patterns. Assigning an update owner in each department and giving them a simple form to post announcements are the kinds of operational details that need to be designed in from the start, not bolted on afterward.

Aiming straight for a complete, company-wide final version tends to make requirements balloon, which makes both cost and timeline hard to estimate. A more realistic approach is to start with the highest-frequency features — announcements, and policy/manual consolidation — and expand step by step, applying the MVP mindset for reducing development costs. A common failure pattern is trying to cram every department's requests into the initial requirements definition, causing scope to balloon; it isn't unusual for a project to end up costing nearly double the original estimate once every department's wish list gets folded in. Reviewing common failure patterns in system development beforehand makes it easier to keep scope narrow.

- Start with high-frequency features: announcements and document search should be top priority
- Decide operating rules first: clarify who updates information and who owns each approval step
- Inventory existing documents first: narrow down what needs migrating before fixing the development scope
- Design with future integrations in mind: if you may connect to attendance or HR systems later, flag that early

Intranet portal costs range from close to zero, using an existing groupware product, up to roughly ¥10 million for a full scratch build integrated with proprietary systems. The cost-effective approach is to first check whether existing products can meet your requirements, then custom-build only the gaps that remain. Because costs vary by requirements, get quotes from multiple vendors and compare before committing.