Web Application Development Cost (2026): Portals, Dashboards and Internal Tools

Web application development typically costs $8,750 to $48,000 for a simple internal dashboard and $26,000 to $156,000 for a customer or partner portal at Eastern European rates, while large multi-tenant platforms run to $480,000 or more. A US onshore team charges roughly twice those amounts for the same hours.

We build web apps and portals for universities, B2B companies and SaaS products, mostly on .NET with React, Angular or Vue. This guide sizes a web application the way we would before quoting it. The ranges are planning ranges at market rates, not a quote and not our price list. If you are budgeting a broader system such as an ERP or a mobile app, start with our custom software development cost guide; this one focuses on browser-based apps: portals, dashboards and internal tools.

Cost at a glance

Each row multiplies an effort range by two rate bands: about $35 to $80 per hour for Eastern Europe and $80 to $160 per hour for US onshore teams.

Calendar time assumes two to four engineers with about 30 productive hours each per week. Large platforms usually ship in stages, so the first release can go live well before the full scope is done.

Web apps for specific business functions have their own guides: custom CRM development cost, custom ERP development cost and SaaS development cost. If you want AI features inside the portal, see AI development cost.

What drives the cost

Screens are the visible part of a web app, but they are rarely what makes one expensive. These are the drivers that move a project from one row of the table to the next.

1. Audiences and permissions. A portal for one type of user is simple. A portal where customers, partners, staff and admins each see different data needs access rules on every screen and every API endpoint, plus tests for each role. Content targeting, where editors decide who sees what, adds more.

2. Authentication and SSO. Email and password login is a solved problem. Single sign-on with Entra ID, Okta, Google or a university identity provider takes extra work for configuration, user provisioning and testing across environments, and it often comes with per-user fees from the identity provider.

3. Integrations. Most portals exist to show data that lives somewhere else: an ERP, a CRM, a billing system, a student information system. Each source needs mapping, error handling, caching and monitoring. This is usually the largest and least predictable line in a portal estimate.

4. Real-time features. Live dashboards, kanban boards that update for everyone at once, chat and notifications need WebSockets or SignalR, connection handling and careful testing under load.

5. Multi-tenancy. If several customer organizations share one app, every query must be scoped to a tenant, and you need tenant onboarding, configuration and admin. Retrofitting this later costs much more than designing it in.

6. Frontend framework. React, Angular and Vue all build good web apps, and the choice rarely changes the budget by much. What matters is that the people who will maintain the app know it. Picking a framework nobody on your side can support is a cost that arrives after launch. Server-rendered pages with a light layer of JavaScript can also be enough for simple internal tools, while a single-page app pays off when users spend hours a day in the interface and expect it to feel instant.

7. Performance, accessibility and content. High traffic, WCAG accessibility targets and editor-managed content through a CMS each add design, development and test time that is easy to leave out of an early estimate.

Pick the modules your app needs and the rate band you are comparing to see a range for your own scope.

Cost by component

These are the same modules as in the estimator, priced at both rate bands, so you can compare a vendor proposal line by line.

The preselected scope, a standard customer portal with one integration, adds up to 770 to 1,940 hours. That is about $26,950 to $155,200 at Eastern European rates and $61,600 to $310,400 at US onshore rates, in line with the portal row above.

Ways to lower the cost without cutting quality

Most of the savings in a web app budget come from scope and reuse decisions made before development starts, not from a lower hourly rate.

Reuse what you already run. If you already have a CMS, an identity provider or a cloud account, build on them. A portal that shares a back end, hosting and editor workflow with your public site avoids a second system to pay for and maintain every year.

Use proven components for commodity features. Calendars, data grids, charts, rich text editors and form libraries are mature. Paying engineers to rebuild them rarely adds value. Spend custom hours on the workflows that make your portal different.

Start with one audience. If customers, partners and staff all need the portal, launch for the group with the clearest need and add the others in later releases. Each audience brings its own permissions, screens and tests.

Integrate in stages. Read-only views of data from your ERP or CRM are much cheaper than two-way sync. Show the data first, then add write-back where users actually need it.

Let admins configure instead of developers coding. A form builder, editable email templates or content targeting set by editors cost more up front, but they save repeated developer time for every change after launch. That trade pays off when the business changes often.

Choose real-time only where it matters. A status board that several people watch at once benefits from live updates. A monthly report does not. Refreshing on page load is free; WebSocket infrastructure is not.

Keep the framework boring. Pick React, Angular or Vue based on who will maintain the app. Exotic choices raise hiring and onboarding costs for years.

Rates in brief

2026 outsourcing rate surveys put Eastern Europe at about $35 to $80 per hour and North America at $80 to $180 or more; 2025 rate surveys estimate offshore hiring at 40-70% cheaper than an equivalent hire in the US or Western Europe. For an in-house comparison, the US Bureau of Labor Statistics reports a May 2025 median wage of $92,650 a year for web developers, before benefits, equipment and management. Our custom software development cost guide covers rates by region and engagement models in more detail.

Running costs after launch

• Maintenance. A common industry rule of thumb puts yearly maintenance at roughly 15-20% of the original build cost. It covers bug fixes, security patches, framework updates and small changes. Frontend frameworks move fast, so budget for regular dependency updates rather than one big upgrade every few years.
• Hosting. App servers, database, file storage, CDN, backups and monitoring. Cost scales with users, traffic and uptime targets. If you might change cloud provider later, our write-up on migrating from Azure to AWS with zero downtime shows what a move involves.
• Per-user services. Identity providers for SSO, email delivery, maps and analytics are often priced per active user or per message, which matters most for external portals with many users.

How to get an accurate estimate

1. List your audiences. Customers, partners, staff, admins: for each, what they must see and do.
2. Sketch the main screens. Even rough wireframes of the five to ten most important screens make an estimate far more reliable.
3. Name every data source. For each system the app reads from or writes to, note whether it has an API and who controls it.
4. Decide on login. Email and password, social login, or SSO with your corporate or institutional identity provider.
5. Mark what must be live. Real-time updates are worth paying for on boards and status screens, not everywhere.
6. Ask for hours per module. Compare proposals line by line, and keep 15-25% contingency for unknowns.
7. Run a short discovery phase. A written specification turns the range into a quote you can sign.

From our work

The Ben-Gurion University portal is a good example of what drives portal cost. It is a login-only portal where each student or staff member sees their own schedule, grades, payments and news. Editors can target any content item by 8 criteria, the Angular app pulls data from more than ten university APIs, and Moodle opens through single sign-on. To keep running costs down, it reuses the public site’s Umbraco back end and AWS setup instead of adding a second CMS and infrastructure.

The support system we built joins a customer request portal with an internal kanban board, calendar scheduling and a form builder, all updated in real time. Customers submit and track requests in the portal, and the same requests appear as cards on the team’s board. It runs on .NET Core and Vue.js with a JWT-secured REST API, and the form builder made form creation 80% faster because staff no longer need a developer to add a form.

Some portals are never finished, because the business keeps adding modules. For HS High Stake, 7 OSKI developers worked over the project on a large .NET and Umbraco business portal that links a German division with its dealers and employees, with work continuing for more than 18 months at review time. That is where a dedicated team usually costs less than a series of fixed-price projects.

Where OSKI fits

OSKI Solutions builds web applications and portals and broader custom software on .NET with React, Angular and Vue. We deliver defined scopes at a fixed price, provide dedicated teams for portals that keep growing, and look after live apps through maintenance and support. Send us your audiences, screens and data sources, and we will turn them into a written estimate with hours per module.