Dev48
Language
  • About
  • Services
  • Industries
  • Technologies
  • Articles
  • Contacts
Book a call
    Home/Articles/The case for pragmatism in fintech
Dev48
info@dev48.org+375 29 320-40-96WhatsApp@isky_by

© 2026 · All rights reserved.

The case for pragmatism in fintech

Source: The future of payments, built for technical teams | Moov•November 16, 2026 at 10:45 PM

The case for pragmatism in fintech

There’s no shortage of people talking about the future of fintech. I’m more interested in the people actually building it.

There’s no shortage of people talking about the future of fintech. I’m more interested in the people actually building it.

That’s the idea behind Money on the Moov, a new series where I spend time with the founders, developers, and industry thinkers figuring out how money should move. And because the best conversations don’t always happen behind a desk, we’re taking these interviews on the move.

For our first episode, we headed to fintech_devcon in Denver, where I caught up with Alejandro from Linker Finance, a company helping community banks build better digital banking experiences.

We talked about everything from the realities of integrating with legacy banking systems to why community banks deserve more credit for their willingness to innovate. We even got into his love of playing drums in a grunge and metal band. But one word kept coming up throughout our conversation.

Pragmatism.

Not exactly the flashiest word in fintech. Especially in an industry where every other conversation seems to involve AI, blockchain, or the next technology that’s supposedly going to change everything.

But the more Alejandro talked about building Linker, the more I appreciated his perspective.

Take Linker’s early approach to building its platform. The team assumed community banks wanted the flexibility to choose their own technology vendors. Linker would handle the integrations, and banks could pick the solutions that worked best for them.

Except that’s not what the banks wanted.

As Alejandro explained:

“We thought they wanted options, but they don’t really. They just want functions to be made.”

“We thought they wanted options, but they don’t really. They just want functions to be made.”

That realization changed how Linker approached its customers. And it was just one example of something I kept coming back to throughout our conversation: Good technology starts with understanding the problem, not just figuring out what you can build.

Here are three lessons from Alejandro that stuck with me.

1. More options aren’t always what customers need

Community banks want to innovate. But that doesn’t mean they want to spend their time evaluating technology vendors and figuring out how to connect everything.

Alejandro explained that many of the banks Linker works with are already overwhelmed by the complexity of modernizing their technology.

Linker’s original approach was to give them flexibility to choose their own providers. But the team learned that banks were more interested in getting the functionality they needed than managing another collection of vendor relationships.

That changed the conversation from which technology do you want? to what are you trying to accomplish?

The takeaway: There’s a difference between giving customers flexibility and giving them more work.

It’s something worth remembering when building infrastructure. We spend a lot of time thinking about how many options we can support. But customers don’t necessarily measure value by the number of choices available.

Sometimes they just want something that works.

2. Good architecture gives you room to adapt

Interestingly, learning that banks wanted fewer decisions didn’t mean Linker stopped building for flexibility. Alejandro described an early architectural decision to create abstraction layers, even when Linker had only integrated with one provider.

Why invest in that complexity so early?

Because community banks have different existing relationships and technology requirements. Linker needed to accommodate those differences without rebuilding its platform every time it added another provider.

The goal was to solve integration challenges once and build those capabilities into the platform.

The takeaway: Build flexibility where it solves a real problem, not just because you can.

It’s a tricky balance for any engineering team. Build too much too early, and you’re overengineering for a future that may never arrive. Build only for today’s requirements, and you risk creating something that can’t evolve.

What I appreciated about Alejandro’s approach is that the architecture wasn’t complicated for the sake of being sophisticated. There was a practical reason behind it.

And that same philosophy carries over to how Linker evaluates its technology partners.

When Alejandro talked about choosing Moov, he described the difference between providers who could explain what they planned to build and providers who were ready to get to work.

Some had impressive presentations, but the actual technology wasn’t ready.

As he put it:

“With Moov it was really, really straightforward. The API is there.”

