Comparison · PeoplePerHour vs. Custom Code
The quote resets every time you're a new client: PeoplePerHour's commission tax explains why
PeoplePerHour is Europe's largest freelance marketplace, with a UK- and EU-heavy pool of freelancers competing openly on price for open project briefs and pre-packaged fixed-price "Offers." That openness is real, and for a lot of small jobs it works. What a listing doesn't spell out is how the fees land: a tiered commission that pushes freelancers to price new clients higher, a buyer fee added on top of the quote at checkout, a 14-day payout hold that can slow a freelancer's availability, and a platform whose own recent reputation on complaint-tracking sites is rough. This page covers what a PeoplePerHour website costs once every layer is counted, the documented friction points, and where the platform is still the right call.
PeoplePerHour vs. hand-coded custom: side by side
Both columns are written to be accurate. Where PeoplePerHour has the edge, the table says so. Fee figures reflect PeoplePerHour's own support documentation as of mid-2026; the buyer-side fee formula in particular varies slightly across sources, so treat exact figures as directional and verify at your own checkout.
| Factor | PeoplePerHour | Hand-coded custom (ArdinGate) |
|---|---|---|
| Upfront cost | No platform price list: freelancers set their own rates. Roughly £300–£1,500 for a small custom site, £1,500–£5,000+ for a fuller build; entry-level fixed-price Offers can start around £10–£50 for a narrow task | $1,200–$2,200 single-page, $2,800–$5,000 multi-page: fixed and agreed in writing before work starts |
| Buyer fee on top of the price | Roughly 10% added at checkout on top of the freelancer's quoted price (one source cites £0.60 + 10% for card/PayPal specifically; exact formula not confirmed against a single current PPH page) | None. The quoted price is the price, with no per-transaction fee layered on top |
| Freelancer commission (built into quotes) | Tiered by lifetime billing with that specific buyer: 20% on the first ~£250, 7.5% up to ~£5,000, 3.5% above that; resets to 20% with every brand-new client, which pushes new-client quotes higher | No commission layer. One fixed quote, no hidden tier that shifts based on your history with the developer |
| Hiring model | Two parallel paths: instant fixed-price "Offers" from a searchable directory, or a free project brief that draws custom proposals from bidding freelancers | One direct conversation, one scoped proposal, no bidding process |
| Hosting | Not provided by PeoplePerHour itself; whatever the freelancer builds still needs separate hosting you arrange and pay for | Optional managed hosting from $60 to $180/mo, or self-host the files anywhere |
| Future edits and revisions | Each new request is a fresh payment, taxed with the same ~10% buyer fee every time | Managed hosting tiers bundle monthly edit hours at one flat rate |
| Payment and payout timing | All work runs through PeoplePerHour's WorkStream escrow; freelancers face a standard 14-day holding period plus a manual withdrawal request and a further 24–48 hour wait | Direct payment terms agreed with your developer; no platform escrow holding period in between |
| Dispute process | A freelancer who wants to formally dispute a refund request must pay a non-refundable fee: 10% of the disputed amount, minimum roughly £5/€7/$8 | A direct relationship and a written scope; no platform fee to contest a disagreement |
| Refund mechanics | Reviewed by PeoplePerHour's Payment Team, typically within 1 business day; escrowed funds auto-release to the buyer if the freelancer doesn't respond within 3 business days | Refund terms set in your written agreement, not a third-party auto-release rule |
| Support responsiveness | Widely described in complaint threads as slow and unhelpful on unresolved disputes; a paid "Fast Track" option (~£10) exists to escalate support issues | The same developer who built the site |
| Freelancer account stability | Reports of accounts being deactivated after a single negative one-star review, regardless of an otherwise strong track record, which can end an established relationship over an unrelated dispute | One relationship with one accountable developer; no platform-level deactivation risk |
| Review reliability | Complaint-focused aggregator sites paint a notably harsher picture than the platform's own, friendlier Trustpilot presence; treat any single rating number as a soft signal, not a precise score | Portfolio and direct references; no marketplace-wide rating trend to weigh |
| Geographic pool | UK/EU-heavy: roughly 60% of freelancers and clients are UK-based, with 1.4M+ members across 100+ countries (company-reported) | Direct hire, no marketplace pool to filter through regardless of location |
| Vetting | Freelancers are described by PeoplePerHour as vetted before joining; the rigor of that process isn't independently detailed | Direct engagement: you evaluate the developer's portfolio and track record yourself |
| 5-year total cost (illustrative) | Roughly $4,550–$8,800 all-in for a comparable multi-page build (buyer fee, several years of revisions, and separate hosting included) | $2,800–$5,000 build plus hosting: about $6,400–$8,600 on the least expensive tier |
| What you're fundamentally buying | A quoted proposal from an individual freelancer, priced through an open bidding process and a tiered commission structure | A scoped relationship with one developer accountable for the whole build and what happens after |
When PeoplePerHour is the right call
PeoplePerHour built its position as Europe's leading freelance marketplace by making it easy to post a brief or buy a fixed-price Offer and get bids from a large, mostly UK- and EU-based pool. For specific situations, that's a strong fit.
A small, bounded task you can judge yourself
A logo tweak, a single landing page section, a small fix to an existing WordPress site: these are the kinds of narrow jobs a pre-packaged fixed-price Offer handles well, often starting around £10 to £50. You already know what "done" looks like, and you can check the delivered work against it directly. That's a low-commitment way to try a specific freelancer before trusting them with something bigger.
You specifically want UK or European time-zone overlap
PeoplePerHour is headquartered in London, with roughly 60% of its freelancers and clients based in the UK. If working hours that overlap with UK or European business hours matter to you, or you're looking for a particular European design sensibility, that concentration is a real advantage a more US-centric marketplace doesn't offer in the same way.
You want to compare open bids before committing
Posting a free project brief and reviewing custom proposals from several freelancers is a legitimate way to shop if you want to compare pricing and approach across multiple people before choosing one. PeoplePerHour's two parallel hiring models (instant Offers or bid-based proposals) give you that flexibility in a way a single fixed quote doesn't.
The calculus changes the moment the site needs to be a durable part of the business rather than a one-off task. Once you're relying on a freelancer whose account could disappear over a dispute that had nothing to do with your project, once support response time on a real problem matters, and once every future edit restarts the same buyer fee, PeoplePerHour's structure starts working against you rather than for you.
Where a hand-coded site outperforms a PeoplePerHour hire
These aren't abstract concerns. They're documented, recurring patterns in how the platform's fee structure, payout timing, and dispute mechanics work, and they compound the longer you rely on it.
The new-client commission tax shapes the quote you get
PeoplePerHour's commission structure is tiered by how much a freelancer has billed a specific buyer over the lifetime of that relationship: 20% on the first roughly £250, dropping to 7.5% up to about £5,000, and 3.5% above that. The catch is that the tier resets to 20% every single time a freelancer starts with a brand-new client, regardless of how established they are on the platform. That's a direct incentive to price a first-time buyer's quote higher than what the same freelancer would eventually charge a repeat client, since the early portion of the job costs the freelancer more in commission. A custom build from ArdinGate has no hidden tier shifting the number based on how long you've worked together. The quote you get on day one is the same math a returning client gets on project ten.
The real five-year cost math
Picture a realistic, apples-to-apples scenario: a multi-page small business site sourced through a PeoplePerHour custom proposal rather than a bottom-tier Offer, since a £30 fixed-price task isn't doing the same job as a hand-coded multi-page build. Proposals for that kind of scope commonly run £1,500 to £3,000, roughly $2,100 to $4,200. Add the buyer's roughly 10% service fee at checkout and the initial build lands around $2,300 to $4,600 before the site is even finished.
Then factor in what happens after launch. A small business realistically asks for a handful of updates a year, maybe four: a new promotion, a staff photo swap, a seasonal hours change, a copy tweak. Each one is its own paid transaction, and each one picks up the same roughly 10% buyer fee. At $75 to $150 per edit, that's $82.50 to $165 per request once the fee is added. Twenty of those over five years (four a year) run $1,650 to $3,300. Add separate hosting, since PeoplePerHour doesn't provide it, at a modest $10 to $15 a month: another $600 to $900 over five years.
Total, all-in: roughly $4,550 to $8,800 over five years. A comparable multi-page build from ArdinGate runs $2,800–$5,000 plus managed hosting, landing at $6,400 to $8,600 over the same five years on the least expensive tier. On the low end, PeoplePerHour is still the cheaper option in cash. On the high end, once four edits a year are tallied up over five years, the two numbers land close enough together that price stops being the deciding factor. What that comparison doesn't price in: the new-client commission tax that may already be padded into your first quote, the platform's currently rough aggregate reputation, and the fact that every one of those future edit requests restarts the same buyer fee whether or not the freelancer who built the site is still reliably available by then.
A platform whose own numbers you can't fully verify
PeoplePerHour's reputation picture is mixed and hard to pin down. Complaint-tracking sites currently paint a considerably harsher picture of the platform than its own, friendlier Trustpilot presence, with a heavy volume of complaints about unresolved disputes. Which side of that gap is closer to reality probably depends on who bothers to leave a rating in the first place: a bad experience motivates someone to go complain in a way an unremarkable, fine one rarely does. Neither picture should be treated as a precise score, and PeoplePerHour's own buyer-fee support page wasn't reachable to confirm the exact current checkout formula against a single authoritative source either. A fixed-price quote from ArdinGate, agreed in writing before work starts, doesn't ask you to reconcile conflicting secondhand figures about what you'll pay or who you're hiring.
Slow money, slow support, and a dispute process that penalizes objecting
Every paid project on PeoplePerHour runs through the platform's escrow system, WorkStream, which is reasonable buyer protection on its own. What it means for the freelancer on the other side is less reassuring: a standard 14-day holding period after funds release, then a manual withdrawal request the freelancer has to remember to make, then another 24 to 48 hours before the money lands. A freelancer juggling that cash-flow lag across several clients may not be as immediately available for a fast turnaround as the timeline in your proposal suggested.
The dispute mechanics add another layer of friction. If a freelancer wants to formally contest a buyer's refund request rather than accept it, they have to pay a non-refundable fee to do so, 10% of the disputed amount with a roughly £5, €7, or $8 minimum. That discourages freelancers from pushing back even in good faith, which can cut in a buyer's favor in a genuine dispute but also means a freelancer wronged by a bad-faith claim has a real financial reason not to contest it. Layer in customer support that's widely described in complaint threads as slow on unresolved issues, plus a paid "Fast Track" (~£10) option to jump the queue, and the pattern is a platform that monetizes friction it created in the first place. A direct relationship with one developer skips all of it: agreed terms, a direct conversation if something's off, and no platform fee standing between you and resolving a disagreement.
Continuity risk that has nothing to do with your project
Reports describe PeoplePerHour freelancer accounts being deactivated after a single negative one-star review from one difficult buyer, regardless of an otherwise strong track record. From your side of a working relationship, that risk is invisible until it isn't: a freelancer you've built history with, whose commission tier with you has already dropped to 7.5% or 3.5% because of that history, can vanish from the platform over a dispute involving someone else's project entirely. That's a different failure mode than a freelancer simply getting busy or raising their rate. It's a platform-level risk to continuity that sits entirely outside the actual relationship you have with them. A custom build with ArdinGate is one direct relationship with no third-party switch that can turn it off.
The most common reasons people choose PeoplePerHour, answered directly
The upfront cost is lower
It usually is, and there's no point arguing otherwise. A small custom site sourced as a PeoplePerHour proposal can run roughly £300 to £1,500; ArdinGate's minimum single-page build starts at $1,200. If cash today is the binding constraint, that gap is real.
What doesn't hold up is treating the sticker price as the whole story. The five-year math above is the plain version: even loaded with a realistic buyer fee, revision requests, and separate hosting, a PeoplePerHour-sourced multi-page build lands around $4,550 to $8,800 against ArdinGate's $6,400 to $8,600 on the cheapest hosting tier. PeoplePerHour still costs less at the low end; at the high end the two numbers are close enough that cash alone doesn't settle it. The case for paying more isn't that it's secretly cheaper long-term; it's that the extra cost buys one accountable developer instead of a bidding process, a quote that doesn't shift based on whether you're a first-time client, and none of the payout-timing or account-deactivation risk described above. If none of that risk matters for your specific project, the lower price is a legitimate reason to choose PeoplePerHour.
I'd rather post a brief and compare bids myself
That's a real preference, and PeoplePerHour is built for exactly it: post a free project brief, review custom proposals from multiple freelancers, message a few before committing, and choose based on price and pitch. If you want the leverage of comparing several people against each other, PeoplePerHour's bid-based model gives you that control in a way hiring one provider directly doesn't.
The tradeoff is that all the vetting PeoplePerHour describes doing on its end (without detailing how rigorous that process is) becomes your job to double-check. You're the one reading through proposals to spot whether a quote looks padded for a new client, the one weighing a platform reputation that's mixed depending on which review source you check, and the one managing the relationship if payout delays slow the freelancer down. For some business owners that's a fair trade for control over sourcing. For others, it's a second job layered on top of running the business the site is supposed to support.
PeoplePerHour can have something live fast
Often true for a small, bounded task. A fixed-price Offer from an available freelancer can turn around in days; a custom build from ArdinGate takes one to two weeks for a single-page site and three to six weeks for a multi-page build. If something narrow and well-defined needs to exist online quickly, PeoplePerHour's Offer model wins on raw speed.
The question worth asking is what the site needs to do after that. A quick fixed-price Offer and a full custom proposal are different products solving different problems, and the comparison that matters isn't which one launches first. It's what happens a year in, once revisions start restacking the buyer fee, once you're weighing a platform reputation that depends on which review site you trust, and once you need the same person to still be reachable for the next change.
The verdict
Bottom line
PeoplePerHour is the right tool when a project is small, bounded, and cheap to redo if it goes wrong, or when working with a UK- or European-based freelancer is specifically what you want. Its two hiring models (instant Offers and bid-based proposals) serve those use cases well. For a site meant to be a durable part of the business, something you'll return to for edits over years, something where a freelancer's continued availability matters, the platform's tiered new-client commission, its 14-day payout hold, its dispute-fee friction, and a currently mixed-to-poor aggregate reputation start working against the relationship the moment it needs to last.
The single number that decides this isn't the quote on day one. It's what happens the fifth or tenth time you need something changed: a fresh transaction with the same buyer fee, and a freelancer whose availability depends on payout timing and account standing you have no visibility into, versus one developer who already knows the site and bills one flat rate. Run your own numbers against your own update frequency before deciding which one that favors.
Pricing
Custom builds are quoted as a fixed price agreed before work starts. Single-page sites run $1,200–$2,200. Multi-page builds with individual pages, a contact or intake form, and technical SEO setup included run $2,800–$5,000. Nothing changes after you approve scope: no buyer fee added at checkout, no commission tier that shifts the number based on whether you're a new client.
Optional managed hosting starts at $60/month (Core) for uptime monitoring, nightly backups, SSL, and server-level patching. Care, at $100/month, adds application-level patching and a monthly block of content edit hours, which covers roughly the same maintenance cadence a small business would otherwise be paying for one edit request at a time on PeoplePerHour, minus the per-request buyer fee. Priority, at $180/month, adds more edit time, same-day response on critical issues, and a test environment. No contract: cancel with 30 days' written notice and no cancellation fee.
For comparison: a realistic PeoplePerHour-sourced multi-page build, with the buyer fee, several years of revisions, and separate hosting included, runs roughly $4,550 to $8,800 over five years. A comparable ArdinGate build runs $2,800–$5,000 plus hosting, landing at $6,400 to $8,600 over the same five years on the Core tier. PeoplePerHour is cheaper in cash at the low end; at the high end the two options land close enough together that cash stops being the deciding factor. What the higher number buys is covered in the sections above: one accountable developer, a quote that doesn't depend on your history as a client, and none of the payout-timing or dispute-fee friction that comes with hiring through an open marketplace.
PeoplePerHour vs. custom: the questions people ask most
How much does a PeoplePerHour website cost once fees are included?
There's no fixed platform price list on PeoplePerHour: freelancers set their own rates and compete openly for the job. For a small entry-level task like a logo tweak or a single landing page section, a pre-packaged fixed-price "Offer" (formerly called an "Hourly") can start around £10 to £50. That's not what a real business website costs, though. For an actual multi-page brochure site or a basic WordPress, Shopify, or Wix build, expect a custom proposal in the roughly £300 to £1,500 range for something small and simple, and £1,500 to £5,000 or more for a fuller custom site with more pages, integrations, or design work. On top of whatever the freelancer quotes, PeoplePerHour adds a buyer service fee at checkout that most sources put at roughly 10%, so a £1,500 quote lands closer to £1,650 once that's added. Budget for the fee on top of the quote, not folded into it.
Why do PeoplePerHour freelancers sometimes quote new clients higher than returning ones?
Because PeoplePerHour's commission structure punishes new relationships. Freelancers pay a tiered commission based on how much they've billed a specific buyer over the lifetime of that relationship, and the tier resets to the highest rate every time they start with a brand-new client. On the first roughly £250 (about $350) billed to a new buyer, the freelancer pays 20% commission. Between roughly £250 and £5,000, that drops to 7.5%. Above £5,000 with the same buyer, it drops again to 3.5%. A freelancer quoting a first-time client absorbs that 20% cut on the early portion of the job, which is exactly why many pad their opening quote to a new buyer higher than what they'd eventually charge a repeat one. It's not a platform fee you pay directly. It's baked into the price before you ever see it.
What is the buyer service fee on PeoplePerHour, exactly?
A separate charge added at checkout, on top of whatever price the freelancer quoted, shown to you before you confirm payment. Most sources describe it as a flat roughly 10% surcharge on the freelancer's price; one source specifically cites £0.60 plus 10% for card and PayPal payments, which suggests the exact formula may vary by payment method. The 10% figure shows up consistently across sources, but PeoplePerHour's own buyer-fee support page wasn't reachable to confirm the precise current formula against a single authoritative source, so treat this as a solid ballpark rather than a guaranteed number. The practical takeaway either way: budget roughly 10% over the freelancer's stated price, and check the exact figure shown at your own checkout before confirming payment, since it's disclosed there regardless of which formula applies.
Does PeoplePerHour host the website it builds for you?
No. Like other freelance hiring marketplaces, PeoplePerHour connects you with the person who builds the site; it isn't a hosting company. Whatever the freelancer delivers, whether it's a WordPress build, a Shopify store, or hand-coded files, still needs somewhere to live online, and that's a separate cost you arrange outside the platform. Budgeting realistically means adding your own hosting on top of whatever you pay the freelancer, the same way you would with any independent contractor who isn't also your host. All paid work on PeoplePerHour does run through the platform's own escrow system, called WorkStream, which holds the agreed funds until you confirm the work is done, but that escrow covers payment security, not hosting.
How do PeoplePerHour freelancers get paid, and does that affect me as a buyer?
It can, indirectly. Funds a buyer pays sit in PeoplePerHour's escrow system, WorkStream, and release to the freelancer only after the buyer confirms the work is complete. Once released, the freelancer still faces a standard 14-day holding period, and the money isn't auto-paid out; the freelancer has to manually request a withdrawal and then wait another 24 to 48 hours for it to land. That's a cash-flow squeeze on the freelancer's side, not a direct cost to you, but it matters to a buyer indirectly: a freelancer juggling slow, manually-triggered payouts across several clients may be less available for quick turnarounds than the timeline in your proposal suggested. It's worth asking directly about realistic response time on revisions rather than assuming the platform's payment mechanics are invisible to how fast your project moves.
What happens if I'm not satisfied with what a PeoplePerHour freelancer delivers?
Refund requests go to PeoplePerHour's Payment Team and are typically reviewed within one business day. If the freelancer doesn't respond to your refund request within three business days, PeoplePerHour can auto-release the escrowed funds back to you. That sounds buyer-friendly, and mostly is, but there's a wrinkle worth knowing: if the freelancer wants to formally dispute your refund request instead of accepting it, they have to pay a non-refundable fee to do so, cited at 10% of the disputed amount with a minimum of roughly £5, €7, or $8. That friction discourages freelancers from contesting a request even in good faith, which can cut in a buyer's favor in a genuine dispute, but it also means a freelancer who feels wronged by a bad-faith claim has a real financial reason not to push back. Customer support handling unresolved disputes is also widely described in complaint threads as slow and unhelpful, so don't assume every disagreement resolves cleanly on the stated timeline.
Can I trust PeoplePerHour's reviews when choosing a freelancer?
Treat the platform's overall reputation as a mixed and possibly declining signal rather than a settled fact, and judge the individual freelancer instead. Complaint-focused review sites currently paint a much harsher picture of PeoplePerHour than the platform's own, considerably friendlier Trustpilot presence, with a heavy volume of unresolved-dispute complaints logged against it. Reconciling the two pictures into one precise score isn't a task any single number is built for: people with a bad experience are far more likely to show up and leave a rating than people who had an unremarkable, fine one, so any aggregator skews toward complaints by design. What's more useful is checking a specific freelancer's individual review history, response time, and portfolio directly, rather than trusting the platform's brand-level reputation either way, good or bad.
Is it risky to rely on a single PeoplePerHour freelancer for an ongoing relationship?
There's a specific risk worth knowing about: reports describe freelancer accounts being deactivated after a single negative one-star review from one difficult buyer, regardless of an otherwise strong track record. From a buyer's perspective, that's not your problem directly until it is: a freelancer you've built a working relationship with, whose lifetime commission tier with you has already dropped to 7.5% or 3.5%, can disappear from the platform over one dispute with someone else entirely. That's a different kind of continuity risk than a freelancer simply getting busy or raising rates. It's a platform-level risk to availability that sits outside either party's control in the relationship you have with them.
Is PeoplePerHour cheaper than a custom-built site over several years?
In raw dollars, usually yes, though the gap is narrower than a quick glance suggests. Picture a realistic multi-page small business site sourced as a custom proposal in the £1,500 to £3,000 range (roughly $2,100 to $4,200), plus PeoplePerHour's roughly 10% buyer fee, landing the initial build at about $2,300 to $4,600. Add four paid revision requests a year, each taxed the same 10% at checkout, plus separate hosting PeoplePerHour doesn't provide, and a realistic five-year total lands closer to $4,550 to $8,800. A comparable multi-page build from ArdinGate runs $2,800–$5,000 plus managed hosting, for a five-year total of roughly $6,400 to $8,600 on the least expensive hosting tier. On the low end, PeoplePerHour still costs less. On the high end, once several years of edits are counted in full, the two options land close enough together that sticker price alone doesn't decide it. What that comparison leaves out: the new-client commission tax that can inflate a first quote, the platform's currently poor aggregate reputation on complaint-tracking sites, the 14-day payout hold that can slow a freelancer's availability, and the deactivation risk that can end a working relationship over a dispute that had nothing to do with your project.
When does hiring on PeoplePerHour make more sense than hiring a developer directly?
When the project is small, bounded, and cheap to redo if it goes sideways, or when you specifically want a UK- or Europe-based freelancer for time-zone overlap or European design sensibility. PeoplePerHour is headquartered in London, describes itself as Europe's leading freelance marketplace, and roughly 60% of its members are UK-based, which is a meaningfully different pool than a US-centric platform. A cheap fixed-price Offer is also a reasonable low-cost way to trial a specific freelancer's work before committing to a bigger custom proposal. Where it stops making sense is the moment the site needs to be a durable, revenue-generating asset you'll keep coming back to: something where a freelancer's account could vanish over an unrelated dispute, where support is reportedly slow to resolve real problems, and where every future edit restarts the same 10% fee. At that point, the per-request friction and platform-level continuity risk start outweighing the lower sticker price.
Wondering what a PeoplePerHour build would cost you over the long run?
Tell me what the site needs to do and how often you expect to update it. I'll walk through the real numbers, fees included, and tell you straight whether a custom build is worth the difference for your situation.
Get a straight answer