Direct answer
KBR Global does not publish one universal website price. A starter site, lead-generation site, ecommerce store, and portal are different scopes; after a short brief, KBR gives a fixed price before work starts. Budget discovery, build, launch, and ongoing maintenance separately.
KBR prices a website after a short brief defines what it must do. Compare a starter site, lead-generation site, ecommerce store, and portal as different scopes, then budget discovery, build, launch, and ongoing maintenance separately.
Four common website scopes
Page count alone cannot price a website. Start by naming the job the system must complete and the operational risk it must carry.
| Scope | Typical job | Main cost drivers |
|---|---|---|
| Starter website | Establish a credible presence for a small business with approved content and a focused enquiry path. | Content readiness, page set, brand adaptation, forms, analytics, accessibility, and launch checks. |
| Lead-generation website | Turn search, campaigns, or referrals into qualified enquiries across several decision pages. | Research, positioning, copy, conversion journeys, CRM or email routing, proof, measurement, and iteration. |
| Ecommerce store | Sell products with reliable catalogue, payment, fulfilment, policy, and support flows. | Catalogue size, platform, payments, tax, shipping, accounts, integrations, migration, QA, and ongoing operations. |
| Portal or custom platform | Support authenticated users, data, permissions, workflows, or bespoke business logic. | Discovery, architecture, integrations, security, data migration, roles, testing depth, documentation, and support. |
What drives website pricing
Two sites with the same page count can require very different work. A brochure site using approved content is not comparable to a multilingual platform with original design, migrations, CRM logic, and regulated data.
- Business job: A credibility site, lead engine, store, portal, and web application require different systems and assurance.
- Content readiness: Research, messaging, copy, photography, localization, and approvals can be larger workstreams than page assembly.
- Design depth: A tailored visual system, motion, responsive states, and accessibility testing increase both value and production effort.
- Technical scope: Commerce, authentication, search, payments, CRM, analytics, and legacy migration introduce dependencies and testing.
- Ownership: Hosting, monitoring, security updates, content operations, measurement, and iteration continue after launch.
How to estimate website scope
KBR converts a short brief into a defined scope and fixed price before work starts. A comparable estimate must state the included website type, assumptions, exclusions, approval rounds, launch responsibilities, and ongoing costs.
- Write the measurable business outcome and primary audience.
- List required page types, content states, languages, integrations, and permissions.
- Separate must-have launch scope from later releases.
- Ask each supplier to state assumptions, exclusions, review rounds, testing, and ongoing costs.
- Compare estimates against the same brief and risk allocation.
Separate the budget into four buckets
A comparable proposal shows where the money and responsibility sit across the whole lifecycle, not only the coding phase.
- Discovery: Research, requirements, content inventory, technical constraints, solution shape, assumptions, and acceptance criteria.
- Build: Content, design system, responsive states, development, integrations, migration, accessibility, performance, and QA.
- Launch: Production setup, redirects, analytics, final content checks, rollback plan, monitoring, and post-launch verification.
- Maintenance: Hosting, security, updates, support, content operations, measurement, optimisation, and future releases.
Hidden costs in website work
The cheapest proposal is often cheap because a necessary activity is missing, deferred, or assigned to the buyer. The most expensive proposal is not automatically the strongest either; trace every line item to an outcome or risk.
- Comparing totals before normalizing scope.
- Treating content and migration as free.
- Ignoring accessibility, performance, analytics, and post-launch ownership.
- Accepting a fixed price built on undefined requirements.
- Buying features before validating the user journey.
Record the how much does a website cost decision
A useful record for how much does a website cost should preserve the decision, not just the final deliverable.
- Outcome: Understand the variables behind an estimate and create a brief that suppliers can price consistently.
- Evidence: Review business job, content readiness, design depth before approval.
- Boundary: Do not accept “Comparing totals before normalizing scope.” as a shortcut.
- Owner: Assign one person to approve inputs, trade-offs and the next review for how much does a website cost.
- Acceptance: Record how the team will verify ownership in the released result.
Related decisions and next steps
Turn the decision into a clear brief
A strong website estimate should make trade-offs visible before work begins. The brief should let the team remove, defer, or deepen scope without losing sight of the business outcome.
Send a short website brief with the goal, required pages, content state and integrations. KBR will return a defined scope and fixed price before work starts.
Sources and further reading
- Web Content Accessibility Guidelines 2.2 — W3C
- Web Vitals — web.dev
- OWASP Top 10 — OWASP Foundation
- Responsive design — MDN Web Docs