“With Moov it was really, really straightforward. The API is there.”

Linker could work with an actual API rather than a roadmap. Alejandro also described being able to get a bank onboarded in less than a week.

His reasoning was refreshingly straightforward: “It was really pragmatism and just being ready to do the work.”

For a company building integrations into banking infrastructure, that readiness matters.

3. Sometimes the best solution isn’t software

This might have been my favorite takeaway from the conversation.

As engineers, we love solving problems with technology. Give us a complicated challenge, and we’ll start thinking about what we can build.

But Alejandro made an important point:

“Maybe you don’t even need software… just a redesign of the flow.”

It’s a simple observation, but one I think the fintech industry could use more often.

We’re surrounded by conversations about AI, blockchain, and whatever technology is going to change everything next. And while those technologies create exciting possibilities, there’s a difference between what’s technically possible and what’s actually useful.

The takeaway: Before asking how to build something, ask whether building something is the right answer.

Sometimes the best solution is a new integration or a more sophisticated architecture.

Other times it’s removing a step, changing a process, or making an existing system work better.

That’s what pragmatism looks like in practice.

Outside of fintech, things get a little louder

One of the reasons I wanted to start Money on the Moov was to get beyond the technology and learn more about the people building it.

And Alejandro has a pretty great answer to what gets him moving outside of work.

He’s a drummer.

Not just occasionally, either. He plays almost every day and performs in a band influenced by the grunge and metal music he grew up listening to. Think Pearl Jam and Tool.

He even tracks his drumming sessions on his Fitbit, which apparently thinks he’s running when he gets going. Naturally, I asked about his neighbors.

Thankfully, he has an electronic drum kit at home.

It’s the kind of thing you probably wouldn’t learn from a typical fintech interview. And exactly why I wanted to start this series.

Watch the first episode of Money on the Moov

My biggest takeaway from Alejandro is that great engineering isn’t just about knowing how to build complicated things. It’s about knowing which problems are worth solving.

That philosophy shows up in how Linker works with community banks, how its platform is designed, and how Alejandro evaluates the technology his team depends on.

And in an industry that loves chasing the next big thing, I think that’s a perspective worth hearing.

Watch our full conversation to hear more about Linker’s approach to community banking, the realities of building fintech infrastructure, and Alejandro’s life behind the drum kit.

There’s more to Alejandro’s story than we could fit into one blog.

Catch our full conversation from fintech_devcon in Denver, where we get into the challenges, unexpected lessons, and a few things you probably wouldn’t expect to hear in a fintech interview.

← All articles

What this article says

More in FinTech & Banking

All →
How to invest in an IPO: step-by-step guide
Revolut

How to invest in an IPO: step-by-step guide

Solana 1.0: Dropping -beta, and what comes next
Solana

Solana 1.0: Dropping -beta, and what comes next

The Complete Guide to Ecommerce Merchant Processing
Rapyd

The Complete Guide to Ecommerce Merchant Processing

Rapyd vs Adyen: Comparing Features, Pricing, Onboarding and Fit
Rapyd

Rapyd vs Adyen: Comparing Features, Pricing, Onboarding and Fit

Wise Platform Mission Update Q3 2026
Wise

Wise Platform Mission Update Q3 2026

2026 Q3 Mission Update: Price
Wise

2026 Q3 Mission Update: Price

More from Moov

Financial institutions are thinking too small about P2P
Moov

Financial institutions are thinking too small about P2P

Hey banks, let account holders fund accounts with a debit card
Moov

Hey banks, let account holders fund accounts with a debit card

Multiple wallets: Flexible fund management for growing businesses
Moov

Multiple wallets: Flexible fund management for growing businesses

How we made payment links faster
Moov

How we made payment links faster

A tap to get paid: Apple Pay & Google Pay for disbursements
Moov

A tap to get paid: Apple Pay & Google Pay for disbursements

The P2P network that's already in your wallet
Moov

The P2P network that's already in your wallet