How to Turn a Figma Design Into a Freelance Frontend Estimate

Follow a three-page Figma project from design review to a client-ready quote. Use the editable worksheet to estimate development hours, compare scope changes and calculate your fee in BDT.

A freelance frontend estimate turns a Figma design into a list of things you will build, connect, test and hand over. Count shared components once, estimate each distinct layout, then add the work a static frame cannot show. In the example below, a three-page website with one enquiry form takes an estimated 28–43 hours. The worksheet shows where every hour comes from and which answers could change the total.

Imagine a client sends you six frames for a small training company. Three show desktop pages and three show their mobile equivalents. The home page looks polished, the services page repeats the same card six times, and the contact page contains only four fields. Before you quote, ask one question: what should happen when someone submits that form? A simple email link, a hosted form and an integration with the client’s admissions system can all look identical in Figma.

This guide follows that brief from the first design review to a message you can send the client. It fits into Blogerhub’s freelancing skills guide. If you are choosing your first service or preparing to work with a client in Bangladesh, start with the freelancing hub.

What belongs in a freelance frontend estimate?

A useful estimate names the deliverable, the quantity, a low and high number of hours per unit, and the assumption that makes those numbers reasonable. “Contact page: four hours” leaves the buyer guessing. “Assemble the contact layout using approved components; form behaviour and submission are priced separately” tells both parties where those four hours stop.

Separate effort from price and delivery date. Effort is your working time. Price depends on the rate or fixed fee you agree. Delivery also depends on your availability, client feedback and access to other people’s work. Someone freelancing after an office job might spend the same number of hours as a full-time contractor and still need a different delivery date. Give each figure its own label when you send the estimate.

1. Read the Figma file like a specification

Start by listing the pages a visitor can reach. Open the prototype from the home page, follow the primary navigation and try each main action. In the training company example, the visitor can browse services and submit an enquiry. A course card appears six times, but the prototype never opens a course detail page. Ask whether the cards should lead to new pages. Six unshown detail pages would change the brief substantially.

Next, record which version you reviewed. Save the design link, review date and the names of the approved frames in your proposal. If the designer later replaces a pricing section with an interactive comparison tool, you can point to the original agreement and estimate the new behaviour. A date and a short list of sections are also useful when the client does not use formal version names.

Send questions that change the hours

Ask who supplies the final copy and images, which screens have mobile designs, where form data goes and who signs off on delivery. Make the questions concrete. Instead of asking whether the content is ready, ask for the longest service name and a real example of the description. A layout that fits “Web design” may break when the client enters “Corporate training for distributed engineering teams.”

For each open question, write down your temporary assumption and what happens if it changes. For example: “Estimate assumes six service cards with a common layout and final copy supplied before development. Filtering or individual detail pages would be estimated separately.” The client can now correct one sentence before it becomes several days of work.

2. Count components, page assembly and interactions separately

On a first pass, mark everything you expect to reuse: header, footer, buttons, service cards, form fields and feedback messages. For each component, list the variations that require different behaviour. A blue button and a green button may share one implementation. A navigation link that expands a submenu needs interaction work even if it uses the same colours and typography as the other links.

In this example, the shared-component row covers the header, footer, button set and service card. The developer builds the card once and uses the approved data to display six instances. The page-assembly row then covers arranging those components, adding page-specific content and wiring navigation on three pages. This keeps repeated cards from inflating the quote and preserves the time needed to put each page together.

Decide what you can actually reuse

Suppose your React project already includes a button component. Open it before offering the client a saving. Does it support a loading state? Can a link look like a button without breaking keyboard behaviour? Does it match the project’s font and spacing? If the component fits, reduce the relevant build hours. If it needs changes, estimate the changes and a quick regression check on screens that already use it.

Use the same reasoning for a WordPress theme or a purchased component library. A prebuilt header might save implementation time while still requiring mobile menu work and checks with the client’s actual menu labels. “We already own the theme” answers a purchasing question. You still need to find out how much of the design that theme can deliver.

3. Estimate responsive work between the frames

Desktop and mobile mockups show two points along a range of widths. Drag a sample layout from wide to narrow and ask what should happen in between. When does the navigation become a menu? Do three service cards become two before becoming one? Which content should move first when the heading wraps? Write those decisions as short acceptance notes a client can recognise on a preview link.

The worksheet allows one to two hours per page for responsive work after assembly. That range assumes the mobile design already exists and the content order is agreed. It covers implementing the adaptations and checking the layout during development. The separate QA row covers the final integrated site. If a client provides only desktop frames and wants you to design the mobile experience, add a design task with its own approval step.

Count hidden states with a small interaction list

For the enquiry form, write down what a visitor sees before typing, after leaving a required field blank, while waiting for the server, after success and after failure. Include one specific retry decision: if the connection fails, should the visitor keep the message they typed? Rebuilding a form that discards a long enquiry after an error is easy to underestimate during a visual review.

Assign each state to one owner in the estimate. The form-interaction row pays for labels, local validation and visible feedback. The API row pays for sending the request and mapping the server response into those states. The QA row pays for testing that the complete journey works. This distinction is especially helpful when a designer, frontend developer and backend developer all contribute to the same form.

4. Price the API work you can describe

Ask the backend owner for a sample request, a success response, a validation error and a test environment. Then describe the integration in plain English: “Send name, email, subject and message to one existing enquiry endpoint. Show field-level errors when supplied and keep the message available for retry.” That is specific enough for another developer to review and for a client to test.

