@LushawnDev I’ve been using Netlify for many years and I don’t believe that “an account per client” makes much sense for a freelance or “small agency” business.
While it’s true that it offloads the cost directly to the customer, since Netlify charges “per seat” it multiplies the “per seat” charge “per customer”, increasing the total cost, whereby each customer pays for their account (which they may or may not need), plus your account that is pushing code to their repository, and then anyone else you may have that commits code.
It also makes it harder for you as a business to manage the client’s sites, as you either need to login/logout, or “switch” between the various accounts.
While it’s more overhead from a billing perspective, you can keep costs closer to hosting expectations of your clients by charging them only the small hosting fee they already expect to pay + (any special itemized usage they may have, e.g. if they need forms at an additional $19), then put their combined funds towards the one Netlify account.
You’re then covering the fair “usage” of resources, but not having every client pay for every developer seat, as if each client is also running the agency.
If you found that one client in particular had excessive usage, you could always transfer ownership of their account to separate it out at a later date.
There’s not much difference between Freelancers and “Small Agencies”, and I know that several small agencies provided feedback to the “partners team” at length when Netlify increased pricing by introducing “git contributors”.
Breakdown of “multiple account” pricing issues here:
https://answers.netlify.com/t/please-read-changes-to-our-recent-pricing-update/56565/10
Concerns around the lack of support for the “business plan” here:
https://answers.netlify.com/t/pricing-and-plans/257/57
Suggestion for a “simpler plan” here:
https://answers.netlify.com/t/pricing-and-plans/257/86