What a Custom Website Starting at $5,000 Includes

Why $5,000 is a range entry, not a promise

Two websites with thirty URLs can be completely different projects. One may contain static marketing pages and a simple form. The other may include products, customer accounts, checkout, a CRM, consented analytics, localization, search, and years of redirect history. Page count is useful, but templates, integrations, data, risk, and acceptance work usually matter more.

PandaCodeGen uses the Scale range for larger migrations, commerce frontends, custom lead journeys, and integration-heavy builds. A project can move below or above a planning tier after discovery. We document the reason before onboarding so a buyer can compare the actual work, not just the headline. The tiers themselves sit on our pricing page, and our website cost guide explains which scope inputs move a project between them.

How many pages does $5,000 get you?

Before you compare any quote against this figure, count your templates rather than your pages: home, a service layout, a listing, a detail page, an article, contact. Six templates and a content model will carry almost any number of pages. If a vendor is quoting you by page count, they are either pricing bespoke design for every page, which is expensive and usually unnecessary, or they are about to build you six templates and charge by URL.

"The Scale tier is a planning range, not a fixed package. The signed statement of work decides what you actually get.

What a Scale build normally contains

Taking the question at face value first, because it is a fair one to ask before reading a contract. A Scale project normally means a custom Next.js front end, a content system your team can actually edit without a developer, a full URL inventory with page-by-page redirect decisions so existing search traffic survives the move, a staged launch rather than a flip of the switch, and the repository handed over to you at the end. Where paid advertising is in scope, it also means server-side conversion tracking rather than a browser tag alone. Hosting for this kind of site typically sits on usage-based infrastructure rather than a fixed monthly platform fee, so what you pay tracks what you use.

The reason the rest of this article is careful rather than a package list is that two projects with the same headline scope routinely need different work, and a buyer who signs a list instead of a scope finds that out late. So the detail below is what belongs in the written scope, and none of it should be assumed until it is in there:

• ✓
  A Next.js frontend plus an agreed way to edit content, naming the content types, who can do what, how preview works and how things get published.
• ✓
  A dated inventory of URLs, templates, metadata, canonicals, structured data, media, internal links, and important search queries.
• ✓
  A page-level keep, replace, redirect, or retire decision for existing URLs, plus rendered-output and redirect-chain checks.
• ✓
  Forms, email, CRM, calendar, commerce, search, analytics, consent, and advertising integrations listed individually.
• ✓
  Server-side conversion tracking where paid advertising is in scope, with the specific events, the consent handling, and the verification method named rather than assumed.
• ✓
  Responsive implementation for the agreed mobile and desktop layouts and current browser support matrix.
• ✓
  Accessibility checks against the standard and conformance target named in the SOW, with exclusions and remediation defined.
• ✓
  Security controls appropriate to the data and workflows, including validation, authorization, secrets, abuse controls, logging, and dependency review.
• ✓
  A staged launch plan with DNS, cache, data freeze, monitoring, rollback, and responsibility assignments.
• ✓
  Documentation, training, credentials, account handover, and a repository transition where agreed.

Our custom engineering service page describes how that work is organized. Where the project starts on an existing platform, our WordPress migration service and our migration cost assessment cover the URL and redirect work in the list above. Commerce scope is described on our ecommerce engineering page.

Conversion tracking is worth naming separately because it is one of the items buyers most often assume is included. Browser-side tags and server-side event forwarding are different pieces of work with different failure modes, and how much of the customer journey you want measured is its own scope driver. A single purchase or inquiry event is a smaller build than a set covering content views, cart, checkout start and pipeline stages, each one implemented, consent-aware and verified. Decide how much of that funnel matters before the scope is written rather than after launch. What the server-side work involves is set out in our guide to Meta Conversions API setup.

The part that is easy to miss when comparing quotes

Most of what is above, another competent team can also deliver. The difference worth asking any provider about is what happens after the tracking is switched on. Plenty of setups hand you a dashboard and end the engagement there, and a dashboard nobody can interpret is just another bill. Because we build the conversion tracking rather than reselling a tool, we can sit with the data afterwards and say which campaigns are worth more budget, which are quietly spending it, and where the measurement itself is unreliable enough that you should not act on it yet.

That is a service description rather than a promised outcome. Nobody can tell you in advance what your ads will do. But when you compare two quotes, it is worth asking each provider who reads the numbers with you once the build is finished, and what happens when the numbers disagree with each other. The mechanics of that work are in our guide to diagnosing a broken ad-tracking path.

What the price does not automatically include

