A county government with limited internal technical capacity is weighing whether to build an in-house benefits-eligibility screening AI tool, buy an off-the-shelf product, or partner with a specialized vendor. Given this constraint, what should guide the decision?

Building an in-house AI tool requires sustained technical resources, including staff who can develop, maintain, and retrain the system over time, and a county that has already identified limited internal technical capacity as a constraint is signaling it doesn't currently have that sustained capability. Buying an off-the-shelf product or partnering with a specialized vendor both shift the technical burden outward, letting the county access capability it lacks internally, which makes either a better fit given the stated constraint. Insisting building in-house always produces the best outcome ignores that ownership only pays off if the organization can actually sustain the tool afterward; an under-resourced in-house build risks stalling or degrading once staff attention moves elsewhere. Claiming technical capacity is irrelevant misreads the sourcing options themselves; building demands far more sustained internal expertise than either buying or partnering does, so capacity is directly relevant to the choice. Assuming buying is always cheaper than partnering treats cost as fixed regardless of fit, when in practice a screening tool with unusual eligibility rules might partner better than a generic off-the-shelf product handles. Before choosing between buying and partnering specifically, the county should map its eligibility rules against what an off-the-shelf product configures out of the box, since a poor fit there is what tips the decision toward a vendor partnership instead.