A Year of Building What Actually Holds Up

What did I build?

I didn’t plan to write this, but the past year feels worth capturing.

Most of my time went into building systems that people actually use day to day. That changes how you think. Every decision carries weight once something is live.

A big part of the year went into Fidelect.

It started small. A simple loyalty idea. Points, rewards, a few basic flows. Then it met real businesses.

What they needed was much broader. Customer management, communication, retention, transactions. One piece kept pulling in another. The scope expanded step by step until it became a full system.

Today it sits closer to a business OS built around loyalty. Everything connected in one place.

Getting there took a lot of iteration.

Some weeks moved fast. Others felt stuck on details that refused to cooperate. Data structures changed more than once. Flows were simplified, then rebuilt in a cleaner way. A lot of time went into making things hold together properly.

Alongside that, I worked on several consulting projects.

Each one came with its own constraints. One of the more demanding ones was a scheduling system with layered rules. Availability, roles, compliance, edge cases. The kind of system where small changes ripple through everything.

You adjust one rule and the outcome shifts entirely. You tighten constraints and suddenly nothing fits anymore. It forces a different level of thinking. Less guessing, more precision.

A lot of effort went into making those systems reliable.

On the technical side, the focus naturally moved deeper into backend and system design. More attention on data models, validation, and long term structure. The goal was simple. Systems that keep working under pressure.

I also spent time integrating AI into real workflows. Support, operations, internal tooling. Some parts clicked quickly. Others needed more iteration to become stable enough to trust.

What changed?

There were also many small friction points along the way.

Deployments that fail at the wrong moment. Access issues that slow everything down. Integrations that behave differently than expected. Those situations become part of the routine. You learn to navigate them without losing momentum.

Looking back, the biggest shift is in how I approach building.

More focus on execution. More clarity on what matters. Decisions are made earlier, with more intent.

I also became more selective with projects.

Some ideas stayed behind. Others were reshaped with a clearer direction.

That focus made a real difference.

A year spent building and refining systems until they hold up properly.

Still going.