It covers the frontend development described in the accepted proposal, including the screens, layouts, and performance work needed for a site that holds up on mid-range Android phones and Safari.
If anything in the proposal and this agreement pull in different directions, I will flag it before I start. Once you sign and the booking payment is in, I’ll schedule the work and run the project on the terms below.
What I’m building
Frontend development means I build the user-facing pages and UI based on your designs and content, then I test and tidy it so it behaves on real phones and typical connections. The deliverables for this project are listed below, and anything not on that list is not included unless we agree a change.
To start cleanly, I need your final copy, logo files, and brand colours and fonts if you have them. If there’s a Figma file, share access. If there’s an existing site, send the live link and any speed reports so I can target the right fixes.
* Built frontend pages * Responsive layout system * Reusable components * Performance pass report * Handover notes * Launch support fixes
Payment
To book the work, you pay 50% of the agreed price when you sign. I’ll then lock in the project slot and start once I have what I need from you. The remaining 50% is due when I hand over the finished frontend development.
I invoice in USD, and each invoice is payable within 14 days of the invoice date. If an invoice becomes overdue, I’ll pause work and any planned handover until the account is up to date. If a launch date is coming up, tell me early so we can avoid a last-minute rush caused by payment timing.
Reviews and changes
My process includes two revision rounds. A revision round means you review what I’ve built, collect feedback in one place (with screenshots where something looks off), and I apply those changes within the agreed scope.
I’ll share a working link during the build so you can check progress. If I ask for feedback by a certain date and I don’t hear back, I treat silence as approval for that round once the next step is due, so the schedule does not stall. Changes beyond the two rounds, or changes that expand scope, are quoted and agreed in writing before I do them.
Who owns what
Once the final payment is made, you own the frontend work I produced for this project. That includes the built pages and the frontend code I deliver at handover. You can use it, edit it, and ship it as part of your product or marketing site.
What I keep are my own tools and building blocks that I already had before this project or that I use across projects, like starter setups, utility snippets, and my personal templates. I may also keep working files and drafts that help me do my job, but I will not reuse your branding, copy, or unique design in someone else’s work.
Portfolio use
Unless you ask me not to, I can show the finished work as part of my portfolio. In practice, that usually means a link and a couple of screenshots, and sometimes a short note about what I built (for example: Figma-to-code, responsive rebuild, or a Core Web Vitals pass).
If the site is not public yet, or you’re working under a quiet launch, tell me and I will wait. If you want a strict no-portfolio arrangement, send it in writing before launch or handover, and I’ll honour it with no questions asked.
What I’m responsible for
I’ll build carefully and test mobile-first, including a Safari pass, but I can’t promise the site will look identical on every device and browser combination. If a detail needs a fallback for a specific browser or phone, I’ll show you the tradeoff before I lock it in.
I’m responsible for the frontend development I deliver, and I’ll fix issues that come from my code during the included launch support fix window. I’m not responsible for outages, hosting problems, analytics or ad platform issues, third-party scripts you add, or changes someone else makes after handover that break layouts or performance.
Ending the project
Either of us can end the project by giving notice in writing. Because timing affects booked work, I prefer to agree the notice period with you in writing when we kick off, so it matches your launch reality and my schedule.
If the project ends, you pay for the work I’ve completed up to the end date, including any non-refundable costs we agreed in advance. Once any outstanding invoices are paid, I’ll hand over what’s ready in a usable state (for example: the current code, built pages, and notes), and I’ll explain what remains unfinished so you can continue with me later or hand it to another developer.
Signature
