Corporate Portal Development

As a company grows, internal information spreads across email, chats, spreadsheets and folders. A new employee does not know whom to ask, requests get lost in threads, and HR and IT spend time answering the same questions. A corporate portal brings everything into one place: employees sign in with their account and see their requests, documents, colleagues’ contacts and company news.

A portal is useful when:

• requests to IT, accounting and facilities go through email and messengers and their status is unclear;
• new employees take long to settle in: they do not know the company structure, rules and where things are;
• HR processes are manual: vacancies, offers, first days and access rights are agreed in threads;
• managers lack the big picture: how many requests there are, where the delays are, how departments perform.

IntraLink is a corporate portal we built. It includes:

• personal accounts: each employee has their own space with important information and ways to interact with colleagues;
• an IT support system: built-in requests help to resolve technical issues quickly;
• an interactive office map and org chart: employees find the right contacts and find their way around the company;
• HR management: creating vacancies, sending offers, notifications about new employees;
• integration with corporate channels: new employees are added to work groups and chats automatically;
• analytics: data on requests and employee activity for management.

The portal’s mobile version gives employees HR features and requests right on their phone. Screenshots and details are in the projects block below.

We choose the portal’s modules for the company’s tasks. Most often they are:

• employee personal accounts with a profile, requests and documents;
• requests and approvals: IT, accounting, facilities, passes, holidays;
• org chart and staff directory with search by name, position and department;
• office map: where a colleague sits, meeting rooms, zones;
• news and knowledge base: policies, instructions, answers to common questions;
• HR processes: vacancies, offers, onboarding, hiring documents;
• notifications in the portal, by email, in messengers and as push notifications;
• analytics for managers.

You do not have to start with every module. Usually the first version solves the most painful problem, for example requests and the org chart, and the rest is added in iterations.

Ready-made corporate portal products have existed for a long time and cover standard scenarios well. Custom development is justified when:

• processes are non-standard and have to be bent to the product’s logic;
• deep integration with your systems is needed, not a set of ready connectors;
• per-employee licences cost more than owning your own solution as the company grows;
• data must stay within your perimeter and on your servers;
• you need your own interface and a mobile app in your brand style.

We do not push you to build everything from scratch: if a ready system solves the task, we will say so in the consultation.

A technically finished portal is not yet a working one. Portals usually fail not because of the code but because of the launch. So we plan the rollout together with you:

• content before launch: the org chart, contacts, policies and answers to common questions must be on the portal on day one, or employees go back to email;
• single sign-on: employees sign in with their corporate account, without separate passwords;
• section owners: news, the knowledge base and the HR section have owners who keep them up to date;
• a pilot in one department: we collect feedback and refine the portal before the company-wide launch;
• moving processes to the portal: requests that used to go by email are accepted only through the portal;
• usage analytics: you see which sections are in demand and which need improvement.

• Faster onboarding: the company structure, rules and contacts are in one place.
• Transparent requests: every request has an owner, a status and a history, and nothing gets lost in threads.
• Fewer repeated questions to HR and IT: the answers are in the knowledge base.
• Visibility for managers: data on requests and department workload without manual reports.
• Single employee data: the portal is connected to HR and accounting systems instead of being maintained separately.

The portal works together with what the company already has:

• sign-in with the corporate account, so employees do not need a separate password;
• email and calendars: notifications, invitations, reminders;
• messengers and work chats: notifications and automatic addition to groups;
• HR and accounting systems: data on employees, departments and positions;
• request and service desk systems, if they are already in use.

We build data exchange to be reliable, with logging, retries and monitoring. See the API integration page for details.

Many employees spend the day away from a computer: on the road, in a warehouse, on site, on the shop floor. For them the portal has to be on their phone. We build a Flutter mobile app for iOS and Android that works with the same back end as the web version:

• push notifications about request statuses, approvals and news;
• quick actions: create a request, approve a document, find a colleague’s contact;
• HR features: applications, documents, information for newcomers.

This is how IntraLink works: HR features and requests are available to employees in the mobile app.

A portal holds employees’ personal data and internal documents, so we:

• deploy it on your servers or in the cloud of your choice, and data stays within your perimeter;
• control access by roles, departments and clearance levels;
• keep an audit log of actions with important data;
• set up backups and check recovery;
• design personal data storage to meet legal requirements and your security team’s rules.

1. Discovery (1–2 weeks): processes, roles, systems, module priorities.
2. Requirements and design mockups: the portal and mobile app interfaces.
3. Technical specification: modules, roles, integrations, security requirements.
4. Development in two-week iterations with a demo after each.
5. Testing and a pilot launch in one department.
6. Company-wide launch and support.

A full portal with web and mobile versions takes 5–7 months; the first modules can launch earlier.

A portal with web and mobile versions, requests, an org chart, HR processes and integrations starts at ₽8M. The total depends on the number of modules and roles, integrations and security requirements. We write routine code and tests with AI tools, so timelines and costs are lower than with fully manual development.

• Experience with portals: we built the IntraLink portal with web and mobile versions.
• One team: web, mobile app, integrations and launch.
• A report and a demo every two weeks.
• 6-month warranty on our work.

Tell us about your company and the portal’s tasks in the form below, and we will suggest the first version and an estimate of time and cost.