OmnentisAbout
Who we are, and why this page exists.
Omnentis is an automation consultancy in San Diego, founded by Noah Fong Neuweg. If you're going to hand someone work your organization depends on, you should be able to judge whether they know what they're doing. That is the whole job of this page.
Why this exists
Months of work a machine should have handled.
We kept watching capable people spend months doing work by hand that could have been done properly once.
Not the work that needs judgment. The other kind. Copying numbers out of a PDF into a spreadsheet. Rebuilding the same report every month because the source moved. Scrubbing back through a recording to find who said the thing about the drainage. Retyping a table that already existed as a table somewhere else. Refreshing a dashboard by hand so the number on it isn't a month old.
That is the tax on the job, and it falls hardest on the people who are best at the part of the job that actually needs a person. Clearing it is the entire reason the company exists. There isn't a bigger story than that, and we'd rather not invent one.
How we work
Small, checkable, and yours.
We start with one task. Something narrow enough that you can tell within a few weeks whether it worked, with a clear before and after. Big rollouts that touch everything at once are how these projects go wrong, and there is almost never a reason to start that way.
Where the work involves reading documents, the accuracy gets measured against a test set built by hand out of your own files before anything goes live. You see the number it scored, whatever it is. Anything the system isn't sure about gets flagged to a person rather than quietly guessed at, and you decide where that line sits.
Everything is containerized, so where it runs is your call. Put it inside your own environment and your files never leave it; or let us host and run it, if you would rather not have another thing to maintain. Either way it is documented, it is handed over, and it does not depend on us continuing to exist — the same container that runs on our infrastructure runs on yours, so changing your mind later is a deployment rather than a rebuild.
We also say when something isn't worth building. If a change to how the work is organised fixes it, that's the answer, and you get it for free.
Case study
The work we can point at.
A workflow built for Scripps Institution of Oceanography that reads very long research cruise reports and indexes them, so people can search them instead of reading them end to end. The write-up covers the problem, what it does, how it gets checked and what it runs on — and it says plainly which figures we haven't published yet.
Who's here
Named where it's a person's record.
The site says "we" because that is accurate. It doesn't give a headcount, an office or a founding date, because those would be decoration rather than information, and this audience checks.
Where a specific person's record is being described, that person is named. The background below is Noah Fong Neuweg's, and it is his rather than the company's.
Background
Noah Fong Neuweg
Studying
Math and applied data science at UC San Diego. The applied half is the part that matters here — measuring whether a model is actually right is a statistics problem before it’s a software problem.
Two years in university IT
Laptop imaging and secure data wiping at the engineering school. Unglamorous work, and the reason this company is built the way it is. When you’ve spent two years wiping drives before machines get reassigned, you stop being casual about where other people’s data ends up.
Built
The document workflow for Scripps Institution of Oceanography described on the case study page — parsing very long research cruise reports and indexing them so they can be searched rather than read.
Want to ask us something directly?
That's the fastest way to work out whether we're any use to you. Twenty minutes, no pitch.