The Hard Season

The squeeze

In regulated financial institutions, adoption is not a simple act of agreement. Even when a customer believes in the problem, many other systems must align before a product can become operational reality: the risk team may understand the pain, the innovation team may see the promise, the technology team may need to validate the architecture, compliance may need explainability, model risk may need governance, security may need review, procurement may need process, finance may need budget clarity, and executives may need internal consensus.

Each layer exists for a reason. A bank cannot casually adopt systems that affect AML/KYC, fraud, compliance, or financial crime workflows. It must ask difficult questions: whether the system can explain itself, whether it can be governed, whether it can integrate with current workflow, whether investigators can use it without confusion, whether auditors can understand what happened, whether the model can be validated, and whether the institution can defend the decision process if challenged.

These are serious questions, and I respected them. Respect did not make the sales cycle shorter.

A founder lives in the tension between customer seriousness and company urgency. Regulated institutions were right to be careful, and Quantiply was also living inside a venture rhythm that required proof, adoption, growth, and financing progress within a different clock. Those clocks did not move together. Venture capital has its own cadence: it wants evidence of momentum, and it rewards speed, growth, repeatability, and expanding conviction. That rhythm can be healthy when the market is ready and the wedge is clean, and it can create extraordinary pressure when the market needs more time to trust what the company is building.

We were asking institutions to adopt a new kind of decisioning system in high-consequence environments. The market was asking us to prove that adoption faster than trust could mature. That was the squeeze.

The private arithmetic of time

I had lived versions of being early before. Optena taught me that a future can be true before the market has language for it. Quantiply was different, because the stakes were more personal. I was no longer only learning from an early infrastructure thesis. I was carrying a company, a team, investors, customers, partners, and a product that represented years of accumulated belief.

The founder’s burden is not only intellectual. It is human. People joined because they believed, investors committed capital because they saw possibility, customers spent time because the pain was real, partners opened doors, and the team worked across geographies, time zones, and uncertainty. Each person carried a piece of the company’s hope, and as founder, you carry the connections among all of them.

You carry the thesis, the financing plan, the product roadmap, the customer pipeline, and the team’s morale. You carry what is said in board meetings and what is not said in all-hands meetings, and you carry the private arithmetic of time.

That arithmetic can become heavy: how much runway remains, which deals can close, which customer can convert, which investor will lean in, which product capability must be finished, which partner path is real, which delay is temporary, and which signal is telling us something deeper. These questions do not stay at the office. They come home with you, they wake you up early, they sit with you in quiet moments, and they change the way you experience time.

Then COVID arrived. It is difficult to describe the impact of that period without making it sound like an excuse, and it was a condition rather than an excuse, and conditions matter. The pandemic changed the operating environment for almost every company, and for a startup selling into regulated enterprises, it added friction to an already difficult adoption path. Institutions became more cautious, internal priorities shifted, budgets were reviewed differently, decision cycles slowed, people were distracted by legitimate human and operational concerns, travel stopped, and relationships moved fully into screens. The informal trust-building that often happens around enterprise adoption became harder.

COVID did not create every difficulty. But it added pressure at the wrong time. That is often how hard seasons work: they are rarely caused by one thing, arriving instead from the convergence of many conditions, timing, capital rhythm, adoption complexity, market language, customer trust, internal execution, external shock, and founder limits.

A system under pressure reveals where it has margin and where it does not. Quantiply had strength. We had a serious thesis, real technology, credible partnerships, a focused wedge, customer interest, and a team that cared. But strength does not remove constraint.

The capital situation became difficult. GPV had been part of the financing context, and as the market changed and pressure increased, the path forward became more constrained. I do not want to turn that into blame. Capital has its own responsibilities and limits, and investors also operate within systems, making decisions under uncertainty with their own constraints, portfolio pressures, and risk judgments. Still, for the founder inside the company, the experience was hard. When capital rhythm, customer adoption rhythm, and market readiness rhythm fall out of alignment, the company feels it everywhere.

Every decision becomes sharper: whether to keep pushing independently, narrow further, cut, raise under worse conditions, seek a strategic path, or preserve the work in another form. These are not abstract strategy questions when people’s lives and work are involved. They are stewardship questions.

What must be preserved?

That word, stewardship, became important to me during the hard season. At the beginning of a company, the founder often thinks in the language of building: the product, the team, the market, the category, the company. In a hard season, another question arrives.

What must be preserved?

Preserving is different from winning in the way founders imagine winning at the beginning. It does not always feel heroic. It may involve grief, it may require accepting an ending you did not choose, and it may ask you to protect the work, the team, the customers, and the thesis even when the original form can no longer carry the full weight of the vision.

