Solutions
Product
Services
Resources
Company
Developer
hello@okaythis.com

Kverndalsgata 8,
3717 Skien,
Norway

Solutions
Embedded Finance Providers and BaaS
Banks
BtoC and BtoB Fintechs
Corporate Sector
Okay Passwordless
Products
Okay KYC
Okay PSD2 SCA
Okay ACS
Okay IAM
Services
Advisory Services
Risk and Security Audits
Integration and Professional Services
Application Management Services
Resources
Blog
Glossary
Patents
PSD2/3 Resources
Company
About
Get In Touch
Partners
Developers
iOS SDK Guide
React Native Module
Android SDK Guide
Server Documentation
API Documentation
©2025 Okay. All rights reserved
Privacy & Policy
Terms & Condition
Back to Blog

Buy vs. Build: the Million-Euro SCA Question

Published: 01.06.2021

Updated: 01.06.2021

Author: Fabien Ignaccolo

Perhaps the most common question we get asked when it comes to SCA software is how to choose between going for in-house development or outsourced expertise. Since the Build vs. Buy debate is heavy and multifaceted, in this blog, we discuss a few of the pros and cons to help you and your team make the best decision.

Should we build in, or should we buy in? When it comes to software, this is one of the oldest questions management teams have to answer.

And obviously, there is a clear temptation from some organisations to contemplate the former option. Perhaps they have an R&D team, an engineering team, the programming skills, and the time and resources readily available. So, why not build it? 

Yet, we believe that this should be less of a question about whether or not an organisation can build it. Rather, the right question organisations should be asking themselves is why they should build it.

Option One: Build-in

SWOT analysis comes in handy when identifying the strengths, weaknesses, opportunities, and threats that come with business planning. While strengths and weaknesses are frequently internal, opportunities and threats are more commonly external. In the case of Buy vs. Build, a quick SWOT analysis should help answer the following:

  1. Is this development strategic for our core offering? 
  2. Will it bring extra value to our customers in a way that is different from our competitors? 
  3. Will this create a new opportunity for us?
  4. Do we have the necessary knowledge, skills, and experience to handle this development and its continued maintenance? 
  5. Do we have a track record of delivering quality projects on time? 
  6. What is the market pressure or required time to market?
  7. What is the overall cost assessment for either option?

We understand that these questions are a bit generic and can therefore apply to any kind of software development. However, it becomes a bit trickier when talking about SCA because SCA is not just about technology - it sits somewhere between software and regulation.


Ignoring SWOT Analysis

If you cannot answer the fundamental questions that accompany a good SWOT analysis well and with confidence, yet you choose to proceed with building your own SCA, you might be facing the following risks:

  1. A defocusing of your teams as you will constantly be playing catch-up on this particular topic, not only with technology but with ever-changing regulation
  2. Missing internal deadlines and external compliance deadlines
  3. Non-compliance
  4. Average or bad UX 
  5. A complex solution that becomes hard to maintain and much more expensive to migrate to market solutions.

Option Two: Buy-in

At Okay, we’ve worked hard to develop a state-of-the-art SCA solution that delivers consistent benefits to our customers. Years of combined research, development and industry experience have sped up time-to-market delivery and helped us avoid SCA project pitfalls. The constant discussions we have with our customers also drive our roadmap so that any new development is industrialised and avoids lock-in.  

As one of the best-of-breed SCA vendors, we solely focused on SCA and have solved the tech, regulation, and even UX equation thoroughly. For subjects where we do not have the complete answer, we have built up an ecosystem of partners that can step in with pre-integrated solutions. All in all, our job is about simplification by taking the integration complexity away from our customers. 


Sign Up for Our Newsletter

Unlock updates, insights, and exclusive content delivered to you.

Conclusion

Buy vs. Build will always be a tricky question to answer. And when it comes to SCA, the topic is complex because of the layer of regulation. Therefore, it makes sense that for SCA, a company would be better off buying rather than building. It all comes down to quantifying the 5 basics values of:

  1. Control
  2. Monetary costs
  3. Maintenance
  4. Opportunity costs
  5. Time to value

Although, if you have a few million euros to spend, why not test out the field of in-house development? After all, more competition means all the more innovation for our industry!


Related Articles

Part 1/8: SCA Industry Challenges - Security and 2FA

Security
13.01.2020

2FA - The Risks of Sending OTP via SMS

Security
23.03.2020

How to Evaluate the Security of Your Mobile Banking App (Part 1)

Security
20.04.2020