At $5,000 the exclusions matter as much as the inclusions, and a clear quote lists both. Without them, two people can sign the same price while imagining different projects. Typical items that need an explicit decision include original copywriting, brand identity, product photography, large data cleanup, paid third-party tools, multilingual content, legal review, complex customer accounts, custom ERP work, ongoing SEO, campaign management, and content entry beyond the agreed inventory.

Extra pages and small feature changes are not a problem when discussed. Minor agreed tweaks may fit inside the project or included support. Material additions receive a written estimate and require approval. The parties can agree fixed-price, hourly, weekly, or another structure for that added work. If the brief is a rebuild of an existing site rather than a new one, our rebuild cost assessment and redesign cost breakdown list the items that most often turn up as exclusions.

How the 90+ performance target works

PandaCodeGen can include a 90 or higher Lighthouse performance acceptance target for the representative pages and environments named in the accepted terms. The test should specify mobile and desktop profiles, tool and browser version, consent state, authentication state, geography or runner, and any third-party conditions.

Our normal acceptance method uses three passing runs for every agreed page and profile. Testing only the homepage is not enough when another template carries the business risk. A site may use lazy loading, but that does not make its other routes irrelevant. Product, article, landing, checkout, or application templates should be represented when they are in scope.

Lighthouse is a controlled delivery measurement. It does not guarantee field Core Web Vitals, rankings, traffic, conversions, or revenue. The SOW states the remedy if an agreed acceptance test is not met. Our explainer on Core Web Vitals covers the field measurement that sits alongside it, and our guide to speeding up a website describes the engineering behind the score.

Payment, refund, and change control

A common PandaCodeGen payment option is 30% at onboarding and 70% at the delivery milestone defined in the accepted terms. A project can use another written schedule when both parties agree. Currency, taxes, invoice dates, approvals, pause rights, cancellation, and delivery conditions should be stated before work begins.

Where the accepted terms include scope protection, a client can be refunded the fees paid under that scope when PandaCodeGen fails to deliver what was signed, following the agreement's acceptance and remedy process. Because payment is normally 30% at onboarding and 70% at the delivery milestone, the practical effect is that your exposure is capped at the deposit and you do not pay the balance for work you have not accepted. It is not an unconditional change-of-mind promise. Cancellation after substantial or near-complete work, exceptional personal circumstances, and any partial refund are handled under the signed contract and the parties' written decision.

An approved refund is normally sent by PandaCodeGen within two or three business days, while the public policy allows up to 10 to 12 business days for processing and banking delays. The signed terms must say which clock controls, what happens to work in progress, and which amounts are refundable.

Support after launch

Package discussions start with 15 business days of included support for Starter and 30 business days for Growth and Scale. The accepted terms define the start event, usually the production launch or another named handoff event, and the exact coverage.

Included support should cover defects in signed deliverables and the minor agreed adjustments described in the SOW. New features, extra pages, new integrations, client changes, and third-party platform changes are separately scoped unless the agreement says otherwise. Custom engagements can use a longer support or maintenance arrangement.

Who owns the finished work

The client keeps its content, data, brand assets, and client-controlled business accounts. Rights in custom deliverables transfer according to the accepted terms, normally after full payment. PandaCodeGen retains its reusable internal tools, templates, methods, and pre-existing code. Third-party components keep their original licenses. Our article on what website ownership actually covers sets out the questions to ask any provider about this.

The domain, hosting, repository, analytics, email, commerce, CRM, and other business accounts can be created under client-controlled credentials when agreed. PandaCodeGen can manage them when requested, but the arrangement, access, billing owner, exit process, and handover must be documented. No vendor or agency lock-in should be assumed merely from the word "custom."

How to compare this quote with another provider

These details make two offers comparable. Provider size, location, or a generic market average does not prove whether a quote is fair for your scope. Seven written details do the work: the exact inventory, the named deliverables and exclusions, the acceptance tests, the revision and change-order terms, the payment and ownership terms, the support definition, and the third-party costs sitting outside the fee.

These details make two offers comparable. Provider size, location, or a generic market average does not prove whether a quote is fair for your scope. Our notes on what a low quoted rate leaves out and how to assess a development agency expand on the same checklist.

Which tier should you start with?

Start with the smallest tier that can honestly contain the required outcome and risk controls. A focused brochure migration may fit Starter. A content-led business with a CMS and more templates may fit Growth. Scale is the better planning anchor when commerce, a larger inventory, custom workflows, or deeper integrations are central.

If one or two pages or features sit outside the initial package, we can add and discuss them in the written scope. The first call is for fit and inventory, not pressure to buy the largest tier. Our delivered project write-ups show what each kind of scope looked like in practice, and our guide to how long a custom website takes covers the schedule side of the same decision.