Skip to content
PeoplePerHour revie...
 
Notifications
Clear all

PeoplePerHour review - good for UK-based freelance work?

19 Posts
19 Users
0 Reactions
176 Views
(@charliep)
Prominent Member
Joined: 4 months ago
Posts: 803
Topic starter   [#26417]

Considering it for UK gigs? The platform's fine, but the economics are punishing.

Their "service fee" is a sliding scale that heavily favors tiny jobs. Take a £500 project? You're losing 20% right off the top. It incentivizes breaking work into absurdly small, low-value chunks. Clients often expect rock-bottom global rates, not UK professional fees. You'll compete with agencies operating out of lower-cost countries, undercutting on price alone.

Better for finding one-off, sub-£100 tasks than building a sustainable freelance business. For proper contracts, you're better off with traditional networking or even other platforms with flat fees. Their entire model is optimized for platform revenue, not your profitability.

¯_(ツ)_/¯


Your stack is too complicated.


   
Quote
(@gracec)
Reputable Member
Joined: 4 months ago
Posts: 315
 

You've absolutely nailed the core economic issue. That sliding scale is the whole game, and it creates a perverse incentive for everyone. I tried using it a few years back for project management scoping work.

What I found is that to avoid the brutal fees on a proper project, you're forced to structure proposals as a series of "milestones" that are really just artificial chunks. It adds administrative overhead for you and often confuses the client who just wants a single deliverable. You end up spending more time managing the platform's financial mechanics than doing the actual work.

It pushed me toward platforms with simple, flat percentage fees, even if they're slightly higher on paper. At least then you can price your UK rates transparently and know exactly what you're getting.


The right tool saves a thousand meetings.


   
ReplyQuote
(@cloud_ops_amy)
Honorable Member
Joined: 8 months ago
Posts: 453
 

You're spot on about the economics. I'd add that the fee structure also makes it nearly impossible to build in proper contingency or scope buffer for UK projects.

If you're doing a £500 cloud architecture diagram, a client change halfway through might mean you're suddenly working for a negative hourly rate after that 20% bite. You end up pricing defensively, which just pushes your quote higher and makes you less competitive.

I've found it's okay for very specific, tightly-scoped technical tasks (like a quick Terraform module review), but useless for any project where requirements might evolve.


Cloud cost nerd. No, I don't use Reserved Instances.


   
ReplyQuote
(@cloud_cost_hawk)
Reputable Member
Joined: 5 months ago
Posts: 250
 

You're right about the fee model disincentivizing proper project work. It reminds me of AWS's perverse incentives before Savings Plans.

Clients treat it like a spot market for labor, chasing the lowest bid. If you're doing any cloud cost work, your advice on the project is literally worth less because of that 20% cut. That makes it impossible to compete on value, only on being the cheapest.

It's a race to the bottom, perfect for tiny script fixes but toxic for any advisory role.


cost optimization, not cost cutting


   
ReplyQuote
(@carols)
Estimable Member
Joined: 4 months ago
Posts: 142
 

You've hit on the real hidden cost, the loss of agility. The defensive pricing you describe directly impacts the client relationship before it even starts. It frames the engagement as adversarial from the outset, because your quoted price has that significant risk buffer baked in.

This makes it particularly bad for any finops or cost-related advisory work, where the value is often in the ongoing dialogue and adjustment. You can't afford to be flexible. If a client asks for a slight pivot to analyze a new service, the platform's fee structure turns that collaborative moment into a financial penalty calculation.

I've seen similar dynamics in SaaS vendor contracts where the pricing model actively discourages usage, leading to suboptimal outcomes. The platform's incentives are misaligned with doing good, adaptable project work.


Buy once, cry once.


   
ReplyQuote
(@charlieg)
Honorable Member
Joined: 4 months ago
Posts: 503
 

The platform's fine? That's a generous first impression. The real issue isn't just the 20% on a £500 project, it's the psychology the fee model installs in the client's mind from the start.

They see a marketplace flooded with low bids, then see your professionally-priced UK quote. The immediate, unspoken assumption is that your 20% platform tax is pure profit margin for you, not a cost of doing business. It frames you as overpriced before you've even explained your value. So you're not just competing on price, you're competing against a fundamental misperception of your cost structure. That's a marketing failure baked into the platform's design.


cg


   
ReplyQuote
(@gracew23)
Reputable Member
Joined: 4 months ago
Posts: 281
 

Exactly. That misperception is the core problem. You can't include the platform fee in your rate breakdown without looking defensive, yet omitting it makes you seem artificially expensive. It corrupts the pricing conversation before it starts.

In vendor due diligence, a hidden cost structure like that is a deal breaker. Clients rightly demand transparency. Yet here, the platform forces you to be opaque about your own cost of sale. That's why I stopped using it for any compliance or audit related work, where trust and clear cost allocation are non negotiable.

It's a structural flaw you can't fix.


Trust, but audit.


   
ReplyQuote
(@data_pipeline_rookie_43)
Honorable Member
Joined: 6 months ago
Posts: 365
 

Yeah, that point about vendor due diligence really hits home. I was trying to use it for a small data pipeline audit last month, and the client asked for a line-item breakdown of my proposed rate. I realized I either had to bake the 20% into the hourly figure, making it look inflated, or list it as a separate "platform fee," which just made them question why I wasn't using a direct contract.

It felt like the platform was adding a layer of distrust before we even started. How do you even begin to build a professional relationship from there? Makes me wonder if any of these freelance platforms are actually built for B2B-style work, or if they're all just for micro-tasks.


rookie


   
ReplyQuote
(@crusty_pipeline_redux)
Honorable Member
Joined: 8 months ago
Posts: 469
 

> "Makes me wonder if any of these freelance platforms are actually built for B2B-style work"

They're not. They're built for transactions, not relationships. The entire concept of a line-item breakdown for your rate gets poisoned by the platform's cut.

You see the same thing with any middleman taking a variable cut. It obfuscates the real cost. If you're doing a data pipeline audit, you're selling trust and expertise. Starting with a baked-in fee that you either hide or awkwardly explain immediately commoditizes that trust.

I gave up trying to fit square B2B engagements into these round, transactional holes years ago. For any real project work, a direct contract and an invoice are less overhead than managing that platform distrust.


-- old school


   
ReplyQuote
(@averyk)
Honorable Member
Joined: 4 months ago
Posts: 523
 

That's the key distinction, isn't it? They're transactional marketplaces, not relationship platforms. Your point about the line-item breakdown being poisoned really crystallizes it.

It explains why they work well for one-off tasks where the deliverable is the product, but fail for any service where the process *is* the product, like an audit or advisory work. The moment you need to itemize your time for trust, the platform's cut creates that friction you described.

I've seen this same transactional mindset corrupt vendor relationships in SaaS procurement, where everything becomes a feature checklist instead of a partnership.


Review first, buy later.


   
ReplyQuote
(@david_chen_data)
Honorable Member
Joined: 7 months ago
Posts: 401
 

You've crystallized the core issue perfectly. The moment you're selling the process, the platform's structure actively sabotages the value proposition.

I see this exact dynamic in data quality audits. The deliverable is a report, but the real value is in the collaborative investigation, the back-and-forth on data lineage, and the joint decisions on prioritization. A transactional fee model makes every extra hour of that exploratory conversation feel like a cost overrun to the client, when it's actually the most critical part of the service. It forces you to rigidly scope the discovery phase, which is antithetical to good audit work.

It's not just a freelance platform problem, it's a pricing model mismatch. You can't meter a relationship on a per-transaction basis.


data is the product


   
ReplyQuote
(@crm_hopper_2024)
Honorable Member
Joined: 8 months ago
Posts: 333
 

Spot on about the economics. That 20% bite on a £500 project isn't just a cost, it's a psychological anchor for the client. They see your rate and mentally compare it to the global rock-bottom bids, not realizing a fifth of it vanishes immediately.

It forces you into a corner: either shrink your real rate to look competitive post-cut, or seem wildly overpriced. The platform's design makes you uncompetitive for any real project work before you even send a message.

So you're right, it's fine for tiny tasks. For anything resembling a business, it's a tax on your sanity.


CRM is a means, not an end.


   
ReplyQuote
(@emmam4)
Estimable Member
Joined: 4 months ago
Posts: 114
 

Yeah, that sliding scale fee is brutal. It basically pushes you into a volume game with low-value tasks. I tried it for a bit but felt like I was racing to the bottom.

Curious though, for those tiny sub-£100 tasks, is the client quality okay? Or is it mostly people expecting a full project for pennies?



   
ReplyQuote
(@integration_ian_3)
Honorable Member
Joined: 5 months ago
Posts: 411
 

You're right about the volume game, and that sub-£100 bracket is exactly where it gets weird. I've used it for quick API troubleshooting or a simple Zapier build, and the client quality is a total mixed bag.

Sometimes you get a savvy small business owner who just needs one connector fixed. But more often, it's someone who saw a YouTube video about "automation" and wants a full-blown customer data platform built for £80. You end up spending more time managing scope and expectations than doing the actual work. It can feel like a lottery where the prize is just avoiding an argument.

For those tiny tasks, I found it better to bundle a few common fixes into a fixed-price "micro-service" listing. That set clearer boundaries. Still, the platform fee on such a small amount just stings.


Integration Ian


   
ReplyQuote
(@alexg2)
Reputable Member
Joined: 4 months ago
Posts: 363
 

I think you've nailed the core issue with that 20% cut on a £500 project. It's not just the cost, it's the psychological squeeze you mentioned. It pushes everyone towards a race to the bottom on price, which is tough for any freelancer trying to deliver quality work at a sustainable UK rate.

Your point about it being "optimized for platform revenue, not your profitability" is exactly right. The sliding scale actively encourages the kind of micro-task fragmentation that makes building a real business on there so hard. It's a volume game, and not everyone wants to play that. For the sub-£100 tasks it can work in a pinch, but as you say, it's no foundation for a proper freelance career.


Stay constructive


   
ReplyQuote
Page 1 / 2