Maverick: a destination that unfold before our eyes

I rewire my inner workings and embrace a new movement: the Maverick community will revitalise my core project.

Twelve months ago, I began a journey. Not a straightforward one. It was bold, unexpected, and at times uncomfortable—but it carried a purpose that became impossible to ignore.

What if we could design our next digital systems with one clear intention?

To stay free from the very traps we’ve normalized.

What does it take to build a strong system?

We’ve spent decades refining the core principles: lean thinking, performance, resilience, secure-by-design.
From these, incredible systems have emerged—robust, reliable, and battle-tested. Around them, vibrant communities have formed, sharing best practices and accelerating adoption.

Today, when we build, the advice is almost universal:

Start with what exists. Reuse what’s proven. Lean into community.

Do we have a safe design for us to deliver our next trap?

Absolutely, we’ve built and refined entire frameworks,from marketers to agencies, designers to developers, and now, the so-called super frameworks. We have created norms. Today, we’re told: just learn them, follow them, and you’ll succeed?

Let’s reclock the watch. Let’s start to walk straight again.

What if we could develop a system with no backup plan, no handrails—and still deliver what we truly deserve?

• The freedom to build and design
• The leeway to make errors and repeat without it
• The ability to move, adapt, and grow without being boxed in

Welcome to a space where we don’t create from templates. We create by composing, trialing, validating—and governing.
And we keep moving the ball toward the next target, again and again.

A Living Architecture: 4 Core Components

This new way of architecting solutions came from confronting the problems businesses face today after my humble journey in IT. My experience is grounded in the e-commerce space—B2B, B2C, and the complex solutions we’ve built to extend and evolve existing business processes.

Across this work, I’ve identified four essential components that show up again and again in modern digital systems:

• Frontend systems – where users engage and interact
• Backend systems – where core logic and business rules reside
• API layers – the bridges that allow systems to speak and sync
• External systems – the ecosystem around us: ERPs, CRMs, payment gateways, logistics platforms, and more

Using this structure, I’ve begun a quiet experiment: a series of projects that implement this architecture, and evaluate how well they absorb, adapt, and improve upon the solutions of our past.

Right now, this method is still embryonic. It’s not a proven framework—it’s a living concept. And that’s the point.

Even if it gains traction—even if it earns validation—I don’t want it frozen.
Each of the four components is a piece of something alive. An architecture that moves—not just with its external environment, but with its inner pieces as well.

Not Another Clone

This new concept is a method designed to let each component breathe and make them future proof as a result. To make that happen, we start with clear separations between parts. Not to isolate—but to ensure each one can evolve independently without unintentionally constraining the others.

A hybrid of black box and layered approach, possibly, but more so a deliverable that takes into account that working within our components is what create our limitations. Frameworks are powerful, particularly when we use them for what they are, as one of these components

When we stop forcing everything through one tool, we unlock a more adaptive, more resilient way to build.

Have we made the promise that our frontend can evolve fluidly?

We’ve heard it before, “AI doesn’t need a UI”? Do we need to rebuild our backend, rewrite our APIs, or reintegrate external systems from scratch? Not if we’ve built with separation, intention, and flexibility. Our frontend component can change—and we have no fear of it.

It’s not about locking down what works—it’s about building to leverage what’s there.