How do I build an internal portal without replacing all our current tools?

You can build an internal portal as a layer on top of your existing tools, not a replacement. The key is to make the portal the front door for employees while your current systems remain the systems of record.

Start with the right goal

Don’t try to recreate every workflow. Instead, focus on:

• Finding information quickly
• Routing people to the right tool
• Surfacing key tasks, links, and status in one place
• Reducing duplicate logins and hunting across systems

A practical approach

1) Define the portal’s jobs

Common portal jobs:

• Company announcements
• HR/self-service links
• Onboarding checklist
• IT support/help desk
• Project dashboards
• Forms and approvals
• Knowledge base/search
• Role-based shortcuts

Ask:

• What do employees do repeatedly?
• What do they forget where to find?
• What causes the most “where do I go for this?” questions?

2) Pick a portal style

There are a few models:

A. Link hub

• Simple homepage with links, widgets, search, and announcements
• Fastest to launch
• Best if you mainly need consolidation

B. Aggregation portal

• Pulls data from existing systems via APIs
• Shows status, tasks, notifications, and summaries
• Best for a better user experience without replacing tools

C. Workflow portal

• Lets users start requests, see progress, and complete lightweight tasks
• Integrates with existing systems for the real work
• Best when you want some process improvement

Most companies start with A, then move into B and C.

3) Integrate, don’t migrate

Keep your current tools and connect them through:

• Single sign-on (SSO): one login, many tools
• APIs: bring in data like tickets, PTO balance, project status
• Embedded views: dashboards, reports, calendars, docs
• Deep links: launch users directly into the right page
• Search federation: search across multiple systems from one place

4) Design around roles

A great portal changes based on who’s logged in:

• All employees: announcements, policies, search, support
• Managers: approvals, team status, reports
• HR: onboarding, policy updates, forms
• IT: system status, tickets, assets
• Sales/Operations/Finance: role-specific dashboards

This avoids clutter and makes the portal actually useful.

5) Use the portal as a navigator

Think of it as:

• A dashboard for awareness
• A launcher for actions
• A search layer for discovery

It should tell users:

• What’s new
• What needs attention
• Where to go next

But the portal should not own every process if your current tools already do that well.

A good architecture

A common internal portal architecture looks like this:

• Frontend portal UI
• Identity provider for SSO and role-based access
• Integration layer / API gateway
• Connectors to HR, ITSM, CRM, docs, BI, calendar, etc.
• Search index for federated search
• Content management for announcements, static pages, policies
• Analytics to track usage and improve the portal

Build vs buy

You have three main options:

Buy

Use a platform like:

• SharePoint / Viva
• ServiceNow Employee Center
• Confluence + plugins
• Liferay
• Zendesk/IT portals
• Customizable intranet platforms

Best if you want speed and standard features.

Low-code

Use:

• Power Apps / Power Pages
• Retool
• AppSheet
• OutSystems

Best if you need faster customization with less engineering.

Custom

Build your own portal with:

• React/Next.js or similar frontend
• Backend integration services
• SSO and API connectors
• Search and analytics

Best if you need strong UX, unique workflows, or many custom integrations.

What not to do

Avoid these common mistakes:

• Trying to rebuild every existing app inside the portal
• Creating a portal that’s just a link dump
• Ignoring search
• Making it the same for everyone
• Skipping SSO
• Launching without ownership/content maintenance

Suggested rollout plan

Phase 1: MVP

• SSO
• News/announcements
• Search
• Top links by department
• HR/IT support entry points

Phase 2: Data aggregation

• Ticket status
• PTO balance
• Team dashboards
• Approval notifications
• Calendar and directory integration

Phase 3: Workflow enhancement

• Simple requests and forms
• Guided onboarding
• Personalized dashboards
• Automated reminders

Success metrics

Measure:

• Portal adoption
• Search success rate
• Reduced help desk questions
• Time to find key info
• Completion rates for common tasks
• Repeat visits by role

Rule of thumb

If a tool already works well, surface it. If users need to know about it, show it. If users need to act on it, link or embed it. If many people repeatedly do the same thing, integrate the workflow.

If you want, I can also help you with:

1. a portal architecture diagram,
2. a buy vs build decision framework, or
3. a 90-day implementation plan.