Summary
You’ll have a site that loads quickly, stays readable and tappable on real phones, and gives you a frontend you can keep building on without rewriting everything after the first campaign.
I’ll build the screens so they hold up on mid-range Android phones and Safari, then I’ll fix the slow bits that show up on real connections. Next I’ll share a simple handover so you can change copy without calling a developer. Here’s how I’d run it and what you’ll get at the end.
I start from your Figma or existing pages and build clean HTML/CSS/JS or a React/Next.js frontend, depending on what you’re launching. I check the layouts on common screen sizes, tighten the CSS for mobile, then do a performance pass focused on Core Web Vitals and real-world load time. I keep changes small and reviewable so you can sign off page by page instead of waiting for a big reveal.
Who you are working with
I’m Amina Mwangi, a Frontend developer. I build landing pages, marketing sites, and product screens for teams that already have something working and now need the frontend to match. Most of my projects start the same way: design in Figma, a deadline tied to sales or onboarding, and a site that has to work on everyday devices, not just a fast laptop.
People pick me when they want fewer surprises at launch. I test on budget-to-mid Android and Safari early, because that’s where layout bugs and tap-target issues show up first. I also build with handover in mind, so changing a headline or swapping an image doesn’t turn into a small “dev project” every time.
Recent projects
A few recent frontend development builds that show mobile layouts, performance work, and clean handover on real projects.
Portfolio
B2B landing page build. Built a fast landing page from Figma with clear sections, mobile-first CSS, and lightweight JavaScript. Tightened font loading and image sizes so the page stayed quick on slower connections.
Marketing site (6 pages). Built a 6-page marketing site with shared components, consistent spacing, and a simple structure for future edits. Set up reusable page sections so new pages can be added without redesigning the whole site.
React product screens build. Converted approved designs into React components, wired up states and empty screens, and matched spacing and typography across the app. Focused on predictable component props so the backend team could plug in data quickly.
“The pages loaded fast on phones, and everything matched the design closely.”
Product lead, a small SaaS team
Built frontend pages
Your landing page, marketing pages, or product screens built in HTML/CSS/JS or React/Next.js, ready to plug into your backend or deploy as a static site.
RESPONSIVE LAYOUT SYSTEM
A consistent set of spacing, type sizes, and breakpoints so new sections don’t feel like one-offs, and mobile doesn’t turn into a separate design.
REUSABLE COMPONENTS
Buttons, headers, cards, forms, and page sections built as repeatable pieces, so future edits stay small and you can add pages without starting over.
Performance pass report
A short checklist of what I changed for speed, what I tested, and what still affects load time (like image weight or third-party scripts), so you can make informed tradeoffs later.
HANDOVER NOTES
Clear notes on how the frontend is structured, where to change copy and images, and what not to touch if you want to keep layouts stable.
LAUNCH SUPPORT FIXES
A short window for launch-day tweaks and bug fixes after you first publish, focused on layout issues, broken links, and device-specific surprises.
What it costs
Pick the tier that matches how many screens you need built and how much performance work you want me to do before launch.
Priced items
Next steps
If you want me to hold time for this frontend development work, the next step is to lock in dates and the build target.
1. Sign this proposal to book the slot. 2. Pay 50% to start the build. 3. Send Figma link, copy, and assets so I can begin.
Signature
Fee summary
Can you build it so it works on budget Android and Safari?
Yes. I build mobile-first and I test the layouts on smaller screens early, then I do a Safari pass for spacing, font rendering, and sticky elements. If something needs a fallback, I’ll show you the tradeoff before I lock it in.
IF I CHANGE COPY OR SWAP IMAGES LATER, WILL I BREAK IT?
You won’t break the site by changing text or images in the places I mark as safe to edit. I’ll structure sections so longer headlines wrap cleanly, and I’ll include notes on image sizes so you don’t accidentally upload a 10MB banner.
What do you need from me, and in what format?
I need your final copy, your logo files, and your brand colours and fonts if you have them. For design, Figma is ideal. If you have an existing site, I’ll also need the live link and any analytics or speed reports you’re looking at.
WHAT HAPPENS AFTER LAUNCH IF SOMETHING’S OFF?
After launch I keep a short fix window for things you only notice once it’s live, like a layout edge case on a specific phone or a missing redirect. If you want ongoing updates after that, I can quote a small monthly block of time.
Payment
50% is due to book the work when you sign. The remaining 50% is due when I hand over the finished frontend development. Invoices are payable within 14 days of the invoice date.
What I need from you. 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.
Feedback and approvals. You’ll get a working link to review during the build. I need feedback collected in one place, with screenshots where something looks off. I treat silence as approval for that round once the next step is due.
Changes to scope. If the scope changes, I’ll price the change before I start it, and I’ll only proceed once you confirm in writing. Common changes are extra pages, extra breakpoints, or new components not in the original design.
Handover
At handover you’ll receive the built pages or frontend code, plus my handover notes on safe-to-edit sections and image sizes. Once the final payment is made, you own the work I produced for this project.
Launch support. After launch I include a short fix window for issues that only show up live, like a layout edge case on a specific phone or a missing redirect. If you want ongoing updates after that, I’ll quote a monthly time block.
Testing limits. I test mobile-first and I do a Safari pass, but I can’t guarantee every device and browser combination. If a design detail needs a fallback for a specific browser, I’ll show you the tradeoff before I lock it in.
