Selling web development without a dev team: how the reseller model works

You want to sell web development work. You are good at winning clients, managing the relationship and knowing what they actually need. What you do not want is a dev team: the hiring, the salaries, the idle time between projects, the management overhead of people whose work you cannot fully check.

So you use freelancers, and you have felt the cost of that. One goes quiet mid-build. Another takes a full-time job the week before launch. A third disappears after handover, and when the client comes back three months later with a broken contact form, it is your name on the email and nobody on the other end of theirs. The continuity you promised the client is the one thing a freelancer roster cannot give you.

There is a cleaner way to sell web work without building it yourself, and it is not “hire developers” or “use a page builder”. It is the reseller model: you sell and own the client, a delivery partner builds under your brand, and you keep the margin and the relationship. Here is exactly how it works - who quotes, who carries the warranty, where the money sits, and what you still own.

One thing up front, because it is why we can write this plainly rather than in theory. We are the build team behind other agencies. About 60% of what we have shipped since 2008 went out under someone else’s brand, across 800+ projects and 437 clients. Reselling our work is the model a large share of our partners run, so what follows is the mechanics from the inside, not a pitch for a program.

What the reseller model actually is

The reseller model is simple: you sell the project to your client and own the relationship, a delivery partner builds it under your brand for an agreed cost, and you mark that cost up. You never hire a developer, never manage one, and never explain to a client why the person building their site is on holiday.

It is the same arrangement as white label development, viewed from the selling side. White label describes the partner staying invisible; reseller describes you earning a margin on their work. Two words for the two ends of one handshake. If you want the definitional version and how crediting works, we covered the trust side in the agency other agencies trust.

What makes it different from freelancers is not the price, it is the continuity. A freelancer is a person; a delivery partner is a standing team with a defined process, a fix window, and code another developer on their side can pick up if one is out. You are buying the promise that someone answers next month, which is the exact promise you make your client.

Who quotes, who builds, who talks to the client

The division of labour is the whole model, so make it explicit:

• You quote the client. You take the partner’s fixed cost, add your margin, and present one number under your name. The client never sees the partner’s price or the partner.
• The partner builds. Under your brand, on your deadline, to the scope you both agreed. Staging links carry your logo, not theirs.
• You talk to the client. Always. A good partner never contacts your client directly. All communication routes through you, or through a shared channel you control. This is the line that protects the relationship you spent years building.

The failure mode to avoid is a partner who treats your client as a lead. If a delivery partner reserves the right to market to, upsell, or “check in with” your client, they are not a reseller partner, they are a competitor you introduced to your best accounts. Rule that out in writing before the first project. A reasonable partner will already default to it.

Who carries the warranty when something breaks

This is the part every reseller-program marketing page skips, and it is the part that decides whether the model makes you money or costs you a client.

To your client, you carry the warranty. Full stop. That is not a burden to engineer away; it is the reason your margin exists. The client bought your name, your accountability and your response time, not an anonymous developer’s. If you outsource the liability along with the build, you have sold nothing worth a markup.

What a good partner does is make that warranty one you can actually keep. That means a defined fix window and a stated response time in your contract with them, so when the client’s form breaks at 4pm you are not hoping someone picks up. Our own support runs on this: 5,000+ support tasks handled in the last 18 months, urgent edits turned around in 1-2 hours. The client sees your brand answering fast; behind it is a partner obligated to answer you faster.

Two liability details worth settling early. First, the code has to be yours: clean, in git, built to the official WordPress coding standards or the equivalent for the stack, so a second developer could maintain it if the partnership ever ended. A build you cannot take with you is a warranty you cannot honour. Second, for European clients, keeping the work inside the EU keeps their data under GDPR jurisdiction rather than wherever a hidden subcontracting chain ends up - a compliance fact your client is right to ask about, and one you can only answer if you know who actually touches the code.

Where the margin actually sits

The margin is the spread between what the partner charges you and what you charge the client. In our experience a markup around 50 to 75% on partner cost is normal and defensible, for the reason above: the client is paying for your relationship, your accountability and your warranty, not just the build hours. If your only edge is that you found a cheap builder, the client could have too. Sell the accountability, price it accordingly. We broke the underlying numbers down in white label WordPress development pricing.

The steadier money is not the build, it is what comes after it. A one-off site is one margin, once. A care plan resold under your brand is a margin every month, for years, with almost no additional selling. Partner maintenance typically runs 150 to 300 EUR per site per month, which you mark up and resell as your own managed service.

That recurring line is also the one your client needs most, whether they know it or not. Patchstack recorded 11,334 new WordPress vulnerabilities in 2025, 91% of them in plugins. Every site you sell needs those patches tested and applied by someone, forever. Reselling the care is how you turn a project into an annuity instead of handing the aftercare - and the next rebuild conversation - to whoever the client finds when something breaks. We walk through the resale mechanics in reselling care plans under your brand.

Why freelancers are the expensive version of this

Freelancers look like the cheaper path to the same place. Per hour, they are. Over a client relationship, they are usually the most expensive option you can pick, for one reason: they are built for a project, and your client is a relationship.

The math that hides this: a freelancer who is cheap per hour but unreachable in month four costs you a scramble to find a replacement, a second developer’s time to understand undocumented work, and a client watching you fail to deliver on the continuity you promised. Now weigh that against a partner priced higher but obligated to be there. The higher number is the lower total cost, because the work does not come back and the client does not walk.

None of this means freelancers are never right. It means they solve a different problem - a defined one-off task, not a standing promise to a client - which is the honest line the next section draws.

How to start reselling without getting burned

Vetting the partner is the entire risk, so spend your diligence there:

1. Confirm they stay invisible. No direct client contact, your brand on everything, in writing. If they hedge on this, stop.
2. Get the fix window and response time in the contract. The warranty you resell is only as good as the one they give you. Vague “we’ll sort it” is worth exactly nothing at 4pm on a Friday.
3. Check who actually writes the code. A partner who quietly re-posts your brief to a marketplace is a subcontracting chain with your name on the risk. Ask, and ask who is accountable when it breaks.
4. Confirm the code is yours. In git, documented, maintainable by someone else. Test this with a real question: “If we parted ways, could our next developer pick this up cold?”
5. Start with one real project, not a framework agreement. A small live build tells you more about a partner than any sales call.

We wrote the full version of this as a checklist we pass publicly: how to choose a white label WordPress agency. The same questions vet a reseller partner.

When reselling is the wrong call

Two cases where the model does not fit, because honest limits are part of the pitch.

If web development is becoming your actual product - if you want to build a real dev capability, own the craft, and compete on it - then reselling is a stage to grow out of, not a destination. At some point you hire, and that is the right call for an agency whose identity is the build.

And if the work is genuinely throwaway - a campaign microsite live for six weeks then gone - a good freelancer is simpler and cheaper, and there is no relationship to protect. The reseller model earns its margin precisely when the site has to live, get maintained, and keep a client happy for years. That is most client work, which is why it is the default worth building your business around.

We build under other agencies’ brands across Europe and North America - you sell and own the client, we build and back the work, NDA by default. If that is the model you want to run, that conversation starts here, and our work is the long version of what your clients would be buying.