Shane Barron Start a project

Blog / White label

Outsourced Web Development for Agencies That Keeps Your Mockup Intact

· 5 minute read · Shane Barron

Outsourced web development for agencies often fails at one place: the handoff. Your designer gets the client to approve a mockup. Then a developer rebuilds it, and the live site looks a little different. The fonts shift. The spacing grows. A button moves. The client notices, and your agency pays for it in revisions.

I work as the developer behind agencies, under the agency's name. My first rule on a mockup job is simple. The approved design is the design. My job is to make it real, not to improve it in secret.

Here is how I did that on a recent job, and how I check the result.

The job: a mockup that was already code

A wellness center sent a full interactive mockup. It had fourteen pages, a working menu, and a layout that already fit a phone. Someone had built it with an AI design tool and hosted it as a preview. The client wanted the real site in Wix. They also wanted to add classes and events themselves, without a developer.

Many developers would open the mockup in one window and rebuild it in another. That is slow. It also creates drift, because every section is a new chance to guess.

I read the mockup's source code first. It was one HTML page, one stylesheet, and one JavaScript file. The JavaScript drew every page. Inside it sat the content the client needed to manage:

  • 13 classes and events
  • the dates, times and prices for each one
  • 6 courses and certifications

Everything else was layout and style.

Keep the design, move the content

That told me the plan. I kept the client's HTML, CSS and JavaScript as they were. I moved the content into two Wix content collections: one for classes and events, and one for certifications. Then I changed only the few lines where the code set up that content. Now those lines read from Wix.

A small loader runs first. It asks Wix for the published entries, in date order. It passes them to the client's own script. Their script draws the pages the same way it always did.

The result is a site that is the approved design, with a real content system under it:

  • The class list sorts by date by itself.
  • The home page shows the classes the owner marks as featured.
  • Each class detail page comes from one shared template.
  • To add a class, the owner fills in one row in the Wix dashboard.

That last point matters to your client most. They do not call you to add an event. They do not call me either.

How I prove it matches

The client asked a fair question afterward: does it really look like the mockup? "It is the same code" is a good reason. It is not proof.

So I took full-page screenshots of the mockup and the new site. I used the same pages and the same browser width. Then I compared them pixel by pixel.

Page Mockup height New site height Pixels that differ
Home 3,633 px 3,633 px about 2,400 of 4.6 million
Classes and events 4,847 px 4,847 px about 2,400
Class detail 2,267 px 2,267 px about 1,300
Training 1,902 px 1,902 px about 2,400

The page heights match exactly. On the home page, the only visible difference is the small badge Wix shows in the corner. I also checked every page at phone width and at desktop width. Nothing ran off the side.

This is the kind of receipt I give an agency. You can forward it to your client as it is.

A second case: off WordPress, same look

Another job this week went the other way. A firm had a one-page site on WordPress. They wanted it as plain static files, with no plugins, no database and no PHP. Fewer moving parts means fewer things to patch and less to attack.

The rule was the same. Keep the look. I measured the live page in a browser: the column width, the gap under the logo and the text size. I also checked how the photo sits on a phone. Then I built the static page to those numbers.

At desktop width, the logo and text land in the same place as the live site. On a phone, the text size and line spacing match too. The client portal button and the regulatory PDF link point to the same addresses as before.

What this means for your agency

When you outsource development, you are trusting someone with your client relationship. The work has to look like what the client approved. It also has to keep working after the developer leaves.

This is what I bring as an agency development partner:

  • Your design, not mine. I build what the client approved. If I think something should change, I tell you first.
  • A content system the client can use. Classes, products, posts or listings go into the platform's own tools, so the client edits them without code.
  • Proof, not promises. I send screenshots side by side and the numbers behind them.
  • Your name on the work. I stay in the background. You keep the client.

I work in WordPress, Laravel, Wix, Shopify and plain static sites. The platform follows the client's choice. You can see finished sites on the work page.

Questions people ask

Can you build from a Figma file or an AI-made mockup? Yes. If the mockup is already code, I usually keep that code and connect it to the platform. If it is a design file, I build it to the measurements in the file.

Will the client be able to edit the site? Yes. Content that changes goes into the platform's own editor or dashboard. Layout stays in the theme, so an edit cannot break the design.

How do I know the build matches the mockup? I compare the two at the same width and send you the results. If a page does not match, I fix it before you see it.

Do you talk to my client? Only if you want me to. Most agencies keep me behind the scenes.

If you have a mockup waiting for a developer, read how I work with agencies on the white label page, or start a project.

Start a project

More posts

Ask a question.

Ask about white label work, a site, an app, hosting or a domain. You get an answer here in a few seconds.

Answers come from the site's automated assistant. For a price, send Shane the details.