I'm a mechanical engineer who got caught in the same repeat cycles of doom everyone else does, and got obsessed with making them disappear. Now I build systems that run, so the people don't have to.
The Engineer's Scratchpad
The scratchpad for the moment you need a quick conversion and don't want to alt-tab to get it. Pull dimensions straight from your model, do the math right in the note, and stay connected, when the model changes, SOLVEpad flags it.
A few things I've built to solve real problems, or just to see if I could.
AJ's business was a bunch of boxes, and every corner of every box was a problem waiting to happen. We wired them all together. From Sales. Engineering. Production. Shipped. One input, zero repeat work, no missed deadlines. Complex challenges don't scare us. They're why we exist. This is what complete looks like.
A fully functional Sudoku puzzle generator built entirely in DriveWorks. Most people use the platform to drive their SolidWorks designs. This proves it can do a lot more than that.
DriveWorks is not a game engine. The physics equations didn't care, and neither did we. This project utilizes physics equations to real time solve cannon ball flight and determines if the ball collides with a castle structure. The project also randomizes the gravity constant each time you enter the game!
Right now, it probably isn't. Here's what that looks like in practice, and what changes when you fix it.
Three flavors, all grounded in how manufacturing actually runs, not how the brochure says it does.
CPQ configurators and design automation, first form to live deployment. SolidWorks architecture built to be driven from day one.
The systems you already have, ERP, CAD, quoting, wired together and running without babysitting. New builds, acquisitions, or fixing what's broken.
Configurator that collapses under real orders? I'll dig into the architecture and tell you one of two things: here's how we fix it, or start over. That's not harsh. That's honesty.
No cheap copy-paste configurators here.
Architected from the ground up, stress-tested against how the shop actually runs, and built to last long enough to be handed down to the next engineer.
They'll smell the craft the second they open the files.
I got into this the same way most people do, caught in repeat cycles of doom. Same drawings, same models, same questions, answered over and over. At some point I stopped accepting that as the cost of doing business and started building systems to make it go away.
In the shop, you don't build the same chair twice if you can build a jig. SOLVESHOP is the jig.
When I'm not solving something, I'm tinkering on something else, usually in the shop. I love the smell of sawdust in the morning. It smells like a problem solved by hand. The quest for perfect lawn stripes is ongoing and not to be underestimated.
Tell me what's stuck. I'll tell you straight whether it's worth automating, and roughly what it'd take to do it right.
We'll automate the repeat work. Therapy's on you.