PandaCodeGen / Webflow development, redesign & migration
Webflow development and redesign for a new website or an existing site that needs attention. We review mobile layouts, CMS editing, forms and integrations, then scope improvements or a move to a custom build when it fits.
01 / See the work
These projects show how we build editors and connected systems; they did not begin on Webflow.
Project / Panda Patches
The team edits storefront content and manages a connected operations workflow in a custom build.
Founder-affiliated work. Panda Patches originally used WordPress and WooCommerce, not Webflow.
A separate client review
“Hassan was super helpful and communicative throughout the process.”
This review describes the client's experience working with us. It is separate from the featured project and does not verify its technical outcomes.
02 / Review your site
We inspect the pages and publishing tasks causing the problem. Your current Webflow setup may only need focused changes; a migration receives its own content, interaction and integration plan.
Measure priority Webflow pages, including images, fonts, scripts and interactions. Record the device and connection so the same checks can be repeated after changes.
Ask an editor to publish a real item. Review collection fields, references, slugs and media, then list the content and relationships a replacement editor must support.
Follow an enquiry from submission into the system that should receive it.
Read the current plan, seats, add-ons and asset usage before comparing alternatives.
What the proposal resolves
For a Webflow redesign, we improve the existing pages and editor. For a move, Next.js handles the public website and a CMS such as Sanity gives your team fields for editing content. We agree those editing tasks before choosing the destination.
Map collections, fields, references, rich text, media and slugs into the chosen editor. Count distinct templates as well as URLs; validate scoped records and publish a representative item before launch.
Decide which animations remain and which interactions perform a business action, such as a form step or calculator. Forms, search, languages and restricted pages need their own replacement and tests where included.
Your team supplies account and domain access, new copy or imagery if required, and a decision maker for the scope and preview. The written proposal identifies who handles content transfer, redirects, cutover and support.
A new site still needs hosting and may need a CMS, seats, forms, search, localisation and maintenance. Compare those charges with the Webflow plan and add-ons you actually pay for.
Website SEO / Search and AI access
A CMS collection can publish many pages, so its page template and fields need useful content and consistent search settings. We review the template as well as individual pages.
Need ongoing buyer research, page improvements and visibility reporting? AI search services are optional monthly work, scoped separately from the build. Search systems choose which pages they index or cite.
03 / Make the right call
We recommend the scope that addresses the evidence from your site and team, then put the work and boundaries in writing.
Our recommendation: keep Webflow when your team can publish comfortably and the problems are specific layouts, scripts or forms. Fix those first; a higher subscription bill alone is a reason to compare costs, not automatically rebuild.
We recommend a move when essential editing tasks, integrations or business rules need a different system. Compare the rebuild and ongoing costs against staying, then test your team's publishing workflow in the proposed editor before launch.
04 / From call to handover
Each stage creates something you can review. Your proposal names the deliverables and the point where you accept them.
Inventory pages, components, interactions, CMS collections, forms and integrations.
Compare a scoped Webflow improvement with the complete cost of a move.
Validate content, fields and connected services against agreed samples.
Crawl the preview, test redirects and forms, then monitor cutover.
05 / Published starting point
From $1,500
Starting point, not an instant quote.
Custom rebuilds start at the published Starter price. Improvements within Webflow are quoted to their own scope. The written proposal states the chosen route, price and dates.
CMS, billing and integration permissions agreed first.
The repair route and the rebuild route costed clearly.
An inventory of important URLs, metadata transfer and tested redirects for changed addresses.
After launch
The build is a one-off. These are the bills that continue, so add them up before you compare quotes.
Site plan
Basic $15 a month or Premium with CMS $25 a month, per site, billed yearly ($25 a month and $39 a month billed monthly)Workspace
If your team needs a paid Workspace: Core $19 a month or Growth $49 a month, billed yearly. Check included seats and additional seat charges against your account.Add-ons
Localization from $9 a month, Analyze from $9 a month, Optimize $299 a monthHelp and changes
Your own records or your developer's invoicesWebflow prices are in USD, plus tax, as of September 2026. For affected existing sites in Freelancer or Agency Workspaces, or on legacy pricing, the pricing transition starts 16 November 2026 and applies at the next renewal or billable plan change. Check your account notice and bandwidth charges before comparing the full bill. Team bundles a Site plan and Workspace, so count included services once.
06 / Ownership & exports
Webflow's ordinary code export downloads website files on a paid Workspace plan, but it does not carry every working feature. Blog content, store records and forms need separate checks. Webflow also offers an Enterprise custom hosting option; that is a different route from downloading code and leaving the platform.
Your project handover
You receive the project code and design files we create for you, plus documentation and control of the production accounts. If you then take a monthly support or care plan, that doesn't change: we keep sharing the code, documentation and accounts with you, so you always have your own copy. Third-party themes, plugins, services and assets remain under their own licence terms.
Yes, but the method matters. A paid Webflow Workspace plan allows a code download for another host, with limits on content and working features. Webflow's Enterprise custom hosting option is different and retains a connection to Webflow. Choose between those routes and a rebuild based on what the business needs to keep.
Webflow's ordinary code export does not include its content editor or ecommerce functionality, and forms need a separate way to send submissions. Content downloads are separate from the code. Before switching hosting, plan how the blog, forms, search and checkout will work and test those replacements. Enterprise custom hosting has different capabilities.
Read each row for the scope and source.
| Website assets | Webflow | Your PandaCodeGen build |
|---|---|---|
| Website design and files | Partly A paid Workspace plan lets you download website files for another host. This ordinary code export does not carry the working editor, store, forms or search. A Site plan alone does not include code export. Webflow docs on Webflow, website design and files (opens in a new tab) ↗ | Yours You receive the website code and design files we create for you. Custom builds use the open-source Next.js framework. Third-party themes, plugins and services keep their own licence terms. Next.js licence on website design and files (opens in a new tab) ↗ |
| Website pages | Partly The ordinary code download includes page files in the main language only. Pages filled from the content editor come out empty, so their content needs a separate download. Webflow docs on Webflow, website pages (opens in a new tab) ↗ | Yours With Sanity, your page content and available uploaded files can be downloaded together. Missing or inaccessible files need separate recovery. WordPress builds use WordPress's content download; text built into the website files comes with those files. Sanity export docs on website pages (opens in a new tab) ↗ |
| Editable lists and business details | Exports Editable content lists download as spreadsheet files. Formatted text includes website formatting; photos and files appear as links, so copy the actual files before deleting the old site. Webflow docs on Webflow, editable lists and business details (opens in a new tab) ↗ | Yours Lists such as services, team members and locations are included in the content download. Sanity's terms say the subscriber keeps ownership of that data. Sanity terms on editable lists and business details (opens in a new tab) ↗ |
| Products | Exports Products, variants and categories export to a spreadsheet file from the Designer. Webflow docs on Webflow, products (opens in a new tab) ↗ | In your account Kept in the store system or database your proposal names, under accounts you control, so you can export it from there. If a new storefront keeps Shopify or WooCommerce behind it, that platform's column still applies. |
| Past orders | Exports Orders export to a spreadsheet backup from the Orders list. Webflow docs on Webflow, past orders (opens in a new tab) ↗ | In your account In the same store system or database as your products, under accounts you control. |
| Images and files | Partly The code export includes the images uploaded to the Assets panel, on Workspace plans. Images and files in editable content lists export only as links, so Webflow says to keep the old site or download them by hand. Webflow docs on Webflow, images and files (opens in a new tab) ↗Second source on Webflow, images and files (opens in a new tab) ↗ | Yours Available images and files uploaded to Sanity come with the content download. Check the download for missing files. Images built into the design are part of the website files you receive. Sanity export docs on images and files (opens in a new tab) ↗ |
| Website address (domain) | Exports Domains bought through Webflow are bought from IONOS and sit in your own IONOS account. Webflow docs on Webflow, website address (domain) (opens in a new tab) ↗ | In your account Control of the production accounts is part of handover. Hosting moves to your own account on request or when an engagement ends. |
The project code and design files we create for you.
Instructions handed over with the project files. If you take a care plan later, we keep sharing the documentation with you.
An editing walkthrough at handover, so your team can update the site. Every build that uses Sanity includes training on Sanity Studio and written documentation for it. On Starter, the content editor is set up, documented, and we train you on it.
Control of the production accounts. Hosting moves to your own account on request or when an engagement ends.
Your build keeps working without a PandaCodeGen care plan. Hosting and other provider services still need their own arrangements.
Licence notes, from the same check:
Vendor columns describe each platform's own documented tools, read on 8 October 2026. Plans and export tools change, so check the linked page before you rely on a row. Our column comes from our published terms; your written proposal states the details for your project, including any third-party licences.
07 / Before you decide
These are starting answers. Project-specific details belong in the written proposal.
Keep exploring
All services ↗Related service
CMS website development ↗