What framework or approach do you use to help you decide when to build vs. buy?
948 views2 Upvotes1 Comment
Sort by:
Content you might like
What portion of your developers use data-focused programming languages like SQL?
All11%
Most56%
Some28%
Few3%
None1%
I am curious if your organization has used code generators in any real way. Not low-code tools, but actual generators like RAD-style scaffolding or Domain Specific Languages. I feel that building simple apps is still as complicated as it was twenty years ago, maybe even more. With everything we have today, why does it still feel this heavy? I would love to hear past experiences, suggestions, or ideas from people who have tried to make this easier in their teams.
React24%
Angular50%
Vue9%
No Framework11%
Other3%

I find it best to drive this decision through organizational strategy and competences within the business and IT.
For instance:
- What tier is the business and BCP group defining this initiative/solution will fall under. This will provide context when reviewing vendors capabilities against your own.
- What is the Recovery Time Objective (RTO) and Recovery Point Objective (RPO) expected for this product?
- Do you have the in house competences to support developing your own solution?
- Is your IT strategy Cloud first? SaaS first etc.?
- What is the business urgency?
- What is the budget?
- Does this need to be resilient and/or scalable? Goes along with Tier and RTO/RPO discussion.
I would have more if I think on it more, but this is some of the core things I am looking at when reviewing a solution. We actually took these types of criteria and ranked the priority and assigned a weight to each item. Then rank SaaS, IaaS, On-Prem etc to see what would win out.
This is not the end all on the decision, but can provide a level of objectivity to the review.