That was the frame through which I came to see the decision to sell Quantiply to Eventus. It was not the ending I had imagined when we began. Founders rarely imagine the responsible ending. We imagine the expansive one, the company growing into the full horizon of the thesis, the market catching up at the right moment, the team continuing to build with increasing strength, the architecture becoming category. Reality often has a different curriculum.

Selling the company was neither a simple failure nor a simple victory. It was an act of stewardship.

Eventus gave the work a path to continue, preserving important elements of what we had built and placing them inside a company with a stronger market position, operational base, and customer context in related risk and compliance domains. That mattered. The thesis did not disappear, the product did not vanish into nothing, and the work found another form.

But I will not pretend there was no grief. There was. A founder grieves more than ownership: the version of the future he had been carrying, the team’s original path, the company that might have become something different under different timing, and the private sacrifices that may not be visible from outside. That grief can coexist with gratitude, with responsibility, and with the knowledge that the decision was right. Human beings are capable of holding more than one truth at once. Founders have to be.

Right and wrong at the same time

Quantiply was early in several ways. The technology direction was right, the market pain was real, and the need for explainable AI, graph reasoning, human-in-the-loop learning, workflow integration, and governance in risk decisioning has only become more obvious with time. Enterprises still need systems that can connect signals into trusted action.

Being early can feel like being right and wrong at the same time, though: right about the direction and wrong about how quickly the surrounding system could move, right about the architecture and wrong about the adoption path, right about the pain and wrong about the timing of budget, trust, validation, and market readiness.

That tension is painful because it resists simple interpretation. It does not let you comfort yourself with either triumph or failure. It asks for a more mature reading, and I had to learn that.

For many years, I had believed deeply in systems. I had learned from soil, circuits, factories, cities, telecom networks, databases, cloud platforms, SaaS applications, big data environments, and AI systems, and I had seen again and again that visible outcomes depend on invisible conditions. The hard season taught me that companies are no different. A company’s outcome depends on conditions that extend beyond the product: market timing, category maturity, customer trust, internal alignment, capital rhythm, external shocks, leadership capacity, and luck. The founder can influence many of these. He cannot fully control them.

This is a humbling realization, and it can also be freeing, but only after it first hurts. Founders are often told to take full responsibility, and I believe in responsibility. I believe deeply in ownership. Responsibility is not the same as believing you control every variable, though. Mature responsibility means seeing the system clearly enough to know what you can change, what you must accept, and what you must preserve.

In the hard season, responsibility meant making decisions I did not want to make. It meant staying honest with myself, protecting the team as much as possible, honoring investors without pretending the path was easier than it was, preserving customer trust, finding a home where the work could continue, and letting one form of the dream end so that something of its substance could survive.

That was not easy. There were moments when I replayed decisions, and every founder does this: whether we could have narrowed sooner, found a sharper wedge earlier, raised differently, paced the company another way, or read the market signals with more discipline. Some of those questions are useful. Some can become punishment. The hard work is to learn without turning reflection into self-accusation.

A more mature reading

Looking back, I can see both the strength and the strain. We built something real, saw a problem before it became widely obvious, brought together graph reasoning, machine learning, workflow, explainability, and human judgment around high-consequence risk decisions, worked with serious partners and serious customers, and carried a thesis that still matters. We also faced a market that was slower, more regulated, more cautious, and more complex than the company’s financing rhythm could comfortably support, especially under the pressure of COVID.

Both are true. That is why I resist clean founder stories. They do not tell the truth. The truth is usually mixed: a company can be early and valuable, a thesis can be right and mistimed, a sale can be painful and responsible, a founder can feel grief and relief in the same week, a team can have built something meaningful even if the company’s path changed, and a hard season can become a source of future wisdom without needing to be romanticized.

Quantiply changed me, not only by what we built but by what the hard season required. It stripped away some of the simpler founder narratives I had absorbed. It taught me that conviction must mature into stewardship, that the market is not an enemy when it moves slowly; it is a system revealing its readiness, that capital has a rhythm which must be respected and also understood as only one rhythm among many, and that trust, especially in regulated environments, cannot be rushed by ambition.

Most of all, it taught me that the founder’s responsibility is not only to begin. It is also to carry the work through forms he did not imagine.

Eventus became the next classroom. After the sale, the question was no longer only how to build decision infrastructure as a standalone company. The question became how trust is integrated, operated, explained, monitored, and earned repeatedly inside an operating company serving real market needs.

Before moving there, I want to honor the hard season for what it was.

Not a neat ending. Not a motivational parable. Not a failure to hide. Not a success to polish. A hard season.

A season of pressure, uncertainty, responsibility, grief, humility, and preservation. It did not destroy the work. It changed the form in which the work could continue, and it changed the person who had to carry it.