White-Label Web Development Without Guesswork

Four ways to answer a custom-build request

A client asks for a custom site and the agency has no development team. There are four honest answers, and each carries a different cost, risk and level of control.

• ✓
  Decline the work: no delivery risk, but the client goes looking for a full-service provider and may take the rest of the account with them.
• ✓
  Place it with an individual freelancer: lowest cost, least structure. Availability, scope and accountability rest on one person, and the agency still carries the client relationship.
• ✓
  Hire in-house: most control and the highest fixed cost, with recruitment time and the question of what the role does between projects.
• ✓
  Work with a delivery partner under written terms: the agency keeps the client relationship and sets its own price, while scope, capacity and accountability are documented rather than assumed.

The fourth option is the subject of this guide. It is not automatically the right one. It is the one that needs the most paperwork to work properly.

White-label, co-delivery, and referral are different

Do not promise that a client will never know a partner exists. The appropriate disclosure depends on the accepted client and partner agreements, procurement requirements, access needed, subcontracting terms, and applicable duties. The honest answer is the one written into the deal.

Run a fit check before the agency quotes

• ✓
  Current platform, domain, hosting, repository, CMS, analytics, consent, and vendor-account control.
• ✓
  Page, template, locale, content, media, product, user-role, and integration inventory.
• ✓
  URLs and search-sensitive assets that must remain stable or receive page-level redirects.
• ✓
  Design source, copy, accessibility level, browser and device coverage, and editor workflow.
• ✓
  Performance method, representative pages, mobile and desktop profiles, and acceptance remedy.
• ✓
  Launch, rollback, training, support, exclusions, dependencies, change control, and decision owners.

PandaCodeGen's public starting tiers are planning anchors: Starter at $1,500, Growth at $3,500, and Scale typically from $5,000 to $10,000, with larger custom engineering work scoped separately. Final price comes from the accepted scope. An agency can add project management, strategy, creative, sales, risk, and support to its retail price, but PandaCodeGen does not publish a guaranteed markup or margin.

How a white-label engagement runs, step by step

The sequence below is the process, not a promise about price, margin or dates. Those come from the specific opportunity.

• ✓
  The agency brings the brief: client type, requirement, hard deadlines, existing assets and platform, and a budget range if one exists. A mutual NDA before project detail is shared is normal practice.
• ✓
  The partner returns a scoped quote: what is included, what is explicitly excluded, assumptions, milestones, and what the agency must supply. Quote turnaround is agreed per opportunity rather than assumed.
• ✓
  The agency sets its own retail price and quotes the client. The client signs the agency's contract, so the agency stays the accountable party.
• ✓
  Build and review: the agency reviews each milestone before it reaches the client, the partner handles technical revisions, and client communication runs through whichever party the terms name.
• ✓
  Launch and handoff: documentation for whoever edits the site, the agreed support window, account and credential transfer, and a defined route for later change requests.

Whether the partner is disclosed, invisible or jointly named is a decision for the accepted agreements, not a default of the model. Write it down at the first step rather than improvising it when a client asks who built the site.

Put this responsibility matrix in writing

• ✓
  Sales: who makes claims, sends the proposal, signs the client, and collects payment.
• ✓
  Discovery: who verifies requirements and who can approve assumptions or exclusions.
• ✓
  Delivery: who designs, writes, develops, supplies content, configures vendors, and runs QA.
• ✓
  Communication: meeting cadence, escalation path, response expectations, and whether developers attend client calls.
• ✓
  Acceptance: who confirms test conditions, records defects, approves launch, and signs handoff.
• ✓
  Aftercare: which team receives incidents and which changes are support versus billable scope.

This split belongs in one reusable document rather than a fresh email thread per project. The agency partner programme covers the same ground from our side, and the guide to choosing a development agency sets out what a client-side buyer tends to ask for in the same paperwork.

What to check in a delivery partner

Most bad outsourcing experiences trace back to something that was never written down. These are the items worth confirming before an agency puts its own name on the delivery.

• ✓
  A fixed-price quote written against a defined scope, with exclusions and assumptions named.
