Start with your existing workplace and HR tools if employees mainly need policies, documents, common forms and links to services. Consider a custom employee portal when a recurring task crosses several systems, the existing tools cannot support it well, and the business can fund the build and ongoing ownership.
TL;DR
- Use existing workplace or HR tools first when staff mainly need policies, documents, routine requests and links.
- Microsoft 365 Business Basic lists $7 per user each month on an annual subscription: $8,400 a year for 100 new licenses.
- If all 100 users need Power Apps Premium, its listed price adds $24,000 a year; the workflow determines which licenses are needed.
- One supplier lists $7,200 and 2–4 weeks for a basic SharePoint setup; another estimates $15,000–$30,000 and 6–10 weeks for a basic custom portal.
- In the three-year example, configuring existing tools costs $21,600 versus $61,000 for a custom portal, before shared licenses and other exclusions.
- At an assumed $50 per hour, the custom option must release about 22 extra staff hours each month to match that example's cost difference over three years.
- Start with one request and approval journey, then test permissions, accessibility, integrations and staff adoption before expanding.
The useful question is whether staff can finish a task, not whether the company has one more homepage. A portal that receives a request, shows its status and routes it to the right owner can help. A page of links to the same confusing process may not.
Which option fits the work?
Use the system that already owns the task where it works. An HR platform can remain the place for payroll or leave; a SharePoint intranet can make approved policies and team information easier to find. A low-code tool can connect a small number of requests when its permissions and integrations meet the need. Build custom software only when those routes leave an important workflow unresolved.

| Option | Choose it for | Check before buying |
|---|---|---|
| Existing workspace or intranet | Policies, news, documents, a directory and links to established services. | Search, content owners, permissions and the licenses your staff already have. |
| HR system’s employee portal | Standard HR tasks already supported by the selected product. | Which tasks, user roles and integrations are included in your plan. |
| Low-code portal | A bounded request or approval flow that can use supported connectors. | Per-user or connector charges, access controls, exports and who maintains it. |
| Custom portal | Several valuable workflows that need a tailored shared experience across systems. | Build cost, data ownership, security, integration support and an operating team. |
For a single problem, a focused internal tool can be simpler than a portal. For example, improve the existing IT request form before building a company-wide hub if employees have no trouble finding their other services.
If the real need is to replace a core business system, compare the broader enterprise application options before treating an employee-facing portal as the whole solution.
What does an employee portal cost?
For a company that needs new licenses, Microsoft lists Business Basic at $7 per user per month, paid yearly, in its US pricing checked November 14, 2026. The plan includes SharePoint along with other services. For 100 newly licensed people, the listed charge is $8,400 for 12 months, before taxes and implementation. If those people already have a suitable license, do not count the entire subscription again as a new portal cost. Additional products, connectors or usage can require separate licenses; check the Power Apps licensing guidance for the proposed workflow.
For example, Power Apps Premium is listed at $20 per user per month, paid yearly. If all 100 employees needed that license, it would add $24,000 a year before taxes and implementation. Not every workflow or user needs that plan; confirm the entitlement for the actual app and its connectors.
For setup, Congruent Software lists a $7,200 SharePoint Quick Start lasting two to four weeks. Its stated scope includes a site, document libraries, basic forms and workflows, permissions, and administrator training. Check whether that scope covers your request journey and what support continues after handover.
For a custom build, Monocubed’s published estimate gives $15,000–$30,000 and six to ten weeks for a basic portal with authentication, a dashboard, leave management, documents and basic reporting. The same supplier estimates $30,000–$60,000 and three to five months for a more involved portal with role-based access, workflow automation, payroll integration and onboarding. These are one supplier’s US dollar planning ranges, not a survey, Hapy quote or promise for your scope. Integration access, permissions and testing can change both cost and time.
A three-year comparison for 100 employees
Assume the company already has suitable Microsoft licenses and wants the same policy directory and one request-and-approval journey from either option. The setup comparison uses Congruent’s published Quick Start price and a hypothetical $25,000 custom build; neither is a quote for this exact scope. The custom assumption sits within Monocubed’s basic range, but does not establish that the supplier would deliver this scope for that amount. Both budgets cover 36 months of operation after launch and exclude the time before each option is ready.
| Cost over 36 months | Configure existing tools | Custom portal |
|---|---|---|
| One-time setup or build | $7,200 | $25,000 |
| Assumed monthly operation and support | $400 × 36 = $14,400 | $1,000 × 36 = $36,000 |
| Three-year total | $21,600 | $61,000 |
The custom option costs $39,400 more in this example. At an assumed $50 per staff hour, it would need to release about 22 additional hours a month for 36 months to match that difference: $39,400 ÷ $50 ÷ 36 is 21.9 hours. This is the value of available staff capacity, not cash saved unless spending actually falls.
Licensing can reverse that result. If the configured option needed Power Apps Premium for all 100 people at the listed price, and the custom option did not, the extra $72,000 over three years would bring the configured example to $93,600. That condition must be checked for the real system; it is not included in the first comparison.
Both options exclude the shared Microsoft licenses, taxes, major scope changes and any extra integration license. The example also excludes the time value of money and assumes the same useful outcome and stable monthly costs. If you need new Microsoft licenses for both options, add their cost to both. If only one option needs them, add them to that option. Change the inputs when your actual scope or support terms differ.
What should the first release do?
Choose one high-friction request that crosses teams, such as equipment for a new employee. The first release can let a manager submit the request, show its status, route approval to the right owner and notify IT when the decision is complete. Keep HR and purchasing records in their existing systems unless there is a reason to move them.
The same approach applies to business process automation: identify the handoff and its owner before choosing a tool.
Test the journey with a small group of staff and the people who receive the requests. Measure completed requests, time waiting for an owner, errors and the number of requests that return to email. Compare those observations with the old process before adding a second workflow. A shorter completion time is useful evidence of capacity, but it does not by itself prove a reduction in payroll spending.
Who protects and operates the portal?
Give each person only the access needed for the job. Test whether a manager can see their own requests without seeing unrelated employee records, and whether access ends when a person leaves. Assign owners for identity, changes, integration failures, backups and support. For sensitive records, agree how audit events, exports and incident response will work before launch.
Use the NIST Secure Software Development Framework to discuss development practices with a supplier. Test the actual interface with a keyboard and relevant assistive technology; the Web Content Accessibility Guidelines describe requirements for accessible web content. A vendor’s feature list does not prove that your configured portal meets either need.
Choose an existing platform when it can deliver the workflow with acceptable ownership and cost. Fund a custom layer when the tested gap is valuable enough to justify the extra build and operating work. Hapy provides business systems and automation services, so we have a commercial interest in that decision. Compare our scope and evidence with the same criteria you use for other options.



