Why I Built Quercio

Quercio

I did not set out to build another software tool.

The problem that led to Quercio appeared long before I had a name for it. I kept finding myself at the boundary between customers, operations, product teams, and engineering organizations. The stated challenge was often technical: choose a platform, redesign a workflow, clarify requirements, build an internal tool, or decide what an AI system should do.

But the difficult part was rarely the technology itself.

The difficult part was helping people develop a shared understanding of the business they were trying to build.

Different groups held different pieces of the truth. People close to the work understood the exceptions and workarounds. Leaders carried the strategic intent. Product teams needed to turn competing perspectives into choices. Engineers and analysts needed enough clarity to create systems that behaved consistently. The knowledge was present, but it was not always connected in a form the organization could inspect, challenge, and carry forward.

I watched teams try to solve this problem with documents, meetings, diagrams, prototypes, spreadsheets, and eventually software. Each was useful. None was quite built for the ongoing work of forming and maintaining a shared operating model as the organization changed.

That is why I built Quercio.

The gap between conversation and implementation

There is a familiar gap in the way organizations change systems.

On one side are conversations: interviews, workshops, planning sessions, requirements discussions, strategy memos, and the informal knowledge people carry about how work actually happens.

On the other side are implementations: applications, workflows, databases, automations, reports, integrations, and increasingly AI agents.

The transition between the two is often treated as a handoff. Teams gather enough information, write it down, and ask a technical group to turn it into something real.

But the most important work happens in the middle.

That is where an organization has to make its assumptions visible. It has to decide what concepts exist, which relationships matter, what rules should guide behavior, and where it is still uncertain. It has to compare perspectives, test a model against real examples, and carry the resulting learning into the systems that will act on it.

I could find tools for the conversation. I could find tools for the implementation. I had a much harder time finding tools for this middle layer: the living, shared model that helps an organization move from emerging understanding to intentional action without pretending that discovery is complete.

Why existing tools were not enough

Documentation tools are excellent for recording and communicating ideas. But they do not naturally reveal when two documents use the same term differently, when a policy conflicts with a workflow, or when a definition in a report has drifted from the operating decision it was meant to support.

Project-management tools are excellent for coordinating work. But a task list cannot tell an organization whether the underlying model is coherent.

Data platforms make information available. They do not resolve what the organization means by the concepts in that information.

Prototyping tools make ideas tangible. But a prototype can remain disconnected from the decisions, rules, relationships, and examples it was meant to test.

AI tools make it possible to generate a great deal, very quickly. But without a durable model of the organization’s understanding, they can generate polished local interpretations that do not add up to a coherent whole.

None of these tools are failures. They solve valuable parts of the problem. The gap is that they assume the organization’s operating model either already exists or can remain implicit while the work moves forward.

I wanted to work with that model directly.

A place for understanding to take shape

Quercio is my attempt to create a practical environment for the work between conversation and implementation.

It is a place to make the important parts of an organization’s understanding visible: the concepts it relies on, the relationships between them, the decisions and rules that shape work, the examples and exceptions that complicate those rules, and the questions that have not yet been resolved.

The goal is not to produce a perfect model before anything can be built. The goal is to give an organization a shared object it can use to explore, negotiate, and refine its understanding as it learns.

That model can then inform a prototype, an application, an automation, an agent, or a report. It can give people a way to ask whether a generated output is faithful to the organization’s intent. It can make the effects of a changed definition more visible. It can preserve context so that the next team does not need to rediscover every important decision.

This is why I think of Quercio less as a system for writing requirements and more as a system for carrying understanding forward.

The tool is part of the experiment

Quercio is not the final answer to the problem it is trying to address.

The work of shared understanding is deeply human. It depends on people recognizing the reality of their work, disagreeing productively, and making judgments that no tool can make for them. A tool can make those activities easier, more visible, and more durable. It cannot make the organization’s choices on its behalf.

That is why I have treated Quercio as an ongoing experiment alongside the organizations and problems I work with. Each use is an opportunity to learn what should be represented, what should remain flexible, and how a shared model can become useful in the actual flow of discovery, decision-making, and change.

The ambition is modest but consequential: help organizations own the understanding that increasingly determines how their systems work, decide, and communicate.

If AI is expanding an organization’s ability to shape those systems, Quercio is a practical expression of what I believe the organization needs in order to use that agency well.

The next question is what the experiment has taught me so far.