Skip to main content
PandaCodeGen

Example migration scopes. A written quote for your actual risk.

Choose the closest starting package, then add or remove pages and features in a written quote. A common package starting structure is 30% at onboarding and 70% at the delivery milestone defined in the accepted project terms; another written schedule can be agreed for a particular project.

Scope is driven by URL and content volume, CMS models, integrations, analytics, compliance needs, stakeholders, and migration risk, not page count alone.

URL inventory · Content model · Integrations · Cutover risk
Acceptance test in writing
Timeline defined by scope
Third-party costs listed
Change terms documented

Website planning examples

Starter

Small business sites, 5 to 7 pages.

Commercial terms
$1,500

Starting package · exact scope in proposal

  • ✓5 to 7 custom pages, with the exact templates and content responsibilities listed in scope
  • ✓Next.js deployment with repository, environment, and handover responsibilities documented
  • ✓90+ Lighthouse performance target on both mobile and desktop for the agreed representative pages
  • ✓Three recorded pre-handover runs per agreed page/profile; every run must meet the target
  • ✓Mobile-First Build (designed on mobile screen first, then scaled up, not the other way around)
  • ✓Hosting and third-party service options documented before approval
  • ✓15 business days of included support for the agreed deliverables; start point and coverage stated in the accepted project terms
Migration example

Growth

10 to 20 pages, CMS, full migration.

Commercial terms
$3,500

Starting package · exact scope in proposal

  • ✓10 to 20 Page Custom Site (full marketing site with service pages, case studies, and resources)
  • ✓Sanity CMS Integration (your team updates content without touching code)
  • ✓Blog migration with a URL inventory, redirect map, metadata preservation, and post-launch monitoring
  • ✓90+ Lighthouse performance target on mobile and desktop, with three passing runs per agreed page/profile
  • ✓Hosting and third-party service costs listed before approval
  • ✓30 business days of included support for the agreed deliverables; start point and coverage stated in the accepted project terms

Final scope, payment, warranty, and remedy terms are confirmed in accepted written project terms.

Moving off WordPress? See the full migration scope

Scale

Headless e-commerce & 30+ pages.

Commercial terms
$5,000–$10,000

Starting range · exact scope in proposal

  • ✓Headless E-Commerce (Shopify or WooCommerce backend, Next.js frontend. The speed of custom, the admin of Shopify)
  • ✓30+ page or template scope for products, collections, content, and landing pages
  • ✓Reviewed integrations such as Klaviyo, HubSpot, Salesforce, Stripe subscriptions, or another documented API
  • ✓90+ Lighthouse performance target on mobile and desktop, with three passing runs per agreed page/profile
  • ✓Sanity CMS + Content Ops (content model designed for your editors, not generic templates)
  • ✓30 business days of included support for the agreed deliverables; start point and coverage stated in the accepted project terms
See our headless e-commerce service

Scale+ Custom Engagement

Bigger project? Let's scope it together.

Enterprise scope, multi-region e-commerce, custom SaaS platforms, complex integrations. We cannot quote without understanding the work. Message us and we will scope it on a call. Curious what this looks like in practice? See our custom engineering service.

How the written quote works.

Scope before price

We first inventory the pages, content, integrations, constraints, stakeholders, and acceptance tests. The written project summary then states what is included, excluded, and assumed.

Written change control

A common payment option is 30% at onboarding and 70% at the delivery milestone defined in the accepted project terms, but another written schedule may be agreed. Revision limits are stated before work begins, and material out-of-scope requests receive a separate written estimate and require approval.

Flexible package starting points

These options may be used, changed, or omitted. A signed agreement or a clear quote or order summary accepted in email or chat supplies the project-specific detail and controls.

