Principal Advisor
Making hard problems solvable.
Barry Cavinaw — Founder, Clariscale Advisors
Clariscale Advisors exists for one situation: an organization standing in front of a problem it cannot fully see yet: real technology, committed capital, and a path to commercial operation that runs through territory no one on the team has crossed. The practice brings senior operational judgment to that moment, scoped to the problem and structured to step away once the work is sustainable without it.
It is led by Barry Cavinaw, a mechanical engineer by degree and a systems operator by 20+ years of experience across semiconductor manufacturing, chemical recycling, and first-of-kind industrial commercialization. His deepest capability is not a technical specialty; it is the ability to walk into uncertainty, read what is actually happening rather than what the organization believes is happening, and ask the questions that produce real answers rather than comfortable ones.
That capability was formed at Agilyx, an early commercial chemical recycling company advancing pyrolysis of waste plastics at scale. There was no established playbook. No precedent. Every system he operated, every failure he diagnosed, every team he aligned was on terrain nobody had mapped before. Before Agilyx, the foundation was built at Ichor Holdings in semiconductor fluid handling, where cross-functional range, materials fluency, and the habit of going to the shop floor when other engineers did not were established as a default operating mode. Eleven years at Agilyx proved that foundation under conditions where the cost of a wrong assumption was real: operationally, commercially, and for the people running the equipment.
The capability runs deeper than operational time. The documents that govern how a facility functions — process flow diagrams, P&IDs, functional design criteria — were not just read. They were built. Sizing and dosing calculations, instrument selection, system architecture: work done from first principles rather than rule-of-thumb shortcuts. That distinction matters in the field. When an EPC walks into a facility and says "you're doing it wrong, the rule of thumb says X," the response — "that's a shortcut, not the basis" — only holds weight when you know what the actual basis is. The ability to read a process document at the level of the engineering decisions behind it, and to recognize which decisions were rigorous and which were convenient, is not the same as the ability to read it for what it says on the page.
In practice, that has looked like this. Early in his operating career he was sent to a client site on a one-way ticket, no fixed return, to read a first-of-kind system he had not designed and was still building expertise in. Show up, read the environment, earn the operators' trust, solve the problem. That pattern repeated for more than a decade: accountable for the answer on systems nobody had run before.
On another deployment, a failing commercial plant he had been sent to fix without redesigning, he made the case directly, in a room calling for better sensors, that you cannot instrument your way out of a process you do not understand: fix the process first, then measure it. Saying it clearly, while executives called for plant status hourly and the room wanted a different answer, was the job.
The honest boundary — and why it is a feature: he is a mechanical engineer who develops the design basis from first principles — functional design criteria, P&IDs, sizing and dosing, instrument selection — and judges whether an engineering output actually addresses the real problem. What he does not do is stamp it: pressure-vessel code, stamped piping design, and formal certification route to a licensed PE. Knowing exactly when to make that call, what to ask for, and how to read the result is part of the value. The specialist handoff is deliberate: it keeps liability clean and puts the right expert on the right problem. The boundary is not a gap; it is how the work stays honest. Clariscale exists because the most valuable thing he brings is not available on a full-time basis to most of the organizations that need it most. The practice is deliberately structured as advisory — engagements are scoped to a defined problem, run with the depth that problem requires, and close when the work is sustainable without his involvement. The engagement ends. The clarity stays.
How the practice works.
These are not values statements. They are operational principles, the result of doing the work under conditions where the cost of a wrong assumption was real.
Principle 01
Think in systems. Question the question itself.
The presenting problem is rarely the whole problem, and sometimes the real work is figuring out how to define it in the first place. A problem that isn't fully formed yet is not a loose end; it is often where the clarity comes from. The leverage usually sits upstream, in the system generating the symptom, so the first thing examined is whether the problem as stated is the problem that actually exists.
Principle 02
Guard perception. Read what is actually happening.
An outside read carries no loyalty to the decisions that produced the current state and no stake in the existing narrative. That is not a judgment on your team: proximity, pressure, and the weight of building something leave little room to step back. What you get is a read of what is actually happening rather than the organization's story about it. The gap between those two is usually where the problem lives.
Principle 03
What silences questions has already answered them.
The questions nobody is asking and the assumptions nobody is challenging are where the leverage sits, because an organization's silences are rarely empty. The work goes there deliberately, surfacing what is known but unsaid, so the decision in front of you is made with it on the table rather than around it.
Principle 04
Build trust before acting.
Nobody accepts a difficult truth from someone they do not trust yet. So the first phase is observation, not recommendations. You will not get a deck of opinions in week one. The right to challenge is earned by reading the situation accurately first. Presence over performance; consistency over intensity.
Principle 05
Structured over reactive.
Input is rarely clean; the real signal often arrives scattered, out of order, or as noise that has to be sorted. The discipline is not avoiding that; it is metabolizing it: imposing structure on messy input so it yields data you can act on rather than impressions you react to. That standard holds across troubleshooting, strategic planning, and organizational diagnosis alike.
If this describes what you need, reach out.
Clariscale engagements start with a conversation about your situation, not a services menu.
Get in touch