Summary

Process

FAQs

• What kind of design files do you need to start?

  We work best with clean Figma files, ideally with consistent naming and layout structure. Not perfect? No worries — we can help tidy up the layers if needed.

• Do you support components, style guides, or variables?

  Yes. Every build is structured with reusable components, CMS collections, and native Webflow variables — so your project stays organized and future-proof, even after handoff.

• Do I need to prep anything before development?

  Just the approved Figma files and page scope. We'll handle setup, CMS logic, and handoff prep. Need input during design? I can jump in pre-handoff too.

• How do we collaborate during the project?

  We work async via Slack, Notion, or your preferred tool. You'll get regular updates, build previews, and check-ins without being left wondering.

• Do you handle custom code or third-party integrations?

  Absolutely. we support most clean custom scripts (e.g., filtering, logic-based behavior), Webflow-compatible integrations (e.g., analytics, email, forms), and CMS syncs where needed.

• How long does a typical build take?

  Single-page builds: 3–7 days. Multi-page builds with CMS and logic: 1–2+ weeks, depending on scope. Delivery windows are defined clearly in your proposal.

• Can I request post-launch edits or retainer support?

  Yes — we offer monthly support plans for updates, maintenance, CMS changes, and component additions. You can scale up or pause anytime.

• Can you join mid-project or late in the design phase?

  Yes — as long as it’s in Webflow, We're in. Mid-design, mid-build, or post-handoff — We slot in fast, clean things up, and carry the project through with structure and zero dev chaos. Just hand us the katana.