Website and web portal development cost calculator. Estimate by scope, not pages.
Choose the kind of site you are building and answer seven questions about its scope. You get a build cost range, a timeline and a line for every answer showing what it added. Below the estimator, the same ranges are broken down for customer, partner, employee and patient portals.
On this page
- 01On our team's pricing guide, a marketing site runs $1,500 to $3,500, a CMS-driven site $4,000 to $10,000 and a web application or portal $20,000 to $50,000 and up.
- 02Web portal development cost sits in that third band because sign-ins, roles and data each user owns change the build. Plan on 10 to 16 weeks.
- 03Scope moves the number more than page count. The seven questions place you inside your band and show what each answer added.
- 04These are planning ranges, not quotes. A fixed price comes after a short discovery, which starts with a call.
Estimate your build by scope.
Pick a band, then answer seven questions about what the site has to do. The result updates as you go and shows what each answer added. The dollar ranges come from our team's pricing guide, and the way they are combined is explained below the estimator.
Your estimate
$6,000 to $8,000
About 5 weeks
| answer | adds |
|---|---|
| Starting pointCMS-driven site, low end of the guide's range | $4,000 |
| Unique layoutsSeveral distinct templates | +$290 to +$570 |
| IntegrationsOne business system | +$290 to +$570 |
| Content model depthSome structured content | +$290 to +$570 |
| Design originNew pages on our brand | +$290 to +$570 |
| Migration and redirectsMoving a low traffic site | +$290 to +$570 |
| Accessibility and complianceWCAG target in the brief | +$290 to +$570 |
| Performance targetsCore Web Vitals, light site | +$290 to +$570 |
| Your range | $6,000 to $8,000 |
A planning range, not a quote. Figures are rounded, so the rows may not add up to the dollar.
Book a call to turn this into a scoped quoteWeb portal development cost, by type and complexity.
A web portal is a site people sign in to: customers checking orders, suppliers updating stock, staff finding a policy, patients booking a visit. The sign-in is what moves the price. Once a site has accounts it needs roles, permissions, records that belong to each person, and testing for every role, which is why the estimator puts every portal in its web application band.
Our team's pricing guide prices that band, its "custom web application or portal" row, at $20,000 to $50,000 and up, built over 10 to 16 weeks. The chart and the first table split the band by complexity using the estimator itself: set all seven answers to light, moderate or heavy, and this is what it returns.
the portal thirds are the estimator's result for all light, all moderate and all heavy answers
By complexity
| answers | what that portal looks like | build cost | timeline |
|---|---|---|---|
| All light | One kind of user, a few screens, email sign-in, nothing connected beyond forms and analytics, your existing design system. | $20,000 to $30,000 | 10 to 12 weeks |
| All moderate | Two or three roles, several distinct screens, one connected system such as your CRM or single sign-on, new screens on your brand. | $30,000 to $40,000 | 12 to 14 weeks |
| All heavy | Many roles with record-level permissions, most screens one of a kind, two or more connected systems, existing users to move in, and a legal or audit requirement. | $40,000 to $50,000+ | 14 to 16 weeks |
The plus on the heavy row comes from the guide, whose portal row has no ceiling. When a result reaches the top of the band, read $50,000 as a floor for that build, not a ceiling. Vendor guides that rank for this search put the top of the range several times higher, mostly for enterprise and patient portals, and that is the ground the plus covers.
By portal type
| portal | who signs in, and to do what | what usually drives the cost | plan from |
|---|---|---|---|
| Customer or client portal | Customers see their orders, invoices, bookings or tickets and update their own details. | The link to your CRM or billing system, and how many account states each screen has to handle. | Moderate row: $30,000 to $40,000 |
| Vendor or partner portal | Suppliers, resellers or agents work on shared records such as purchase orders, stock levels or deal registrations. | Permissions by company and by person, and two-way sync with an ERP or inventory system. | Moderate to heavy rows: $30,000 to $50,000+ |
| Employee intranet | Staff find people and policies, submit requests and see what applies to their team. | Sign-in through your company directory, and who may see which content by department. | Light to moderate rows: $20,000 to $40,000 |
| Patient portal | Patients book visits, fill in intake forms, message the practice and see their own information. | Protected health information: a business associate agreement, audit logging, access by role and compliant hosting. | Heavy row: $40,000 to $50,000+, with the top read as a floor |
The last column is where we would start planning each type, not an average we measured. Your own answers in the estimator replace it.
On a patient portal, HIPAA's Privacy Rule requires the provider to have a written business associate contract with any vendor that handles protected health information on its behalf (45 CFR 164.504(e)). We sign one whenever we handle PHI, and our healthcare builds run on AWS, Azure or Google Cloud under the provider's BAA. Writing into an EHR such as Epic is a separate integration project we do not build, as our healthcare software page explains.
How to answer the seven questions for a portal
The estimator's questions were written with websites in mind. On a portal each one asks about something slightly different:
| question | on a portal it asks about | answer heavy when |
|---|---|---|
| Unique layouts | Distinct screens: dashboards, lists, record pages, forms, settings and admin. | Each role gets its own screens, or most screens are one of a kind. |
| Integrations | Every system the portal reads from or writes to, including the identity provider behind single sign-on. | Two or more systems, or any two-way sync. |
| Content model depth | Roles and permissions: who can see and change which records. | Record-level permissions, approval chains or access split by company. |
| Design origin | Whether the screens reuse a design system you already own. | A new product design from scratch. |
| Migration and redirects | Accounts and records moved in from the system the portal replaces. | Users and their history must arrive intact, with old links redirected. |
| Accessibility and compliance | WCAG on every signed-in screen, plus rules such as HIPAA. | A legal or audit requirement, such as protected health information. |
| Performance targets | Dashboards, searches and reports staying fast as the data grows. | Large tables, heavy reports or live data. |
In the web application band each question adds $0 to $1,430 on a light answer, $1,430 to $2,860 on a moderate one and $2,860 to $4,290 on a heavy one. Equal weights are the estimator's stated assumption. On a real portal, integrations and permissions usually outweigh the other five, so if either runs heavy, plan around the top of your range.
Two requirements are worth settling before the first quote. If the portal holds anything sensitive, plan for multi-factor sign-in: NIST's digital identity guidelines (SP 800-63B) require two distinct factors at their two higher assurance levels. And WCAG, the W3C accessibility standard, applies to every signed-in screen, not only to the public pages.
A portal we built: Planivo
Planivo is a workforce planning platform for clinics and hospitals, and in 2026 we built all of it: the signed-in app and its public website. It holds monthly shift rosters and tasks. Vacation requests pass three levels of approval, with a check for clashes within a speciality.
Staff are reminded before a certification expires, training sessions record attendance, duty screens show who is on, and an audit history keeps every change. There are six roles, and no role can see beyond its own scope. In estimator terms, six roles and a three-level approval chain are a heavy answer on content model depth, and the audit history is the kind of requirement the compliance question asks about. We do not publish what it cost.
Who builds it, and in what order
Every portal needs the same skills, whoever supplies them: someone who owns the scope and makes decisions, a designer for each role's screens, front-end and back-end developers, and testing that signs in as every role and checks what each one can and cannot see.
Our own sequence is the one on our software development services page: a written scope within 48 hours of a call, two weeks of discovery before a fixed build price, then build sprints with a recorded demo at the end of the first, in repositories held in your name.
We do not break this estimate into hours per role, because the estimator places scope inside the guide's range rather than counting hours. The questions at the end of the page say where to get an hours view.
Build, buy or configure
Check what you already pay for before you fund a build. HubSpot's Service Hub offers a customer portal for support tickets, Salesforce Experience Cloud builds customer and partner portals on your Salesforce data, and Microsoft SharePoint is a common intranet for companies on Microsoft 365. If one of them does the job, configuring it costs less than building.
Build when the workflow is your own and those tools force a workaround, when the portal is part of what you sell, or when per-user licence fees climb past what a build would cost over a few years. A middle path also works: keep the CRM as the system of record and build only the portal on top of it, connected through an API integration.
What a portal costs to run
A portal costs money every month after launch: hosting and the database, the sign-in service, email delivery, monitoring and backups, security updates, and a budget for changes once people use it daily. Our pricing guide names these costs without a figure, so this page does not invent one. Ask every quote for a yearly running cost next to the build price, and see website maintenance services for what upkeep covers.
How the number is put together.
Where the ranges come from
Every dollar and week figure in the estimator comes from the web development pricing guide our team wrote for small businesses in the USA. The estimator uses three rows of its project table, one per band, and never goes outside them. The guide calls these planning ranges rather than fixed prices, and so do we.
| band | guide row used | build cost | timeline |
|---|---|---|---|
| Marketing site | Basic 3 to 5 page website | $1,500 to $3,500 | 2 to 3 weeks |
| CMS-driven site | 6 to 15 page business website | $4,000 to $10,000 | 4 to 6 weeks |
| Web application | Custom web application or portal | $20,000 to $50,000+ | 10 to 16 weeks |
Why the band comes first
Page count alone is a weak way to price a website. Twenty pages from one template cost less than five pages that each need their own design and logic, so the estimator starts from what the site has to do. A marketing site, a CMS-driven site and a web application are different products, not sizes of the same one.
The jump from the second band to the third is the one that surprises people, and it is not incremental. Authentication, roles, state and data ownership change the engineering, the testing and the ongoing cost together.
Each band uses one row of the guide: the marketing site uses the basic 3 to 5 page row, the CMS-driven site the 6 to 15 page row, and the web application the custom web application or portal row. A marketing site that runs past about five pages or templates belongs on the CMS-driven row. The layouts question positions you within the row; it does not move you to a bigger one.
How your answers move the range
Your band sets a low end and a high end. The seven questions share the gap between them equally, so each one controls a seventh of it. A light answer places that question in the bottom third of its share, a moderate answer in the middle third, and a heavy answer in the top third.
Add the seven shares to the band's low end and you have your range. The timeline is worked out the same way on the guide's week ranges, rounded to whole weeks.
With every answer on its middle option, a CMS-driven site comes out at $6,000 to $8,000 over about five weeks, which is the default result above. Equal weights are an assumption, and we would rather state it than hide it: in a real project integrations are the biggest silent multiplier, so if your integrations answer is heavy, plan around the high end.
What the estimate leaves out
- 01Running costs. Hosting, domain, maintenance, security and content updates are the cost of owning a site, and they are where a cheap build gets expensive. The guide lists them without a single figure, so this estimate does not invent one. Budget for the year, not the launch, and see website maintenance services.
- 02Copywriting. The estimate assumes your content is ready. Content is the most common reason projects slip: design and build finish, copy does not.
- 03Brand identity. If brand work is in scope it is a separate line, and it is worth it when the brand is the differentiator. See brand identity.
- 04Online stores. Products, payments, shipping and order management are priced differently. Use the ecommerce website cost guide instead.
- 05Custom software beyond a website. The software development cost calculator covers it, working from hours and a blended hourly rate, so its numbers will not match this page.
Before you plan around it, test three answers.
Change these in the estimator and watch the estimate move. They are the answers most worth questioning before a budget is set.
The band. Do not buy band three by accident. Plenty of "portals" are a well-structured CMS site plus an email. Test whether you truly need accounts before you pay for them: leaving the web application band moves the estimate further than any other single change in the estimator. If you do need them, the portal section shows where each kind of portal starts.
Unique layouts. Cut templates, not quality. Fewer, better layouts beat many mediocre ones, and they cost less to build and to maintain.
Integrations. Phase them. Launch with the one that earns money and add the rest once you know how people actually use the site.
Ten answers on website and portal cost.
How much does website development cost?
On our team's pricing guide, a basic 3 to 5 page site runs $1,500 to $3,500 over 2 to 3 weeks, a 6 to 15 page business site $4,000 to $10,000 over 4 to 6 weeks, and a custom web application or portal $20,000 to $50,000 and up over 10 to 16 weeks. What the site has to do moves the price more than its page count, which is why the estimator asks about scope.
How much does it cost to have someone develop a website?
It depends on who you hire as well as what you build. A freelancer usually quotes less and works alone, which suits a small site with a clear scope. An agency usually quotes more because design, development, testing and project management come from different people. Either way, our guide's bands start at $1,500 to $3,500 for a basic site and rise with pages, features and logins. Ask for an itemized quote so you compare the same scope.
Is $1000 a good price for a website?
For a template you set up and fill yourself, it can be. For a site built for you, $1,000 sits below the lowest band in our pricing guide, which starts at $1,500 for a basic 3 to 5 page site, so ask what is left out: custom design, content, SEO setup, testing or help after launch. A cheap site that has to be rebuilt within a year ends up costing more than a fair one.
Is web design still worth it in 2026?
Yes, when the site has a job to do. Searches, ads, social posts and referrals all end on a page, and that page decides whether a visitor calls, books or buys. What has changed is how much of it you need to pay for: a small business can often start with a well-built template, while anything with logins, payments or integrations still needs design and development work.
How long does a web portal take to build?
Our team's pricing guide gives 10 to 16 weeks for a custom web application or portal. In the estimator, all light answers come out at 10 to 12 weeks, all moderate at 12 to 14 and all heavy at 14 to 16. Content, decisions and access to the systems you connect usually set the pace more than coding does, so launch with the roles and the integration that matter most.
How much should I budget for portal maintenance each year?
Our pricing guide lists running costs without a figure, and we will not invent one here. Plan for hosting and the database, the sign-in service, email delivery, monitoring and backups, security updates and a budget for small changes. A portal people use every day tends to collect more change requests than a marketing site, so ask every quote to state a yearly figure next to the build price.
Should we build our own portal or configure one we already license?
Ready-made is usually cheaper to start, as long as it fits. A portal inside a tool you already license costs configuration and per-user fees rather than a build. Custom pays off when the workflow is your own, when the portal is part of what you sell, or when those fees grow past the build cost. Compare both over three years rather than one; the portal section names the usual ready-made options.
What does launching a portal in stages save?
It saves building screens and integrations nobody ends up using, and it is often the cheapest way to learn what the portal needs. Launch with one role, the screens that role uses every day and the one integration that pays for the build, then add roles and systems once you see how people use it. In the estimator, moving integrations or layouts from heavy to moderate shows roughly what a smaller first phase saves.
What hourly rate does the calculator assume?
None. It does not count hours. It positions your answers inside the ranges in our pricing guide. The software development cost calculator works the other way, from hours multiplied by a blended rate, so the two tools will not agree on the same website and are not meant to.
How accurate is this estimate?
It is a planning range, only as good as your answers. It places your scope inside our pricing guide's ranges without scoping the project, and it weights seven questions equally where a real build does not. For a firm quote, bring your band, a rough count of templates or screens, the systems to connect and who writes the content: usually enough for a range in one call and a fixed price after a short discovery. Book a call.
Last reviewed .
Turn the range into a fixed number.
The estimate above is a planning range. Bring it, your seven answers and, for a portal, the roles and systems it involves to a call with a developer, and leave with a scoped next step.
Why work with Digital Heroes
115 people in New York, Delhi, Lucknow, London and Sydney, shipping ecommerce, web, software and mobile work for founder-led brands. Senior engineers only, no account-manager relay, and the same team from kickoff to launch.
- Shopify Select Partner, as listed in the Shopify Partner Directory
- Tier 1 registered supplier on the United Nations Global Marketplace, which requires audited company documentation
- Top Rated Plus on Upwork, the bracket for the top 3% of talent by client outcomes
- 397 public five-star-weighted reviews across four Fiverr gigs, from clients in 36 countries
- DUNS verified business, No. 650878346, so procurement can check us before signing
- Listed by Clutch in Top 1000 Global B2B Companies and Top Web Designers 2024
- Verified profiles on GoodFirms, DesignRush, Digital.com, AppFutura and TopDevelopers
- 2,000+ brands built across 40+ countries, with $50M+ in client revenue scaled
Published · Last updated .