• ✓
  A written scope before work starts rather than an agreement to settle the detail later.
• ✓
  An agreed check-in cadence and milestone review, so project status is never a guess.
• ✓
  A signed NDA and a written rule on whether, when and how the partner may contact the client.
• ✓
  Named accountability: who performs the work, and who responds when something breaks after launch.
• ✓
  Evidence an agency can actually show a buyer: delivered work, method and acceptance records rather than screenshots alone.
• ✓
  Support, revision and change-control terms written into scope rather than offered as goodwill.

Ownership and account control

Client content, data, brand assets, and client-controlled accounts remain the client's. Rights in paid custom deliverables transfer or are licensed only as the accepted terms state. PandaCodeGen retains reusable internal tools, templates, know-how, and pre-existing code. Third-party components keep their original licenses.

Domain, hosting, repository, CMS, analytics, payment, CRM, and email accounts should be created under client-controlled identities when that is the agreed model. If the agency manages them, document access, billing, security, transfer, suspension, and exit procedures. “No lock-in” should mean a tested handoff, not a slogan.

Commercial terms for a PandaCodeGen project

• ✓
  The normal payment structure is 30 percent at onboarding and 70 percent on delivery, subject to the signed contract.
• ✓
  A 100 percent refund applies when PandaCodeGen does not deliver the signed scope under the contract, not merely because preferences change after work starts.
• ✓
  Refund timing is governed by the agreement. PandaCodeGen normally initiates an approved refund in 2 to 3 business days and publishes a maximum of 10 to 12 business days for processing.
• ✓
  Starter includes 15 business days of agreed support; Growth and Scale include 30 business days. Start date and coverage belong in the accepted terms.
• ✓
  Minor agreed tweaks may be handled in support. New features and out-of-scope work use written change control and an agreed fixed, hourly, or other billing model.

The agency's own retail number and dates sit on top of those terms. Two references help when that number is set: what shapes the cost of a custom website and how long a custom build takes.

Quality acceptance without universal guarantees

Where the signed scope includes PandaCodeGen's 90+ Lighthouse target, name the representative pages, mobile and desktop profiles, environment, exclusions, three-run method, acceptance threshold, and remedy. A lab score is not a ranking, traffic, conversion, or revenue guarantee.

• ✓
  Crawl and compare the approved old and new URL inventories.
• ✓
  Test forms, CRM writes, calendars, payments, analytics, consent states, errors, and notifications.
• ✓
  Verify responsive behavior, keyboard paths, labels, focus, contrast, and content states.
• ✓
  Record releases, versions, environment, test evidence, known limitations, and rollback steps.

Two explainers are worth attaching when acceptance is drafted: Core Web Vitals explained for how lab and field measurement differ, and what happens to search visibility during a migration for the URL-level checks that belong in the test plan.

What the agency can say about the finished build

An agency does not need to explain its supply chain to describe the product accurately. These statements can be made without stepping outside what the scope actually commits to.

• ✓
  The site is built to the agreed scope rather than assembled from a theme or template.
• ✓
  Deliverables, licences and account control are as the accepted terms set out, in the accounts those terms name.
• ✓
  Where a CMS is in scope, the client can edit content without developer involvement, within the editor and roles that were built.
• ✓
  Where the signed scope includes the 90+ Lighthouse handover target, describe it as a target measured on the named representative pages across mobile and desktop, with three recorded runs before handover, and not as a promise about rankings, traffic or revenue.
• ✓
  Hosting, service and vendor costs are itemised in the scope. Ongoing cost is a line to quantify, not a benefit to imply is zero.

How to start without overselling

Bring one real opportunity to a partner fit audit. PandaCodeGen can return a migration plan, assumptions, exclusions, evidence needed, proposed acceptance method, and a project-specific quote. The agency can then decide whether to refer, co-deliver, or propose a documented white-label engagement.

Agencies weighing outsourcing options usually read around first. Our shortlist of US custom development agencies and the comparison of Pagepro alternatives show how scope and fit are described elsewhere. When a live opportunity is ready, the contact form is the fastest route in.