JJenso
Jenso navigation
Loading Jenso
Jenso is resolving the requested route and preparing the next view.
Loading the requested view.
Jenso navigation
Jenso is resolving the requested route and preparing the next view.
Services · Jenso LLC
I am Trevor Stark. I run Stark Side Gear, an overlanding gear company, so the first floor I test anything on is my own. Two lines of work here: continuous improvement on the floor, and AI projects that ship.
Jenso is software I am building. The other two are work I do. They are bought separately, and this page exists so nobody has to guess which is which.
The agentic operations manager for the shop floor.
A live 3D twin of your floor. It spots the bottleneck, drafts the fix, shows the numbers behind it, and hands you the call. It is being built now, and Founding Design Partners use it free while that happens.
See JensoContinuous improvement, run on your floor with your people.
Site audits, kaizen events, process improvement. I follow the part, not the org chart. You get a ranked list of where your throughput is going, and the first fix already started.
See the floor workProjects, integrations, workflow automation. Built, not advised.
Command centers, trackers, support agents, Shopify builds, fitment selectors. I build the thing and hand it over. If something off the shelf already does it, I will tell you that instead.
See the build workI follow one part from order to shipped and time the real changeovers, not the standard ones. You end up with a short list of where your throughput is going, in order, and the first one already moving.
I walk the floor with you, follow a part end to end, and count the WIP and the scrap where they actually sit.
You getA written, ranked list of what is costing you throughput, and which one to fix first.
One cell or one changeover, with the operators in the room. We change it on the floor and prove it on real parts before anyone goes home.
You getA rebalanced cell, a written standard the operators helped write, and before-and-after numbers your own team took.
The whole flow, order to ship, including the waiting nobody counts. Layout, changeover, scheduling — whatever the audit says is the actual limit.
You getThe changed process, the standard behind it, and your people able to keep it running without me.
Roto-Fab is a manufacturing client.
I build the thing. No strategy deck, no pilot that dies in a slide. Most of this work is unglamorous: the tracker your team opens instead of rebuilding the spreadsheet, the selector that answers a fitment question before it becomes an email.
I sit with whoever pulls the numbers now, find where they actually live, and build one screen off them.
You getA financial or sales tracker your team opens on Monday instead of rebuilding it.
An assistant that answers from your own support history rather than from the open internet.
You getA support assistant handling the questions that arrive every single day.
Store builds and features, plus selectors that show a customer only what fits their rack or their truck.
You getA selector on your product pages that answers the fit question before it becomes an email.
AI work for Intrepid Camp Gear and Dethloff Manufacturing. The tent fitment selector runs on my own store, which is where I get to break things first.
The problems are the same shape whether you make tents or brackets. These are the two rooms I am usually standing in.
Rooftop tents, racks, bumpers, trailers, campers. Powder coat, weld, CNC. I build in this space myself, so you do not have to explain your product mix or your season to me.
The problems are the same shape whether you make tents or brackets. You do not need a corporate program with a binder. You need someone on the floor who has run one.
Every method I use gets published in full — the whole thing, not a teaser with the real part behind a call. The working files sit behind an email address. Read it, run it yourself if you have the people. If you do not, that is what you are hiring.
Both guides up right now are build work. The floor methods are not written yet — that is the next one.
Fill in the form with the part or the process that is the problem. A paragraph is plenty.
A call to work out whether this is a floor problem, a software problem, or both. If it is neither, I will say so.
Scope, price and dates in writing before any work begins. No retainer to find out what is wrong.
Jenso LLC is mine — Trevor Stark, Buena Vista, Colorado. I run Stark Side Gear, an overlanding gear company, so the floor I test things on first is my own. Roto-Fab is a manufacturing client. Intrepid Camp Gear and Dethloff Manufacturing are AI clients. I am also building Jenso, an operations product for the shop floor, and recruiting Founding Design Partners for it. That is the list. No case-study numbers here, because I am not going to make them up.
Name, company, and a paragraph is enough. It comes straight to me.