TL;DR: Every refinery, chip fab, pharma plant and power facility starts as thousands of engineering documents that engineers keep in sync by hand. Verno is AI for how the physical world gets built. Today it edits and checks those documents, so one change carries through the whole project and errors get caught on paper instead of in the field.
Here's the actual product, unedited: Verno checking a full set of P&IDs and engineering deliverables for errors across documents.
Hi everyone! We're Oliver and Ujjawal, building Verno.
Why we're building this
At Blue Origin I built ML systems for rocket manufacturing, and watched great engineers spend more time on documents than on engineering. Process EPCs, the firms that design refineries, chemical plants, chip fabs, pharma and food plants, have the same problem at a much bigger scale.
Every plant project runs on thousands of interconnected documents. At the center is the P&ID (piping and instrumentation diagram): the master map of every tank, pump, pipe, valve and sensor in the plant. Engineers call it the bible of a facility, because nearly everything downstream is built from it.
Changing it today is slow. An engineer redlines a PDF, hands it to a drafter, waits, checks the result, and sends it back when something's off. Then every downstream document gets updated by hand. Miss one, and the error shows up in the field. Engineering design is a $130B+ industry in the US alone, and a lot of it goes into this loop.
What Verno does today: engineers make the change directly
We started with the P&ID because it matters most. Most tools for engineering documents read drawings. Verno edits them.
Days of back-and-forth become minutes.
Where we're starting, and where we're going
We're starting with process EPCs in oil and gas, chemicals, semiconductors, pharma, food and beverage, and plastics, where the need is biggest.
We've also shown internally that Verno can generate lists, datasheets and even P&IDs from scratch, and we'll bring that to customers after our current pilot. From there, we're expanding into water and power, and into the rest of the drawings every project depends on: process flow diagrams, utility flow diagrams, single-line diagrams, loop diagrams and beyond.
The goal: become the IDE for engineering documents, the place where every drawing and document a project needs gets created, changed and checked, so engineers spend their time on engineering, not paperwork.
Who we are
We've been friends for years. We've traveled the world together and worked side by side on the same engineering and AI teams.
Our ask