Just throwing a thought: if many EA orgs have software needs and are struggling to employ people who’ll solve them; and on the other hand, part-time employees or volunteer directories don’t help that much—would it make sense to start a SaaS org aimed at helping EA orgs?
I could see a space for software consultancies that work with EA orgs, that basically help build and maintain software for them.
I’m not sure what you mean by SaaS in this case. If you only have 2-10 clients, it’s sort of weird to have a standard SaaS business model. I was imagining more of the regular consultancy payment structure.
In this part I argue that each problem could be mitigated or even fixed by consolidating the workers into a single agency. I focus here on the benefits common to any form of agency
This post explicitly compares the low-bono option with various others on two axes: on entity type (ie individual or agency) and on different funding models.
Just throwing a thought: if many EA orgs have software needs and are struggling to employ people who’ll solve them; and on the other hand, part-time employees or volunteer directories don’t help that much—would it make sense to start a SaaS org aimed at helping EA orgs?
I could see a space for software consultancies that work with EA orgs, that basically help build and maintain software for them.
I’m not sure what you mean by SaaS in this case. If you only have 2-10 clients, it’s sort of weird to have a standard SaaS business model. I was imagining more of the regular consultancy payment structure.
EA Software Consultancy: In case you don’t know these posts:
Part 1
Part 2
Part 3
Yea, I was briefly familiar.
I think it’s still tough, and agree with Ben’s comment here.
https://forum.effectivealtruism.org/posts/kQ2kwpSkTwekyypKu/part-1-ea-tech-work-is-inefficiently-allocated-and-bad-for?commentId=ypo3SzDMPGkhF3GfP
But I think consultancy engineers could be a fit for maybe ~20-40% of EA software talent.