Marketing site — agency handoff
Northlight Studio — read the case study
A 14-page marketing site built from a finished Figma file, with a filterable resource library.
Bricks Builder development partner
You design it.
I build it.
I build WordPress sites in Bricks for design, branding, and marketing agencies — working from your finished Figma file, so what ships matches what you approved.
Available for white-label work, project builds, and ongoing development.
Figma → Bricks
Approved designs implemented as designed
Dynamic WordPress
Custom post types, fields, query loops
Global Classes & Variables
One system, not per-element styling
Performance
Fast on real devices, not just in tests
Accessibility
Keyboard, contrast, semantics
Agency Support
White-label and ongoing development
Selected work
Builds, and what went into them
Screenshots only tell you a site exists. These describe what the implementation actually involved.
White-label build for a branding agency
Meridian — read the case study
A component-driven site built behind the scenes for a branding agency, delivered under their name.
Existing Bricks site — rebuild and repair
Atlas Field Services — read the case study
An inherited Bricks site restructured into a maintainable system and brought up to standard.
Why work with me
What you actually get when you hand over a build
I work as a development partner rather than a subcontractor you have to manage. Most of my work is white-label, under your agency's name.
01
Your design stays your design
I build what was approved. If something in the file is ambiguous or breaks down at a certain width, I raise it and we decide together — rather than reinterpreting it halfway through the build and handing back something you have to re-review.
02
Built as a system
Global classes, variables, reusable components, and templates. Spacing and type come from defined values, so a change happens in one place instead of on forty pages.
03
Comfortable beyond the builder
When a requirement goes past what the builder does natively, it gets solved with CSS, JavaScript, PHP, or an API — not worked around with a plugin that becomes someone else’s problem later.
04
Built for handoff
The finished site should make sense to whoever opens it next, including your team or your client. Predictable naming, documented components, and content that is editable without touching layout.
How a build is structured
A site is a system, not a stack of pages
Every project gets built in these four layers. Select one to see what it covers.
The values everything else is built on, defined once.
- Global Classes
- CSS Variables
- Type & Spacing Scale
- Breakpoints
Repeated patterns built once and reused, not copied.
- Reusable Components
- Nestable Elements
- Interactions
- Custom Code
Content that editors control, wired into the layout.
- Custom Post Types
- ACF / Meta Box
- Query Loops
- Conditions
What turns a layout into a site you can hand over.
- Templates
- Performance
- Accessibility
- Integrations
How I work
From your file to a site you can hand over
Five steps. You always know which one we are on.
01
Send the design
Figma file, functionality notes, and any content or integration requirements. I come back with questions and a fixed quote.
02
Architecture
Before building: which patterns become components, what needs to be dynamic, which fields and post types are required, how templates are structured.
03
Development
The build, with responsive behaviour and integrations handled as I go. You get a staging link early and can follow progress.
04
QA
Cross-browser and cross-device testing, keyboard and contrast checks, performance review, and a pass against the original design file.
05
Handoff
Documented components and editing notes, then a support window. I stay available if you want an ongoing development partner.
Services
Ways agencies work with me
Defined engagements rather than open-ended 'web development'. If your project sits between two of these, describe it and I will tell you which fits.
Figma → Bricks development
A finished design turned into a complete, responsive WordPress site.
- Full template build
- Component and class system
- Dynamic content setup
- QA and handoff
White-label agency development
I work as the development arm behind your agency, under your name.
- Direct or via your PM
- Your staging environment
- No client-facing presence
- NDA on request
Bricks support & retainer
Ongoing development for sites already in the world.
- New pages and components
- Fixes and improvements
- Content structure changes
- Monthly or ad hoc
Advanced WordPress development
The work that goes past what the builder handles natively.
- Custom PHP and JavaScript
- API integrations
- Complex query and filter logic
- Performance work
Portrait
About
I care about what the build looks like from the inside
I have spent my time in WordPress getting good at one thing: taking a design that is already decided and building it properly. Bricks is where I work day to day, but the part that matters is what happens underneath — how components are structured, where values are defined, what an editor can change without breaking a layout.
Performance and accessibility are not extras I quote separately. A site that loads slowly or cannot be used with a keyboard is not finished, so that work is part of the build.
The problems I enjoy most are the awkward ones — filtering that has to work three ways at once, content models that need to stay simple for the client, an inherited site that needs restructuring while staying live. If you have a design and need someone to take responsibility for turning it into a working site, that is the job I want.
FAQ
Questions agencies ask first
Do you work white-label?
Yes — most of my work is white-label. I can stay entirely behind the scenes, work in your staging environment, communicate through your project manager, and sign an NDA if you need one.
Can you work directly from Figma?
Yes. A Figma file with defined styles and reasonably structured frames is the ideal starting point. I inspect it directly rather than eyeballing exported images, and I will flag anything ambiguous before building instead of guessing.
Do you only work with Bricks Builder?
Bricks is my primary environment and where I am strongest, so it is where you get the most value from working with me. I also work in WordPress more broadly — custom code, integrations, and existing sites built other ways.
Can you work on an existing Bricks website?
Yes, and it is a common request. That covers new pages and components, fixing inherited structural problems, migrating per-element styling into a global class system, and performance or accessibility work.
Can you build dynamic WordPress websites?
Yes. Custom post types, custom fields with ACF or Meta Box, query loops, filtering, conditional content, and templates that let your client manage content without touching layout.
Do you handle custom code?
Yes — CSS, JavaScript, and PHP as required. When a requirement goes past what the builder does natively, it gets solved properly rather than approximated with an extra plugin.
Can you work with our existing design system?
Yes. If you already have tokens, a type scale, spacing rules, or a component library, I implement against them so the build stays consistent with the rest of your work and stays consistent as you extend it.
Do you provide ongoing support?
Yes. Every project includes a support window after handoff, and I can continue on a retainer or ad hoc basis if you want a developer who already knows the site.
How do you price projects?
Fixed price per project for defined scope, based on the design file and requirements — so you know the cost before work starts. Ongoing support is monthly or hourly. Send me the design and I will come back with a quote.
Start a project
Have a design that needs building?
Send the Figma file and a short note about what it needs to do. I will come back with questions, a timeline, and a fixed quote — usually within two working days.
Prefer email? avinashdhauni36@gmail.com