Agency delivery

How to Structure a White-Label Web Development Partnership

Bringing in an outside development partner can widen what your agency sells. None of it is automatic though, not the margin, not the delivery time, not the capacity, not who ends up owning the code, and not the result the client gets. Write down how the commercial side and the delivery side will work before anyone sells the project.

Offer and terms reviewed August 8, 2026.

Hassan Jamal·March 6, 2026·5 min read

Hassan scopes search-sensitive migrations and partner delivery systems.

The workable model

✓
Choose referral, co-delivery, or white-label delivery and document what the client is told.
✓
Before you quote, find out what they have, what it connects to, who writes the content, what could go wrong in the migration, how it gets signed off, and who supports it afterwards.
✓
Use a partner quote as an input. Your retail price and margin remain your own commercial decision.
✓
Agree who signs the contract, who holds the accounts, who approves changes, who owns the work, and who answers the phone after launch.
✓
Confirm capacity and schedule for each project. A general partnership is not a reserved production slot.

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: usually the lowest cost, and the least structure. Availability, scope and accountability rest on one person, so ask how each is covered, 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.

What you can actually offer once you have a delivery partner

Four things, and they behave differently in a quote, so it is worth knowing which one you are being asked for before you price it. Each has a scope driver that moves it between tiers, and none of them is priced by page count.

✓
WordPress or platform migrations. The scope driver is distinct template count and integration complexity, not URL count. A hundred pages on six templates is a smaller job than twelve bespoke layouts, and the redirect map is a line item rather than an assumption.
✓
Custom ecommerce and headless commerce. The driver is whether there is a real backend behind the storefront: catalogue, variants, orders, tax, fulfilment and the reconciliation obligations that come with money moving. This is the one we see under-scoped most often.
✓
CRM-connected builds, including GoHighLevel. The driver is a defined funnel and booking flow plus the integration contract behind it. The frontend is usually the smaller half; the field mapping, consent capture and failure handling are the work.
✓
Internal tools and dashboards. The driver is data-model design, multi-user authentication and client-specific business logic, which is exactly why these cannot be fixed-tiered honestly. Price them after a discovery call, not from a rate card.

Two of those are the reason agencies bring in a partner at all: commerce and internal tools are where a request most commonly exceeds what a design-led team can deliver alone. The other two are usually within reach if you have someone to hand the engineering to. Knowing which of the four a client is describing is the difference between quoting confidently and quoting defensively.

"Bringing in a delivery partner widens what you can sell. None of it is automatic, least of all the margin.

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

The axis that separates the three is who signs the client contract. White-label keeps the client relationship with the agency, co-delivery makes both teams visible, and referral has the developer contracting directly. Do not promise a client will never know a partner exists; the appropriate disclosure depends on the accepted agreements, procurement requirements and the access the work needs.

White-label

The agency owns the client. Partner terms cover the rest.

Co-delivery

Both teams are visible, and the paperwork says who does what.

Referral

The developer contracts directly with the client. Referral fees, if any, require a separate written agreement.

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

Six things have to be established before a number goes out, because a quote written without them is a guess with a decimal point. Who controls the platform, domain, hosting, code and vendor accounts; the full inventory; which URLs carry search value; the design and accessibility inputs; how performance will be measured; and who owns launch, support and change control.

✓
Who currently controls the platform, domain, hosting, code, CMS, analytics, consent tool and vendor accounts.
✓
A list of every page, template, language, piece of content, image, product, user role and integration.
✓
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.

Illustrative arithmetic only

If a partner quote were $5,000 and an agency chose a $7,000 client price, the gross spread would be $2,000 before sales, account management, revisions, tax, payment fees, warranty work, and overhead. That scenario is not a recommended rate or promised profit.

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 worth asking for.
✓
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

Six lanes need a named owner before the project starts: sales, discovery, delivery, communication, acceptance and aftercare. This belongs in one reusable document rather than a fresh email thread per project, because the lane nobody claimed is the one that fails at handover.

✓
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