01
Scope and additions
The starting package is adjusted for the approved pages and features. Deliverables, integrations, content responsibilities, exclusions, and any separately priced additions are listed explicitly.
02
Written scope protection
When included in the accepted project terms, PandaCodeGen refunds 100% of the fees paid under that scope if it fails to deliver the promised deliverables. The written terms define the trigger and cure process; this is not a change-of-mind refund.
03
90+ performance handover target
The accepted project terms name the representative pages and test conditions for mobile and desktop. Each of three recorded runs per agreed page/profile must reach 90+ before handover.
04
Support option
Package discussions may start with 15 business days for Starter and 30 business days for Growth and Scale. Support applies only when the accepted project terms state when it starts, what defects or minor adjustments it covers, and any bespoke arrangement.
05
Payment, changes, and ownership
A common payment option is 30% at onboarding and 70% at the defined delivery milestone; the parties may agree otherwise in writing. Currency, taxes, revision limits, separately priced additions, ownership transfer, licenses, accounts, and third-party costs are stated before implementation.
06
Launch and rollback
Responsibilities for redirects, analytics, forms, DNS, monitoring, rollback, and post-launch review are included in the cutover plan.

Contract clarity

Compare the scope, not just the headline price.

Feature
High-level quote
Reviewed project scope
Scope
High-level quoteMay be described at a high level
Reviewed scopeURLs, content, integrations, and exclusions listed
Performance
High-level quoteTarget may be unspecified
Reviewed scope90+ Lighthouse target, pages, profile, and three-run handover check written into scope
Migration
High-level quoteRedirect and cutover detail varies
Reviewed scopeInventory, redirect map, QA, and rollback plan
Ownership
High-level quoteDepends on the contract
Reviewed scopeOwnership and license terms stated in the proposal
Ongoing cost
High-level quotePlatform and vendor charges vary
Reviewed scopeKnown third-party costs documented before approval
Changes
High-level quoteProcess varies
Reviewed scopeOut-of-scope work requires a separate written quote
What to compare
High-level quoteImportant assumptions can remain unresolved
Reviewed scopeNamed acceptance, ownership, cost, and change rules

Evidence standard

Review the migration scope, baseline, implementation, measurement date, and limitations before relying on a result figure.

Project evidence
Method, permission, date, and limitations
Review the publication standard →

Common Questions

Which package should I start with?

Starter begins at $1,500, Growth at $3,500, and Scale normally falls between $5,000 and $10,000. Choose the closest base; extra pages or features are discussed and priced in the written scope before work starts.

Do I need a long contract for every project?

No. A straightforward project can use a clear written quote or order summary accepted in email or chat. Regulated, sensitive, or complex work may need a signed statement of work or other detailed agreement. In either case, the accepted written project terms control.

How do payment milestones work?

A common option is 30% at onboarding and 70% at the delivery milestone defined in the accepted project terms, but the parties may agree to another written schedule. The accepted terms also state currency, taxes, due dates, approval points, and any pause or cancellation terms.

What if my project is bigger than Scale?

Larger, multi-region, e-commerce, application, and integration-heavy work is scoped separately after discovery. The proposal lists the team, deliverables, dependencies, exclusions, and schedule for that engagement.

What support is included?

A package discussion may start with 15 business days of support for Starter and 30 business days for Growth and Scale. Support is included only when the accepted project terms state the period, start event, covered defects or minor adjustments, response expectations, exclusions, and any bespoke arrangement. Material new features, extra pages, and third-party changes are separately scoped.

When does the 100% refund apply?

When that protection is included in the accepted project terms, it applies if PandaCodeGen fails to deliver the promised deliverables under that written scope. The terms define the trigger, verification, and any cure process. It does not apply merely because preferences change, a new direction is requested, or work outside the agreed scope is desired.

How should I compare providers?

Compare the actual scope, migration plan, acceptance tests, ownership and licensing terms, third-party costs, change process, launch responsibilities, warranty, and remedies, not just the headline price.

What determines the quote?

The main drivers are URL and content volume, CMS structure, custom design and functionality, integrations, analytics, accessibility and compliance needs, stakeholders, migration risk, and deadline.

What happens before you quote?

We review your current platform and URL, primary goal, content and traffic scale, required integrations, timeline, budget range, and known constraints. We then document assumptions and open questions before pricing.

How is the 90+ performance target checked?

The accepted project terms name the representative pages and reproducible Lighthouse conditions for mobile and desktop. Each of three recorded pre-handover runs per agreed page/profile must score 90 or higher. This is a lab acceptance target, not a guarantee of field Core Web Vitals, rankings, revenue, or unchanged results after third-party or client changes.