The sample assigns three to five hours to one documented endpoint. It assumes a usable test environment and an existing backend that accepts the agreed fields. Creating the endpoint, configuring email delivery, building a staff inbox and adding authentication would each be separate work. If your client has no backend developer, say who will investigate those items before quoting the integration.

Offer a useful fallback when the API is late

Give the client a choice about sequencing. You can build the form against agreed sample responses and demonstrate its states while the backend is being finished. Make clear that live integration and an end-to-end submission still remain. Agree who will provide access and when you will schedule the final check. This lets the project move forward without promising a production-ready form on a date outside your control.

5. Fill in the frontend estimate worksheet

The table uses a deliberately small scope: approved desktop and mobile designs, three public pages, one service-card pattern, one documented enquiry endpoint and one consolidated feedback round. Each total is quantity multiplied by hours per unit. The figures are illustrative estimates you can replace with your own delivery history.

Work itemQuantityHours per unitTotal hours
Design review12–32–3
Shared components15–75–7
Page assembly32–36–9
Responsive work31–23–6
Form interaction13–43–4
API integration13–53–5
QA and fixes14–64–6
Review and handover12–32–3
Total28–43

Three pages at two to three hours per page produce six to nine assembly hours. Adding the eight work rows gives 28 hours at the low end and 43 at the high end. The upper end allows ordinary variation within the stated scope, such as resolving awkward navigation wrapping or correcting a validation response. A new booking system or a fourth page changes the scope and deserves its own row.

In the editable worksheet, change the blue quantity and unit-hour cells first. For a four-page version with the same components and form, change both page assembly and responsive work from three to four. This adds three to five hours and moves the total to 31–48 hours. If the fourth page includes a new interactive price calculator, adding one page alone would miss most of the work. Estimate the calculator separately.

6. Convert hours into a fee and delivery window

At an illustrative rate of BDT 1,000 per hour, the original 28–43 hours produce a fee range of BDT 28,000–43,000. Replace that example rate with one that makes sense for your own business. If you are deciding what to charge a Bangladesh-based client, the freelance pricing guide covers rate setting. Keep third-party costs, hosting and ongoing maintenance explicit when they apply.

To estimate the schedule, divide the hours by the focused time you can actually give the project each working day. At five focused hours a day, the worksheet rounds the range up to six to nine working days. Client approval, weekends or delayed assets may extend the calendar window. If you have two hours each evening, change the daily capacity to two. The same work now occupies 14 to 22 working sessions.

What if the client asks for a fixed quote?

First settle the uncertainties that carry the most hours. In this example, seeing a working API response and agreeing on the mobile menu will narrow the range more than discussing the button colour. Then choose a fixed amount you are comfortable delivering for the written scope. State the number of review rounds, what counts as a correction and when you will price a new request.

If the client’s budget is lower, offer a specific change they can evaluate. For example, they might launch with an agreed hosted enquiry form and defer custom submission behaviour until a second phase. Recalculate the integration, form and QA rows together. A hosted form introduces its own setup and testing, so deleting the entire form allowance would give a misleading saving.

7. Include QA, revisions and handover before sending the estimate

Define a short delivery test while you still have the design open. For this example, the agreed checks could include navigating the header using a keyboard, reading the services page on a narrow screen, submitting the form successfully and recovering from a failed request. Name the browser and device coverage you will check with the client. Record anything that depends on a device or account they need to supply.

Define one revision round as one consolidated list from the person approving the work. Correcting a button that fails the agreed acceptance test belongs to delivery. Adding a testimonial carousel after approval is a new request. During handover, give the client the preview or production link as agreed, a note about the form destination, and instructions for changing the service text. Put these small tasks in the estimate so the last stage has time reserved.

A client-ready freelance frontend estimate

You can adapt the following message after checking the actual design. Replace the assumptions and hours before you send it. The client should be able to answer your open question without understanding React, CSS or the internal names of your components.

“Thanks for sending the home, services and contact designs. I estimate 28–43 hours to build the three responsive pages, connect the enquiry form to your existing endpoint, test the agreed user journeys and complete one feedback round. At BDT 1,000 per hour, the estimated fee is BDT 28,000–43,000. I can allocate five focused hours per working day, which gives six to nine working days of development and review work. Please confirm that the service cards stay on the services page and send a sample form response. Once I have those details and the final content, I can confirm the scope and start date.”

How do you know whether your estimate was accurate?

After delivery, compare estimated and actual hours by work item. Suppose page assembly took seven hours, comfortably inside its range, while API integration took eight because the documented validation response differed from the real response. Increasing every future estimate would make simple layout work look expensive. A better adjustment is to request a working error example earlier and record the integration delay against that task.

Keep a short note on what you learned from the comparison. If you later present the work in a freelance portfolio case study, explain one assumption you tested and one decision it changed. For the next freelance frontend estimate, that record gives you something more useful than a generic hourly benchmark: your own evidence for how long a familiar task takes under clearly described conditions.

Razib Chandra Ghosh

Editor at Blogerhub

Razib Chandra is the founder of BlogerHub, a website focused on helping people learn how to earn money online and build sustainable digital income streams.He writes about online income, remote jobs, blogging, SEO, and Google AdSense strategies. Through practical guides and tutorials, Razib shares real methods, tools, and insights to help beginners start earning money online and grow profitable websites.

Reviewed for accuracy · No unrealistic income claims

← Previous
How to Withdraw Upwork Earnings to bKash or Nagad in Bangladesh
Next →
WordPress Website QA Checklist for Freelancers Before Client Delivery