The First Months at Subvisual: Building Where Things Actually Matter

Coming from years in tech and business development, you get used to patterns. Agencies supposedly sell thinking but struggle to ship. Product teams ship but lack direction and ownership over what they ship. The traditional agency model should “evolve”, and we’re constantly told it is evolving, but that’s not what I experienced. I saw it quietly becoming irrelevant for any company operating in real complexity.

Fixed scopes break the moment reality changes, timelines drift because assumptions were wrong from day one, and teams optimize for protecting scope instead of solving problems. That might still work for marketing sites or internal tools, but it won’t work when you’re dealing with financial infrastructure, payment systems, or anything that touches real money.

This is why when I joined Subvisual, I wasn’t looking for another company. I was looking for a system that worked. Something real, rather than the polished version everyone sells. The kind that operates in messy, high-context environments where things get built, shipped, and improved under real constraints.

That context, of course, matters. Subvisual doesn’t operate in generic tech. It operates in fintech and crypto, where complexity isn’t optional, and mistakes aren’t cheap. And that changes everything.

Subvisual sits in an uncomfortable middle, and that’s exactly why it works. What we do is not outsourcing, nor is it pure consulting. We’re not a traditional studio either. It’s closer to a product and engineering partner that embeds into complexity and stays there long enough to actually move things forward, which only makes sense if the way you work reflects that reality.

One of the first things that stood out was how little time is spent pretending. There’s no excessive process theatre, no obsession with frameworks for the sake of it, and definitely no fake sense of velocity. It sounds obvious that we’d keep the focus simple, but after a few years in the industry, you’ll learn that basic things like understanding the problem properly, reducing coordination overhead as much as possible, shipping continuously, and adjusting constantly are not standard.

Subvisual is optimizing for output while most companies are still going for control. This shouldn’t really be a preference for fintech and crypto. Edge cases are the default, regulation adds friction, integrations are never as simple as they look, and failure has a financial impact. You don’t get to hide behind process. What you ship either works or the consequences happen in your client’s pocket. I’ve seen this happen.

In one of the first projects I got close to, what looked like a straightforward flow quickly turned into a mess of dependencies. Third-party integrations behaving inconsistently, edge cases stacking up, and compliance constraints forcing constant adjustments. The kind of situation where a fixed scope would have been dead within two weeks.

Instead of freezing the plan or escalating the process, the team just… kept moving. Small iterations, constant validation, and real-time adjustments. It was enlightening to watch the progress with no drama and no over-engineering. Just continuous delivery under constraints. The Subvisual team is used to operating with no fixed methodology. Always evolving, change and adaptation as default.

You can’t define everything upfront and execute linearly in fintech and crypto. Working in crypto long enough makes you indifferent to hype. It’s refreshing. No one cares whether things “look Web3”. No one chases narratives or attaches themselves to whatever’s trending.

The focus is on things like payment infrastructure, wallets, compliance-heavy flows, and backend systems that actually support financial operations. The kind of work that doesn’t get attention, but ends up delivering results and making customers money.

Business development also changes in this context. It’s not just about generating pipeline or closing deals. It’s about understanding where complexity is about to hit. Which teams are scaling into problems they’re not ready for. Which products are about to break under regulatory or technical pressure. Where timing matters more than persuasion. It’s less about selling and more about being early and relevant. And that’s harder, because you can’t fake it.

Looking back at these first months, the biggest impact came from small, precise decisions. Focusing on the right clients. Refining positioning instead of expanding it. Running targeted events instead of broad ones. Tightening the way we operate internally. Nothing particularly flashy. But in environments like fintech and crypto, that’s usually how progress actually happens.

What I underestimated was how hard it is to stay simple in complex systems. Keeping things clear, fast, and effective requires constant pressure against unnecessary complexity, process inflation, and the comfort of doing things the way they’ve always been done.

The second significant factor was joining at a breakthrough moment for software engineering and product development. Harnessing the power of AI within our systems is already a present reality. AI is already changing how fast teams execute, how much output can be generated with fewer people, and how teams are structured. Our team is now significantly more effective. Others will slowly become irrelevant.

Joining Subvisual felt like stepping into a system that operates under real constraints. Things are harder and more complex, but this is because the work here actually matters. When you’re building systems that move money, handle compliance, and support real-world operations, there’s no room for theatre.

Either it works, or it doesn’t. And that’s exactly the point.