Because this package focuses on development rather than design, the project begins with the client providing a finalized landing page design. In most cases this is delivered as a Figma file that includes desktop and mobile layouts, along with any required assets such as images, icons, brand fonts, or supporting media. The development process works best when the design has already been reviewed and approved internally before implementation begins. This ensures the focus of the project remains on building the page accurately rather than revisiting earlier design decisions.

The standard timeline for this package is 1 week. This timeframe assumes the design files are finalized and ready for development when the project begins. Because the work focuses on implementation rather than design exploration, the timeline can move quickly once the design handoff is complete. If additional functionality, interactions, or scope changes are introduced during development, the timeline may extend accordingly. An expedited timeline may also be possible if the launch schedule requires a faster turnaround.

This package includes 2 revision rounds. A revision round is a structured feedback cycle where you review the implemented landing page and provide consolidated feedback so any adjustments can be addressed before final delivery. In a development-focused project, revisions typically relate to implementation details such as spacing adjustments, responsive behavior, interaction behavior, or small visual refinements. The revision process is intended to ensure the page reflects the provided design accurately rather than introducing major design changes.

This package focuses specifically on implementing an existing design rather than redesigning the landing page itself. Minor adjustments sometimes occur during development when translating designs into responsive layouts or interactive components, but broader design changes or layout exploration are outside the scope of this package. If the design needs to be significantly revised or expanded during the project, that work can be scoped separately so the development process remains focused and efficient.

Yes. The completed site is delivered through a Framer Remix Link, which allows the full project to be transferred directly into your own Framer workspace. This means the site ultimately lives in your environment rather than someone else’s account. Once transferred, you’re free to edit, expand, publish, or hand the project off to another collaborator whenever you need.

Yes. Because the site will live in your Framer workspace, you’ll need an active Framer plan to host and manage it after delivery. The right plan depends on the size and needs of the site, but in most cases this is straightforward and I’m happy to advise if needed. Keeping the site under your own subscription also ensures you retain full ownership and control.

Post-launch support includes a 7-day support window covering minor layout adjustments, small content updates, bug fixes, and light clarification around the Framer setup if anything needs attention after launch. This period is intended to address practical issues that appear in the live environment rather than reopening strategy, redesigning the site, or expanding the original scope. If additional work is needed beyond the support window, it can always be scoped separately.

Payments are handled securely through Contra’s platform. When a project begins, the agreed project fee is funded through the platform so work can start immediately. The platform then manages the release of funds as the project progresses and once the final site has been delivered. This structure ensures the project can move forward smoothly while providing clarity and protection for both sides.