Webflow Developer — Rebuild Designed Pages

Company: Siman Builds — residential construction & remodeling, Washington DC Metro Platform: Webflow Engagement: Fixed-price preferred, single defined build Timeline: Designs delivered ~[DATE]; build window [X] weeks from kickoff The job in one line We provide finished page designs as exported HTML/CSS from Claude Design . You build the complete Webflow site from them — the visual build and the CMS — collaboratively with us. We keep one piece in-house (the Zoho CRM mapping); everything else is yours. What you're building Visual build. Rebuild every page in the Webflow Designer, pixel-faithful to the supplied designs, including shared header, footer, and navigation. Responsive across desktop, tablet, and mobile, plus any interaction/hover states. CMS. Design and build the Collection structure — collections, fields, and reference relationships — for repeating content (e.g. portfolio/project pages, likely one template driving many items). Build the Collection Template(s) and bind Designer elements to the CMS fields. Populate structure, not final data. Set up the CMS so it's ready for content. We handle final item population and SEO field entry in-house (see below). Hand back a clean, publishable Webflow build. This is a collaborative build. We'll be involved in CMS decisions — you're not designing our data model in a vacuum — but you own the Webflow-side execution end to end. What the designs are — and what you'll build from Our pages are designed in Claude Design (Anthropic's AI design tool). You'll get three inputs that work together: Exported, standalone HTML/CSS — one file per page, including shared header/footer/nav. This is the build target: clean markup to rebuild faithfully in the Webflow Designer. The Claude Design pages themselves — the visual reference for layout intent, spacing, hierarchy, and overall feel. Content docs — the finished copy for each page. When the HTML and the visual reference differ, the HTML is the source of truth; the Claude Design pages exist to communicate intent, not to override the markup. Build to the HTML, use the visual reference to confirm you've captured the look. This is not a Figma handoff and not a live site to reverse-engineer. If you're expecting Figma, this isn't that. What stays in-house (out of scope for you) Zoho CRM mapping and integration. We handle how form/lead data maps to our CRM. You build the forms in Webflow; we own where the data goes. If you have a clean way to structure form fields so they hand off well to a CRM, we want your input — but the mapping itself is ours. Final content population and SEO fields. We load final copy, images into CMS items, and page metadata ourselves. You build the empty structure and templates; we fill them. Domain, DNS, redirects, publishing (we run the launch). What you'll receive at kickoff Exported HTML/CSS files for every page (from Claude Design), including shared header/footer/nav — the build target. The Claude Design pages as a visual reference for layout intent. Content docs — finished copy for each page. A page classification — which pages are standalone and which are templates driving CMS items. Final image assets and fonts — or a clear note where anything is still placeholder. Pricing note — read before quoting The full page/template inventory isn't final until the designs land ~[DATE], so we're not asking for a binding fixed price in your application. We're pre-qualifying now and will lock a fixed-price, fixed-scope quote once you've seen the actual files and we've agreed the CMS structure together. Because this is a collaborative build, scope discipline matters to both of us — we'll define the page and collection count up front so you can quote a fixed number rather than billing open-ended hours. Help us keep it tight and you'll get a job you can price confidently. Requirements Strong Webflow portfolio — live sites you built, not template installs. Demonstrated CMS work: you've designed collections, fields, and references, built Collection Templates, and bound elements to them. Point us to a specific example. Comfortable rebuilding faithfully from provided HTML/CSS rather than from Figma. Clean, responsive execution and attention to design fidelity. Collaborative and communicative — this build involves shared CMS decisions, not a black-box handoff. To apply — answer these (generic proposals will be skipped) Link one Webflow site where you designed and built the CMS yourself (collections + templates + bindings). Roughly how many collections and templates? Have you rebuilt a site in Webflow from exported HTML/CSS (not Figma)? How did you approach fidelity? Your pricing model — per page, per template, or a range — understanding we finalize scope together after you see the files.