4 ms·
How is this exact model different from regular freelancing? Taking on 6 clients at once is a bit much for my taste, there’s a lot of overhead involved usually.
by manmal 4y ago
How is this exact model different from regular freelancing? Taking on 6 clients at once is a bit much for my taste, there’s a lot of overhead involved usually. Now you not only need to manage various OSS communities, but also multiple clients and their expectations towards your contributions.
- simonw 4y agoThey're not paying him to do custom freelance work for him. They're paying him to continue contributing to the projects that he is already maintaining. The higher tier plans also get what sounds like a few hours of custom consulting time (think calls with their team) per month.
- manmal 4y agoAnd those paying clients won't want to influence the direction the project is taking?
- simonw 4y agoThat's described in the article: > it boils down to this: I go in, meet the engineers, and learn what parts of my projects they use and how; then, I keep those use cases in mind in my own planning and I reach out and involve them for feedback when there are relevant changes on the roadmap. This improves outcomes for everyone: I want my projects to work well for users (regardless of whether they are paying me) and no one wants to find out something’s wrong after the release. That model is expanded on here: https://words.filippo.io/dispatches/reciprocal/ https://words.filippo.io/dispatches/reciprocal/
- manmal 4y agoThanks for pointing that out. It's certainly more pleasant to work that way vs normal freelancing.