When do you build capabilities vs buy apps/services - what are deciding factors?

Development, Engineering For us it’s whether or not the apps or services someone wants to acquire can meet our federal requirements. With FEDRamp now we are starting to get a little more flexibility but it is really hard on the Federal Sector to find companies willing to meet federal requirements.

12 comments

https://www.pulse.qa

Pulse User

For us it’s whether or not the apps or services someone wants to acquire can meet our federal requirements. With FEDRamp now we are starting to get a little more flexibility but it is really hard on the Federal Sector to find companies willing to meet federal requirements.

Pulse User

Total cost of ownership for me. What innovation will you get in the future if you buy vs. cost/business priority of doing it yourself. I’d always prefer to buy and tweak vs. build from scratch. Don’t headaches regarding performance, scalability etc. Also predictable costs from a buy scenario.

Pulse User

TCO and time are the big factors.

Pulse User

TCO, time, information security, maintainability.

Pulse User

Cost, time to market, business need and alignment would be the deciding factors.

Pulse User

TCO and time

Pulse User

I use the Theory of constraints to decide it.

Pulse User

Total cost of ownership, time, and number of competitors in a particular space.

Pulse User

Would do a ROI analysis based on cost, effort & shelf life of the services required

Pulse User

When capability needed doesn't exist. Or to gain a competitive advantage

Pulse User

How unique vs standard is the business requirement. How long will it likely be in place. If there aren't really tools fo it yet and it will likely in use for a while, I'd build.

Pulse User

Only if it’s super proprietary otherwise build integration capabilities. Haven’t come across a requirement we could integrate products/apps to solve.