A small non-profit with a two-person operations team and a limited annual technology budget wants a chatbot to answer common donor questions on its website. An affordable, ready-made chatbot product already exists that many similar non-profits use successfully. What is the most appropriate build-buy-partner approach?
Select an answer to reveal the explanation.
Short Explanation
A two-person team, a tight budget, and a well-worn problem other non-profits already solved with the same product isn't a build-it-yourself situation, and it's not a big-partnership situation either. When an affordable, proven off-the-shelf tool already does the job, buying is the move that actually fits your team's size.
Full Explanation
The correct answer fits because it matches the organization's real constraints: a two-person team, a limited technology budget, and an affordable product already proven at similar non-profits. That's the classic case for buying a commoditized solution rather than building or partnering. Building a custom chatbot from scratch to control every feature is wildly disproportionate here; a small team with a limited budget doesn't have the capacity to design, build, and maintain custom software for a basic FAQ need. Partnering with a large technology company to co-develop a proprietary chatbot is even more mismatched, since a full co-development relationship demands far more time, staffing, and negotiation than a two-person operations team can realistically sustain. Delaying the project until the team grows large enough to build in-house sacrifices a low-cost, low-risk improvement that's available right now, with no real justification given the constraints described. The operational check: when the need is well-defined, common across similar organizations, and already solved by an affordable vendor product, buying is almost always the most resource-efficient path for a small, budget-constrained team.