SoftVolt AISoftVolt AI
From the blog

Notes from the people doing the work.

Scoping decisions, build notes and the reporting agencies forward to their clients — written up as the job finishes.

Figma to WordPress for Agencies: Process and Pricing

How to turn a Figma design into a WordPress build for a client, what affects the price and how agencies hand this off cleanly.

Published
Updated
Written by
Md Alamgir Hossen
Reading time
7 min read

Figma to WordPress for agencies works best as a fixed sequence. Turn the design’s variables into tokens, map each component to a block or Elementor widget, and build templates. Then check every screen width and WCAG 2.2 before launch.

The price depends on unique templates and components far more than on page count. When we build an approved Figma file on WordPress, we send a fixed-price scope within two business days of the brief.

Here is the process step by step, what changes the price and how we scope it.

What to hand over with the Figma file

Most delays on a Figma to WordPress build start with a missing file, not with code. Before we price a build, we check the handover for these:

  • Approved frames for mobile, tablet and desktop, with the date of sign-off
  • Components with their variants and states: hover, focus, error, empty and loading
  • Variables or styles for colour, type and spacing
  • A list of templates, such as home, service, blog post, archive and contact
  • Real copy, or at least real lengths for headings and product names
  • Font licences and image rights for web use
  • Who edits the site after launch, and how often
  • Forms, CRM and tracking needs, plus a list of old URLs that will change

Client names can wait until you have the NDA. We turn anything missing into a question in the scope, so nobody prices a guess.

What we flag in the file before pricing

Some design choices cost more to build than they look. We point these out in the scope, with a cheaper option where one exists:

  • Text set inside images, which editors cannot change and screen readers cannot read
  • One-off spacing and colour values that match no token
  • Hover effects with no tap equivalent on phones
  • Fonts licensed for print but not for the web
  • Components edited by hand instead of through a variant
  • Cards that break when a heading runs long or a translation is wordier

Step 1: Turn Figma variables into design tokens

Figma stores raw values such as colours, numbers and strings as variables, grouped into collections with modes. Figma’s overview of variables, collections and modes explains how aliasing one variable to another lets a team implement design tokens.

We copy those tokens into WordPress once, before we build any page:

  • Block themes: colours, font sizes and spacing become presets in theme.json. WordPress then outputs each preset as a CSS custom property, which the editor and the front end share. The WordPress theme handbook on presets explains how.
  • Elementor: tokens become global colours and global fonts. Elementor provides four default colours and four default typography sets. A custom widget control can inherit them through its global argument, as Elementor’s developer docs on global styles explain.

With the tokens in place, a later brand colour change takes one edit instead of fifty.

Step 2: Map each component to a block or widget

Choose the build approach by who edits the site and how much layout freedom they need. The scope names the approach and the reason.

Figma element Custom theme with ACF Block theme Elementor
Colour, type and spacing variables CSS custom properties in the theme theme.json presets Global colours and fonts
Repeated sections such as heroes and cards ACF field groups in fixed templates Custom Gutenberg blocks Custom widgets in a plugin
Headers, footers and archives Theme templates Block theme templates Theme builder templates
Who it suits Editors who fill in fixed layouts Editors who rearrange pages Teams who already use Elementor

Each Figma component becomes one block or widget, built once and reused. We give it the same name in code as in Figma, so your designer and our developer talk about the same thing.

Custom Elementor widgets expose only the controls the design allows, so editors change text and images while spacing and structure stay fixed. If Elementor cannot reproduce a component cleanly, the scope flags it and suggests a custom widget or a small design change.

Step 3: Build templates, then pages

We build a blog post template once, whether the site has 10 posts or 500. So we build and review each template before we fill in pages, and you sign off per template rather than per page.

We register image sizes per template and give every changed URL a tested redirect. Editor roles let the client’s team publish and edit, while plugin installs and theme settings stay with an administrator.

Step 4: Check every width, not just three frames

Figma shows the frames your designer drew, usually three. A browser shows every width in between, and that is where layouts break.

We compare each built page with your frames side by side, then drag the window through the widths between them. We test on real phones and tablets as well as in desktop browsers.

WCAG 2.2 sets two checks here. Content must reflow at a width of 320 CSS pixels without scrolling in two directions. Text must also resize to 200 percent without losing content or function.

Step 5: Test accessibility against WCAG 2.2 AA

WCAG 2.2 became a W3C Recommendation on 5 October 2023. The W3C’s summary of what’s new in WCAG 2.2 lists nine new success criteria. Several catch problems that start in the Figma file, so we check the design first and the build again.

  • Text contrast: at least 4.5:1, or 3:1 for large text (1.4.3).
  • Non-text contrast: at least 3:1 for input borders, icons and other parts of the interface people need to see (1.4.11).
  • Visible focus: keyboard users can always see where they are (2.4.7). Sticky headers and cookie banners must not hide the focused item completely (2.4.11, new in 2.2).
  • Target size: tap targets of at least 24 by 24 CSS pixels, or enough spacing around smaller ones (2.5.8, new in 2.2).
  • Dragging: sliders and drag-to-reorder lists also work with a single tap or click (2.5.7, new in 2.2).
  • Forms: every field gets a label, and multi-step forms do not ask for the same information twice (3.3.7, new in 2.2).
  • Structure: headings, lists and tables use real markup, so screen readers get the structure sighted visitors see (1.3.1).

Automated tools catch some of these. Focus order, reflow and target spacing need a person with a keyboard and a phone.

Step 6: QA, staging and launch

The build lives on a password-protected, noindexed staging site under your brand from the first day. A named producer posts progress in your shared Slack Connect or WhatsApp channel.

Before you see it, the build passes our published QA checklist: cross-browser, real-device, accessibility and Core Web Vitals checks. At launch we test redirects, forms and tracking that waits for cookie consent, then hand over an editing guide in your brand. We remove the staging site within 14 days of launch unless you ask us to keep it.

Figma to WordPress for agencies: what drives the price

Page count is a weak guide to price. A 40-page site built from five templates can cost less than a 12-page site where every page is unique. These factors move the price most:

  • the number of unique templates
  • the number of components and states to build
  • the editing approach: ACF fields, custom blocks or custom Elementor widgets
  • forms, CRM and other third-party integrations
  • how much content we migrate or enter
  • store logic, such as subscriptions, bundles or custom shipping
  • a deadline shorter than the normal turnaround

We bill premium plugins and Elementor Pro licences at cost, or you hold them in your own account. Either way, we add no mark-up.

How we scope a Figma to WordPress project

  1. You share the Figma file, the prototype and the brand system.
  2. We ask the missing questions on a short scoping call.
  3. Within two business days, you get a written scope: platform, component list, timeline and a fixed price.
  4. Nothing starts until you approve it, and we price any change in writing before anyone builds it.
  5. You sign off each template, and we fix post-launch defects in the agreed scope at our cost.

Builds can also run inside a monthly plan. Essential, from £500 a month, covers WordPress and WooCommerce builds of up to 5 pages per project. Growth (from £1,200) and Premium (from £2,400) raise the limit to 10 and 15 pages and run more projects at once.

Send us the Figma file

If you have an approved design, our white-label WordPress development team builds it with ACF templates or custom blocks. Our white-label Elementor development team builds it with custom widgets and global styles instead.

If you only have a brief, our white-label web design team produces the Figma file first, and the same team builds it. Send us the Figma link with the date you promised your client. You get a written scope and a fixed price within two business days.

Comments

No comments yet. Yours would be the first.

Leave a comment

Your email is not published. Comments are read before they appear, so give it a few hours.

Not published.