The Freelancer’s Guide to Taking On Bigger WordPress Projects

A prospect describes a project worth four times your usual invoice. It needs a custom theme, a WooCommerce build with subscriptions, a migration off a legacy host and a launch date you could hit only by cloning yourself. You could refer it away, or you could take it and become the freelancer who learns to outsource WordPress work instead of turning revenue down.

This guide covers how to decide whether a big project is worth taking, how to scope and price it so the risk is survivable, how to bring in delivery help without pretending to be something you are not, and the contract terms that keep you solvent if it goes sideways.

Not every big project is a good project

The temptation with a large enquiry is to say yes and work out the details later. Resist it for one afternoon and run four checks.

• Can you survive the cash-flow shape? A $40,000 project with 25 per cent up front means you may be carrying costs for weeks before the next payment. If a delayed milestone would put you in trouble, restructure the payment schedule or pass.
• Is the decision-maker in the room? Large projects with a committee of approvers and no named owner run long as a matter of physics.
• Is the scope knowable? “Rebuild the site” is not a scope. If the client cannot describe the outcome in concrete deliverables, sell a paid discovery phase first.
• Would one bad outcome sink you? If the project represents more than about half your annual revenue, the concentration risk is real. Take it with tighter terms, or take a smaller piece.

Turning down a bad big project is a legitimate business decision. Freelancers who grow steadily tend to be the ones who say no to the wrong work early rather than escaping from it late.

Scope like an agency, not like a solo builder

Solo scoping usually means a rough hour estimate and a friendly proposal. That works at $5,000. At $30,000 it does not, because the gap between what the client imagines and what you priced is proportionally larger and the consequences are heavier.

1. Run a paid discovery. One to two weeks, priced at 5–10 per cent of the expected build. Output: a sitemap, a template inventory, a data and integration list, and a technical approach. You get paid to remove the unknowns, and the client gets something useful even if they hire someone else.
2. List every template, not every page. Twenty pages often means six templates. Six templates is what you price.
3. Name the integrations explicitly. Payment gateway, CRM, ERP, shipping, tax, marketing automation, SSO. Each one is a source of surprise; each one gets its own line and its own contingency.
4. Estimate by discipline. Design, front end, back end, content migration, QA, project management. Solo freelancers routinely forget PM and QA, which together are commonly 20–25 per cent of a build.
5. Add contingency you can see. 15 per cent for familiar work; 25–30 per cent where there is a legacy site or an unfamiliar API.
6. Write the exclusions down. Content writing, stock imagery, licences, hosting, translations, ongoing support. Exclusions prevent more arguments than any other part of a proposal.

If the pricing side of this is new territory, the model we set out for agency project pricing and margin protection applies just as well to a one-person business.

Where the extra hands come from when a freelancer outsources WordPress work

Option	Upside	Downside for a solo operator
Refer the project out	Zero risk, possible referral fee	You lose the client and the revenue
Partner with another freelancer	Peer-level skill, flexible	Availability clashes; unclear who owns quality and deadlines
Subcontract to a marketplace freelancer	Cheap, fast to start	Vetting, briefing and QA fall entirely on you; high variance
White label development partner	Managed team, QA, PM, NDA, defined capacity	Monthly commitment; you must keep it fed with work

For a freelancer, the deciding factor is usually management overhead. Coordinating three marketplace hires is a full-time job you did not price for. A white label WordPress development partner hands you a project manager, a QA step and an NDA as part of the arrangement, which is precisely the machinery a solo business lacks.

Cost-wise, published pricing at the time of writing puts hourly white label work at roughly $50–$99 per hour and monthly hour blocks between about $749 and $3,999 depending on the band of hours. Our monthly plans start at $699 for 15–20 hours, which is a realistic entry point for a freelancer with one large project, and step up to $1,199 for 30–35 hours and $1,899 for 50–60 hours once full builds are involved. Note that the Starter tier does not include full builds — if you are handing over an entire site, budget for Standard or Pro.

Keeping delivery invisible and the relationship yours

Clients hire freelancers for the person. That does not have to change when the hands multiply, provided you hold the parts of the job that they are actually buying.

• You run every client conversation. No developer email addresses on the thread, ever. A genuine white label partner will guarantee no direct contact with your client.
• You write the brief. You sat in the meeting; you know what the client meant. Turning that into an unambiguous brief is your highest-value hour of the week.
• You do final acceptance. Review on staging, check the code and the block structure, and only then show the client.
• You own the code. Confirm in writing that full ownership transfers to you and there are no proprietary dependencies.
• You control credentials. Named accounts with least privilege, revoked at project end.

Whether you tell the client is your decision and depends on your contract. Many freelancers say plainly that they work with a delivery team on larger builds; clients rarely object, because what they wanted was your judgement and a site that launches on time. The mistakes that cause problems — a stray branded email, a partner logo in a plugin footer — are covered in our post on outsourcing without losing the client.

Contract terms that matter more at this size

Your $5,000 contract probably runs to two pages. For a project several times that, tighten five things.

• Payment schedule. 30–40 per cent up front, milestone payments tied to deliverables rather than dates, balance before launch. Never let the final payment sit behind a live site.
• Client dependency clause. Late content or late approvals pause the timeline and may re-price. Big projects stall on the client side far more often than the build side.
• Revision limits. Two rounds per deliverable with consolidated feedback from one named approver.
• Change orders. Written, priced, agreed before work starts. On a long project you will use this repeatedly.
• Liability cap. Cap it at fees paid. A solo business cannot carry uncapped exposure on an ecommerce site.

Get a proper contract template drawn up once. It costs less than a fortnight of unpaid revisions and you will reuse it for years.

Frequently asked questions

Can one freelancer realistically deliver a $30,000 build?

Yes, if you stop treating delivery as something you must do personally. Your role becomes scoping, client management, briefing and acceptance, with production capacity bought in. The constraint is your management bandwidth, not your typing speed.

Do I need to register a company first?

Not necessarily, though limited liability, professional indemnity insurance and a clear contract become materially more valuable as project size grows. Take local advice — the answer differs across the US, UK, EU and Australia.

What if the outsourced work is not good enough?

Test with a small paid task before the flagship build, review on staging rather than trusting a demo, and choose a partner with no long-term lock-in so a bad fit costs one month. Build your own QA checklist and apply it every time regardless of who built the work.

How much margin should I keep on outsourced work?

You are carrying sales, scoping, client management, QA and commercial risk, so a healthy markup on delivery cost is normal rather than greedy. Aim for a gross margin similar to an agency’s — 45–60 per cent — and price the outcome rather than the hours.

Which parts should I hand over first?

Start with well-defined production work: template builds from an approved design, WooCommerce configuration, a migration, a speed pass. Keep architecture decisions and anything requiring client context with you until trust is established.

Taking the next project up a level

Bigger projects are not mostly a technical challenge. They are a scoping, cash-flow and delivery-management challenge, and all three are learnable. If you want the wider picture of how the outsourced delivery model works, our guide to white label WordPress development is written for agencies but applies directly to a solo practice.

If you have a big enquiry sitting in your inbox right now, the plan tiers will tell you quickly whether the delivery maths works before you send the proposal.