Page and component inventory
The proposal lists every page, template, reusable component, state, form, locale, and content responsibility included in the price.
Webflow proposal review: know what you are buying before the deposit.
A beautiful portfolio does not define ownership, migration, launch, or acceptance. Review the operating deal behind the Webflow build before money and momentum make vague language expensive.
A Webflow proposal is ready for a deposit when it names the complete build inventory, site and Workspace ownership, migration and redirect work, responsive and accessibility tests, launch duties, handover, support, and a measurable acceptance rule for every paid milestone.
The safest review happens against one proposal, one project inventory, and one shared definition of done.
The 12-point Webflow proposal review
Workspace and site ownership
The agreement names the Workspace owner during the build, the intended site owner after handover, who pays each plan, and which access each party retains.
CMS and data migration
Collections, fields, item counts, references, assets, redirects, import method, cleanup, validation, and content freeze responsibilities are explicit.
Forms and integrations
Forms, CRM, analytics, consent, search, automation, payments, memberships, APIs, and failure handling have named owners and test paths.
SEO metadata, URLs, and 301 map
Indexable pages and templates have scoped titles, descriptions, headings, alt-text duties, and schema; changed URLs have an approved redirect map and pre-launch and post-launch checks.
Responsive breakpoints
The proposal identifies supported breakpoints, representative devices and browsers, responsive states, and the evidence used to confirm them.
Accessibility criteria
The parties name the target, test method, known exclusions, content duties, manual checks, and correction path instead of promising undefined compliance.
Performance and technical acceptance
Performance budgets, image and font handling, third-party scripts, browser coverage, console errors, broken links, and test conditions are stated.
Milestones, evidence, and payment
Each payment maps to named deliverables, acceptance criteria, evidence, a reviewer, a review window, and an in-scope correction path.
Revisions, exclusions, and changes
Feedback rounds define what a round is; common adjacent work is excluded; new scope requires written price and schedule approval before work starts.
Launch, plan, domain, and rollback
The launch owner, current Site and Workspace plan needs, billing payer, DNS access, freeze window, backup, go/no-go decision, monitoring, rollback route, and post-launch checks are assigned.
Handover, export, and support
The buyer receives the site or Workspace transfer, credentials, assets, licenses, documentation, training, known-issue list, and separately defined support.
Rewrite one vague launch milestone
Before
Webflow rebuild and SEO migration — 50% at launch
Build a modern responsive site, move the CMS, preserve SEO, connect forms, and launch after two feedback rounds.
Review-ready structure
Migration, acceptance, and launch milestone
- Deliverable: the approved page, template, component, collection, field, form, and integration inventory on the agreed staging site.
- Acceptance: the agreed content sample matches the migration map; representative paths pass at the named breakpoints and browsers; forms and integrations complete their test paths.
- SEO evidence: approved old-to-new URL CSV, redirect test results, crawl comparison, metadata sample, and known-exception list.
- Ownership evidence: final Workspace or site owner, billing owner, access list, licenses, and handover steps are recorded before launch.
- Review path: the named buyer reviewer has five business days to accept or cite the unmet criterion; one in-scope correction and resubmission is included.
- Payment: the milestone amount becomes due only after explicit acceptance under the agreed commercial terms.
Illustrative structure, not a universal contract or legal advice. The actual inventory, tests, timing, remedies, and payment rule must fit the deal and be agreed by both parties.
Webflow-specific facts the proposal should account for
Webflow states that a Workspace is the default owner of sites inside it and recommends that client agreements define ownership, billing, and access. It also warns that if a freelancer or agency becomes unreachable, Webflow cannot simply transfer or export a site from that party's Workspace to the client. That makes ownership wording a delivery requirement, not an administrative afterthought. See Webflow's site ownership guidance.
Transfer and code export are different. Webflow documents that a site transfer can carry site data and settings, while exported code does not include hosted features such as CMS, Ecommerce, User Accounts, or Localization, and some forms and search behavior will not work as they did on Webflow. Compare the official site transfer and code export guidance against the promised handover.
For redesigns and replatforms, URL preservation must be scoped. Webflow supports individual 301 redirects and CSV import/export, but the proposal still needs a person responsible for the map, validation, and fixes. Review the official 301 redirect guidance and CSV workflow.
Frequently asked questions
Who owns a Webflow site built by an agency?
Webflow says the Workspace is the default owner of sites inside it. A proposal should therefore name the build Workspace, intended final owner, billing responsibility, transfer timing, access, and what happens if the relationship ends.
Is exporting Webflow code the same as handing over the whole site?
No. Webflow documents that paid Workspace plans can export HTML, CSS, JavaScript, and assets, while CMS, Ecommerce, User Accounts, Localization, and some hosted functionality are not included. The proposal should choose the correct handover method for the features used.
Should a redesign proposal include 301 redirects?
If URLs may change, the proposal should assign ownership for the old-to-new URL map, approval, import, testing, and post-launch correction. Webflow supports redirect management and CSV import/export, but the commercial scope must still define who does the work.
Does passing Webflow’s Audit panel prove accessibility?
No. Webflow describes the Audit panel as a way to find some accessibility and SEO issues, and its accessibility checklist does not guarantee conformance. A proposal should state the target and combine appropriate automated and manual review.
Primary Webflow guidance used
This checklist is an original Ratly32 review framework. Product behavior can change, so verify current Webflow documentation and the exact plan and features used in the deal. The sources support platform mechanics; they do not endorse Ratly32, establish contract terms, certify accessibility, or guarantee search results.
- Webflow — Site ownership
- Webflow — Transfer a site
- Webflow — Export site code
- Webflow — Set up 301 redirects
- Webflow — Import and export redirects
- Webflow — Breakpoints overview
- Webflow — Accessibility checklist
- Webflow — Audit panel
- Webflow — Choose a Site plan
- Webflow — May 2026 plan and pricing updates
Next move
Run a free structural scan before the deposit.
Paste the proposal locally, find the missing decision terms, and turn the open items into a neutral provider brief or working Deal Spec.