Hard-won experience forged the best practices for developing, integrating, and fielding systems. They hold up well until they encounter a horizon where perception blurs and comprehension resists even the most disciplined effort. Requirements drift. Interfaces never quite close. Decisions escalate without end.
When your system is understood on its own terms, grounded in a law governing every system's existence, clarity emerges. What seems unrelated turns out to be structurally connected, and what needs to change becomes traceable rather than guessable.
We bring that clarity to the problems that matter most to our clients.
First contact is a free, no obligation conversation. We take a small number of engagements at a time.
If you're here, you've likely felt the divergence at the horizon firsthand. You brought the best practices to bear, navigated the maze, and found a solution, but it cost more than it should have, took longer than it needed to, and fell short of what was possible.
The divergence has a consistent, characteristic signature that tends to deepen as the system grows in complexity: unstable requirements, overlapping authority and responsibility, dropped handoffs, cascading compensations, questions that multiply rather than resolve, conflicts that resist reconciliation. No one truly knows where the system ends, let alone begins.
The best practices say one thing. Your experience with the system says another. An echo of dissonance nibbling at the edge of your awareness.
We felt it too. And when we investigated, we stumbled over something we couldn't ignore: a dim light beckoning through the horizon's dense fog. With every application, the radiance strengthens and the bridge extends further toward the increasing clarity we found on the other side. That clarity starts from a set of conditions every system must satisfy to exist at all.
By working together, you gain clarity into your system and we continue building the bridge. And for those who choose to invest fully, you may never see systems the same way again.
The moment you're in shapes what the partnership looks like in practice. You may recognize more than one of these:
Your destination may be unclear and the path to get there absolutely is. Sometimes the territory is uncharted. Sometimes the end is known but no systems-level approach can get you there. Perhaps no one on your team knows how to apply the available best practices.
Every engagement starts by collaborating with your team to clarify what must emerge in the end. Your team brings the context, domain knowledge, and program realities. We derive what must be true to satisfy the need: the solution form and its dependencies, grounded in the constraints you know best. The architectural design and optional roadmap emerge where our results meet your program.
The capability is real. What problem it truly solves, what mission it enables, what need it was built to satisfy — that's less clear. This uncertainty can surface at any stage of the development process: a product ready to market but whose operational context hasn't been derived, or a system in operation that is unanchored to a clearly derived mission need.
Your team brings knowledge of what shaped the capability: the decisions, constraints, and design intent embedded in its implementation. Together we surface the system's latent objective and derive what need in context would necessarily call for exactly that. The result is a findings brief: where the capability fits, where it delivers most, and what must be true about the system around it to succeed.
The analysis has been done. The answers are there. Something about them doesn't sit right — and you can't tell if the problem is in the analysis itself, the assumptions underneath it, or something the framework couldn't reach.
The engagement starts by collaborating with your team to clarify the need. Your team brings knowledge of the original question, the conditions under which the analysis was conducted, and the choices the analyst made in framing it. From there we derive what must be true to satisfy the need, independent of the existing analysis. Mapped against what you've been given, the results confirm what the analysis gets right and surface where it hits its limits.
AI produces outputs. Whether you can trust those outputs depends on the quality of the data, the underlying data handling, and the alignment between what the system was built to do and what it's actually being asked to answer. When the existing analysis was done by AI, the same engagement applies: derive what must be true to satisfy the need, independent of the output, and map against what you've been given.
You've encountered resistance that won't yield, a roadblock standing between you and success: invisible, persistent, and immune to everything you've thrown at it. Sometimes it's a decision or architectural change that triggers rework, instability, and cascading compensations. Sometimes the system simply can't cohere in its current form. Workarounds multiply and decisions spiral out.
Whatever form the resistance has taken, the starting point is the same: working with your team to clarify the need. Your team brings knowledge of how the current configuration came to be, the decisions that preceded experiencing the resistance, and what's been tried to remedy it. We derive what must be true to satisfy the need and map your existing solution against that derivation, revealing what the wall is, where it comes from, and what must change to dissolve it.
You deployed AI and your operations didn't improve. Maybe they became even more intractable. The capability worked as advertised, but something about the system it landed in didn't. The same engagement applies to identify and rectify the source of the resistance.
Something new is on the table. A technology, a capability, a process change — something that promises to help. Whether it actually fits your system, what it demands from the surrounding structure, and what must be true for it to cohere are questions that deserve a rigorous answer before it's wired in.
Whatever is on the table, the engagement begins the same way: with your team, clarifying the need and deriving what must be true to satisfy it. Your team brings knowledge of the system as it stands and the element you're introducing or replacing. Together we assess which existing gaps it closes and whether it opens new ones, what the surrounding structure must look like to receive it coherently, and what must change to wire it in cleanly. The result is a findings brief: where the element fits, what it requires, and what refactoring is needed — if any.
AI is the new element most organizations are grappling with right now, generating uncertainty about whether to introduce it and how to integrate it well. The same analytical basis applies: derive what the system needs, assess whether AI closes existing gaps or opens new ones, and determine what the surrounding structure must look like for it to cohere.
A focused engagement with defined scope and endpoint, delivered as an actionable findings brief tailored to your situation. The analysis surfaces the concise need statement from the noise, derives what must be true to satisfy it, and assesses current state, existing analysis, or both against it. The findings identify what coheres well and what doesn't, with recommendations for reframing or refactoring as needed.
Think of it as an MRI of your system. A precise, complete picture of what's actually there: what the system requires, where it stands, and what must be true to close any gaps.
Most relevant to Moment 3 ("I'm not confident in the answers I've been given"), Moment 4 ("I've hit a wall"), and Moment 5 ("I'm introducing something new into the system").
A collaborative engagement with defined scope and endpoint for situations where one end of the analysis chain must be constructed or recovered. Sometimes the mission need exists but the system to satisfy it doesn't; we derive forward to define an architectural design, with an optional roadmap. Sometimes the system exists but was built around capability optimization rather than a pre-defined mission need; we surface the system's latent objective and work backward to recover the mission need it uniquely satisfies. Delivered as an actionable findings brief: an architectural design with optional roadmap, or a capability fit assessment.
Most relevant to Moment 1 ("I don't know where to start") and Moment 2 ("I know what it does. I'm not sure what it's for").
For clients who want to see the findings through. A sustained partnership geared toward maintaining alignment of the implementation to the derivation as the program encounters reality: guiding implementation to conform to the success criteria, running additional diagnostics and studies as new situations arise, adjusting roadmaps and architecture as needed, and developing the team's analytical lens so that decisions made independently reinforce rather than undermine.
Relevant to any moment.
We're an early-stage firm and our pricing reflects that. Final rates are shaped by the level of effort and risk of the engagement, with a heart toward mutual benefit.
Clients without deep pockets are welcome here. The analytical work you need is often the same work that helps us extend the bridge beyond the horizon — and where it does, it's worth a conversation.
Don't see your situation here? Reach out. If there's a fit, we'll find it.
Schedule a consultationFirst contact is a free, no obligation conversation. We work with a small number of clients at a time — this kind of work requires genuine commitment from both sides.
Our experiences working with systems whispered...an echo of dissonance nibbling at the edge of our awareness. When we investigated, we stumbled over something we couldn't ignore: a dim light scarcely piercing the fog shrouding the edge of what best practices can see.
Following the light, we discovered the fog had not just concealed uncertainty at the horizon but a chasm between paradigms. Finding ourselves on the other side before fully grasping what we'd crossed, we set out to build a bridge so that others could follow.
The Skeptical Systemist describes this bridge, starting from where the field currently stands and striving toward the clarity beckoning from the other side. It shares how we've reasoned through the nature of systems and offers a lens we've found useful across an unusually wide range of problems. We offer it in that spirit: not as arrived answers, but as an open invitation to explore and build upon.
Our foundation is the Second Law of Thermodynamics: a law with no known exceptions. Energy disperses. The universe tends toward disorder. Which raises an immediate and fundamental question: how can any system cohere at all?
Unifying Systems Theory (UST) is how we've reasoned through that question. Our mission is to develop it into a candidate early systems science through application to problems that matter.
The theoretical roots trace to doctoral work at MIT where the application of entropy-based principles generated insight into how to strategically evolve complex systems under legacy constraints. Years of technical work across many programs and domains followed. Patterns kept appearing: something fundamental hidden beneath the surface behavior of systems, consistent across contexts with nothing obvious in common. Hypotheses formed, and emerging patterns and approaches grew sharper and more refined with each application.
The effort since has been to systematically derive from empirical law and first principles what intuition first revealed. Like the law it follows from, UST is discovered, not invented, belonging to no one and to everyone.
A doctoral thesis, a peer-reviewed publication in Springer Nature, and a granted patent mark the points where the thinking became visible enough to present publicly. The evidentiary record documents this intellectual lineage as well as the confirming and challenging evidence accumulating from applications cleared for public release.
The Skeptical Systemist whitepaper series shares how we've reasoned through the nature of systems and offers a lens for exploring what follows, starting from where the field currently stands and striving toward the clarity on the other side.
For those interested in a formal assessment of UST against established criteria for a candidate science, the science subpage lays that out plainly.
Client engagements advance the science through application. The R&D program advances it through structured research: developing and refining the science, exploring its implications and predictions across domains, testing those predictions, and where validated, advancing implementations for societal benefit.
The model: systematic and domain-specific; turning theory into tested implementations with the independence to follow the work wherever it leads.
Domain programs are in development. We will say more when there is more to say.
If you are a scientist, researcher, engineer, or domain expert who wants to engage with the science directly: to explore its implications and predictions in your own domain, or to be part of building what comes next — we want to hear from you.
If you represent an academic institution or R&D organization interested in partnership as the program develops, we'd like to hear from you as well.
Get in touch →A world where systems are understood, designed, and adapted on the basis of a science derived from empirical law and first principles — examinable, transferable across domains, and strengthened by every application.
To develop UST into a candidate early systems science through application to problems that matter.
Von Bertalanffy called for universal principles applying to systems in general, principles that would hold across domains without having to be rediscovered in each one.¹ INCOSE has pursued a theoretical foundation for systems engineering for decades.² Hazelrigg and Saari note that this pursuit has been ongoing for over fifty years, and that attempts at theories have so far failed to accommodate even a sizable fraction of the systems engineering community.³
We believe starting from an empirical law governing the existence of every system holds promise for the theoretical foundation the field has long sought. Exunum Strategic Solutions exists to explore that possibility.
¹ Von Bertalanffy, L. (1968). General System Theory: Foundations, Development, Applications. George Braziller, New York.
² INCOSE Fellows (2019). A World in Motion: Systems Engineering Vision 2025. INCOSE. See also INCOSE (2023). Systems Engineering Vision 2035.
³ Hazelrigg, G.A. and Saari, D.G. (2022). "Toward a Theory of Systems Engineering." Journal of Mechanical Design, 144(1). DOI: 10.1115/1.4051873.
Exunum: A contraction of the Latin ex uno ad unum — from one, always back to one. Starting from the whole, differentiating around what must necessarily be true to always cohere back toward the one.
Strategic Solutions: Where the science meets the work. Aligning people, processes, and capabilities toward the system's core structure, in service of decisions and outcomes that matter.
Have questions about the approach, the science, or why we're structured the way we are? So did we.