The outsourcing failures we have been called in to repair traced 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.

Signals worth slowing down for

Uncapped hourly billing. Scope that stays vague after questions. Reluctance to put disclosure and client-contact rules in writing. A price or a delivery date offered before anyone has seen the current site, the inventory or the integrations. Any promise about rankings, traffic or revenue. Revision limits set by count alone, with no reference to whether the work met the agreed scope.

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

These are the terms a partner agency is quoting on top of, reviewed July 24, 2026. Read them as the starting position rather than the final one: every line below is subject to the signed contract, and the full wording lives on our terms page, which governs if this page and that page ever disagree. What a partner pays is quoted per project and is not assumed to equal our public retail tiers.

✓
A common payment option is 30 percent at onboarding and 70 percent at the delivery milestone, and another written schedule may be agreed, subject to the signed contract.
✓
Where the accepted project terms include it, a refund covers fees paid under that scope if the promised deliverables are not delivered, 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; the receiving bank or payment provider controls settlement after that, which can take up to 10 to 12 business days.
✓
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.

The part most partnerships get wrong: what happens after launch

Build scope gets negotiated carefully and the month after launch usually gets a sentence. That is the wrong way round, because the build ends and the relationship does not. A client who emails at nine in the evening about a broken contact form is emailing the agency, not the delivery partner they have never heard of.

Ongoing maintenance is also where a reseller relationship becomes worth having. A one-off build is a one-off margin; a monthly retainer covering hosting oversight, dependency and security updates, content changes and small improvements is recurring revenue the agency owns. Agree three things in writing before launch, not after the first incident.

✓
Who triages, and who fixes. These are different jobs. An agency can reasonably own first response — reproduce it, establish urgency, tell the client something true within an hour — while the partner owns the code fix. Agreeing that split is most of the value, because it decides what the agency has to be able to do itself.
✓
What counts as a defect versus a change. A form that never worked is a defect. A form that now needs a new field is a change, and it is billable. Without that line written down, every request arrives as a warranty claim and the margin quietly disappears.
✓
Response expectations, in hours, and who is on the hook outside working days. Publish something you can actually meet rather than something that sounds reassuring, because the first missed response is what a client remembers.

Key Insight

The support included with a build is a defined window, not an open-ended arrangement, and it is stated in the project terms rather than assumed. Decide before launch what happens the day after it ends — whether the agency sells its own retainer and calls on the partner for code work, whether ongoing work is quoted separately each time, or whether the client is handed over entirely. All three are legitimate. Not choosing is the one that damages the client relationship the agency spent the project protecting.

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 tend to 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.

Scope a real partner opportunity

We will review the current site, client requirements, migration risks, responsibility split, acceptance method, and handoff before either party promises price or timing.

Frequently Asked Questions

What is white-label web development?

It is a delivery arrangement in which an agency leads the client relationship while another team performs defined development work. Branding, disclosure, access, confidentiality, ownership and support must be written into the partner and client terms.

What margin can an agency make?

There is no promised margin. Use the partner's project-specific quote, then price your sales, strategy, creative, management, revisions, risk, tax, payment fees and support. The agency controls its retail price and remains responsible for its own economics.

Will the client know a delivery partner is involved?

That depends on the accepted agreements, procurement requirements, access needed and applicable duties. PandaCodeGen does not promise concealment. Choose and document a referral, co-delivery or white-label model before sale.

Who owns the finished website?

Client content, data and brand assets remain the client's. Rights in fully paid custom deliverables, reusable PandaCodeGen tools or pre-existing code, and third-party components are defined in the accepted terms. Third-party licenses continue to apply.

What happens when the client requests changes?

The responsibility matrix and change-control process decide who receives, scopes, approves, prices and delivers the request. Minor accepted fixes may fall within support; new features or expanded scope require written approval and agreed pricing.

Does a partnership reserve development capacity?

No general promise should be assumed. PandaCodeGen confirms scope, dependencies, current capacity and schedule for each accepted project.

Agency13 min