People occasionally ask why we're building an industrial software company in Pittsburgh rather than in San Francisco or New York. The question always feels a little backwards to me. If you're building tools for process plants — the people who run the actual production side of chemical, food, and pharma manufacturing — Pittsburgh is one of the more obvious places to be. Let me explain why.
The Memory in the Ground
Pittsburgh's identity is inseparable from heavy process industry. The Monongahela and Allegheny river valleys were once home to the largest concentration of steel production in the world. The furnaces are largely gone, but the institutional knowledge that grew up around them — the process engineering culture, the understanding that continuous operations require different thinking than discrete manufacturing, the respect for what happens when a process gets away from you — that doesn't disappear when the physical infrastructure changes.
The Pittsburgh region still has significant chemical manufacturing presence — specialty chemicals, industrial gases, coatings and adhesives operations. Glass manufacturing (Pittsburgh was historically where modern flat glass production developed) continues with industrial ceramics and specialty glass operations in the broader region. Pharmaceutical manufacturing has grown in western Pennsylvania and the surrounding states. These aren't legacy industries frozen in time; they're operating facilities running modern DCS systems and historian infrastructure, dealing with the exact operational challenges we built Twynvex to address.
When we need to understand how an operator actually experiences a bad alarm night, or what a plant manager cares about when evaluating new process control software, we can drive 45 minutes and have that conversation with people whose professional context is real and specific. That matters in ways that are hard to quantify but easy to feel when a product design decision comes up.
The Engineering Talent Pool
Carnegie Mellon University's Department of Chemical Engineering has been doing serious process systems engineering work for decades — optimization, process control, dynamic simulation, and more recently, data-driven process modeling. The quality of chemical engineering education in Pittsburgh is a competitive advantage for a company that needs people who can think simultaneously about process physics and software architecture. That's not a common combination, and having a university producing people who are good at it nearby is genuinely valuable.
The University of Pittsburgh's Swanson School of Engineering adds depth in industrial engineering and systems thinking. Carnegie Mellon's computer science and machine learning programs are well-known — the combination of process engineering depth and software engineering depth in the same city is rare. We've benefited from that combination directly in building our team.
More practically: Pittsburgh has a cost structure that lets a small, focused company operate without burning through capital on overhead before the product is ready. We can build a technically serious team here for a budget that would get you a much smaller, less experienced team in coastal tech centers. For a bootstrapped company where every hiring decision has to be right, that matters.
The Process Manufacturing Geography
One useful mental model for industrial software sales: the customers aren't concentrated on the coasts. The process manufacturing facilities we're building for — specialty chemicals, food ingredients, pharmaceutical API production — are distributed throughout the Midwest, Mid-Atlantic, Gulf Coast, and Southeast. Pittsburgh sits at the eastern edge of the industrial heartland. Drive in most directions from Pittsburgh and you're near a significant concentration of process manufacturing within 3–4 hours: the Ohio Valley chemical corridor, western Pennsylvania food processing, the Northeast pharma manufacturing belt.
For a company that needs to do on-site pilots, that geography is directly practical. Getting to a pilot plant facility to work through an OPC-UA connection issue or a model calibration challenge doesn't require a cross-country flight. The ability to be physically present with a plant team during the early phases of a pilot deployment — when trust is being built and operational context is being shared — is something we take seriously. It's not a feature you can describe in a product spec, but it's often the difference between a pilot that turns into an ongoing relationship and one that stays stuck in evaluation.
The Case Against the Obvious Objection
The argument that industrial software companies need to be in San Francisco or New York to be taken seriously is a legacy assumption from an era when the industrial software market was served primarily by large enterprise vendors through enterprise sales processes. That world is changing. Process plants are increasingly making their own software procurement decisions for point solutions — especially for pilot-scale deployments where a plant manager or VP of Operations can authorize a trial without a multi-million-dollar procurement cycle.
In that environment, being close to the customer and deeply embedded in the problem domain matters more than being visible to the venture capital ecosystem on Sand Hill Road. We're not building for the Series A narrative; we're building for the process engineer who needs to trust that the model we've given them for their reactor train actually encodes the right physics. That trust comes from engineering credibility and operational proximity, not from an office address.
Pittsburgh is where the problem lives — in the history, in the talent, in the operating facilities within driving distance. Building Twynvex here wasn't a geographic accident. It was the right decision for a company that wants to understand process manufacturing from the inside.
